HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"D.Nash@utexas.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 30 Aug 92 21:14:40 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Reprocessing channel
X-To:         D.Nash@utexas.edu, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

There's no explanation of the reprocessing channel largely because there's
very little to explain. You add a channel called "reprocess" to your
configuration. You can assign it whatever official host name you like.
The expandlimit keyword then uses this channel directly and automatically.
There is no need to do anything else.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DMPM%DUKEMC.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 29 Aug 92 08:51:40 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: From, relpy_to, sender addresses?
X-To:         DMPM@DUKEMC, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Message bounces don't go to the Sender: (if they do something is seriously
busted), they go to the envelope From: address (what you normally see in a
Return-Path:). PMDF SEND does not provide any way at present to set this
field. We plan to address this in the future, although there are some
fairly compelling reasons for not letting users blithly specify this
address. Security considerations aside, you can generate some really nasty
loops very easily if you use envelope addresses carelessly.

                                Ned
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:         Fri, 4 Sep 92 09:47:40 GMT
From:         Jeremy Begg <JEREMY@VSM.COM.AU>
Subject:      RE: Erroneous output from CONFIGURE.COM
Newsgroups: bit.listserv.pmdf-l

>There is no problem with CONFIGURE, per se, but rather with how you answered
>the questions.  The host name which is associated with the local (l) channel
>is that given in response to the question "Official local host name".  No
>rewrite rule is generated for this host: it is assumed to have been a host name
>which was given earlier in the configuration query/response session.  Ned just
>went ahead and added some additional DCL to CONFIGURE.COM to support what you
>did.

That makes sense, I told it the official local host name was r.s.g.a, not
SERF.r.s.g.a which was the default response.  Although this does mean I
have mis-understodd how the rewrite rules and the channel blocks interact.

>> But when I tried to send a message to a user on PAPER, the message was
>> encoded using BASE64 and was not readable:
>
>This was a bug in the interaction between linelength and charset7 which was
>fixed early on in 4.1 but your 4.1-2 tape pre-dates that fix.  The mail you
>sent must have had some long lines (> 255 characters) and PMDF went ahead and
>wrapped the lines but also encoded them when that wasn't necessary.

Actually, no.  I just did this:
$ MAIL
MAIL> send
To:   in%"sysprgg@paper"
Subj: Test mail to paper
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
This is a short test message to paper.
^Z
MAIL>

>
>Fortunately, there is a simple work around: remove the "charset7 us-ascii" from
>your d and l channels.  It's superfluous anyhow since charset7 us-ascii is the
>default.  Removing it will, however, remedy the problem.

Didn't work.  I removed the "charset7 us-ascii" without success, and then
also the "charset8 iso-8859-1" and that didn't help either.

Regards,

        Jeremy Begg

  +----------------------------------------------------------+
  | VSM Software Services,  |  E-Mail:  jeremy@vsm.com.au    |
  | P.O.Box 801, Unley,     |   Phone:  +61 8 4145074 (pager)|
  | South Australia 5061    |     FAX:  +61 8 3734911        |
  +----------------------------------------------------------+
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: IPMDF,GHC
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 25 Aug 92 20:52:35 GMT
From:         Gerson H Cohen <GHC@VGER.NIDDK.NIH.GOV>
Subject:      RE: Problem with personal aliases
X-To:         NED@INNOSOFT.COM
X-cc:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Ned,

    I think thast you're hitting me pretty hard on this one.
While it may be documented that pmdf test is not appropriate
to use for personal aliases, I didn't know and stepped into
it.  It did seem reasonable - I'm sorry!

    I am not responsible for the condition of the miriad of
mishappen sendmails in the world.  Their purpose is just to
haunt us all.

    As for:

> Finally, I don't know what you expected to get, but this is the expected
> result when you use a persnoal alias that is marked private and noexpand.
> If you want the alias to expand into the real address just mark it expand
> and it will. If you want it to expand into an alias other people can use
> mark it public.

