Hello!
I'm getting "bounces" like this from a misconfigured site which bounces
to the header From instead of the envelope from.
Perhaps that recipient should just be removed from the list?
The "bounce" has envelope from
[EMAIL PROTECTED]
(should be empty!)
header from
[EMAIL PROTECTED]
and stems from
[193.74.71.21] (helo=xizor.is.scarlet.be)
(helo matches the reverse-mapping of the IP, double reverse check
matches)
Its received lines seem to be echoed from the original mail (bad!).
The upmost received lines from the original mail are:
Received: from (smtp-vbr10.xs4all.nl [194.109.24.30])
by fundy.is.scarlet.be with ESMTP id j9NJNaoW011305
for <[EMAIL PROTECTED]>;
Sun, 23 Oct 2005 21:23:36 +0200
Received: from bag.python.org (bag.python.org [194.109.207.14])
by smtp-vbr10.xs4all.nl (8.13.3/8.13.3) with ESMTP id j9NJNV5u040983
for <[EMAIL PROTECTED]>; Sun, 23 Oct 2005 21:23:36 +0200 (CEST)
(envelope-from [EMAIL PROTECTED])
Received: from bag.python.org (bag [127.0.0.1])
by bag.python.org (Postfix) with ESMTP id E0E2B1E411D
for <[EMAIL PROTECTED]>; Sun, 23 Oct 2005 21:23:14 +0200 (CEST)
So something at or after smtp-vbr10.xs4all.nl or fundy.is.scarlet.be is
heavily misconfigured. Please fix this (CC is set to people who could be
responsible): DSNs should have an empty (null) envelope sender and
should be sent *only* to the envelope sender of the original message,
the header (From/Reply-To) should never be evaluated for creating
DSNs/bounces.
Kind regards,
Hannah.
----- Forwarded message from [EMAIL PROTECTED] -----
From: [EMAIL PROTECTED]
To: Hannah Schroeter <[EMAIL PROTECTED]>
Date: Wed, 26 Oct 2005 17:38:30 +0200
Subject: Returned mail: User unknown
The original message was received at 2005-10-26 17:34:24 +0200
from postoffice.local [10.0.0.1]
----- The following addresses had permanent fatal errors -----
<[EMAIL PROTECTED]>
-----Transcript of session follows -----
... while talking to postoffice.local.:
>>> RCPT To:<[EMAIL PROTECTED]>
<<< 550 5.1.1 unknown or illegal alias: [EMAIL PROTECTED]
550 <[EMAIL PROTECTED]>... User unknown
Reporting-MTA: dns; postoffice.local
Received-From-MTA: DNS; postoffice.local
Arrival-Date: 2005-10-26 17:34:24 +0200
Final-Recipient: RFC822; [EMAIL PROTECTED]
Action: failed
Status: 5.1.1
Remote-MTA: DNS; postoffice.local
Diagnostic-Code: SMTP;550 5.1.1 unknown or illegal alias: [EMAIL PROTECTED]
Last-Attempt-Date: 2005-10-26 17:34:24 +0200
From: Hannah Schroeter <[EMAIL PROTECTED]>
To: mailman-users@python.org
Date: Sun, 23 Oct 2005 21:23:00 +0200
Subject: Re: [Mailman-Users] Disable Subscriptions/Unsubscriptions
Hello!
On Sun, Oct 23, 2005 at 09:11:00PM +0200, Bernd Petrovitsch wrote:
>Hi all!
>Is there a possibility to disable the member subscription/unsubscription
>through the web interface?
>The list-members are added and removed with a script which is fed from a
>DB so there is no point in self-subscription.
I don't know whether there's a specific knob in mailman itself, but
you could either just not publish the list info address at all, or
deny access to it, using appropriate web server configuration (access
control or rewrite rules to show explanatory text instead).
> Bernd
Kind regards,
Hannah.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/jjbl3213%40tiscali.be
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
----- End forwarded message -----
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
