At 12:52 AM 8/26/03 -0700, Kevin Sexton wrote: <much cut>
it's not messages posted by you that would have bounced, but messages sent to you
Considering that the list generates one or two messages per month, the bounce limit must have been set incredibly low. More importantly, why was no attempt made to inform me that messages were bouncing? My e-mail address has always worked as it should for everything else. And they had no problem sending the 'unsubscribe' notice to me. (purging invalid addresses) is what the server was trying to do Probably, but check the two letter fragments attached below, which I received from the list on the day before I was unsubscribed. Do you think this could possibly have had anything to do with the event. And if so, could the 'administrator' have taken corrective action if he, she, or it, had been more alert. FIRST LETTER FRAGMENT----------------------------- Originator: <tieu@ai.mit.edu> Recipients: <fracprogrammers-list@terindell.com> Subject: Your details WARNING: The file document_9446.pif you received was infected with the W32/Sobig.f@MM virus. The file attachment was not successfully cleaned. SECOND LETTER FRAGMENT---------------------------- Originator: <Kilauea9402-46-24955791-0@flonetwork.com> Recipients: <fracprogrammers-list@terindell.com> Subject: Your details WARNING: The file document_9446.pif you received was infected with the W32/Sobig.f@MM virus. The file attachment was not successfully cleaned. END LETTERS--------------------------------------- I am not defending my loss of temper. Doing so is never the best course of action. I will accept a proper chastising by anyone who has never lost their temper. And I did count to 10. The 'administrator of the fracprogrammers list' was in the unfortunate position of being number 11. Jim (tempest in a teapot) Muth