Again I have to plead ignorance.  I had to search for a while
[for the manual as well as for the answer] to understand what you
were saying.  I note that I could only use the resultant address
[when I used expand] if I set transport to in%.  I couldn't come
up with any suitable combination of quotes to get the address through.
Is that correct?

Gerson

-
Dr Gerson H Cohen
National Institutes of Health
Bldg 2, Room 312
Bethesda, MD  20892
'Phone: (301)496-4295
Internet: ghc@vger.niddk.nih.gov
BITNet:   ghc@nihklmb
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ECF_STBO%JHUVMS.BITNET@ymir.claremont.edu"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 29 Aug 92 10:25:22 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: postmaster bounces - 4.1-10
X-To:         ECF_STBO@JHUVMS, info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

> I would recommend that people on bitnet with a heavy mail load install
> bn_master and bn_gateway /open/head/shared. Here these images are invoked
> hundreds of times a day. I have also streamlined task_server.com by adding a
> set nover and letting all the logfile information just go into the single
> process log file. If there is a problem, we can always go back to the old
> one. Wirth the one shipped there are way too many files created, with way too
> much data in them for normal operation. Our [log] directory was getting up to
> 10,000 blocks w/ hundreds of files!

We've considered adding some things to PMDF to reduce (or eliminate) the normal
level of logging for high-traffic sites.  The sorts of things you've done
would be included in that.  About the only drawback is tracking things down
when a problem occurs.  We're thinking about the best way to reduce logging
with the least adverse impact to problem-tracking.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: INFO-PMDF@YMIR.CLAREMONT.EDU
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 27 Aug 92 18:36:48 GMT
From:         "Shawn Allin - Alcan KRDC Computer Services"
              <ACCESS@KRDC.INT.ALCAN.CA>
Subject:      Can I set up a form of directory service (ala X.500 or WHOIS) in
              PMDF?
X-To:         INFO-PMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Date sent:  27-AUG-1992 12:13:45

     Hi,

Now that we have a number of widely disparate mail systems connected with
PMDF-glue, (CC:mail, TCP, VMS...) my management would like me to set up a
lookup service for usernames at the various locations.  Can this be done
with PMDF in a non-interactive method?  I say non-interactive, because
something like WHOIS would require (I assume) a full-time link and the
transport to be supported.  We have a variety of periodic Phonenet, UUCP,
etc connections here.  So we'd like to set something up so that you send a
message to a MAILSERV-like address and it sends the lookup results back
to the user via mail.
Has anyone done this?  Is this a FAQ?

     Thanks,

     Shawn Allin
     Alcan International Ltd.,
     P.O. Box 8400,
     Kingston, Ont.,
     Canada  K7L 5L9
     (613) 541-2178

     ACCESS@KRDC.INT.Alcan.CA
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 2 Sep 92 04:38:24 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject:      Use of mail/prot=deliver_mailshr
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

A long time ago I wrote a procedure to send mail using PMDF
It uses the format:

$ define/job pmdf_from "soandso"
$ mail/prot=deliver_mailshr/subj="test" t. "in%""dmpm@dukemc"""

I am not sure why this is so.

One thing I do notice is that rewrite rules behave differently.
It appears that mail sent with above is not treated as from the
local channel.  If not, what is its channel?
Reason I say this is I have some rules that have

$Nl

on them so that they are not used when from the local channel.
If I send the mail as above these rules are used.
If I do not use the /prot bit, the rules are not used.

One reason for using the above, is that the sender field is what
I define PMDF_FROM to be.  If I simply send it with

mail/subj="test" t. "in%""dmpm@dukemc"""

The sender field is the username it was sent with and not the logical
PMDF_FROM -- this causes problems with what I am doing.

Does this all make sense?

-Jim

P.s.  I have tried using PMDF SEND and have same problem with sender field.

