You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by sp...@incubator.apache.org on 2004/07/08 19:56:19 UTC
[SpamAssassin Wiki] Updated: TestingInstallation
Date: 2004-07-08T10:56:19
Editor: DanKohn <da...@dankohn.com>
Wiki: SpamAssassin Wiki
Page: TestingInstallation
URL: http://wiki.apache.org/spamassassin/TestingInstallation
Added command line test , fixed wording, added link
Change Log:
------------------------------------------------------------------------------
@@ -14,14 +14,16 @@
If installing from source, before running "make install", run "make test".
-=== After installation ===
+=== Command line ===
-Send yourself GTUBE, the Generic Test for Unsoliticed Bulk Email:
+From the command line, try {{{spamassassin -D --lint < sample-spam.txt}}}
-http://www.spamassassin.org/gtube/
+=== In mail ===
-Due to a bug in some versions of SpamAssassin, don't send it using your own account if you are using the Auto-Whitelist. Send it using a throwaway account or just delete the auto-whitelist file after sending the test.
+To test your mail setup (such as your UsedViaProcmail or IntegratedinMta, send yourself GTUBE, the Generic Test for Unsoliticed Bulk Email:
-If SpamAssassin is working, the message will be marked as spam. Note that SpamAssassin only marks messages as spam and that how it
-does this marking may be affected by your front-end. If you're not using the "spamc" or "spamassassin" program and are using a third-party
-front-end ('''especially amavisd'''), then it may not be completely obvious how spam messages are handled.
+[http://www.spamassassin.org/gtube/ GTUBE]
+
+Don't use GTBE with versions of SpamAssassin prior to 2.63, since it can pollute your AutoWhiteList. However, you don't want to be using old versions of SpamAssassin in any case.
+
+If SpamAssassin is working, the message will be marked as spam. Note that SpamAssassin only marks messages as spam and that how it does this marking may be affected by your front-end. If you're not using the "spamc" or "spamassassin" program and are using a third-party front-end ('''especially amavisd'''), then it may not be completely obvious how spam messages are handled.