Ha ha, speak of misconfigured autoresponders, look what I just got in my email box after posting to the list: On Fri, 18 Jan 2002, Mailer-Daemon wrote:
Sorry. Your message could not be delivered to:
paonia,Mass College Art (The name was not found at the remote site. Check that the name has been entered correctly.)
Be careful out there! --paul CueMan -- http://www.cuenet.com Info@cuenet.com -= At the speed of the Internet =-
At 7:47 PM -0500 1/18/02, Paul Thomas is rumored to have typed:
Ha ha, speak of misconfigured autoresponders, look what I just got in my email box after posting to the list:
Everyone who posts to the list gets that one. It got so annoying I stopped accepting SMTP connections from exon.massart.edu (209.6.44.8, I think). (*sigh*) If the brain-dead mailer had the clue to send it's bounce to the envelope sender (if memory serves, it's one of those stupid Lotus Notes machines), maybe the mailing list could unsubscribe the dead address. But by sending it to the From: header field, it's just annoying anyone who posts to the list. I tried sending a complaint to various upstream addresses, but it's pretty clear there's no one at the "school" who knows how to plug in a computer let alone fix a misconfigured application, so I gave up and just reject inbound connections. I had hoped maybe the bounces would get the postmaster's attention, but my guess is that no one bothers to read postmaster's mail. Charlie (who also tried to get the list owner to remove the bad address with equally ignored results)
On Sat, 19 Jan 2002, Charlie Summers wrote:
Everyone who posts to the list gets that one. It got so annoying I stopped accepting SMTP connections from exon.massart.edu (209.6.44.8, I think).
the list. I tried sending a complaint to various upstream addresses, but it's pretty clear there's no one at the "school" who knows how to plug in a computer let alone fix a misconfigured application, so I gave up and just reject inbound connections. I had hoped maybe the bounces would get the postmaster's attention, but my guess is that no one bothers to read postmaster's mail.
Sounds like a job for procmail. Why not make a little recipe that catches that bounce and just forwards it on to the following addresses: Administrative Contact: Laura Chmielecki Massachusetts College of Art 621 Huntington Ave Boston, MA 02115 UNITED STATES (617) 879-7878 lchmielecki@massart.edu Technical Contact: Randy Brinson Massachusetts College of Art 621 Huntington Ave. boston, MA 02115 UNITED STATES (617) 879-7857 rbrinson@massart.edu --Paul -- http://www.cuenet.com Info@cuenet.com -= At the speed of the Internet =-
At 4:56 PM -0500 1/19/02, Paul Thomas is rumored to have typed:
Sounds like a job for procmail.
You are, of course, welcomed to do so. I tried alerting various addresses, including the two you mentioned, some pulled from a lookup of the netblock owners, and culled from the website *, numerous times and was completely ignored. I frankly prefer not to hear from their machine if it's so damaged, and so just reject SMTP conections (with the hopefully helpful error, "572 Fix your broken mailer"). In this case, an autoresponse seems the _worst_ way to deal with it, since it is a complaint about a broken autoresponse. I _know_ the bounce is going to the envelope sender in this case, since the SMTP connection is dropped on the floor before the DATA transaction. (Besides...we ain't talking about AOL here. Do you really think anyone on your machine would notice if massart.edu couldn't mail into your box? Ever even _hear_ of the place before they started annoying those of us who post to this list?) Charlie * Specifically postmaster@exon.massart.edu, postmaster@massart.edu, lchmielecki@massart.edu, rbrinson@massart.edu, boudreau@massart.edu, postmaster@rcn.com, noc@rcn.com
On Sat, Jan 19, 2002 at 03:32:33PM -0500, Charlie Summers wrote:
Everyone who posts to the list gets that one.
I tried sending a complaint to various upstream addresses...
I sent a note to this list's maintainer, smartlist-owner@... There doesn't seem to be much point in trying to reform a determined mis-configed site, but if the list human can be woken to remove the offending subscriber, that works for me. I always appreciate it when my list's posters give me a heads up to these situations so I can remove the culprit; after all, with this mis-config, my smartlist isn't going to get the info to remove the guy. Jim
participants (3)
-
Charlie Summers -
Jim -
Paul Thomas