Re: 70.155.100.149 not listed but list.dsbl.org still fails lookup

George A. Petrick wrote:

> The following is a snippet from the log file from MDaemon that shows what
> happens if we use list.dsbl.org to try to trap spam - it does a great job on
> the problem emails, and we really want to use it, but in this case, it
> doesn't allow an email sent from me to Chuck in the same domain.

I'm not familiar with MDaemon or its log files, so I don't know what
"failed" means. If it means a DNS server failure (it is not unusual for
one or two of DSBL's name servers to have a temporary problem, see
http://dsbl.org/nsstatus) then that should not be a reason for rejecting
the client.
If "failed" means that MDaemon thinks that the client is listed, then
there is something really strange going on.

> Thu 2006-12-21 09:50:46: 'Recipient unknown' given and connection dropped to
> divert future spam
>
> Thu 2006-12-21 09:50:46: --> 550 <[email protected]>, Recipient
> unknown

Is this normal behavior for MDaemon? If a client is listed (or a server
is misconfigured!) then the DSBL name servers return a text message that
refers to the DSBL site, e.g. "http://dsbl.org/listing?127.0.0.2". Mail
servers are advised to include that string in their rejection message.
This is particularly useful if the server is misconfigured. For example
when using lists.dsbl.org (plural) instead of list.dsbl.org the DNS
server returns "Your mail has been rejected because the server you are
sending to is misconfigured and using dsbl.org incorrectly".

"Recipient unknown" is not a message generated by the DSBL name servers.

> Please help! Any information you can provide will be greatly
> appreciated .

My best guess is that the problem is MDaemon specific, did you already
try their tech support?