On Fri, 24 Feb 2012 12:23:21 +0100 Michelle Konzack wrote: > 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)
That doesn't sound like like a optimum solution unless you're optimizing for minimum administrative effort. I have the probvlem, that > receiving MTAs runing spamassassin consider my mails as spam du to > the received headers... > ... > c) Public mail server mail.tamay-dogan.net > (78.47.247.21) d) Receiving mail server > > If now d) is runing spamassassin, thaen my messages are to 90% > rejected. As far as positive scoring rules are concerned, Spamassassin should only care about the reverse dns of the last external relay, and mail.tamay-dogan.net has impeccable dns. You haven't quoted any rules that are firing inappropriately. Do you have any evidence that this is anything to do with Spamassassin or reverse dns? On Fri, 24 Feb 2012 12:32:35 +0100 Robert Schetterer wrote: > I am not realy sure if this fixes your problem but i have set > > score RDNS_NONE 0 > > cause the "default" points at this parameter looks like nonsense to me > i have also a scenario with private net relays which will not have any > reverse dns records ever RDNS_NONE shouldn't fire on a private IP address unless you've done something a bit "challenging".
