LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (29 lines)
Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
From:
Nathan Brindle <[log in to unmask]>
Date:
Tue, 12 Oct 1999 11:45:40 EDT
In-Reply-To:
Message of Tue, 12 Oct 1999 10:33:29 -0500 from <[log in to unmask]>
Organization:
L-Soft international, Inc.
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
On Tue, 12 Oct 1999 10:33:29 -0500 mp said:
>I was wondering how listserv caught this Out-of-Office message.
>
>I have been told LSOFT can not identify and protect the list from these.

Starting with 1.8d this is not entirely true.  LISTSERV can identify
<some> formats of OOO mail and ignore them.  I don't know which formats,
unfortunately, but since most OOO mail is freeform and there is no standard
for it, the problem is one of deciding exactly how to <identify> a given
piece of mail as an OOO message.

>I assume it must be OPENMAIL specific flag in the header - Autoreplied

Nope.  It was caught because it was sent to the owner-mxg-l address,
exactly as it says in the error you forwarded.  Anything explicitly sent
to that address is evaluated as an error, period, whether it is OOO
mail, user unknown, whatever.

Nathan

>
>---------------------------Message
>The enclosed message has been identified as a delivery error for the MXG-L
>list because it was sent to [log in to unmask]
>
>------------------------------ Message in
>error -------------------------------
(snip)

ATOM RSS1 RSS2