P.s.s.  What I am trying to do is send mail on behalf of someone and set
        the return address to go to them.  If someone has a better way I
        would love to hear it.  Thanks.

   =======================================================================
      James D. Dryfoos -- Postmaster    |  dmpm@mc.duke.edu
      Duke University Medical Center    |  dmpm@dukemc.bitnet
      Box 2914 DUMC                     |  (919) 684-6421 - office
      Durham, NC 27710 Earth            |  (919) 684-8675 - fax
   =======================================================================

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 28 Aug 92 22:08:03 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject:      Suggestion for DELIVER
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

I would like to use DELIVER to file certain message.
Problem I have is that we do a lot of MAIL-11 mail that we do not
want to go through PMDF.  When mail gets processed by DELIVER and
even if the rule says just put it in the NEWMAIL folder, it ends
up with the in% inducer on the front.  This means when I go to reply to it,
it goes through PMDF when I wish it would not.

All I am trying to feel out is, if an option that says do not modify
the message in any way (i.e. do not add the in% to the from address)
and just place it in NEWMAIL folder would be possible.


Thanks,

Jim
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.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 29 Aug 92 02:11:46 GMT
From:         "L. Thomas Skipper, MCP VAX Systems Manager" <SKIPPER@MEDCOLPA>
Subject:      PMDF 4.1 L Channel error message (bad prolog??)
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

The following error information was noticed in the the MAIL$BATCH queue
earlier this week; however, mail is currently coming and going without
any problem (As far as I can tell).  Whatever the problem was seems to
have corrected itself.  BUT, my curiosity has been peaked.  Without
making a major issue out of this, what type of situtations could happen
to cause this message?  I do NOT have debug on the L channel line so
the output from that is not available.

All activity appears to be normal and NO user has had problems gaining
authorization from the System UAF file.

Batch queue MAIL$BATCH, on ERNIE::

  Jobname         Username     Entry          Status
  -------         --------     -----          ------
  PMDF delivery   SYSTEM         456          Holding until 28-AUG-1992 17:02
    File: _ERNIE$DUA0:[PMDF.V41.EXE]POST.COM;3
  PMDF message bouncer
                  SYSTEM         409          Holding until 29-AUG-1992 00:30
    File: _ERNIE$DUA0:[PMDF.V41.EXE]RETURN.COM;3
  PMDF channel L master
                  SYSTEM          87          Retained on error
    %LOGIN-F-FILEACC, error accessing system authorization file
    -RMS-F-PLG, error detected in file's prolog (reconstruct file)
    File: _ERNIE$DUA0:[PMDF.V41.EXE]MASTER.COM;3


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
L. Thomas Skipper (Tom)                             M     M   CCCCCC  PPPPPPP
VAX Systems & Networking Manager                    MM   MM  C        P      P
Medical College of Pennsylvania                     M M M M  C        P      P
College Computer Center                             M  M  M  C        PPPPPPP
2900 Queen Lane                                     M     M  C        P
Philadelphia, Pennsylvania 19129                    M     M   CCCCCC  P

BITNET:  SKIPPER@MEDCOLPA  Internet: SKIPPER@SINGER.ASRI.EDU
PHONE:   (215)991-8180          -OR- SKIPPER%MEDCOLPA.BITNET@PUCC.PRINCETON.EDU
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
From: khatri@PCMAIL.INRE.ASU.EDU
Newsgroups: bit.listserv.pmdf-l
Subject: Aliasing
Date: 26 Aug 92 14:56:00 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Encoding: 23 TEXT
X-Mailer: Network Courier V2.1b
X-To:         CW-EMAIL%TECMTYVM@CUNYVM.CUNY.EDU, PMDF-L%IRLEARN@CUNYVM.CUNY.EDU


We've acquired PMDF v4.1 and need to make some decisions concerning
mailbox aliases before implementing a campus-wide postoffice.

We're planning to have a pseudo-domain ASU.EDU and a pseudo-node ASU (for
BITnet) for the entire university.

