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 (20 lines)
Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Tue, 3 Sep 1996 14:04:32 -0400
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Subject:
From:
Stan Ryckman <[log in to unmask]>
Content-Type:
text/plain; charset=US-ASCII
In-Reply-To:
<[log in to unmask]> from "Thomas Kern" at Sep 3, 96 08:59:55 am
Organization:
Amber & Sneakers Fan Club
MIME-Version:
1.0
Tom Kern asked:
> I am trying to have a list serve as the distribution mechanism for some
> automated status reports from some processees such as nightly backups,
> database reorganizations, etc. Mostly these messages come from third
> party products and are NOT changeable. I am getting message rejections
> with LISTSERV 1.8A saying that the message is rejected because its content
> is the same as a previous message. If all goes right, these duplicate
> messages will all say that everything worked right, and I want all of these
> messages to get through to the list recipients. I can understand the
> desire to filter out duplicate messages from general audience lists, but
> is there anyway I can permit them on this ONE specialized list?
 
Can you get your processes to put their output into a file?  If so,
then just tack a date and time onto the output before mailing to
your list, and each message will be different.
 
(Just my 2 cents worth).
 
Stan.

ATOM RSS1 RSS2