Difference between revisions of "SpamAssassin"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search| Line 1: | Line 1: | ||
We're using the default spamassassin setup. No fancy custom filters, no frontends, just a reference in /etc/postfix/master.cf and that's it. If spam becomes an issue, we can have users give us some spam messages to train with, which is just a command or two away, found in the spamassassin documentation. <br> | We're using the default spamassassin setup. No fancy custom filters, no frontends, just a reference in /etc/postfix/master.cf and that's it. If spam becomes an issue, we can have users give us some spam messages to train with, which is just a command or two away, found in the spamassassin documentation. <br> | ||
Spamassassin is currently quietly discarding messages marked as SPAM. We shouldn't have any issues with this, because our filters are set somewhat conservatively. | Spamassassin is currently quietly discarding messages marked as SPAM. We shouldn't have any issues with this, because our filters are set somewhat conservatively. | ||
| + | <br>'''Important Note'''<br> | ||
| + | SpamAssassin needs to have a user account named spamd, and this has to be a local account as well as being in the LDAP database. | ||
Revision as of 15:13, 18 January 2010
We're using the default spamassassin setup. No fancy custom filters, no frontends, just a reference in /etc/postfix/master.cf and that's it. If spam becomes an issue, we can have users give us some spam messages to train with, which is just a command or two away, found in the spamassassin documentation.
Spamassassin is currently quietly discarding messages marked as SPAM. We shouldn't have any issues with this, because our filters are set somewhat conservatively.
Important Note
SpamAssassin needs to have a user account named spamd, and this has to be a local account as well as being in the LDAP database.
