On Thursday 16 December 2004 23:27, jdow wrote: > Humble (moi! humble?) request, please be careful with terminology, even > if AOL and Microsoft are sloppy as hell. Bounce sends a message back to > the purported sender, [EMAIL PROTECTED] Rejects simply reject it from the > server forwarding the email to your mailbox. The purported sender is not > involved and never sees the failure unless something ELSE, like the sending > server, informs him of the error.
Well, I was being a little loose with the term, referring to the fact that a REJECT code will often generate a bounce message from the MTA whose connection has been rejected. However, that does NOT mean that the spoofed address gets the bounce message unless their address just happens to be on the same MTA as the domain of the spoof. Thus, if you REJECT a message from hotmail.com MTA and the spoofed from just happens to be from hotmail.com, that address will likely get a bounce message. With SPF coming into play and more and more exploited machines, this is very likely to start to happen more often. Hopefully, it will provide some incentive for administrators to monitor their systems and make sure that they don't have tons of zombie machines on them. > 100% correct. If you use fetchmail you're stuck. Filtering is all you > can do. I reiterate SARE is WONDERFUL. Not totally, of course. You can use fetchmail and then generate a reject code back to the server based on criteria. When doing this, the message gets rejected by your system but, in most cases, will NOT result in a bounce being sent as the MTA will most likely just dump the message unless it just happens to be from a local user on that MTA. -- Bryan Phinney
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
