Is anyone else receiving the "Your message to REDACTED (was: $oldSubject)" auto-responses to posts to NANOG?
I've been seeing them for three or four days now.
Yes, someone needs to forcefully remove this subscription:
I have also received these and I sent an email to the NANOG administrators about it.
Thanks ~ Bryce Wilson, AS202313, EVIX AS137933
Yes, someone needs to forcefully remove this subscription:
Agreed.
Subject: Re: Your message to lemanm@yahoo-inc.com (was: Re: Extending network over a dry pair)
Yep.
I've received multiple private replies from a number of people who have also stated that they are receiving them and have contacted nanog-owner asking them to do something about it. (Something I've also did myself days ago.)
I brought it up on the list to confirm my suspicious and to test the temperature of the water.
Here's trusting ~> hoping that the nanog-owner(s) will "do the needful" (with or without "reverting") as soon as time permits.
Yes. Same email address.
That email addy is from an employee that just left the company. For any of the administrators it should be safe to remove the subscription for that address. ( I can confirm directly from my company email account if that’s required for confirmation. )
I can try and chase someone internally to see if I can get the auto-responder replied stopped to the list.
Can I request that the (any) auto-responder be enhanced to:
1) Not respond to emails with Precedence: List
2) Retain a list of source addresses that it has responded to such that it can respond only once to each source.
3) Possibly reply with the null reverse path (if systems will allow).
The pedantic part of me would also like to see the Auto-Submitted: header with a value of auto-replied, or less accurate auto-generated. [1]
[1] https://www.iana.org/assignments/auto-submitted-keywords/auto-submitted-keywords.xhtml
We got something in to fix the behavior of the auto-responder to not reply to things with a Precedence header present.
I’m told something was already in the pipe on the auto-submitted header as well.
Cool.
Thank you for the update.
BUMP
This has been going on for more than a week now. I'm quite confident that there have been hundreds of auto-replies. (I'm seeing 285 incoming message from the NANOG mailing list since I became aware of the auto-reply.)
I'm really surprised that there has not been any reply or action by the NANOG list owner(s). I would have hoped, if not expected, better, or any, response by now.
This can happen for many reasons.
Quitting employees, dropping domains, death whatever.
They should be somehow auto removed after a certain number of bounces.
M.
Well, somebody who seemed to be from Yahoo claimed they were fixing
their auto-responder. Obviously, that hasn't been deployed yet.
I’m glad that the bounces are not sent to the list, but that means that the list does not know about them and therefore can’t do anything automatically. There is little we can do other than block the email individually until the list owners or Yahoo themselves manage to remove them.
This should be a lesson to those running email auto-reply systems to set up some way to have them not make these auto-replies to mailing lists which should not be too hard to automate.
Thanks ~ Bryce Wilson, AS202313, EVIX AS137933
This can happen for many reasons.
Quitting employees, dropping domains, death whatever.
Yep. I get it.
They should be *somehow* auto removed after a certain number of bounces.
The catch is, they aren't /bounces/. They are auto-responses to the sender of the email. Meaning I'll get one to me for this reply. You very likely got one to you for the message that I'm replying to.
Delivery to the problematic recipient is very likely succeeding at an SMTP level.
So, the mailing list manager doesn't see them and has no opportunity to do anything about them.
Here, I have added the admins to this mail to let them know what bugs us…
And sure with each response I do too get an email like the one attached screenshot.
Yeah, these are notes bounces but one of the auto responders which is hard to track.
Maybe there should be a reporting address listed on NANOG page just for this purposes.
M.
Here, I have added the admins to this mail to let them know what bugs us...
Okay.... (See below.)
Maybe there should be a reporting address listed on NANOG page just for this purposes.
I would have thought (read: expected) that the nanog-owner@nanog.com email address would have gone to the list owners.
I agree that there should be an easy way to contact list owners. Hence the standard convention of $LIST-owner address / alias.
I don't know. Maybe something got broken during an upgrade. I'll stop harping.
To be clear, I got this reported to the team internally that handles the auto responder stuff. I’m a network guy, not a mail guy.
If the list admins can unsubscribe the address it’s probably going to be faster, especially around the holidays here.
I would have thought (read: expected) that the nanog-owner@nanog.com email
address would have gone to the list owners.
It should. If it doesn't, then the mail system is broken. Note that
the -owner address is supported by Mailman (which runs these lists) and
that it will generate an alias for that -- among others -- when the
list is created.
I agree that there should be an easy way to contact list owners. Hence the
standard convention of $LIST-owner address / alias.
Yes. Y'know, on my never-ending todo list there's an item to write an
update to RFC 2142 with that in it. And possibly "listmaster" as the
role address for the keeper-of-all-mailing-lists.
---rsk