-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
BTW, the issue is with the ASF's mail servers -- sadly they're inundated with spam, and without using dynamic-IP blocking, they cannot keep up with the spam volume with the hardware they have. (apache.org addresses are on a *lot* of spam lists.) Aecio, is there any reason you do not use your ISP's smarthost relay for outbound SMTP? That's general best practice nowadays, and avoids this problem. - --j. Matt Kettler writes: > jdow wrote: > > > Note that received from at Apache shows it came from 192.168.0.252. > > That is NEVER going to get through any properly configured mail setup. > > It looks like a forgery attempt to make mail look like it came from an > > internal address even when received from outside. That won't fly, in > > general. > > Erm, J.. drink some coffee... > > > Received: from unknown (HELO www.harvest.com.br) (192.168.0.252) > > by localhost with SMTP; 14 Jul 2005 13:52:34 -0000 > > That Received: wasn't generated by apache, it's on the local side. Apache > never > accepted the mail, so apache never generated a Received: at all. > > Besides it would be IMPOSSIBLE for it to show up at Apache from 192.168.0.252. > You'd never establish a TCP connection because the IP is unroutable. > > Sure apache.org could possibly receive the TCP syn packet with such a source > address, if it wasn't firewalled out, but the syn-ack generated by the apache > server would go nowhere due to lack of route. Apache's MTA would never even > know > an attempt was made to connect, as all of this happens within the OS's tcp > stack. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFC1p9jMJF5cimLx9ARAlOsAJ48uryKiF++IjoM7EeQC0Dcd9L5rACgvfbF WsHSSw820oaQmHB1a7dRlLU= =W+Lu -----END PGP SIGNATURE-----
