> It seems, ther is a bug in thsis SA rule... because from the header I
> see, that I was authenticated and SA see this too, so why it does reject
> MY OWN MESSAGE?
Does your header definitely include an ESMTP marker as per the RFC? Mine
didn't; that was the real issue. We didn't find a bug in
> Spamassassin does honor authentication headers that are -properly- added.
> (see rfc3848 for an official statement of what needs to be done). In your
> example that MTA (qmail?) did not add proper authentication headers.
Ah right. Yes, it's qmail. It appears that RFC3848 is not directly support
> no. You should just properly configure trusted_networks and
> internal_networks so all dnsbl rules would be used as they should.
OK, so I need to add all of my ISPs dynamic IPs as trusted? (as suggested in
http://wiki.apache.org/spamassassin/DynablockIssues)
It sounds backwards though; the abo
> You should use SMTP authentication when posting through your SMTP
> server.i guess you are not.
> (And the SMTP server should not be on dynamic IP, of course)
I am using SMTP authentication, and it's on a static IP. It's the PC with my
Thunderbird that's on a dynamic IP.
> The dynamic checks
> your IP isn't backlisted. It's listed as a DUL, which is correct:
OK, right, that makes sense.
> You'll have to use a smarthost or get a static/business connection.
I'm not sure I understand this bit. From what I see on
http://en.wikipedia.org/wiki/Smart_host, I already use a "smart host", in
Like so many people, I get a dynamic IP from my ISP. Right now, any emails I
send to myself show up as "RCVD_IN_SORBS_DUL". Somehow I thought that as
long as my SMTP server isn't blacklisted, something like this wouldn't
happen.
The exact message is: RCVD_IN_SORBS_DUL RBL: SORBS: sent directly fr