We're thinking about automatically assigning each person with an e-mail
account an Internet alias, e.g., Shah_Khatri.  Should we use periods instead
of underscores?  What if we have two people with the same name?  Do we use
middle names or numbers to distinguish between them?

Also, we don't know if we should also automatically assign a BITnet alias,
e.g., IDSAK.  There are some advantages of having only one alias for both
Internet and BITnet, e.g., SKhatri, but we'd like our aliases to be
descriptive and that's not always possible with 8 characters.

We'd be much obliged if you made any comments regarding this subject.  Thank
you for your support.

  Shahjehan Khatri
  Khatri@PCMAIL.INRE.ASU.EDU
  IDSAK@ASUACAD
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: rickm
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 25 Aug 92 23:51:31 GMT
From:         Rick Millhollin <RICKM@OREGON.UOREGON.EDU>
Subject:      PhoneNet Channel Problem
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

One of our systems is the slave end of a PhoneNet channel, and since I upgraded
it to PMDF V4.1 this past weekend, the channel has not worked.  The slave log
contains a bunch of messages like:

25-AUG-92  10:14:10: Timeout on acknowledgement read, retransmitting

The PMDF.CNF stuff related to this channel and P_OPTIONS file are the same, and
I can't find anything different to explain the problem.  The other end is still
PMDF V4.0.  Can anybody help me with this?  Thanks...
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: root@se
Errors-to: epmdf@YMIR.BITNET
Organization: Alcatel Bell, Antwerpen, Belgium
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"alcbel-list-pmdf@alcbel.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.pmdf-l
Date:         Fri, 28 Aug 92 22:10:19 GMT
Reply-To:     gdha@se.alcbel.be
Comments:     Warning -- original Sender: tag was root@SE.ALCBEL.BE
From:         Gratien D'haese <gdha@SE.ALCBEL.BE>
Subject:      How to rewrite UUCP bang style addresses
X-To:         alcbel-list-pmdf@alcbel.UUCP



The problem I have with UUCP style addresses is the following:
My PMDF conf appends the localhostname "se" to an UUCP address, e.g. "b!a". I
 would rather
rewrite such an address to something like "b!a@alcbel" instead of "b!a@se".
That's all.
--
  _______               Gratien D'haese    Switching Systems Division  se121
  \     /Alcatel                          F. Wellesplein 1, B-2018 Antwerpen
   \   /  Bell          e-mail: gdha@se.alcbel.be    Phone: (32) 3 240 94 51
    \/ Telephone                gdha@alcbel.be       Fax:   (32) 3 240 99 50
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"JEREMY@vsm.com.au"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 4 Sep 92 08:47:38 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Erroneous output from CONFIGURE.COM
Newsgroups: bit.listserv.pmdf-l

> I recently installed PMDF V4.1-2 and used the CONFIGURE.COM procedure to
> generate the initial configuration.  I have found two problems with it so
> far, which other people might like to know about.
>
> 1) The local host information didn't work.  Here's part of CMDF.CNF:
>
> !
> ! Rewrite rules for the local host/VAXcluster
> !
> SERF                            $U@r.s.g.a
> SERF.r.s.g.a                    $U@r.s.g.a
> WKVA                            $U@r.s.g.a
> WKVA.r.s.g.a                    $U@r.s.g.a
> WKVB                            $U@r.s.g.a
> WKVB.r.s.g.a                    $U@r.s.g.a
> WKVC                            $U@r.s.g.a
> WKVC.r.s.g.a                    $U@r.s.g.a
> r.s.g.a                         $U@r.s.g.a
>
> l nox_env_to defragment charset7 us-ascii charset8 iso-8859-1
> r.s.g.a
>
> The "r.s.g.a" rule was not generated by CONFIGURE.COM: when I tried to
> send a message to myself on SERF (the node I had just installed PMDF on) it
> resulted in an infinite bounced message loop, which didn't go away until I
> added the "r.s.g.a" rewrite rule.

There is no problem with CONFIGURE, per se, but rather with how you answered
the questions.  The host name which is associated with the local (l) channel
is that given in response to the question "Official local host name".  No
rewrite rule is generated for this host: it is assumed to have been a host name
which was given earlier in the configuration query/response session.  Ned just
went ahead and added some additional DCL to CONFIGURE.COM to support what you
did.

> 2) I  included a few DECnet-mail hosts:
>
> !
> ! Rewrite rules for the D (MAIL-11) channel
> !
> paper                                   $U@paper
> pencil                                  $U@pencil
> ruler                                   $U@ruler
>
> d 733 nox_env_to defragment linelength 255 charset7 us-ascii charset8 iso-8859
   -1
> DECNET-MAIL
> paper                                   paper
> pencil                                  pencil
> ruler                                   ruler
>
> But when I tried to send a message to a user on PAPER, the message was
> encoded using BASE64 and was not readable:

This was a bug in the interaction between linelength and charset7 which was
fixed early on in 4.1 but your 4.1-2 tape pre-dates that fix.  The mail you
sent must have had some long lines (> 255 characters) and PMDF went ahead and
wrapped the lines but also encoded them when that wasn't necessary.

Fortunately, there is a simple work around: remove the "charset7 us-ascii" from
your d and l channels.  It's superfluous anyhow since charset7 us-ascii is the
default.  Removing it will, however, remedy the problem.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Organization: Ascom Tech Ltd. - Corporate Research Div. - Berne - Switzerland
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: list_ipmdf
X-VMS-Cc: wittwer
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 26 Aug 92 08:20:00 +0200
From:         Fritz Wittwer <WITTWER@TECH.ASCOM.CH>
Subject:      vrfy and expn commands
X-To:         LIST_IPMDF@tech.ascom.ch, ~WITTWER@tech.ascom.ch
Newsgroups: bit.listserv.pmdf-l

Hello

A sendmail guru told me sometimes ago, that our pmdf does not support the
commands expn and vrfy correctly.

The vrfy command answers '250 Possible DECnet address not checked.' if he
specifies a decnet address, and this is not the answer he expexted.
Is there a chance that this will change sometime? And what's the meaning of
250, I saw this codes somewhere in an RFC, but i can't remeber the exact
meanings.

He told me to that the expn command didn't work. For me it seems to work,
except the inclusion of the personal name (sendmail seems to do it). Are there
any other differences?

Sorry for this stupid questions, but we have a lot of SUN (and sendmail) users
here, and some of them have an understanding like 'SUN OS is the standard,
anything wich is different violates the standards and should be shut down; if
there are standards wich differ from SUN OS, then the standards ar just wrong'.


Regards
        Fritz

Newsgroups: bit.listserv.pmdf-l
From: stodola@orion.fccc.edu (Robert K. Stodola)
Subject: Strange forwarding problem.
Organization: Fox Chase Cancer Center
Date: Thu, 3 Sep 1992 16:02:50 GMT

We have a situation where a network alias (J_Blow@fccc.edu) points to Joe's
VMS account (Blow@rm.fccc.edu).  Joe wishes to forward his VMS mail to his Unix
account (J_Blow@xyz.fccc.edu).  Unfortunately, xyz recognizes J_Blow as an
alias which then loops.  We had hoped to fudge the problem by putting a
backslash in the forwarding address on the VAX side.  Unfortunately, putting
in one backslash (set forward "in%""\j_blow@xyz.fccc.edu""") appears to
swallow the backslash, while putting two backslashes causes PMDF to complain
about a bad address (\J_Blow...).

Flames aside (and I recognize that many are deserved in this situation!), if
someone could explain how one might do this in PMDF, I'd be most grateful.
We have some workarounds which may be better anyway, but I'd like to understand
the options.

-- 

stodola@fccc.edu -- Robert K. Stodola (occasionally) speaks for himself.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU