On 20/10/11 13:07, Dennis Guhl wrote: > On Thu, Oct 20, 2011 at 12:27:27PM +0200, Daniele Nicolodi wrote: >> Hello Dennis, thank for your comments, they are much appreciated. >> I hope I understand enough to formulate a valid reply. > > It looks quite good (at least to me as a native german).
I was intending my understanding at the technical level, not at the language one, my understanding of the matter is not limited by my English :-) >> My point is that no backscatter is generated from the use of >> spamassassin as content filter. The back scatter is generated from the > > Indirect yes. > >> rejection of an email in the content filter. If I explicitly instruct >> spamc to tell postfix to reject the email based on the spamassassin > > In most cases this is the configured and intended behaviour. But this > is not the only option you have to treat a spammy email. > >> rules, then, I would have backscatter. My English is maybe not very >> good, but I find the above statement confusing, because at a first read >> it may look like that the filtering itself may cause backscatter. > > Indeed this might be a language barrier. > > [after queue rejection == backscatter] I think I have been misunderstood. I think the statement: This configuration does not allow rejecting messages within the SMTP transaction, so it unfortunately contributes to backscatter email. in http://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix is missleading. It is the action of rejecting an email in after queue processing that generates backscatter, not the use of an after queue filter. But I consider this question solved. >> That's exactly the point. My spamassassin does not tell postfix to >> reject the email, I simply discard it, without notice to the sender, as > > This is a way to handle spam. But I see two problems: first and > foremost, you will have false positives (ham detected as spam), and > nobody will know about this as the sender only see that your MX > accepted his email and the recipient never knows about the email. The > second issue may regard the law. At least here in Germany we are not > allowed to discard an email we acceptet beforehand. I don't know > italic laws or if european laws say something about suppression of > (e)mails. Agreed. But others in the thread suggested to use spamassasin with procmail at local delivery time, and that would have the same problem, so it is not a valid solution either. >> What is the recommended way to use spamassassin to reject emails at the > > The (TM) recommended way does not exist ;) > >> SMTP level? A few have been suggested in this thread, but honestly I do >> not have time to try them all. Simplicity, assuming a low volume smtp >> server, is highly appreciated. > > In this case I would recommend spamass-milter > (http://savannah.nongnu.org/projects/spamass-milt/) I'll have a look at it. Thank you. Cheers, -- Daniele
