LIST-UPDATE-L ArchivesArchiver > LIST-UPDATE > 2006-08 > 1155999663
Subject: Re: [LIST-UPDATE] Advising List Subscribers re change
Date: Sat, 19 Aug 2006 11:01:03 EDT
In a message dated 8/19/2006 6:55:41 AM Eastern Standard Time,
That's not good. Just today I handled two bounces from of of my lists, both
of the subscribers using the same ISP. The bounce message said, "----- The
following addresses had permanent fatal errors -----
(reason: 571 prohibited. We do not relay)"
This let me know that the addresses were still good, so I contacted both
subscribers directly to let them know that list messages were bouncing.
Presumably they will be able to straighten things out with suscom. I'm not
sure what "we do not relay" means, but at least it gave the subscribers
something to go on.
I agree this will become a serious problem over time with Mailman--the
failure to show us the bounces. I'd be happy with some sort of bounce log
accessible to admins but I think we NEED to be able to check if someone asks us if
their list mail is bouncing when they are not receiving it. We need to be
able to troubleshoot it.
Like this block on mail to AOLers from the new server--I'm at a loss when I
report the problem to AOL to explain where the problem lies. Under SmartList
I could have told them--RootsWeb says the mail is sitting in a queue on
their server and AOL is refusing to pick it up for thus and such reason--but I
can't even do that--because I have NO idea where the problem lies or what the
problem is. AOL tells RootsWeb the server is white listed and that there may be
a general bug with delivering mail from mailing lists--but that doesn't
explain why we receive mail from all the other RootsWeb list servers but NOT from
lists9 at all.
Troubleshooting is essential for running mailing lists--and our hands are
tied when we can't see the bounces to help our list subscribers with delivery
|Re: [LIST-UPDATE] Advising List Subscribers re change by|