DNSBL -Bset:URL mode

Kostik koc@fax.ru
Mon Nov 29 13:30:42 UTC 2010

Vernon Schryver wrote:
> "Just send 8 bits" for SMTP was nonsense 15+ years ago because it did
> not not work.   It's still is nonsense and doesn't work, although it
> no longer crashes sendmail.  Few except spammers care, because we now
> have the ESMTP encoding negotiation as well as MIME.
> "Just put non-ASCII into domain names" has also always been and is
> still nonsense.  Few except spammers care because we have Punycode.

Yes, I'm talking about 8-bit encoded message:
Received: from jupiter.usedns.com (jupiter.usedns.com [])
        by mx.google.com with ESMTP id x83si2413778weq.125.2010.;
        Fri, 19 Nov 2010 02:45:57 -0800 (PST)

[ SKIP ]

MIME-Version: 1.0
Content-Type: text/html;charset=koi8-r
Content-Transfer-Encoding: 8bit

In the real world such messages are exist. Is it possible to somehow encode
such domains in Punycode and only then use DNSBL?

Now this situation in the logs looks like this:
DNSBL helper URL \208\210\201\215\197\212.\210\198
gethostbyname(\208\210\201\215\197\212.\210\198.dbl.spamhaus.org): Unknown

> There might be bugs in the dccifd/dccproc/dccm parsing of URLs containing
> Punycode in mail message bodies.  Do you have an example that looks bad?

If the message body already contains a ponycoded URL, there is no problem.
Everything works well:
DNSBL helper URL xn--d1acufc5f.xn--p1ag
gethostbyname(xn--d1acufc5f.xn--p1ag.dbl.spamhaus.org): Unknown host

>> 3. Parsing html-encoded domain name problem:
>> ---
>> DNSBL helper URL
>> grand-ptc.ru
>> gethostbyname(grand-ptc.ru.dbl.spamhaus.org):
>> Unknown server error
> That might be a bug.  What was complete %-encoded URL in the mail message?

Like this:


More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.