[Cross post alert... This should have been posted on `talk' I had my wires crossed for a few posts which will no be posted to `talk']
The online docs at: http://spamassassin.org/doc/Mail_SpamAssassin_Conf.html Come within a hairs breadth of giving full details of what will work with whitelist_from but then leaves a lot of room for doubts. Even down to how to list more than one. Are they supposed to be whitespace separated or comma separated, or something else? Are these legal: whitelist_from *(Cron Daemon)* <reader> My experiments indicate they are not but I'm not sure if it is something else happening. The debug output indicates my conf files are found: debug: using "/usr/local/share/spamassassin" for default rules dir debug: using "/etc/mail/spamassassin" for site rules dir debug: using "/home/reader/.spamassassin" for user state dir debug: using "/etc/mail/spamassassin/user_prefs" for user prefs file But then no mention at all of `white_list_from' which is in the one cited /etc/mail/spamassassin/user_prefs and looks like: whitelist_from *(Cron Daemon)* also tried: whitelist_from (Cron Daemon) and whitelist_from root and whitelist_from root (Cron Daemon) None of those seems to work and none leave any particularly illuminating info in debug output. The actual `From: ' line looks like: From: root (Cron Daemon) Can it be white listed? Or maybe there is some other way to force a message to be accepted. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
