Arne Fischer wrote: > "Our spam filter rejected this transaction." is generated by a program on MY > side. I get a message, that this eMail couldn't be delivered.
Which was delivered to you because the bounce (being sent to [EMAIL PROTECTED]) was undeliverable, and the 'bounce of a bounce' ended up going to you. This is why bouncing spam generally doesn't work, unless it can be done during the SMTP conversation; because 99% of spams have a false return addresses. Either some poor valid non-spam sending user gets hit (because the spammer has set this poor victim as the return address) or the return address doesn't exist at all (which is what I assume is the case in this example). There is now the ability to use spamassassin at SMTP conversation time, which still has the same functionality, but gets around having to accept the spam to check it's not spam. Check out: http://marc.merlins.org/linux/exim/sa.html Regards, Drav. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
