Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTOWN-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Menu
LISTSERV Archives LISTSERV Archives
LSTOWN-L Home LSTOWN-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Subject:
Re: Error blues again.
From:
Nicolas Graner <[log in to unmask]>
Reply To:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Sat, 20 Jan 1996 02:15:18 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Many seem to agree that it would be nice if listserv could interpret more
error formats, but not everybody has the same needs. Wouldn't it be easier to
make this customizable on a list-by-list basis? There could be keywords to
define patterns (regular expressions?) indicative of transient and permanent
errors respectively. L-Soft could predefine any number of these if they wish.
Then, a listowner who gets loads of errors of a particular type would add a
pattern for it, under their own responsibility. Errors matching a pattern
would be handled appropriately by auto-delete, others would be sent to the
owner. Is there any difficulty in implementing this?
 
Similarly, the problem of digests included in error reports could be handled
by truncating all error reports to "max-error-length" lines, where
"max-error-lines" is a list header keyword. Wouldn't this satisfy everyone,
and be trivial to implement?
 
Nicolas

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV