After wasting some time attempting to stop YAML (Yet Another Mail
Loop) on Infonets, I'd like to know, what the criteria are which
allow Listserv to detect rejection notices and similar mailer mess.
I don't expect that it will help much, but at least I'd like to
give postmasters of sites with offending mailers some hints how
a rejection notice should look like to reduce the risk of mailing
loops. And after all, a guy here is writing gateway code to support
mail to a bunch of Xerox workstations. Up to now only a 'feature' of
the Crosswell-mailer (rejecting RCPT FROM: <>, used by this gateway
for rejection notices) saved us from trouble. But as soon as I replace
X1.25 by version 2, this guy probably should know how to send
Listserv-proof rejection notices :-)
 
  Thomas
 
P.S.: The trouble maker of today (in case you'd like to increase the
size of Listserv's hate list by some more SERVE <addr> OFF commands):
 
  [log in to unmask]
  [log in to unmask]
 
------- the following isn't appropriate for a technical list,
        but anyway, here it goes ... ------------------------------
 
P.P.S.: This is a request for help from an EARN site. After reading
the notebooks of the EARNTECH list of the last few months, I
understand if Eric will not bother to reply to this question.
I understand his position regarding EARN well enough, so that
I'm now wondering if I'm really interested in how to prevent
mailing loops. But then, the flow of information (and rejection
notices :-) does not know anything about administrative domains,
and affects the whole Bitnet/Earn/Netnorth ...
 
Eric, at least let me know if I should send questions like this
to DEAR-BOD. From what I have heard, there are the guys who
know how to run this network - even without asking some techies.
And I'm really interested in competent answers :-)