Wed, 7 Jan 2015 16:34:33 -0500
|
By this time, [log in to unmask] has already been served out (either by
Listserv postmaster action, or more probably, by by that address sending
Listserv email that Listserv did not understand). It will stay "served
out" until someone (anyone) sends Listserv a command "serve
[log in to unmask]".
Now, if the mail that address is sending to your list is problematic
(perhaps it is too big or contains nothing but HTML on a non-HTML list or
whatever), Listserv may send an email back to it explaining the problem.
If that email is not expected, perhaps it shoots something back to
Listserv ... and the counter goes up ... hit a number (normally 50, as I
recall) and Listserv gets tired of listening and serves the address out.
Cheers, Wayne
On Wed, Jan 7, 2015 at 1:55 PM, F J Kelley <[log in to unmask]> wrote
, in part
:
> ...
>
> An error occurred while processing file 4200162
> from
> [log in to unmask]: "Mail has been received for delivery to the
> NOTIFICATION-L list from a user that had been served out". Because of its
> size,
> the original message has been transferred to [log in to unmask];
> what
> you are seeing below is only the first 500 lines.
>
############################
To unsubscribe from the LSTOWN-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1
|
|
|