Opened 4 years ago

Closed 15 months ago

#2528 closed defect (fixed)

Bounce messages - Announcement list

Reported by: vrautenbach Owned by: cvvergara
Priority: critical Milestone: Unplanned
Component: SysAdmin/Mailman Keywords:
Cc:

Description

After sending a email to the announcement mailing list. I received a large amount of bounced messages linked to various subscribers. Below is an example of the emails received:

This is a Mailman mailing list bounce action notice:

List: Announce Member: Subscribers email Action: Subscription disabled. Reason: Excessive or fatal bounces.

The triggering bounce notice is attached below.

Change History (14)

comment:1 by neteler, 4 years ago

Can you please check if a yahoo.com email is involved? (they may trigger these "bounce storms")

comment:2 by vrautenbach, 4 years ago

I check now, there weren’t any yahoo emails. It was quite a range from usgs to gmails. Let me know if I can give any more information.

Thank you the assistance.

comment:3 by neteler, 4 years ago

(somewhat related: ticket:2475#comment:21 etc.)

comment:4 by cvvergara, 3 years ago

I could subscribe

comment:5 by cvvergara, 3 years ago

I don't think I really solved the problem. But a testing message from me has arrived to the mailing list

https://lists.osgeo.org/pipermail/announce/2020-December/000522.html

Up to now I have not received bounced messages. Maybe only administrators receive the bouncing messages. @vrautenbach Please report

comment:6 by vrautenbach, 3 years ago

I think it is only the administrators that receive the bounce emails. But the mass unsubscribe and bounce emails (over 50) happend when I posted an email to the list.

Should I add the emails removed during the bounce storm and post a new email to the list to test if it happens again?

comment:7 by vrautenbach, 3 years ago

Priority: majorcritical

comment:8 by cvvergara, 3 years ago

Setps:

  • make a backup of currently registred subscriptions (Vicky)
  • Send a test mail (Victoria)
  • See if more unsubscriptions occur (Victoria)

if they do not occur, then add the missing unsubscribed if more un-subscriptions occur the restore the backup

comment:9 by cvvergara, 3 years ago

made a backup of subscribers: regular and digest subscribers

/usr/lib/mailman/bin/list_members -r announce > announce-regular-dec04.txt
/usr/lib/mailman/bin/list_members -d announce > announce-digest-dec04.txt

comment:10 by neteler, 3 years ago

To check the current bounce states, you may

  • activate in the mailman list settings that you (list admin) want to be notified by email
  • check on the server:
    root@osgeo6:~# cat /var/log/mailman/bounce
    

Hint: To reset all bounce levels for all lists and members, run

root@osgeo6:~# withlist -a -r reset_bounce --   ## reset all mailman bounce levels

comment:11 by vrautenbach, 3 years ago

Good day All

This was recently again an issue. We had over 120 emails that bounced. This occurred on 29 April. Is there anything from a user side that we can do?

I checked now all these subscribers with bounced emails in this round is still subscribed, but if I check some of the previous bounced mails (from 6 months ago), those subscribes are not listed as members of the mailing list anymore, did the system remove them?

Regards Victoria

in reply to:  11 comment:12 by neteler, 3 years ago

Replying to vrautenbach:

Good day All

This was recently again an issue. We had over 120 emails that bounced. This occurred on 29 April. Is there anything from a user side that we can do?

We need to check once more if our list server complies with the continuously changing email requirements/security measures.

I checked now all these subscribers with bounced emails in this round is still subscribed, but if I check some of the previous bounced mails (from 6 months ago), those subscribes are not listed as members of the mailing list anymore, did the system remove them?

I am afraid yes, see also my comment here: https://trac.osgeo.org/osgeo/ticket/2475#comment:15

comment:13 by robe, 2 years ago

Since we've upgraded the server, which upgrades postfix, I'm hoping that fixed whatever this issues is. Is this still happening?

comment:14 by cvvergara, 15 months ago

Resolution: fixed
Status: assignedclosed

Not happening for a while so its sorted out.

Note: See TracTickets for help on using tickets.