On Fri, 2 Apr 1993 15:16:39 CST THE GAR said:
>
>When we looked at what was coming to which reader, what we saw was that
>everything that went to LISTSERV had type MAILDIST and had multiple
>recipients.  Everything that went to MAILER had type MAIL, and was
>delivered normally...all the MAILDIST mail ended up bouncing to the
>POSTMAST id.
 
Now that  GITVM1 has been removed  from the backbone and  EMUVM1 has been
added, we  (EMUVM1) are the closest  (in net terms) backbone  LISTSERV to
SAMFORD so much  of the mail destined for SAMFORD  gets exploded here. To
meet the NJE requirements of 1.7f, I  added LMAIL as a second mailer here
and notes  to SAMFORD started bouncing  because LMAIL was not  defined to
your MAILER as a  trusted agent. As a result, I  have configured LMAIL to
send  DIRECT to  SAMFORD, bypassing  your  MAILER altogether.  This is  a
temporary situation because I hope to make LMAIL our primary MTA soon and
then its name will match what you already have configured.
 
I  believe  that  I  have  dealt with  this  situation  with  respect  to
LISTSERV@EMUVM1, but you  may have problems from other sites  that had to
do similar  things. As a  temporary measure, you  may want to  change the
"allow-charlatans" tag in your XMAILER  profile to "TRUE". This will tell
mailer to accept as valid any mail even if the RSCS origin does not match
the RFC822 tags.
 
In any event, since I'm almost a neighbor, please let me know if there is
anything that I can do.
 
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Bert Bruner                     BITNET: OSAKB@EMUVM1                ::
:: VM Specialist/Postmaster        Internet: [log in to unmask] ::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::