Some months ago I had a lot of bounces alerts :
~~~~ To: server-owner@lists.fedoraproject.org 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). Von: "postmaster" postmaster@redhat.com Betreff: Your message couldn't be delivered Datum: 25. Dezember 2024 um 08:12:01 MEZ An: "Peter Boy via server" server-bounces@lists.fedoraproject.org Logo Your message couldn't be delivered The message you sent to miminar@gapps.redhat.com couldn't be delivered due to: Recipient email address is possibly incorrect. Further information 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. For more information, go to https://support.google.com/mail/?p=NoSuchUser e9e14a558f8ab-3c0df28e9bfsi68962515ab.66 - gsmtp If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive. © 2003 - 2019 Mimecast Services Limited. ~~~~
~~~~ To: server-owner@lists.fedoraproject.org
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).
Von: "postmaster" postmaster@redhat.com Betreff: Your message couldn't be delivered Datum: 25. Dezember 2024 um 08:12:01 MEZ An: "Peter Boy via server" server-bounces@lists.fedoraproject.org
Logo
Your message couldn't be delivered The message you sent to miminar@gapps.redhat.com couldn't be delivered due to: Recipient email address is possibly incorrect.
Further information 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. For more information, go to https://support.google.com/mail/?p=NoSuchUser e9e14a558f8ab-3c0df28e9bfsi68962515ab.66 - gsmtp
If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive.
© 2003 - 2019 Mimecast Services Limited. ~~~~
I removed the user miminar@gapps.redhat.com from the server subscription list after checking the address., and the bounces stopped .
Now they were back, multiple times, several days in a row (last week while I was on vacation). I checked our subscripted users list, it does not contain that address. Maybe you can check, what is going on. It is neither urgent nor likely to be harmful, but it is annoying.
Not urgent.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, lists, low-gain, ops
Yeah, I am seeing this on a number of lists.
Interestingly, the bounces I see are all from January... like it's processing a backlog or reprocessing old bounces... Very odd. We will need to investigate.
Other lists seeing lots of bounces: devel devel-announce epel-package-announce
It's in feb now... I really don't see how/why this is happening yet though. ;(
I have had no time to investigate this much, but it seems to be that it's processing all the old bounces slowly...
It is also unsubscribing some people for bouncing. So far as I can see from a quick check, those unsubscriptions are valid, ie, there's a real bounce that caused it.
It's up to april 22nd now.
The entire backlog was processed. It also marked a bunch of people as 'suspended' then just today (a month later) it's unsubscribing people with bounces.
I think it's processing as expected now, but if you see some cases where it failed I can investigate those more?
ok, please do open a ticket if you see this anymore...
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)