On Thu, Oct 27, 2005 at 06:42:08PM +0300, Timo Sirainen wrote:
On Thu, 2005-10-27 at 10:16 -0500, /dev/rob0 wrote: Switched back now.
If you have any future SORBS problems, advise people not to use that list for blocking. :) And of course try to contact SORBS ... Mat might listen. I think he tries to be reasonable. Since you *do* have rDNS, you cannot be considered a dynamic IP by most measures.
Well, I tried to remove it from the dynamic block using the automatic interface, but it says "No acceptable MX records found for dovecot.org". I guess the first problem was that I was using smtp.dovecot.org and its PTR pointed to dovecot.org, but after changing that it's still failing. Oh well.
The view from here is that the sending address is no longer listed in SORBS. I can tell 'cuz my personal delivery script tags the header with a list of various interesting DNSBLs, e.g.:
X-DNSBLs: spamcop, sorbs
which tends to jump out at me. Also:
41% dnsblc 80.64.10.60
42%
Anybody using SORBS to block at SMTP-time (esp. without whitelisting or taking other factors into account) deserves what they get, IMHO. It's not your responsibility to pander to them. I'm not saying it's not a valuable metric.. just, well, a race between a receiver making bad blocking decisions and a sender trying to get around those decisions helps prop up those bad decisions, and dumbs everything down.
mm (who probably makes bad blocking decisions too, but would rather fix them than having them accomodated)