Resent-Organization: Academic User Services, The University of Akron
X-Resent-Date:  Wed, 02 Dec 92 12:04:27 EST
X-Resent-From:  Gary Sponseller <SPONSELL@AKRONVM>
X-Resent-Organization: Academic User Services, The University of Akron
X-Resent-To:    postmaster@banyan.com
Newsgroups: bit.listserv.banyan-l
Date:         Thu, 17 Dec 1992 14:59:15 EST
Comments:     Resent-From: Gary Sponseller <SPONSELL@AKRONVM>
Comments:     Originally-From: Revised List Processor (1.7e)
              <LISTSERV@AKRONVM.BITNET>
From:         Gary Sponseller <SPONSELL@AKRONVM.BITNET>
Subject:      Problem processing mail file from MAILER@AKRONVM

Hello Banyan-l subscribers,

I think that the people who use Banyan (you reading this mail) should
follow up on the Banyan mail problem explained below...

After all, most Listservs worldwide will complain when they sees any
non-standard mail.  The most logical course of action for a Listserv
Postmaster is to remove the problem subscription after finding repeated
rejections and no correction in sight.  What this means is that Banyan
subscribers are suffering because the software does not conform to
expected e-mail norms.

I sent the letter below to Postmaster@Banyan.Com with no response as of
yet.  Basically, Banyan Inc. should follow the RFC822 e-mail standard so
that Banyan users can maintain dependable mail services with the rest
of the Internet and Bitnet.

Thank you for your attention.
Gary
----------------------------Original message----------------------------
...Please forward this mail to your e-mail support staff...

Currently we are receiving hundreds of invalid e-mail files from various
Banyan VINES systems like the one below.  Hundreds of messages like this
are returned to Listserv@vm1.cc.uakron.edu weekly.  VM1.CC.UAKRON.EDU is
sponsoring the BANYAN-L list with approximately 300 subscribers -- most
are internet address (probably Banyan), many are sublists to further
explode Banyan-l mail into local networks.

The problems with this mail is that it is not "standard" format, as
required by RFC822, the de facto e-mail standard on Bitnet and on the
Internet.  All such mail is forwarded to a human reader for sorting
out -- you can imagine that the volume of mail makes this task hard
enough without having to discard invalid mail as well!

Please contact me for any further questions or clarifications on
this problem.  Thank you for your timely response.

Regards,
Gary Sponseller
Listserv Manager at the University of Akron

E-mail: SPONSELL@vm1.cc.uakron.edu
Phone:  216/972-6200
U.S. Mail:  Gary Sponseller
            Computer Center 144
            The University of Akron
            Akron, OH  44325-3501
----------------------------Original message----------------------------
Error occurred while processing file 1912 from MAILER@AKRONVM: "Command
mailfile contains invalid RFC822 fields and could not be parsed".

RFC822 parser messages follow:

<W> Invalid RFC822 field - "Undeliverable Message Notification:". Rest
    of header flushed.

------------------- Message causing the problem (43 lines) --------------------
Received: from AKRONVM by VM1.CC.UAKRON.EDU (Mailer R2.08 R208004) with BSMTP
 id 9114; Tue, 01 Dec 92 11:29:07 EST
Received: from dpnet.hq.af.mil by VM1.CC.UAKRON.EDU (IBM VM SMTP V2R1) with TCP;
   Tue, 01 Dec 92 11:29:04 EST
Received: by dpnet.hq.af.mil with VINES ; Tue,  1 Dec 92 10:59:30 EST
Date: Tue,  1 Dec 92 10:59:25 EST
From: MS%7CGDO1%SERVERS@dpnet.hq.af.mil
Subject: Undeliverable Message
Undeliverable Message Notification:
To: BANYAN-L@VM1.CC.UAKRON.EDU
Cc:
Bcc:

To:            Multiple,recipients,of,list,BANYAN-L
                 <BANYAN-L@AKRONVM.BITNET>
Cc:
Subject:       Errors in VANGuard log

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.

        VNM3043:  K Younger@SysAdmin@7CG


*****  ATTACHMENT: ORIGINAL MESSAGE *****


If on the PC you have more than one entry in the Login Search List you can see
these errors.

Example:
           List Contains:
                   1. Dean@Business
                   2. Accounting@Business

An accounting user trys to login using the name 'Greg Burgess' the login
program will first try 'Greg Burgess@Dean@Business', but since there is no
such user in the group Dean@Business VanGuard reports a failure on NiceName
(1013 can't find name).
Then the login program trys 'Greg Burgess@Accounting@Business' which succeeds.

-Greg..