Difference: Mail-relatedFiles (16 vs. 17)

Revision 172019-09-12 - WilliamSeligman

Line: 1 to 1

META TOPICPARENT	name="Mail"

Files that affect your mail

Line: 54 to 54

`~/.spamassassin/user_prefs`

Changed:

<
< For the most part, you can ignore the contents of your ~/.spamassassin/ directory, which is automatically created for you the first time you receive mail at Nevis. The one file that you might want to look at is ~/.spamassassin/user_prefs, which allows you to control the functionality of SpamAssassin.

>
> For the most part, you can ignore the contents of your ~/.spamassassin/ directory, which is automatically created for you the first time you receive mail at Nevis. The one file that you might want to look at is ~/.spamassassin/user_prefs, which allows you to control the functionality of SpamAssassin.

Deleted:

<
<

Your mail reader may also offer spam-filtering options. The advantages of SpamAssassin

are similar to those of using procmail:

SpamAssassin offers more flexibility than most mail readers. For example, you can control the exact weighting assigned to each one of the tests that SpamAssassin performs.

SpamAssassin runs on the mail server, which means it operates on your e-mail as it receives it. A mail reader can only process your messages as it reads them off the server. In particular, if you blacklist an address in ~/.spamassassin/user_prefs, it will be bounced by the mail server and never get into your INBOX.

If you're interested in configuring SpamAssassin, I recommend the following resources:

The SpamAssassin web page.
The SpamAssassin Wiki.
The spamassassin man page.
WilliamSeligman's SpamAssassin preferences file at ~seligman/.spamassassin/user_prefs.

\ No newline at end of file

Added:

>
> Your mail reader may also offer spam-filtering options. See this page on configuring SpamAssassin for why this is not the best option.

\ No newline at end of file

View topic | History: r18 < r17 < r16 < r15 | More topic actions...