In response to my post to LSTOWN-L, I got two messages personally of the
same nature, for "out of office" replies from LSTOWN-L subscribers.  One was
from fredlaw.com and the other was from indiana.edu.

There must be some company who is handling all these out of office message
responses as bounces without identifying who it is and suddenly my server
has decided to send them to me.

I have written the verizon people and told them I was setting them to
"nomail" and to change it if they are actually getting messages.  Since the
LSTOWN-L
subscribers did the same thing, I could not be sure it is only verizon, and
have checked and find that other companies are involved, earthlink and more.

So I will post a message to my list about the out of office messages, and
wait it out, I suppose.

Barbara Passmore


----- Original Message -----
From: "Barbara Passmore" <[log in to unmask]>
Cc: "Keith MacVicar" <[log in to unmask]>
Sent: Thursday, January 01, 2004 9:22 PM
Subject: Fw: Error messages


> Because of the number of error messages coming in, I am setting all
> verizon.net subscribers to "nomail."  With the exception of the one from
> whom I have heard.
> If you are okay and are getting messages, send this message to:
> [log in to unmask]  set floridabirds-l mail
>
> If you are away and get this message when you return, do the same.
>
> Barbara Passmore
> Listowner
>
> ----- Original Message -----
> From: "Barbara Passmore" <[log in to unmask]>
> Sent: Thursday, January 01, 2004 8:54 PM
> Subject: Error messages
>
>
> > If you get this message, you have a verizon.net address and are
subscribed
> > to FLORIDABIRDS-L.
> >
> > Apparently, someone or more than one on verizon.net is not accepting
> > messages from FLORIDABIRDS-L.  The address given is none of yours but
may
> be
> > a forwarding address.
> >
> > If you get this message, let me know so that I will know you are not the
> one
> > causing the trouble.  I will set the ones I do not hear from to
"nomail."
> > --
> > Barbara Passmore
> > Listowner, FLORIDABIRDS-L
> > [log in to unmask]
> >
>