I'm owner of perl-devel@l.f.o and I get following bounce from Google MTA. Because current mailman cannot recognize it, it forwards it to list owner.
Could you modify mailman to recognize following bounce format?
{{{ ----- Forwarded message from mailman-bounces@lists.fedoraproject.org -----
Date: Tue, 01 Nov 2011 14:13:57 +0000 From: mailman-bounces@lists.fedoraproject.org To: perl-devel-owner@lists.fedoraproject.org Subject: Uncaught bounce notification
The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s).
For more information see: https://admin.fedoraproject.org/mailman/admin/perl-devel/bounce
Date: Tue, 01 Nov 2011 14:13:56 +0000 From: Mail Delivery Subsystem mailer-daemon@googlemail.com To: perl-devel-bounces@lists.fedoraproject.org Subject: Delivery Status Notification (Delay)
This is an automatically generated Delivery Status Notification
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipient has been delayed:
michaelrf.hunter+fedoraproject.org@gmail.com
Message will be retried for 10 more day(s)
Technical details of temporary failure: Account temporarily disabled
----- Original message -----
Received: by 10.52.36.41 with SMTP id n9mr566472vdj.41.1319802004295; Fri, 28 Oct 2011 04:40:04 -0700 (PDT) Return-Path: perl-devel-bounces@lists.fedoraproject.org Received: from bastion.fedoraproject.org (bastion01.fedoraproject.org. [209.132.181.2]) by mx.google.com with ESMTP id et1si4765739vcb.81.2011.10.28.04.40.03; Fri, 28 Oct 2011 04:40:04 -0700 (PDT) Received-SPF: pass (google.com: domain of perl-devel-bounces@lists.fedoraproject.org designates 209.132.181.2 as permitted sender) client-ip=209.132.181.2; Authentication-Results: mx.google.com; spf=pass (google.com: domain of perl-devel-bounces@lists.fedoraproject.org designates 209.132.181.2 as permitted sender) smtp.mail=perl-devel-bounces@lists.fedoraproject.org Received: from lists.fedoraproject.org (collab01.vpn.fedoraproject.org [192.168.1.21]) by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id CB83A20E99; Fri, 28 Oct 2011 11:39:22 +0000 (UTC) Received: from collab1.fedoraproject.org (localhost.localdomain [127.0.0.1]) by lists.fedoraproject.org (Postfix) with ESMTP id 9499B326768; Fri, 28 Oct 2011 11:39:22 +0000 (UTC) X-Original-To: Perl-devel@lists.fedoraproject.org Delivered-To: Perl-devel@lists.fedoraproject.org Received: from smtp-mm03.fedoraproject.org (vm4.fedora.ibiblio.org [152.19.134.143]) by lists.fedoraproject.org (Postfix) with ESMTP id 51CC63266EF for Perl-devel@lists.fedoraproject.org; Fri, 28 Oct 2011 11:39:19 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by smtp-mm03.fedoraproject.org (Postfix) with ESMTP id C96A537D0E for Perl-devel@lists.fedoraproject.org; Fri, 28 Oct 2011 11:39:18 +0000 (UTC) Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9SBdI1o008486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for Perl-devel@lists.fedoraproject.org; Fri, 28 Oct 2011 07:39:18 -0400 Received: from mx1.redhat.com (ext-mx13.extmail.prod.ext.phx2.redhat.com [10.5.110.18]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9SBdIZv019302; Fri, 28 Oct 2011 07:39:18 -0400 Received: from bastion.fedoraproject.org (bastion01.phx2.fedoraproject.org [10.5.126.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9SBdH0d008482; Fri, 28 Oct 2011 07:39:17 -0400 Received: by bastion01.phx2.fedoraproject.org (Postfix) id E7C3420DFE; Fri, 28 Oct 2011 11:39:16 +0000 (UTC) Delivered-To: perl-io-socket-ssl-owner@fedoraproject.org Received: from pkgs01.phx2.fedoraproject.org (pkgs.fedoraproject.org [10.5.125.44]) by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id DD87620DF9; Fri, 28 Oct 2011 11:39:16 +0000 (UTC) Received: by pkgs01.phx2.fedoraproject.org (Postfix, from userid 100109) id A7CB221616; Fri, 28 Oct 2011 11:39:16 +0000 (UTC) To: perl-IO-Socket-SSL-owner@fedoraproject.org, scm-commits@lists.fedoraproject.org From: Paul Howarth pghmcfc@fedoraproject.org Subject: [perl-IO-Socket-SSL] Update to 1.49 MIME-Version: 1.0 Keywords: perl-IO-Socket-SSL X-Project: perl-IO-Socket-SSL X-Git-Refname: refs/heads/master X-Git-Oldrev: fa11cf0c506a794d4b550fbc93128c62899327ab X-Git-Newrev: edb47ab0e1ccc8ab3d5b349dfa201f2357ac40a0 Message-Id: 20111028113916.A7CB221616@pkgs01.phx2.fedoraproject.org Date: Fri, 28 Oct 2011 11:39:16 +0000 (UTC) X-RedHat-Spam-Score: -1.504 (ALL_TRUSTED,RP_MATCHES_RCVD) X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11 X-Scanned-By: MIMEDefang 2.68 on 10.5.110.18 X-BeenThere: perl-devel@lists.fedoraproject.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Fedora perl development team perl-devel@lists.fedoraproject.org List-Id: Fedora perl development team List-Unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/perl-devel, perl-devel-request@lists.fedoraproject.org?subject=unsubscribe List-Archive: http://lists.fedoraproject.org/pipermail/perl-devel List-Post: perl-devel@lists.fedoraproject.org List-Help: perl-devel-request@lists.fedoraproject.org?subject=help List-Subscribe: https://admin.fedoraproject.org/mailman/listinfo/perl-devel, perl-devel-request@lists.fedoraproject.org?subject=subscribe Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: perl-devel-bounces@lists.fedoraproject.org Errors-To: perl-devel-bounces@lists.fedoraproject.org
commit edb47ab0e1ccc8ab3d5b349dfa201f2357ac40a0 Author: Paul Howarth paul@city-fan.org Date: Fri Oct 28 12:38:07 2011 +0100
Update to 1.49 - New upstream release 1.49: - Another regression for readline fix: this time it failed to return lines at EOF that don't end with newline - extended t/readline.t to catch this case and the fix for 1.48
perl-IO-Socket-SSL.spec | 8 +++++++- sources | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec index a2a862c..49f5311 100644 --- a/perl-IO-Socket-SSL.spec +++ b/perl-IO-Socket-SSL.spec @@ -4,7 +4,7 @@ #
Name: perl-IO-Socket-SSL -Version: 1.48 +Version: 1.49 Release: 1%{?dist} Summary: Perl library for transparent SSL Group: Development/Libraries @@ -59,6 +59,12 @@ rm -rf %{buildroot} %{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog +* Fri Oct 28 2011 Paul Howarth paul@city-fan.org - 1.49-1 +- Update to 1.49 + - another regression for readline fix: this time it failed to return lines + at EOF that don't end with newline - extended t/readline.t to catch this + case and the fix for 1.48 + * Wed Oct 26 2011 Paul Howarth paul@city-fan.org - 1.48-1 - Update to 1.48 - further fix for readline fix in 1.45: if the pending data were false (like diff --git a/sources b/sources index 34316ab..e58c583 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -c96d57d5089c4eeba2d7a891d7ec5726 IO-Socket-SSL-1.48.tar.gz +236c754eb3755d280504a7ca8ba5ba01 IO-Socket-SSL-1.49.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
----- End forwarded message ----- }}}
Filed upsteam: https://bugs.launchpad.net/mailman/+bug/886296
If someone wants to work on a patch for DSN.py in the mean time, please do. ;)
Upsteam is asking:
"The example DSN attached is a "delay" message. If Mailman did recognize it, it would just be ignored anyway. If we are going to recognize it, it would help if we had the entire, raw message source with all headers rather than what appears to be an MUA's rendering of it.
More importantly, what does the ultimate "I give up" DSN look like?"
Do you have the full email with headers you can attach? I can attach it upstream, or you could. ;)
Google delay warning forwarded by mailman to list owner google-delay.mbox
Replying to [comment:2 kevin]:
More importantly, what does the ultimate "I give up" DSN look like?" I haven't seen any. Maybe the final error message is recognized properly, maybe the user can re-enable his Google account before time-out. Do you have the full email with headers you can attach? Attached as google-delay.mbox. I can attach it upstream, or you could. ;) Please do so, I have no account on that horrible bug tracking system.
I haven't seen any. Maybe the final error message is recognized properly, maybe the user can re-enable his Google account before time-out.
Do you have the full email with headers you can attach? Attached as google-delay.mbox.
I can attach it upstream, or you could. ;) Please do so, I have no account on that horrible bug tracking system.
Updated upstream.
Looks like this was added/fixed in 2.1.11... so when we move to rhel6, it should be fixed. ;(
This should now be done with the move to the new mail server. ;)
Please reopen if its not.