Amedee Van Gasse wrote:
On Tue, December 2, 2008 13:10, Sandy Drobic wrote:
There are several caveats to your approach:
- if you reject mails at the smtp level you should have your own mailserver that is the responsible mx for your domain, otherwise you will become a source of backscatter
I know. Just check it yourself:
$ dig amedee.be +short $ dig amedee.be mx +short $ dig intrepid.warp.be +short
My list was more for the benefit of those that stumble on that thread later and wish to implement something similar. Hopefully they will also find my comments and reconsider if they don't meet the requirements. (^-^)
It is my opinion that even if SpamAssassin is better in theory, it is a bulky behemoth compared to my simple header_checks. I'm afraid that my server will run out of memory or cpu when I use SA. Since it's a virtual xen server shared with a couple of people, I'm trying to be polite to the others. I once had a trashing error because of Amavis (yet another memory monster), and I won't let that happen again.
I heartily approve of such a considerate approach. Amavisd-new is indeed quite a resource hog, even more, if it is running as a proxy filter. My solution against pesky mails is to use dedicated mailaddresses for mailinglists and a restriction class in Postfix to reject all mails to these addresses when the submitting client is not the listserver. It is also the reason for my footer and my nonexistant spam problem. (^-^) -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org