On Thu, 1 Mar 2012 16:18:56 +0100 Michelle Konzack wrote: > Hello RW, > > Am 2012-02-25 22:42:47, hacktest Du folgendes herunter: > > I think that this is pretty conclusive that it's nothing to do with > > Spamassassin. It doesn't look anything like what I'd expect for a > > Spamassassin-based rejection. I looks like some basic MTA check. > > > > Another thing is that it's failing to find an A-record, so nothing > > to do with rDNS either. > > Why should I have an A-Record for my <work1> if it can not > public accessed? I do not know a singel MTA (like courier, > exim, postfix, Exchange, MSMTP) which does recursive A-Record > checks on Received: Headers.
My point was that it was rejected for a single specific reason, not based on a score. And that the error referred to forward dns not reverse. Given that this is the only actual evidence about the rejections. I don't see any basis for speculation about Spamassassin, let alone Spamassassin checking reverse DNS - unless there's more to the rejection message. > > Have you checked to see if you are sending mail with > > an @work1.intranet1.tamay-dogan.net address in the smtp envelope. > > Yes, ant ist seems to be correctly. > > Thanks, Greetings and nice Day/Evening > Michelle Konzack >
