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/ReadmeTxt
------------------------------------------------------------------------------
Welcome to SpamAssassin!
------------------------
+ What SpamAssassin Is
+ --------------------
+
SpamAssassin is a mail filter which attempts to identify spam using
a variety of mechanisms including text analysis, Bayesian filtering,
DNS blocklists, and collaborative filtering databases.
- Using its rule base, it uses a wide range of heuristic tests on mail
- headers and body text to identify "spam", also known as unsolicited
- commercial email.
+ What SpamAssassin Is Not
+ ------------------------
+
+ SpamAssassin is not a program to delete spam, route spam and ham to separate mailboxes or folders, or send bounces when you receive spam. Those are mail routing functions, and SpamAssassin is not a mail router. SpamAssassin is a mail filter or classifier. It will examine each message presented to it, and assign a score indicating the liklyhood that the mail is spam. An external program must then examine this score and do any routing the user wants done. There are many programs that will easily perform these functions after examining the score assigned by SpamAssassin.
+
+ How SpamAssassin Works
+ ----------------------
+
+ Using its rule base, SpamAssassin uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for
later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and
non-spam in between 95% and 100% of cases, depending on what kind of
+ mail you get and your training of its Bayesian filter. Specifically, SpamAssassin has been shown to produce around 0.9% false negatives (spam that was missed) and around 0.1% false positives (ham incorrectly marked as spam). See the rules/STATISTICS*.txt files for more information.
- mail you get and your training of its Bayesian filter. Specifically,
- SpamAssassin has been shown to produce around 0.9% false negatives (spam
- that was missed) and around 0.1% false positives (ham incorrectly marked
- as spam). See the rules/STATISTICS*.txt files for more information.
+ SpamAssassin also includes plugins to support reporting spam messages automatically or manually to collaborative filtering databases such as Pyzor, DCC, and Vipul's Razor.
- SpamAssassin also includes plugins to support reporting spam messages
- automatically or manually to collaborative filtering databases such as
- Pyzor, DCC, and Vipul's Razor.
The distribution provides "spamassassin", a command line tool to
perform filtering, along with the "Mail::SpamAssassin" module set
+ which allows SpamAssassin to be used in spam-protection proxy SMTP or POP/IMAP server, or a variety of different spam-blocking scenarios.
- which allows SpamAssassin to be used in spam-protection proxy SMTP or
- POP/IMAP server, or a variety of different spam-blocking scenarios.
+ The distribution also provides "spamd", a daemonized version of SpamAssassin which runs persistently. Using its counterpart, "spamc", a lightweight client written in C, an MTA can process large volumes of mail through SpamAssassin without having to fork/exec a perl interpreter for each message.
- In addition, "spamd", a daemonized version of SpamAssassin which
- runs persistently, is available. Using its counterpart, "spamc",
- a lightweight client written in C, an MTA can process large volumes of
- mail through SpamAssassin without having to fork/exec a perl interpreter
- for each message.
+ If you have questions about SpamAssassin, please check the Wiki[2] to see if someone has already posted an answer to your question. (The Wiki doubles as a FAQ.) Failing that, post a message to the
+ spamassassin-users mailing list[3]. If you've found a bug (and you're sure it's a bug after checking the Wiki), please file a report in our Bugzilla[4].
- If you have questions about SpamAssassin, please check the Wiki[2] to
- see if someone has already posted an answer to your question. (The
- Wiki doubles as a FAQ.) Failing that, post a message to the
- spamassassin-users mailing list[3]. If you've found a bug (and you're
- sure it's a bug after checking the Wiki), please file a report in our
- Bugzilla[4].
[2]: http://wiki.apache.org/spamassassin/
[3]: http://wiki.apache.org/spamassassin/MailingLists
@@ -68, +63 @@
----------------------
IMPORTANT: If you are upgrading from a previous major version of
+ SpamAssassin, please be sure to read the notes in UPGRADE to find out what has changed in a non-backwards compatible way.
- SpamAssassin, please be sure to read the notes in UPGRADE to find out
- what has changed in a non-backwards compatible way.
Installing SpamAssassin
@@ -81, +75 @@
Customising SpamAssassin
------------------------
+ These are the configuration files installed by SpamAssassin. The commands that can be used therein are listed in the POD documentation for the Mail::SpamAssassin::Conf class (run the following command to read it: "perldoc Mail::SpamAssassin::Conf"). Note: The following directories are the standard defaults that people use. There is an explanation of all the default locations that SpamAssassin will look at the end.
- These are the configuration files installed by SpamAssassin. The commands
- that can be used therein are listed in the POD documentation for the
- Mail::SpamAssassin::Conf class (run the following command to read it:
- "perldoc Mail::SpamAssassin::Conf"). Note: The following directories are
- the standard defaults that people use. There is an explanation of all the
- default locations that SpamAssassin will look at the end.
- /usr/share/spamassassin/*.cf:
@@ -255, +244 @@
means that you can translate messages, test descriptions, and templates
into other languages.
+ If you do so, we would *really* appreciate if you could send a copy back of the updated messages; mail them to
+ <spamassassin-users@incubator.apache.org> . Hopefully if it takes off, I can add them to the distribution as "official" translations and build in support for this. You will, of course, get credited for this work ;)
- If you do so, I would *really* appreciate if you could
- send a copy back of the updated messages; mail them to
- <spamassassin-users@incubator.apache.org> . Hopefully if it takes off,
- I can add them to the distribution as "official" translations and build
- in support for this. You will, of course, get credited for this work ;)
Help With SpamAssassin
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/ReadmeTxt
------------------------------------------------------------------------------
Welcome to SpamAssassin!
------------------------
+ What SpamAssassin Is
+ --------------------
+
SpamAssassin is a mail filter which attempts to identify spam using
a variety of mechanisms including text analysis, Bayesian filtering,
DNS blocklists, and collaborative filtering databases.
- Using its rule base, it uses a wide range of heuristic tests on mail
- headers and body text to identify "spam", also known as unsolicited
- commercial email.
+ What SpamAssassin Is Not
+ ------------------------
+
+ SpamAssassin is not a program to delete spam, route spam and ham to separate mailboxes or folders, or send bounces when you receive spam. Those are mail routing functions, and SpamAssassin is not a mail router. SpamAssassin is a mail filter or classifier. It will examine each message presented to it, and assign a score indicating the liklyhood that the mail is spam. An external program must then examine this score and do any routing the user wants done. There are many programs that will easily perform these functions after examining the score assigned by SpamAssassin.
+
+ How SpamAssassin Works
+ ----------------------
+
+ Using its rule base, SpamAssassin uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for
later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and
non-spam in between 95% and 100% of cases, depending on what kind of
+ mail you get and your training of its Bayesian filter. Specifically, SpamAssassin has been shown to produce around 0.9% false negatives (spam that was missed) and around 0.1% false positives (ham incorrectly marked as spam). See the rules/STATISTICS*.txt files for more information.
- mail you get and your training of its Bayesian filter. Specifically,
- SpamAssassin has been shown to produce around 0.9% false negatives (spam
- that was missed) and around 0.1% false positives (ham incorrectly marked
- as spam). See the rules/STATISTICS*.txt files for more information.
+ SpamAssassin also includes plugins to support reporting spam messages automatically or manually to collaborative filtering databases such as Pyzor, DCC, and Vipul's Razor.
- SpamAssassin also includes plugins to support reporting spam messages
- automatically or manually to collaborative filtering databases such as
- Pyzor, DCC, and Vipul's Razor.
The distribution provides "spamassassin", a command line tool to
perform filtering, along with the "Mail::SpamAssassin" module set
+ which allows SpamAssassin to be used in spam-protection proxy SMTP or POP/IMAP server, or a variety of different spam-blocking scenarios.
- which allows SpamAssassin to be used in spam-protection proxy SMTP or
- POP/IMAP server, or a variety of different spam-blocking scenarios.
+ The distribution also provides "spamd", a daemonized version of SpamAssassin which runs persistently. Using its counterpart, "spamc", a lightweight client written in C, an MTA can process large volumes of mail through SpamAssassin without having to fork/exec a perl interpreter for each message.
- In addition, "spamd", a daemonized version of SpamAssassin which
- runs persistently, is available. Using its counterpart, "spamc",
- a lightweight client written in C, an MTA can process large volumes of
- mail through SpamAssassin without having to fork/exec a perl interpreter
- for each message.
+ If you have questions about SpamAssassin, please check the Wiki[2] to see if someone has already posted an answer to your question. (The Wiki doubles as a FAQ.) Failing that, post a message to the
+ spamassassin-users mailing list[3]. If you've found a bug (and you're sure it's a bug after checking the Wiki), please file a report in our Bugzilla[4].
- If you have questions about SpamAssassin, please check the Wiki[2] to
- see if someone has already posted an answer to your question. (The
- Wiki doubles as a FAQ.) Failing that, post a message to the
- spamassassin-users mailing list[3]. If you've found a bug (and you're
- sure it's a bug after checking the Wiki), please file a report in our
- Bugzilla[4].
[2]: http://wiki.apache.org/spamassassin/
[3]: http://wiki.apache.org/spamassassin/MailingLists
@@ -68, +63 @@
----------------------
IMPORTANT: If you are upgrading from a previous major version of
+ SpamAssassin, please be sure to read the notes in UPGRADE to find out what has changed in a non-backwards compatible way.
- SpamAssassin, please be sure to read the notes in UPGRADE to find out
- what has changed in a non-backwards compatible way.
Installing SpamAssassin
@@ -81, +75 @@
Customising SpamAssassin
------------------------
+ These are the configuration files installed by SpamAssassin. The commands that can be used therein are listed in the POD documentation for the Mail::SpamAssassin::Conf class (run the following command to read it: "perldoc Mail::SpamAssassin::Conf"). Note: The following directories are the standard defaults that people use. There is an explanation of all the default locations that SpamAssassin will look at the end.
- These are the configuration files installed by SpamAssassin. The commands
- that can be used therein are listed in the POD documentation for the
- Mail::SpamAssassin::Conf class (run the following command to read it:
- "perldoc Mail::SpamAssassin::Conf"). Note: The following directories are
- the standard defaults that people use. There is an explanation of all the
- default locations that SpamAssassin will look at the end.
- /usr/share/spamassassin/*.cf:
@@ -255, +244 @@
means that you can translate messages, test descriptions, and templates
into other languages.
+ If you do so, we would *really* appreciate if you could send a copy back of the updated messages; mail them to
+ <spamassassin-users@incubator.apache.org> . Hopefully if it takes off, I can add them to the distribution as "official" translations and build in support for this. You will, of course, get credited for this work ;)
- If you do so, I would *really* appreciate if you could
- send a copy back of the updated messages; mail them to
- <spamassassin-users@incubator.apache.org> . Hopefully if it takes off,
- I can add them to the distribution as "official" translations and build
- in support for this. You will, of course, get credited for this work ;)
Help With SpamAssassin