HDTenEightyP/NetNews huggingface dataset:
From: KLENSIN@INFOODS.MIT.EDU (John C Klensin)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: Internet mail address in RFC 822 header
Date: 28 Sep 92 11:47:01 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@INNOSOFT.COM"
X-VMS-Cc: IN%"jobes@mayo.edu", IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>

>> We use PMDF and PMDF-MR to interface smtp to Message Router which integrates
>> All-in-1 IOS, All-in-1 Mail, OfficeVision (PROFS) via MRP, and VMS Mail via
>> MRGATE.  It works very well.  PMDF has given OfficeVision users access to the
>...
>> Is it possible to configure PMDF so that the sender's Internet mail address
>> appears in the RFC 822 header?

>This question is somewhat nonsensical. The sender's address appears in the
>RFC822 header by definition. PMDF-MR converts this information into Message
>Router header information. Any header information that remains after conversion

Ned,
   Let me see if I can pose this question a slightly different way,
since I'm guessing, based on a few recent experiences, at what is going
on here.  If my guess is wrong, consider this a separate question...
  Let's assume that I've got a situation in which most of my users have,
or can have, VAX-based mail accounts (VMSMail and, in some cases,
anxiously waiting for your UA, plus maybe an MM user or two).  And many
of them have access to LAN-based and/or weird-protocol products that
have the same symptoms as the list in the original message: at least for
sending purposes, mail is travelling out via MR.  This typically gives a
given user at least two addresses: something of the VMSMail/easy-RFC822
persuasion (vms-userid@domain) and something of the X.400 persuasion in
the local-part.
  I want only the easy-RFC822 addresses to appear "outside": whether the
user originates mail in one environment or another should be invisible
to external users and, if the user switches receiving/delivery
environments back and forth, that should *clearly* be invisible outside.

  Now, the question is "how to do that?".  Clearly the reversal database
works, but, if I correctly understand things, I've got to include one
record in it for each user with an X.400-ish address, rewriting that
address into a simple-822-mailbox address.  But those X.400-ish things
clearly obey patterns, since the local mail administrator controls most
of their content if not their actual syntax.
  So, the revised question (or at least my revised question) is "given
that I can state a rule that maps the X.400-like addresses given to
users onto the VMS User IDs we give out, is there a way to apply that
rule to rewrite the local-part of outgoing mail so that I don't have to
list every single user in the address reversal database?"
     --john
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: PMDF-L%IRLEARN.bitnet@nic.SURFnet.nl
X-VMS-To: IN%"PMDF-L%IRLEARN.bitnet@HEARN.nic.SURFnet.nl"
X-VMS-Cc: SMITHM
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Date:         Mon, 28 Sep 92 17:26:45 GMT
From:         SMITHM@ADMINA.RFERL.ORG
Subject:      PMDF_SIGNATURE logical name
Newsgroups: bit.listserv.pmdf-l


I have been using the PMDF_SIGNATURE logical recently and noticed that
when I use the MAILSERV channel on one of my own nodes (SUB / UNSUB) I get
a successfully added/removed message but also a separate bounce message
saying it doesn't understand my signature.  Is there a way around this ?


                                        Thanks,

                                                Michael.



                        ################################
Michael J Smith - Systems Programmer                    SMITHM@RFERL.ORG
RFE/RL inc                                      Phone  : 089 210  23723
Munich                                          Fax    : 089 2102 3752
Germany
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
Date:         Thu, 1 Oct 92 13:40:27 GMT
From:         paul jones <pjones%lambada@LAMBADA.OIT.UNC.EDU>
Subject:      please unsubscribe me from the pmdf list
Newsgroups: bit.listserv.pmdf-l

I'm on as ultima@unc.bitnet

=================================================================
     Paul Jones
     Office FOR Information Technology
     University of North Carolina
     Chapel Hill, NC
     Paul_Jones@unc.edu
 Self-determination for Kernow, Alba, Cymru, Eire, Mannin, and Breizh
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SKIPPER%MEDCOLPA.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 28 Sep 92 19:43:39 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Problem with valid??? address...
Newsgroups: bit.listserv.pmdf-l

