I want to thank Mike for his efforts on the Team Ada email list.
He is doing the right things, in my opinion. I believe he is also
a volunteer, so he is doing them on his own time.
Note, tho, that Mike corrected the problem of the moment. The next
time some sysop (or the like) on some system receiving the Team Ada
broadcasts installs a new email system or changes the existing one
and sets the mailer to send error messages to the Reply-To field
instead of the Errors-To field, we will have the same problem again.
I've seen it over and over on the PAL lists. So, we can expect it
An alternative is to use a newsgroup, like comp.lang.ada (maybe
we need a comp.team_ada?). That makes the discussion a pull rather
than a push for the readers (they have to go out of their way
to read the messages rather than having them delivered), but it
does eliminate the mail loop problem. Also, when it comes to
spam, most newsreaders I've seen allow you to download the subject
info without downloading the messages until you ask to see a message.
That helps a lot with the spam.
Michael Berman wrote:
> Topic 1: Ads
> The Team Ada list is currently set up as unmoderated and unrestricted in
> who may post. We have mostly been spared from spam - the listserver is
> able to detect when a message is sent to multiple lists and filter it
> out as probable spam. However, clever spammers can still get mail
> through somehow.
> We have the option of restricting posting to list subscribers only. We
> voted a while back and decided not to do so at that time. If the spam
> becomes intolerable, we may need to revisit the issue.
> Topic 2: Bounce notices from cc:Mail
> These have been occurring since late last week. The server reporting the
> bounce is supposed to send this notice to the list administrator (me),
> not the entire list. I will remove the offending account so that no
> future bounces are generated.
> When you see bounce messages like this one distributed to the list,
> please send me a quick note ([log in to unmask]). I get several of
> these daily, and don't often recognize when one is distributed to the
> list instead of coming directly to me.
mailto:[log in to unmask] http://monmouth.com/~conn/
Opinions expressed are my own and not necessarily those of anyone else.