>
> http://www.freesoftwaremagazine.com/articles/focus_spam_postfix/
>
That's a great article. Where do you implement the changes he
suggests on the first page? I searched /etc/postfix/main.cf for the
configuration options but they aren't there.
- Grant
-
Just add them to main.cf and do a /etc/init.d/postfix reload (make sure not to include the line numbers in his examples)
For the lines that reference external files, you will have to create the files and the content and the issue the command:
postmap <filename>
The guide puts all of the files in /usr/local/etc/postifx, but I just put the files in /etc/postfix (If you put the files in /etc/postfix instead of /usr/local/etc/postfix, make sure to change the path main.cf). I left off the spf filter since it seems that many people still have not adopted spf. Postgrey is great and I use it on my person email server, but I left that off of the business system I manage. I work for a real estate company and postgrey can delay email by 4 hours or more depending on the sending server configuration. Although no one should depend on email for speedy delivery, it is my experience that most users expect it. All of the other options have really helped a lot and cut down on spam.
A couple of things to remember, each time you change main.cf or any other postfix configuration file, you need to issue the command:
/etc/init.d/postfix reload
to get postfix to take the new configuration changes.
Also, if you change any of the external files that main.cf refrences, you need to do a :
postmap <filename>
and then
/etc/init.d/postfix reload
It is probably a good idea to tail your mail logs for a while after you make the changes just to make sure you are not blocking anything you didn't intend
to.
tail -f /var/log/mail/current
or
tail -f /var/log/mail.info
depending on your logger.
Also, I would recommend sending email to an account on your new system from any and all external email accounts you may have such as yahoo or gmail just for extra testing.
Good Luck,
Preston
