On Sat, Sep 18, 2010 at 06:46:18PM -0500, Dave Funk wrote: > On Sat, 18 Sep 2010, Chuck Campbell wrote: > > >I have SA set up and working (mostly) on my mail machine, however I've put > >the > >following into my user_prefs: > > > >whitelist_from *...@zyngamail.com > >and > >whitelist_from_rcvd *...@zyngamail.com zyngamail.com > >and > >whitelist_allows_relays *...@zyngamail.com > > > > > >when email comes in from them it is flagged as spam. > > > >Here is an example spam report from the headers: > > > >X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on helium.inexs.com > >X-Spam-Flag: YES > >X-Spam-Level: ***** > >X-Spam-Status: Yes, score=5.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, > > DKIM_VALID_AU,FSL_HELO_NON_FQDN_1,HTML_MESSAGE,MIME_HEADER_CTYPE_ONLY, > > MIME_HTML_ONLY,RDNS_NONE,SPF_FAIL,TO_NO_BRKTS_NORDNS_HTML > >+autolearn=disabled > [snip..] > >I have contacted them about their SPF failure, and am awaiting a response, > >but > >I don't see any reference to my whitelisting, is it not working as I > >anticipated? > > > >If it is there, and I just don't see it, let me know where, and how to > >increase it's score to ensure whitelisted emails are not flagged as spam. > > > >thanks, > >-chuck >
First, thanks for the reply. > I assume when you say "into my user_prefs" you mean the per-user prefs > (as opposed to the site-wide config). yes, those in the /home/user/.spamassassin/user_prefs file > > Have you enabled per-user prefs in the site-wide config? (default is not > enabled). Is SA integrated in your mail system in a way that it "knows" Not sure where to enable this. Will dig more in the docs. > the user name of the recipient? (some integration methods do not make that > info avaialble to SA so the per-user prefs don't work). > Have you checked to make sure that your user_prefs are available/readable > to the SA daemon? How do I test this? > > Try putting those white-list statements in the global "local.cf" config > file (do a --lint check & what ever steps are necessary to restart SA so > that it will see the changes) and then test to see if the whitelist works. Done this in /etc/mail/spamassassin/local.cf waiting for appropriate message(s) to arrive and check headers. > If it does then there's an issue with your per-user prefs, if not then > there's an issue with the white-listing itself. I'll be back...
