On Sat, 2010-09-18 at 15:57 -0500, 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
This generally is not a good idea, and it is much better to use the con-
strained variants, whitelist_from_rcvd or whitelist_auth. Besides, it
renders the following entries redundant... ;)
> whitelist_from_rcvd *...@zyngamail.com zyngamail.com
> whitelist_allows_relays *...@zyngamail.com
The second argument to whitelist_from_rcvd is matched against the rDNS.
> 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
> * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
> * valid
> * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
> * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
But there is no rDNS.
> 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.
Nope, the whitelisting did not trigger indeed. The rcvd one did not,
because there is no rDNS. Dunno why the unconstrained didn't fire, you
did not provide the relevant headers.
Anyway, assuming at least one of the matched addresses for whitelisting
(see the docs) matches the message, and seeing that DKIM is valid (even
though they borked rDNS), you probably should try whitelist_auth.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