> Hope someone on the list can either answer this question or at least
> point me in the right direction.  I received a message from one of
> my users regarding a mail message that he received but was NOT able
> to reply to it successfully.  I have include excerpts from the message
> within this request.  Obviously, someone don't like the RETURN address.
> I can see that it is a "mess" but am not familiar enough with mail
> standards to know if it is legal or not.  Any help would be appreciated
> with this.

> Batch SMTP transaction log follows:
>
> 220 PUCC.PRINCETON.EDU Columbia MAILER R2.09 ptf000 BSMTP service ready.
> 050 HELO MEDCOLPA.BITNET
> 250 PUCC.PRINCETON.EDU Hello MEDCOLPA.BITNET
> 050 TICK 0001
> 250 0001 ... that's the ticket.
> 050 MAIL FROM:<HOFFMAN@MEDCOLPA.BITNET>
> 250 <HOFFMAN@MEDCOLPA.BITNET>... sender OK.
> 050-RCPT TO:</PN=DALE.A.BEGLEY/DD.ID=SSW.DABEGLEY/PRMD=UPJOHN/ADMD=TELEMAIL/C=
   US
> 050 /@sp
> 553 Mailbox syntax error.
> 050 rint.com>

Looks like your user has run up against the line length limit in BSMTP.  There
have been numerous discussions of this topic in the past.  If you wish, I can
dig one or two of them out of the archives for you.  The "work around" requires
coordination/cooperation between you and PUCC: you must agree upon a wrapping
convention and both do whatever is necessary to implement it.

If you are connected to the Internet, which I suspect you are not, then I'd
advise your user to route his mail directlyu to sprint.com via the Internet and
not through BITNET.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"dan@innosoft.com"
X-VMS-Cc: IN%"info-pmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 30 Sep 92 18:47:21 +1000
Comments:     Warning -- original Sender: tag was
              CHRIS@UCSVC.UCS.UNIMELB.EDU.AU
From:         C.Chaundy@ITS.UNIMELB.EDU.AU
Subject:      Problems with PMDF-FAX V4.1-12
Newsgroups: bit.listserv.pmdf-l

Dan,

I am trying to get PMDF-FAX V4.1-12 going with a WorldPort 2496 modem and
I am running into trouble.  I have tried using it in both 19200bps mode
and 9600bps mode.  Neither work but the results are different.  With
19200bps, I get some junk (short sheet of all white or all black paper)
on the fax machine I am using to test it and the following log entries:

29-SEP-1992 21:25:08 g3_to_fax    212153212508 A 2 SYSTEM@muwayb.ucs.unimelb.edu
   .au
 347-4803 CED-212508 DIS-212508 CFR-212508 CO-212508 DCN-212508
29-SEP-1992 21:31:03 g3_to_fax    212801213102 A 2 SYSTEM@muwayb.ucs.unimelb.edu
   .au
 347-4803 CED-213102 DIS-213102 CFR-213102 CO-213102 UN-213102 AC-213103
29-SEP-1992 22:32:13 g3_to_fax    222857223213 A 2 SYSTEM@muwayb.ucs.unimelb.edu
   .au
 347-4803 CED-223213 DIS-223213 CFR-223213 CO-223213 UN-223213 AC-223213

With 9600bps, I do get a cover page, but then a short sheet of all white
paper and no body of my mail and the following log entries:

30-SEP-1992 13:32:42 g3_to_fax    132509133242 W 2 SYSTEM@muwayb.ucs.unimelb.edu
   .au
 347-4803 CED-132636 DIS-132636 CFR-132636 CO-132636 MCF-132636 DCN-133242
30-SEP-1992 14:32:30 g3_to_fax    142510143227 W 2 SYSTEM@muwayb.ucs.unimelb.edu
   .au
 347-4803 CED-142637 DIS-142637 CFR-142637 CO-142637 MCF-142637 DCN-143228

