HDTenEightyP/NetNews huggingface dataset:
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: 116B9BD10800
X-Hop-count: 1
Date:         Thu, 19 Nov 92 22:32:05 GMT
From:         "Steven L. Jobes" <jobes@MAYO.EDU>
Subject:      "Illegal host/domain name" errors
Newsgroups: bit.listserv.pmdf-l

This morning, I saw a half dozen inbound messages bounce with "illegal
host/domain name" errors.  All were addressed to user%rocvm@mrp.mayo.edu for
delivery to OfficeVision through PMDF-MR and MRP.  These were legal addresses;
in fact, subsequent attempts to send to the same addresses succeeded.  Section
15.3.7 says that such errors can occur, even with legal addresses, if the
network transport is unable to accept the message.  The VAX's pagefile space
was critically low during this time.  Since then, I've added another pagefile
and rebooted.  Do you think the pagefile problem explains these failed
deliveries?  Thank you.
..............................................................................
Steven L. Jobes                                                 jobes@mayo.edu
Network Management, Mayo Foundation, Rochester, MN 55905          507-284-4047
..............................................................................

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,ipmdf@ymir.bitnet"
X-VMS-Cc: GOMIDE
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 19 Nov 92 13:56:39 GMT
Reply-To:     gomide@BRFAPQ.BITNET
Comments:     @FAPQ.FAPESP.BR - @FAPQ%FPSP.HEPNET - @BRFAPQ.BITNET - .BR
              gateway
Comments:     Warning -- original Sender: tag was GOMIDE@BRFAPQ
From:         gomide@FPSP.FAPESP.BR
Subject: RE: PMDF 3.2 - job enqueue error
Newsgroups: bit.listserv.pmdf-l

>
> Date: 18 Nov 1992 12:50:25 -0700 (PDT)
> From: "Daniel C. Newman" <DAN@INNOSOFT.COM>
>
> ...
>        $ STOP/QUEUE/NEXT MAIL$BATCH
>        $ MAIL/SUBJECT="Test 1" SYS$LOGIN:LOGIN.COM IN%SYSTEM
>        $ MAIL/SUBJECT="Test 2" SYS$LOGIN:LOGIN.COM IN%SYSTEM
>        $ SHOW QUEUE/FULL/ALL MAIL$BATCH
>
> Do you see one or two pending L channel jobs in the MAIL$BATCH queue?
>
>      My guess is that the superfluous pending jobs are being created by PMDF
> channel programs which are running under an account which lacks either SYSPRV
> or CMKRNL or both and is therefore following (2) above.  To isolate this
> problem, you'll have to determine which all accounts may be running PMDF
> channels and what privileges that they have.  (For instance, do you use
> DECnet, PhoneNet, or PSI channels and if so does your PMDF server account
> lack these privileges?)
>
> Dan

Thank you for answering. It follows that your guess is correct. I
tested the job enqueue with the above script, and no L channel job was
generated. I have several decnet, phonenet, psi and uucp channels,
with a good deal of activity on them. The account PMDF lacked sysprv
and cmkrnl privileges - I have just granted those privileges to the
account PMDF.

Thank you,
--
Alberto Courrege Gomide | Fundacao de Amparo `a Pesquisa - (11)831-3357
Software Supervisor     | Rua Pio XI, 1500 - CEP 05468-901 - Sao Paulo
<gomide@fapq.fapesp.br> | FAX (11)261-4167 Telex (11)82014 - Brazil
(ACG8) - .BR Domain Technical Contact. |        [this space for rent]
--
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"S.ROSS@CGNET.COM"
X-VMS-Cc: IN%"ipmdf@INNOSOFT.COM", IN%"service@TGV.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 21 Nov 92 01:02:49 GMT
Reply-To:     Kenneth Adelman <Adelman@TGV.COM>
From:         Kenneth Adelman <adelman@TGV.COM>
Subject:      RE: Multinet TCP/IP parameter settings
Newsgroups: bit.listserv.pmdf-l

> Lately some hosts have been unable to connect to our Multinet TCP/IP
> channel.  Currently the multinet/configure utility shows the
> following parameters:

> SERVER-CONFIG>sho smtp /full
> Service "SMTP":
>         TCP socket (AF_INET,SOCK_STREAM), Port 25
>         Socket Options = SO_KEEPALIVE
>         INIT() = TCP_Init
>         LISTEN() = TCP_Listen
>         CONNECTED() = TCP_Connected
>         SERVICE() = Run_Program
>         Program = "PMDF_ROOT:[EXE]MTCP_SLAVE.EXE"
>         Working Set = 400
>         Max Servers = 2
>         Backlog = 2

> We are interested in increasing the last two, Max Servers and Backlog to
> allow more SMTP slave processes to be running simultaneously and to allow
> more calling machines to be queued while waiting for one of the processes
> already running to finish.

> We have a 9600 bps compressed SLIP line to the internet and we're running
> PMDF 4.1-13 and Multinet 3.0.

> Can anyone recommend appropriate settings for these parameters that allow
> more calls to come in at once?  Is it better to increase Max Servers or
> Backlog or both?

    You really want to increase MAX-SERVERS.

                                                                    Ken
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MAC@gvg34.gvg.tek.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 19 Nov 92 20:38:55 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: ccMail question
Newsgroups: bit.listserv.pmdf-l

> Yes, I had added a ``linelength 80'' to the ccMail channel.  I had
> several complaints about ccMail messages from the VAX appearing as
> attachments that had to be double clicked on to be read.  I attempted
> to resolve the problem before I read the documentation by adding the
> linelength keyword to the ccMail channel.  Then I read that PMDF was
> sending messages with lines longer than 80 characters as attachments
> as part of the normal channel processing.  But of course, I did not go
> back on change my configuration, because it looked like that was the
> default action of the channel anyway.

The problem is that cc:Mail has some limitations on the length of lines in
messages.  So you have two choices: do nothing in which case PMDF has to stuff
the message into a cc:Mail file attachment which doesn't have the line length
limitation, or tell PMDF that there is a line length limitation in which case
PMDF will wrap the lines using the MIME quoted printable encoding.

You may wish to take up with Ned the possibility of having an option or
something for the cc:Mail channel which says to just blindly wrap long lines
rather than resort to a file attachment.  (Ned is away this week at IETF.)

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"  "Daniel C. Newman"
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:         Fri, 20 Nov 92 10:30:47 +1030
From:         Andrew Rutherford <andrewr@ITD.ADELAIDE.EDU.AU>
Subject:      RE: ccMail question
Newsgroups: bit.listserv.pmdf-l
              <01GRC1RSC9TE9AMIDG@INNOSOFT.COM>

In message <01GRC1RSC9TE9AMIDG@INNOSOFT.COM> you write:

+ The problem is that cc:Mail has some limitations on the length of lines in
+ messages.  So you have two choices: do nothing in which case PMDF has to stuf
+ f
+ the message into a cc:Mail file attachment which doesn't have the line length
+ limitation, or tell PMDF that there is a line length limitation in which case
+ PMDF will wrap the lines using the MIME quoted printable encoding.

        This file attachment approacg does create a slight problem -
it creates a file attachment with no name associated with it. This
makes it impossible to associtae a default action with the file. As
such, I have filter I whipped up on the PC that does the
import/export, which looks for a file attachment without a name and
calles it "MAIL.TXT", or .tx1, .tx2, etc, if mail.txt is already
taken. This makes it possible to associate a default action (in most
cases this is fire up Notepad) with the attachment, otherwise you have
to fiddle around (save it as something, then fire up an app manually
to read it).
        I don't use cc:Mail myself, so I (and all the regular cc:Mail
users) might be missing something - is there an easier way of handling
this?
        The real fix, of course, is for Lotus to fix the import/export
routines to handle more than 80 characters, so I don't see this as
Innosoft's problem. After having a godd look at what it's capable of,
including restrictions mentioned in the manual an those not mentioned,
Ned and co. have done remarkably well given the interface they've got
to deal with, IMHO. It's not nice, with things like "No text item can
be larger than 20K" all over the place...

Cya,
        Andrew.

/*
 * Andrew Rutherford                 andrewr@itd.adelaide.edu.au
 * +61 8 228 5669            Real Programmers always confuse Christmas and
 * Room 1060, Adelaide Uni      Halloween because OCT 31 == DEC 25 !
 */
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"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 19 Nov 92 18:01:43 GMT
From:         The PMDF Postmaster <MAC@GVG34.GVG.TEK.COM>
Subject:      RE: ccMail question
Newsgroups: bit.listserv.pmdf-l

>>We are seeing some of the messages that PMDF leaves for ccMail to
>>deliver that contain what looks like some form of line wrapping that
>>uses the ``='' as the continuation character.  There message also
>>appear to have hex quoting for some characters like maybe =20 means
>>a space and maybe =9 means a tab.  I know this is a marginal
>>description of the problem.  I will enclose a part of one of these
>>message at the end of this message.  What is going on?  Any help
>>greatly appreciated.
>
>You're seeing line wrapping which uses the quoted printable MIME
>encoding. The "=xx" means "ASCII character with hex value xx".  You
>see some =20 at the end of lines because PMDF wrapped the line and
>was now afraid that if it left a naked space at the end of the line
>some other mailer would strip it away.  The =9 are tabs.
>
>Send your PMDF.CNF to service@innosoft.com and some sort of
>indication as to how this message originally entered PMDF.  It
>probably came in on some channel with a "linelength" keyword
>specified.

Yes, I had added a ``linelength 80'' to the ccMail channel.  I had
several complaints about ccMail messages from the VAX appearing as
attachments that had to be double clicked on to be read.  I attempted
to resolve the problem before I read the documentation by adding the
linelength keyword to the ccMail channel.  Then I read that PMDF was
sending messages with lines longer than 80 characters as attachments
as part of the normal channel processing.  But of course, I did not go
back on change my configuration, because it looked like that was the
default action of the channel anyway.

So, I have stripped the keyword off the ccMail channel.  I will let
you know if that fixes it.  This has been particularly hard to track
down because we have not seen a pattern in the source addresses of the
mail messages that get the MIME wrapping or in the messages
themselves.  The original source for wrapped messages are from PMDF
machines running 4.0 and 4.1, but these same machines also generate
other messages correctly.  I will send the configuration to service so
they can look at it, but I won't bore the list with the details.  I
really suspect that the problem is resolved with removing the
linelength keyword.

Thanks for the help,

Bill
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SYSMARK@minna.iit.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 23 Nov 92 18:54:30 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Sudden switchover to JNET protocol...
Newsgroups: bit.listserv.pmdf-l

This is a problem caused by a bug in the BN_SLAVE program coupled with your
use of nosendpost on the bit_local channel. The combination of the two
produces an attempt to enqueue a message with no recipients. This is an
illegal condition and causes the BN_SLAVE program to exit. The solution is
to use something weaker than nosendpost; errsendpost would be an excellent
candidate for this.

Note that use of nosendpost in this fashion can cause the silent loss of
any message that has no valid originator or recipient specified. While there
is nothing wrong with this per se it may or may not be a good idea.

The underlying problem here will be corrected in PMDF V4.2.

                                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@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Posting-date: 20 Nov 1992 08:12 -0500 (EST)
Importance: normal
Priority: non-urgent
X-Hop-count: 1
A1-type: MAIL
Date:         Fri, 20 Nov 92 13:50:05 GMT
From:         "Sue Ake (814) 863-2524" <SUE@A1.PSUPEN.PSU.EDU>
Subject:      Errors in MAILSERV command processing
Newsgroups: bit.listserv.pmdf-l


I was using mailserv when it was unsupported in version 4.0.  Now that I've
upgraded to 4.1 and it is supported, I received the following message when I
tried to subscribe to one of my mailing lists:

        Mailing lists are not enabled, command: subscribe inservice-l
        Subsequent commands ignored because of previous error.
        Ignored:
        Use the HELP command to get a list of legal MAILSERV commands.

So, how do "enable" mailing lists in version 4.1?

Sue
------------------------------------------------------------------------------
Susan Ake                                       Internet: SUE@PSUPEN.PSU.EDU
Systems Project Analyst, Computer Services      BITNET:   SUE@PSUPEN
College of Agricultural Sciences                FAX:      (814) 863-7209
The Pennsylvania State University               Voice:    (814) 863-2524
------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"fineberg@wupost.wustl.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 17 Nov 92 06:47:04 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Additional mailing list security
Newsgroups: bit.listserv.pmdf-l

>>With the MAPPINGS file now in PMDF, it is possible to control who add
>>subscribe and unsubscribe users from MAILSERV mailing lists, get copies
>>of the list, etc., but has anyone implemented a system where only a
>>restricted group of users may actually mail to particular lists?
>
> Hmm.  When I read the 4.1 docs it seemed trivial to limit who could post
> to a list, but allowing mailed list ownership didn't seem to be there at
> all.  So what did my denseness ignore?  That is where in the manual is
> the reference to controlling who may add and delete users?

This information did not make it into the printed documentation.  Look in your
on-line docs (4.1-10 or later).  It should be under the MAILSERV documentation.
This additional documentation (complete with crucial typo) was posted to
info-pmd back in September (or thereabouts) by Ned.  Let mek know (anyone)
who wants this information e-mailed to them.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MAHENDRA@Meena.CC.URegina.CA"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 17 Nov 92 03:22:35 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Help needed with setting up the 'd' channel
Newsgroups: bit.listserv.pmdf-l

>    We have a few VAXstations on our LAVC that do not run PMDF. Internet
>    mail to these systems are forwarded by the PMDF host
>    Meena.CC.URegina.CA using the decnet channel as follows:
>
>!
>! Rewrite rules for the D (MAIL-11) channel
>!
>ponna                   $U%ponna@DECNET-MAIL
>regie1                  $U%regie1@DECNET-MAIL
>regie2                  $U%regie2@DECNET-MAIL
>Lang                    $U%Lang@DECNET-MAIL
>
>d 733 nox_env_to header_733
>DECNET-MAIL
>ponna           ponna
>regie1          regie1
>regie2          regie2
>Lang            Lang
>
>    The trouble with this is that on all out-going mail from these
>    systems, the From: field shows up as just user@host (e.g.
>    User@Lang) which is not replyable.
>
>    What we would like to have is
>    the From: address to be User%Lang@Meena.CC.URegina.CA. Please
>    explain how this can be accomplished?

Add $E$F's to each of the rewrite rules so that they only work on forward
pointing envelope addresses.

  ponna                   $E$F$U%ponna@DECNET-MAIL
  regie1                  $E$F$U%regie1@DECNET-MAIL
  regie2                  $E$F$U%regie2@DECNET-MAIL
  Lang                    $E$F$U%Lang@DECNET-MAIL

Then remove the ponna, regie1, regie2, and Lang from the D channel.  Also,
get rid of the header_733 unless you really need that for some reason:

  d 733 nox_env_to
  DECNET-MAIL

The problem with what you had is that for mail passing from, say, PONNA through
your PMDF system to the outside world, the PONNA rewrite rule was being
invoked and rewriting the reverse pointing PONNA addresses to user@ponna
(which is what that rule says to do).  As it turns out, you only need rules
for PONNA, et. al. for inbound mail for those systems at which point you
do want to see the address user@ponna.  And thus the addition of the $E$F to
the rewrite rules for PONNA, et. al.  (so that the rules only fire for
inbound mail for those systems and then only affect envelope addresses).

Dan
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: IN%"service@tgv.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 21 Nov 92 00:29:21 GMT
From:         S.ROSS@CGNET.COM
Subject:      Multinet TCP/IP parameter settings
Newsgroups: bit.listserv.pmdf-l

Lately some hosts have been unable to connect to our Multinet TCP/IP
channel.  Currently the multinet/configure utility shows the
following parameters:

SERVER-CONFIG>sho smtp /full
Service "SMTP":
        TCP socket (AF_INET,SOCK_STREAM), Port 25
        Socket Options = SO_KEEPALIVE
        INIT() = TCP_Init
        LISTEN() = TCP_Listen
        CONNECTED() = TCP_Connected
        SERVICE() = Run_Program
        Program = "PMDF_ROOT:[EXE]MTCP_SLAVE.EXE"
        Working Set = 400
        Max Servers = 2
        Backlog = 2

We are interested in increasing the last two, Max Servers and Backlog to
allow more SMTP slave processes to be running simultaneously and to allow
more calling machines to be queued while waiting for one of the processes
already running to finish.

We have a 9600 bps compressed SLIP line to the internet and we're running
PMDF 4.1-13 and Multinet 3.0.

Can anyone recommend appropriate settings for these parameters that allow
more calls to come in at once?  Is it better to increase Max Servers or
Backlog or both?

Thanks in advance for any recommendations!

Steve Ross
CGNet Services International
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SETH@SPEECH.MIT.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 04:11:06 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Incoming notification From: prefix = SMTP%
Newsgroups: bit.listserv.pmdf-l

>       A while back I posted a note concerning occasional file
> create errors of the following form:
>
> %MAIL-E-SENDERR, error sending to user audiodev@cbgrle.mit.edu at
> -PMDF-E-FCRT, File create error, Pascal status = 2, VMS statuses = 99684 and 0
> -PMDF-I-TEXT, cannot create channel queue entry
>
>       It turned out that we were mixing IN% and SMTP% protocols
> in a given MAIL session. Simply requiring the use of only one
> of these form solved the problem, but in hindsight brings up an
> interesting question.

Yes, you cannot mix these two foreign protocols in a single VMS MAIL session.
Doing so can exercise an RMS bug which DEC doesn't seem interested in fixing
and for which we cannot work around (TGV neither).  You also have to watch
for people who have their mail forwarded to SMTP%"...".

>       Why would all incoming mail on a machine newly updated
> from CMU TCP/IP to Multinet suddenly start using the SMTP prefix
> on ALL incoming Internet mail? I don't seem able to determine the
> cause of this change. As far as I know, it was nothing I did during
> the switch from CMU to TGV code, at least knowingly... :-)

This will happen if you do not configure MultiNet to use PMDF's SMTP
server.  Issue the MultiNet commands

  $ MULTINET CONFIGURE/SERVER
  MultiNet Server Configuration Utility 3.1(30)
  [Reading in symbols from SERVER image MULTINET:SERVER.EXE]
  [Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
  SERVER-CONFIG> SHOW SMTP
    Service     Proto      Port               Action
    -------     -----      ----               ------
    SMTP        TCP        25         Run Program PMDF_ROOT:[EXE]MTCP_SLAVE.EXE

You should be running PMDF_ROO:[EXE]MTCP_SLAVE.EXE as your SMTP server.
My guess is that this is not the case.  If you are running MTCP_SLAVE.EXE,
then check to make sure that this is the case on all cluster members.

Dan
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: MAHENDRA
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 16 Nov 92 08:20:00 -0600
From:         "A. Mahendra Rajah,
              System Manager" <MAHENDRA@MEENA.CC.UREGINA.CA>
Subject:      Help needed with setting up the 'd' channel
Newsgroups: bit.listserv.pmdf-l

Hello all:

    We have a few VAXstations on our LAVC that do not run PMDF. Internet
    mail to these systems are forwarded by the PMDF host
    Meena.CC.URegina.CA using the decnet channel as follows:

!
! Rewrite rules for the D (MAIL-11) channel
!
ponna                   $U%ponna@DECNET-MAIL
regie1                  $U%regie1@DECNET-MAIL
regie2                  $U%regie2@DECNET-MAIL
Lang                    $U%Lang@DECNET-MAIL

d 733 nox_env_to header_733
DECNET-MAIL
ponna           ponna
regie1          regie1
regie2          regie2
Lang            Lang


    The trouble with this is that on all out-going mail from these
    systems, the From: field shows up as just user@host (e.g.
    User@Lang) which is not replyable. What we would like to have is
    the From: address to be User%Lang@Meena.CC.URegina.CA. Please
    explain how this can be accomplished?

    Thanks.

    -- mahendra (A. Mahendra Rajah :: Mahendra @ Meena.CC.URegina.CA)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU