Hi Mark,
Thanks for your reply, and no problem with the delayed response. I knew you
were away from a note you left.
I don't know what a DSN looks like, but there is only that 1 attachment.
Below is the whole thing including headers and unsubscribe email attachment.
BTW, does this list allow me to attach files? Might do that next time.
I've obfuscated some parts with "XXX". Here it is. See more comments below
the email.
Return-Path: <mailman-boun...@serverxxx.webhostingbuzz.com>
Delivered-To: te...@xxx.net
Received: from serverXXX.webhostingbuzz.com
by serverXXX.webhostingbuzz.com with LMTP id gHWCD8eMplm6SwAA9jRSrA
for <te...@xxx.net>; Wed, 30 Aug 2017 05:00:39 -0500
Return-path: <mailman-boun...@serverxxx.webhostingbuzz.com>
Envelope-to: te...@xxx.net
Delivery-date: Wed, 30 Aug 2017 05:00:39 -0500
Received: from [127.0.0.1] (port=58524 helo=serverXXX.webhostingbuzz.com)
by serverXXX.webhostingbuzz.com with esmtp (Exim 4.89)
(envelope-from <mailman-boun...@serverxxx.webhostingbuzz.com>)
id 1dmznb-00069e-4b
for te...@xxx.net; Wed, 30 Aug 2017 05:00:39 -0500
Received: from [127.0.0.1] (port=58490 helo=serverXXX.webhostingbuzz.com)
by serverXXX.webhostingbuzz.com with esmtp (Exim 4.89)
(envelope-from <all-boun...@rivexxx.org.nz>)
id 1dmznZ-000681-Me
for all-ow...@rivexxx.org.nz; Wed, 30 Aug 2017 05:00:37 -0500
Subject: Bounce action notification
From: mail...@rivexxx.org.nz
To: all-ow...@rivexxx.org.nz
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4320979077890092118=="
Message-ID: <mailman.4.1504087236.1346.all_rivexxx.org...@rivexxx.org.nz>
Date: Wed, 30 Aug 2017 05:00:36 -0500
Precedence: list
X-BeenThere: a...@rivexxx.org.nz
X-Mailman-Version: 2.1.23
List-Id: RLC All <all.riveXXX.org.nz>
X-List-Administrivia: yes
Errors-To: mailman-boun...@serverxxx.webhostingbuzz.com
Sender: "ALL" <mailman-boun...@serverxxx.webhostingbuzz.com>
--===============4320979077890092118==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
This is a Mailman mailing list bounce action notice:
List: ALL
Member: te...@xxx.net
Action: Subscription bounce score incremented.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mail...@rivexxx.org.nz.
--===============4320979077890092118==
Content-Type: message/rfc822
MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ALL unsubscribe notification
From: mailman-boun...@rivexxx.org.nz
To: all-ow...@rivexxx.org.nz
Precedence: list
Message-ID: <mailman.0.1504087235.23494.all_rivexxx.org...@rivexxx.org.nz>
Date: Wed, 30 Aug 2017 05:00:35 -0500
X-BeenThere: a...@rivexxx.org.nz
X-Mailman-Version: 2.1.23
List-Id: RLC All <all.riveXXX.org.nz>
X-List-Administrivia: yes
Errors-To: mailman-boun...@rivexxx.org.nz
Sender: "ALL" <mailman-boun...@rivexxx.org.nz>
x...@xxxtraining.co.nz has been removed from ALL.
--===============4320979077890092118==--
That's the end of it.
In this case my email address is both the owner and an UNmoderated member of
the list, but I get the same problem when the owner address is not a member of
the list at all. If I click my email address link from the Membership List
page, it says this near the top, in case it is relevant:
"We have received some recent bounces from your address. Your current bounce
score is 2.0 out of a maximum of 20.0. Please double check that your subscribed
address is correct and that there are no problems with delivery to this
address. Your bounce score will be automatically reset if the problems are
corrected soon."
Also, sometimes I might receive emails relating to subscribes but not
unsubscribes.
I think all these problems started happening in the last year or so, on lists
which I've had for years without such problems.
Some of my lists still don't seem to have any of these problems, but I haven't
worked out what's different about them yet.
I can delete & recreate a list as a test, if required.
Thanks Mark.
Terry
________________________________
From: Mark Sapiro <m...@msapiro.net>
Sent: 29 August 2017 10:09
To: mailman-users@python.org
Subject: Re: [Mailman-Users] "Bounce action notification" emails for
subscribes/unsubscribes
Sorry for the delayed reply. I've been away.
On 08/18/2017 08:11 PM, Terry . wrote:
>
> But in recent months I’ve noticed that, as list owner, when I subscribe or
> unsubscribe someone, instead of just receiving an email with the subject:
> “<listname> subscription notification”
> or:
> “<listname> unsubscribe notification”
> I receive an email with the subject:
> “Bounce action notification”
> Which contains:
>
> “This is a Mailman mailing list bounce action notice:
>
> List: Bro [for example]
>
> Member: mylistadminaddr...@mydomain.com [for example]
>
> Action: Subscription bounce score incremented.
>
> Reason: Excessive or fatal bounces.
>
> The triggering bounce notice is attached below.
>
> Questions? Contact the Mailman site administrator at
> mail...@somedomain.com<mailto:mail...@somedomain.com>.” [for example]
>
>
>
> And that email contains an ATTACHMENT which has the subject:
> “<listname> subscription notification”
> or:
> “<listname> unsubscribe notification”
This is very strange. What seems to be happening is the (un)subscription
notification is bouncing, causing a bounce notification to be sent to
the list owner, but a bounce notification should only be sent if the
original (bounced) message was to a list member, not the owner.
Also the bounce notification should also have an attached DSN with
details of why the (un)subscription notification bounced. What does that
say?
> Notes:
> - This didn’t used to happen with these same lists, and I don’t know what’s
> triggered the change in behaviour.
>
> - Even if I change the list “owner” address to another of my addresses, it
> still happens.
>
> - I have admin_notify_mchanges set to “Yes”.
>
> - I don’t have any moderators set up.
OK
> Questions:
>
> Q1. Is this a known issue?
No
> Q2. What’s the likely cause of this problem suddenly starting to happen?
Post the full raw bounce action notice with all headers and MIME parts
and I might be able to say more.
> Q3. What’s the likely solution?
See Q2
> Q4. Do you need any more info to troubleshoot the cause of this? If so,
> what, exactly?
See Q2
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