In both cases, the message stays queued, but since our fax machine is left
in an 'ERROR IN COM. E46' state (whatever that is), I have deleted the
message to remain popular with other staff using the fax machine.  I reset
the fax modem between trying these different approaches and made sure I
could talk to the modem at the right speed (2400 for 19200bps).  The modem
is connected directly to a DHV11 in a MicroVAX II (don't laugh).

I am also trying to use the same modem for receiving faxes, and each time
the batch job that sends a fax grabs the modem line and returns it to the
detached fax receive job, this seems to open another file in the DATA_TO_BITMAP
queue area but it does not close/delete the previous file that it had open.

Where should I go from here?

Thanks, Chris Chaundy (Technical Manager, Networks)

Information Technology Services, Thomas Cherry Building,
The University of Melbourne, Parkville, Victoria 3052 Australia
Phone:    +61 3 344 7045                Fax:   +61 3 347 4803
Internet: C.Chaundy@its.unimelb.EDU.AU  (X.121 505233430003)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 28 Sep 92 10:13:54 GMT
From:         alistair@MYRDDN.MITS.COM.AU
Subject:      Summary: Mail system to use with PathWorks
Newsgroups: bit.listserv.pmdf-l

In article <1992Sep9.214100.3556@mits.com.au>,
alistair@mits.com.au (me) writes:
> We are currently in the process of connecting all our PC's to the
> network using PathWorks, and I am trying to determine the most
> appropriate mail system to put in place.  It must be able to integrate
> with VMS Mail.
>
> The possibilities seem to be:
>
> 1.    The unsupported mail client.  This is a DOS application and
>       most of our users use Windows, so this is a bit clunky.
>
> 2.    Microsoft Mail as licensed with MS Office.  Has anyone
>       integrated this with PMDF?
>
> 3.    DEC's Mailworks.

Two mail systems were reported in responses:

        DEC MAILworks
        WordPerfect Mail

The person who is using WordPerfect Mail is quite happy with it.  We
are moving to MS Office, so aren't interested.

Most of the responses were for MailWorks, and most people seem to be
quite happy with it.  One person criticised the interface (buttons not
working, menu items not being updated), and the mail editor.

There were no responses in relation to MS Mail, so I'll be
investigating that further myself.

Thanks to:
        Murray  Penno
        Mark Strawcutter
        Tom Hayes
        Mitch Russell
        Carl Makin
        Kevin Carosso
        Tom Hayes
        Ta Fuh Chiam
        Laura Halliday
        Peter Whisker

for their help.

If anyone would like more information, I am quite happy to mail (or
post) it out.

Thanks,

Alistair Grant

Internet:     alistair@mits.com.au
Alternate:    alistair%mits.com.au@ucsvc.ucs.unimelb.edu.au
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: tkslen@ubvmsb.cc.buffalo.edu (Lenny Miceli)
Newsgroups: bit.listserv.pmdf-l
Subject: REPOST (for lack of any answer) Problems with % addressing.
Date: 5 Oct 92 20:04:00 GMT
Organization: University at Buffalo
News-Software: VAX/VMS VNEWS 1.41

Every so often I find a mail message in my local queue addressed to:

user%node  where "node" is greater than seven characters
(e.g. joe%abcdefgh)
   or
user%node.decnet  where "node" is less than seven characters
(e.g. joe%abc.decnet)

I know addressing like this is frowned upon, but since pmdf will still accept
it I feel this problem should be resolved.  Reading the manual tells me that
if pmdf can't rewrite the address then it will treat the address as
user%node@localhost.  The only problem with this is, if "node" is not a valid
decnet nodename then vms can give strange error messages.  For example,

$ set ho node.decnet
%RMS-F-SYN, file specification syntax error
$ set host s.s
%RMS-F-SYN, file specification syntax error
$ set ho abcdefg
%SYSTEM-F-NOSUCHNODE, remote node is unknown
$ set ho abcdefgh
%RMS-F-NOD, error in node name

When I look at one of the L_MASTER.LOG files I find the following error
when trying to deliver either style of nodename address"

%MAIL-E-LOGLINK, error creating network link to node ABC.DECNET
-SYSTEM-F-IVDEVNAM, invalid device name
or
%MAIL-E-LOGLINK, error creating network link to node ABCDEFGH
-SYSTEM-F-IVDEVNAM, invalid device name

As you can see, mail thinks these wierd addresses are a device name.
Is there anyway pmdf can check the validity of the nodename?

Thanks,
  Lenny Miceli
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 2 Oct 92 08:13:49 GMT
From:         Keith Wolters <KWOLTERS@LUCY.WELLESLEY.EDU>
Subject:      PMDF on a cluster
Newsgroups: bit.listserv.pmdf-l

To: IPMDF@YMIR.CLAREMONT.EDU
X-VMS-To: NET::"IPMDF@YMIR.CLAREMONT.EDU"

Hi.  I apologize if this is a stupid question, but
What special considerations (if any) need to be
taken when running PMDF on a cluster.  We have
been running V3.2 on a single machine for a
while and are now setting up a cluster.  I did
not see anything in the System Manager's Guide
discussing it.

Keith Wolters
System Manager
Wellesley College
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir.claremont.edu"
X-VMS-Cc: PETER
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 5 Oct 92 08:29:14 +0100
From:         PETER@EMBL-HAMBURG.DE
Subject:      switching master_debug on and off
Newsgroups: bit.listserv.pmdf-l

Hi!

Because I'm having trouble with sending mails to some Danish nodes from
Germany, I put master_debug on the appropriate channel to get more info.
It tells me what I want. Perfect!

I need this from "time to time" but not permanently:

1. Is it not possible to have ! on a channel line act as a delimiter?
   I thought it would save me from my own one-hand typing if I left the
   tag on the end of the line and commented it off..

2. Is there a way of switching master_debug on and off for an SMTP Channel
   (MTCP_Local) without CNBUILD and INSTALL twice - especially on a cluster
   where only one node is handling the channel anyway and where I want it
   just long enough to monitor one message?

regards

Peter Bendall
European Molecular Biology Laboratory,
Hamburg Outstation.

 Date:      5-OCT-1992 08:19:35.30
 From:     Peter Bendall        : WIN-Mail        PSI%(0262)45050150057::PETER
 Dept:     Computer Group       :
 Tel:      +49  40 - 899 02 133 : Internet        Peter@EMBL-Hamburg.de
 FAX:      +49  40 - 899 02 149 : EAN-Mail        Peter@Hamburg.embl.dbp.de
                                :       (S=Peter;OU=Hamburg;P=embl;A=dbp;C=de)
----.------------------------------------------------------------------.----.
|    |             This space intentionally left blank !                |    |
`----`------------------------------------------------------------------'----'
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"BAJGOT@adler.mec.mass.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 2 Oct 92 02:50:10 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: listserv error in send/list
Newsgroups: bit.listserv.pmdf-l

> User get the following message when using the listserv on my node:
>
> Subject: Errors in MAILSERV command processing
>
> You are not authorized to obtain the contents of list MCET-PHYSICS
> Use the HELP command to get a list of legal MAILSERV commands.

By default MAILSERV restricts the use of the SEND/LIST command to prevent
just anyone from obtaining the list membership.  Ned posted back a few
weeks ago documentation on how to change these defaults.  If you wish I
can send you a copy of that documentation.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Autoforwarded: false
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Importance: normal
Priority: non-urgent
Sensitivity: Private
UA-content-id: 116A32AE2500
X-Hop-count: 1
Date:         Tue, 6 Oct 92 22:13:05 GMT
From:         "Steven L. Jobes" <jobes@MAYO.EDU>
Subject:      RE: Internet mail address in RFC 822 header
Newsgroups: bit.listserv.pmdf-l

>> If the
>> sender hasn't set a personal name, his Internet mail address may appear in
>> the
>> From field but, typically, it can't be found anywhere in the PROFS header or
>> the attached RFC 822 header.
>>
>> Is it possible to configure PMDF so that the sender's Internet mail address
>> appears in the RFC 822 header?

> This question is somewhat nonsensical. The sender's address appears in the
> RFC822 header by definition. PMDF-MR converts this information into Message
> Router header information. Any header information that remains after
> conversion
> is placed in a separate text attachment. I believe that this attachment is
> what
> you're calling the "attached RFC 822 header". It isn't the RFC 822 header and
> it isn't supposed to be the RFC 822 header -- it is only the unconverted
> remnants of the original header.
>
> You can force preservation of the entire RFC 822 header if you set the
> DELETE_HEADERS option to 0 in the MR_LOCAL_OPTIONS file. Alternately, you
> could
> modify the TO_MR.TXT rules so that the entire address is placed in the free
> form name (it sounds like this, at least, is preserved). We have also added
> some facilities to PMDF V4.2 to make PMDF-MR do the same sort of substitutions
> MRP does now, but of course we also insert the original addresses into the
> message text so they aren't lost.

Ned understood the question correctly, my nonsensical phraseology
notwithstanding.  The context is messages from smtp to OfficeVision though PMDF
and MRP.  Stated more correctly then, is it possible to configure PMDF so that
the sender's address appears in the separate text attachment containing the
unconverted remnants of the original header?

Setting the DELETE_HEADERS option to 0 in the MR_LOCAL_OPTION file, as Ned
suggested, solved the problem quite nicely.  Thanks, Ned.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@innosoft.com"
X-VMS-Cc: AE
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 30 Sep 92 12:03:49 -0300
From:         Aidan Evans <AE@AC.DAL.CA>
Subject:      MAILSERV mailing list distribution file format
Newsgroups: bit.listserv.pmdf-l

  The PMDF System Manager's Guide (May 1992) says in 11.6.2.3, the first
paragraph (page 11-16) "the mailing list distribution file has the same format
as the alias file, see also section 3.3".  It doesn't seem that this can be
right because the alias file format in 3.3.2 on page 3-58 is

        alias: a1,a2,...,am

and by observation the mailing list distribution file format is

        abc@def (subscribed by ...)

This is a minor quibble, but I discovered the discrepancy while I was trying
to figure out how far the mailing list distribution file format can be
extended from the observed form.
  I have a user with a mailing list who would like people who do a SEND/LIST
to see the real names of subscribers to the list as well as their addresses.
Is this possible?  I have tried

        SUBSCRIBE listname xxx (comment)
        SUBSCRIBE listname "something" <xxx@yyy>

and these show up in the file as

        XXX (COMMENT) (subscribed by ...)
        "something" <XXX@YYY> (subscribed by ...)

I guess what I'm really asking is, when the SUBSCRIBE documentation says

        SUBSCRIBE list-name [address]

can "address" be anything that's allowed on an RFC-822 "To:" line or a liberal
subset thereof?

Aidan Evans (AE@AC.Dal.CA), Computer Facilities & Operations, University
Computing & Information Services, Dalhousie University, Halifax, N.S., Canada
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"jobes@mayo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 28 Sep 92 01:24:16 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Internet mail address in RFC 822 header
Newsgroups: bit.listserv.pmdf-l

> We use PMDF and PMDF-MR to interface smtp to Message Router which integrates
> All-in-1 IOS, All-in-1 Mail, OfficeVision (PROFS) via MRP, and VMS Mail via
> MRGATE.  It works very well.  PMDF has given OfficeVision users access to the
> Internet which they lacked otherwise.  The addressing channel allows them to
> send messages to Internet mail addresses not registered in Message Router's
> DDS.  MRP V1.2 allows them to receive messages from unregistered addresses,
> although such messages will be unrepliable (they're from userid MRP).  If the
> sender hasn't set a personal name, his Internet mail address may appear in the
> From field but, typically, it can't be found anywhere in the PROFS header or
> the attached RFC 822 header.

> Is it possible to configure PMDF so that the sender's Internet mail address
> appears in the RFC 822 header?

This question is somewhat nonsensical. The sender's address appears in the
RFC822 header by definition. PMDF-MR converts this information into Message
Router header information. Any header information that remains after conversion
is placed in a separate text attachment. I believe that this attachment is what
you're calling the "attached RFC 822 header". It isn't the RFC 822 header and
it isn't supposed to be the RFC 822 header -- it is only the unconverted
remnants of the original header.

You are losing the useful information out of the Message Router header because
of the silly DDS requirements. It is definitely an improvement for MRP to
deliver messages from unregistered users, but why they could not take the next
step and put the original addresses into the message text eludes me.

You can force preservation of the entire RFC 822 header if you set the
DELETE_HEADERS option to 0 in the MR_LOCAL_OPTIONS file. Alternately, you could
modify the TO_MR.TXT rules so that the entire address is placed in the free
form name (it sounds like this, at least, is preserved). We have also added
some facilities to PMDF V4.2 to make PMDF-MR do the same sort of substitutions
MRP does now, but of course we also insert the original addresses into the
message text so they aren't lost.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU