Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by LorenWilton:
http://wiki.apache.org/spamassassin/BetterDocumentation/UsageTxt
------------------------------------------------------------------------------
Important Note For Users Upgrading From Earlier Versions
--------------------------------------------------------
+ SpamAssassin no longer includes code to handle local mail delivery, as it was not reliable enough compared to procmail. If you previously relied on spamassassin to write the mail into your mail folder, you'll have to change your setup to use procmail as detailed below.
- SpamAssassin no longer includes code to handle local mail delivery, as it
- was not reliable enough, compared to procmail. So now, if you relied on
- spamassassin to write the mail into your mail folder, you'll have to
- change your setup to use procmail as detailed below.
If you used spamassassin to filter your mail and then something else wrote
it into a folder for you, then you should be fine.
@@ -165, +162 @@
- If you have an unusual network configuration, you should probably
set 'trusted_networks'. This allows SpamAssassin to determine where
your internal network ends and the internet begins, and allows DNS
- checks to be more accurate.
+ checks to be more accurate. If your mail host is NATed you almost
+ certainly will have to set trusted_networks to get correct filtering
+ results.
- A very handy new feature is SPF support, which allows you to check
@@ -187, +186 @@
- The distribution includes 'spamd', a daemonized version of the
- perl script, and 'spamc', a low-overhead C client for this,
+ SpamAssassin perl script, and 'spamc', a low-overhead C client for this;
contributed by Craig R. Hughes. This greatly reduces the overhead of
checking large volumes of mail with SpamAssassin. Take a look in the
'spamd' directory for more details.
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by LorenWilton:
http://wiki.apache.org/spamassassin/BetterDocumentation/UsageTxt
------------------------------------------------------------------------------
Important Note For Users Upgrading From Earlier Versions
--------------------------------------------------------
+ SpamAssassin no longer includes code to handle local mail delivery, as it was not reliable enough compared to procmail. If you previously relied on spamassassin to write the mail into your mail folder, you'll have to change your setup to use procmail as detailed below.
- SpamAssassin no longer includes code to handle local mail delivery, as it
- was not reliable enough, compared to procmail. So now, if you relied on
- spamassassin to write the mail into your mail folder, you'll have to
- change your setup to use procmail as detailed below.
If you used spamassassin to filter your mail and then something else wrote
it into a folder for you, then you should be fine.
@@ -165, +162 @@
- If you have an unusual network configuration, you should probably
set 'trusted_networks'. This allows SpamAssassin to determine where
your internal network ends and the internet begins, and allows DNS
- checks to be more accurate.
+ checks to be more accurate. If your mail host is NATed you almost
+ certainly will have to set trusted_networks to get correct filtering
+ results.
- A very handy new feature is SPF support, which allows you to check
@@ -187, +186 @@
- The distribution includes 'spamd', a daemonized version of the
- perl script, and 'spamc', a low-overhead C client for this,
+ SpamAssassin perl script, and 'spamc', a low-overhead C client for this;
contributed by Craig R. Hughes. This greatly reduces the overhead of
checking large volumes of mail with SpamAssassin. Take a look in the
'spamd' directory for more details.