I use exactly this format in my local.cf and it works. whitelist_from *@anbtx.com
I also have some users where I: whitelist_to [email protected] and a couple of domains where I am backup MX: all_spam_to *@domain.com all of these work fine for me, I do not have the allow_user_rules 1 that Gilbert has, but I am running a system wide spamassasin and not per user. Make sure you restart the processes after you add the rules - at least I do. I just stop and restart the whole qmail system with qmailctl. Hope that helps. -----Original Message----- From: Gilbert T. Gutierrez, Jr. [mailto:[email protected]] Sent: Tuesday, September 04, 2012 4:54 PM To: [email protected] Subject: Re: [qmailtoaster] Whitelisting in SpamAssassin If you are adding the whitelist rules on a user by user case, you need to add the flag "allow_user_rules 1" to your local.cf. I store all my user specific rules in MySQL for spamassassin and I use whitelist_from. The whitelist_from never worked until I added the allow_user_rules 1 in the local.cf. Gilbert T. Gutierrez, Jr. Operations Manager Phoenix Internet On 8/30/2012 1:41 PM, Casey James Price wrote: > Hi all, > > One of my customers is having an issue with emails being incorrectly > classified as spam by SpamAssassin. They are using a 3rd party site > with a form to handle registrations from customers. The form is > configured to send the mail to a specific user on their domain (in > this case lets call that [email protected])...the form is also setup so > that the From and reply-to addresses point to whatever email addresss > the user filling out the form inputs. > > I can see in my spamdyke logs that those messages are originating from > skyride.digiknows.com, so I went ahead and tried whitelisting that > address in spamdyke for the whitelist_senders list, but where I'm > having problems is that spamassassin is still classifying the mail as > spam. I tried whitelist_from *@skyride.digiknows.com as well as > whitelist_from_rcvd (not sure if I fully understand how this one works > though). > > Running the latest release of QMT/QTP. > > Here is a snippet from my local.cf > > ok_locales all > skip_rbl_checks 1 > > required_score 5 > report_safe 0 > rewrite_header Subject [SPAM] SA1 > > use_pyzor 1 > > use_auto_whitelist 1 > > bayes_path /home/vpopmail/.spamassassin/bayes > use_bayes 1 > use_bayes_rules 1 > bayes_auto_learn 1 > bayes_auto_learn_threshold_spam 6.5 > bayes_auto_learn_threshold_nonspam 0.1 bayes_auto_expire 1 loadplugin > Mail::SpamAssassin::Plugin::URIDNSBL > > score FH_DATE_PAST_20XX 0.0 > > # Rule2XSBody - speedup by compilation of rulseset to native code > loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody > > trusted_networks 69.7.35.11 69.7.35.25 69.7.35.131 69.7.35.42 > > whitelist_from *@skyride.digiknow.com > whitelist_from_rcvd *@skyride.digiknow.com skyride.digiknow.com > whitelist_allows_relays [email protected] > > > Anyone have any ideas? > > Thanks! > > -- > Casey James Price > > Smile Global Technical Support > Submit or check trouble tickets http://billing.smileglobal.com > www.smileglobal.com <http://www.smileglobal.com> > > Follow us on Twitter <https://twitter.com/#%21/SmileInternet> > Find us on Facebook <https://www.facebook.com/smileglobal> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
