Cameron Arnott <[EMAIL PROTECTED]> schrieb/wrote:
> Received: from muncher.math.uic.edu([131.193.178.181]) by
> 21cn.com(JetMail 2.3.2.1)
> with SMTP id /aimcque/jmail.rcv/0/jm1b3860678d; Wed, 22 Dec 1999
> 00:00:34 -0000
> Received: (qmail 210 invoked by uid 1002); 21 Dec 1999 23:59:56 -0000
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Precedence: bulk
> Delivered-To: mailing list [EMAIL PROTECTED]
These lines mean that 21.com is malconfigured and forwards messages to
the address in the To header (which is the list address) instead of
correctly handling the envelope addresses.
Obviously, a user at 21.com is subscribed to the list, but the broken
mailer forwards the messages back to the list instead, which detects the
loop and bounces the message.
Useful for spammers: Just send the messages to [EMAIL PROTECTED] with the
actual recipients in the To header.
I already informed [EMAIL PROTECTED] and qmail-owner, but 21.com's
admins did not react.
Did I say I hate those ***** domain POP3 systems?
Hm, maybe in the future, ezmlm should check for such brokenness and
refuse to subscribe users of such broken systems.
> also.. i'm getting and reading mail right.. then i'm also getting mail
> saying that qmail couldn't deliver my mail
...
> <[EMAIL PROTECTED]>:
> 203.87.57.227 does not like recipient.
> Remote host said: 550 <[EMAIL PROTECTED]>: Relay access denied
> Giving up on 203.87.57.227.
But this is really strange.
Is it possible that qmail already sends a bounce message if the primary
MX fails and before it tries to send messages to the secondary.
Anyway, whatever 203.87.57.227 is, it does not accept messages for
[EMAIL PROTECTED]
--
Claus Andre Faerber <http://www.faerber.muc.de>
PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
