Fred Moyer wrote:
Hello,
We're running qpsmtpd in production and an email to an address we
host was returned with the following message [1]. Can someone clue me
into if this is an issue with my qpsmtpd setup?
Thanks for your help.
- Fred
<[EMAIL PROTECTED]>:
64.71.135.162 does not like recipient.
Remote host said: 550 Mail from HELO smtp113.sbc.mail.re2.yahoo.com
rejected because it does not accept bounces. This violates RFC
821/2505/2821 http://www.rfc-ignorant.org/
Giving up on 64.71.135.162.
--- Below this line is a copy of the message.
Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 20847 invoked from network); 12 Sep 2005 22:12:27 -0000
Received: from unknown (HELO ?10.0.47.212?)
([EMAIL PROTECTED]@128.164.228.7 with plain)
by smtp113.sbc.mail.re2.yahoo.com with SMTP; 12 Sep 2005 22:12:27 -0000
Message-ID: <[EMAIL PROTECTED]>
Date: Mon, 12 Sep 2005 15:12:26 -0700
From: Email Sender <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Yes, qpsmtpd setup.
rbldns or dnsbl or spamassassin's blacklisting
is using rfc-ignorant.org's blacklist, and that is
telling you that yahoo is bad. You can set your
loglevel down to 4 in ./config/loglevel and see
in your log file which plugin returns that code.
I took out rbldns and dnsbl and spamassassin and
rely on dspam to figure out who's bad. As a first step
you could take either whitelist yahoo or take the
rfc ig blacklist out of the list used by those checks.
As I always say, this sort of thing is proof that the
witch-hunt hysteria and lynch mob mentality is a
dead-end. The law and order mob has to be put in
its $3.50/hr place before we see another Blackwater
FEMA evacuation of all email boxes in New Orleans.
-Bob
