ND HECN E-mail Postmaster <INFO@NDSUVM1>
Mon, 8 Aug 88 18:29:36 CDT
|
Two things that would be "nice" or maybe are already there but I
don't know about. This was prompted after wading through thousands and
thousands of lines of bounced messages (and over 100 messages) because
domain ".PT" was not yet defined in the TREARN LISTSERV... ;-(
1. Would it be possible (maybe as an option) to put the LISTSERV error
message mail in the same RDR file as the error mail? Eg. with -----
or something separating them? I know it is much easier and probably
a lot safer to transfer the mail but with hundreds of bounces this
would cut the number of mail items in half and also make it easier
to diagnose what is going on (some messages like syntax errors or
sender/daemon flags are not obvious at first...).
2. Is there a way (with DIST2) to easily and safely "blackball" a LISTSERV?
I would LOVE to be able to send NOTHING to LISTSERV@TREAN! Of course
with the lag lately they might have fixed the problem by the time
I get the mail but... I am sure there are ways to do this with DIST2.
I had also though of having a "priviliged" flag in the list entry
which a maintainer could set to "mail directly only" for that one
subscriber entry in that list no matter what "Mail-Via" is. However,
something like "TELL LISTSERV DONTUSE TREARN" and
"TELL LISTSERV USE TREARN" or whatever to dynamically alter what
DIST2 would use locally would be VERY nice - I think... =:-)
As usual, messages in the heat of battle can get garbled - and this
isn't even the Persian Gulf. But any suggestions and pointers would be
welcomed I am sure... Thank you!
----------
Marty Hoag ND HECN E-mail Postmaster
ND Higher Education Computer Network US Mail: NDSU Computer Center
Work Phone: (701)-237-8639 PO Box 5164 / UCCS
Fargo, ND 58105
Bitnet: INFO@NDSUVM1 (Including EARN, NetNorth)
ARPA: [log in to unmask]
UUCP: ...!psuvax1!NDSUVM1.BITNET!INFO
AKA: [log in to unmask]
|
|
|