On 9/18/2010 4:57 PM, 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 > version=3.3.1 > X-Spam-Report: > * 0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1 > * 0.9 SPF_FAIL SPF: sender does not match SPF record (fail) > * [SPF failed: Please see > +http://www.openspf.org/Why?s=mfrom;id=notifications%2Bvvvo8mu4wy%40zyngamail.co > +m;ip=10.49.16.82;r=helium.inexs.com] > Your trusted_networks is broken. SA thinks that helium.inexs.com is not a part of your normal mail delivery, and thus is assuming that is the originating outside server for zynga.
Looking at the message you sent to the list, helium is actually your server.
