24.2.2012 13:23, Michelle Konzack kirjoitti: > In relation to the previous poster with the fetchmail problem (the > receiver should hide fetchmail received header by adding "set invisible" > in the "global" section) I have the probvlem, that receiving MTAs runing > spamassassin consider my mails as spam du to the received headers... >
Not here. Great negative score and no fear of spammines.
X-Spam-Level:
X-Spam-Status: No, score=-12.6 required=5.0 tests=KHOP_PGP_SIGNED,
KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RCVD_IN_RP_CERTIFIED,
RCVD_IN_RP_SAFE,SPF_FAIL,T_RP_MATCHES_RCVD autolearn=unavailable
version=3.3.1
X-Spam-Virus: No
X-Spam-Report:
* -3.0 RCVD_IN_RP_CERTIFIED RBL: Sender is in Return Path Certified
* (trusted relay)
* [Return Path SenderScore Certified (formerly]
[Bonded Sender) - <http://www.senderscorecertified.com>]
* -2.0 RCVD_IN_RP_SAFE RBL: Sender is in Return Path Safe (trusted
relay)
* [Return Path SenderScore Safe List (formerly]
[Habeas Safelist) - <http://www.senderscorecertified.com>]
* -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/,
high
* trust
* [140.211.11.3 listed in list.dnswl.org]
* -0.1 RCVD_IN_HOSTKARMA_W RBL: HostKarma: relay in white list (first
pass)
* [140.211.11.3 listed in hostkarma.junkemailfilter.com]
* -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
* domain
* 0.0 SPF_FAIL SPF: sender does not match SPF record (fail)
* -3.0 KHOP_PGP_SIGNED Message seems to contain PGP signature
* 0.5 KHOP_RCVD_UNTRUST DNS-whitelisted sender is not verified
X-Spam-ASN: AS3701 140.211.0.0/16
I just wonder where my BAYES went. Strange.
--
Abandon the search for Truth; settle for a good fantasy.
signature.asc
Description: OpenPGP digital signature
