HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.pmdf
Subject: RE: DELIVER query - return message to sender
From: Ned Freed <ned@innosoft.com>
Date: 11 Dec 1992 18:09:38 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Dec 1992 18:09:38 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS75YM2DVM8ZL9MQ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ccvj@misty.latrobe.edu.au"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Check out PMDF_ROOT:[DELIVER]TRIP.COM. This is a sample program that does
precisely what you want, I think.

				Ned
Newsgroups: vmsnet.mail.pmdf
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF V4.1 and Jnet V3.6
From: Eliza Lau <laue@vtcc1.cc.vt.edu>
Date: 16 Dec 1992 14:48:01 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Dec 1992 14:48:01 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSDS4CRVPE8ZLZK9@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"Dan@TOE.TOWSON.EDU"
X-Vms-Cc: IN%"info-pmdf@ymir.claremont.edu",LAUE
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>
> We upgraded to Jnet V3.6 using 3 DNANJE links and 1 BSC/370 link last Friday.
> As Jack Pernice said, the new install does not replace your lmd.com.  Along with
> other user-configurable procedures, they give you a template file and tell you
> to merge your local modifications into it.
>
> For LMD.COM, I just left the Jnet template alone and used the LMD.COM from PMDF
> V4.1.  We've had no problems since then (related to Jnet, that is - but that's
> another story :-).
>
> Dan
>
>    Daniel A. Dinkin
>    Network Services Manager                   BITNET: dan@towsonvx.bitnet
>    IR Academic Computing                    Internet: dan@toe.towson.edu
>    Towson State University                            dan@midget.towson.edu
>    Towson, Maryland 21204                UMSA DECnet: toe::e7opdan
>    (410)830-3320
>
>      Any thoughts in this message are purely random and my employer had
>            nothing to do with them... especially if I was right.
>
What release of JNET did you upgrade from?  We are running JNET V3.4 and
PMDF V4.1-10.  Do I have to switch to the LMD.COM (V3.5) from PMDF 4.1 or
stick with LMD.V34 after upgrading to Jnet V3.6?

------------------------------------------------------------------------------
 Eliza Lau
 Virginia Tech Computing Center                Internet : LAUE@VTCC1.CC.VT.EDU
 1700 Pratt Drive                               Bitnet  : LAUE@VTCC1
 Blacksburg VA 24060                            Voice   : (703) 231-9399
------------------------------------------------------------------------------
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Encrypted mail
Date: 17 Dec 92 16:17:31 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Dec 1992 09:17:31 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSF14T0IEQ90MX6H@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SMITH%NYUMED.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> A couple of years ago I got a program called ENCRYPT from Wesleyan and have
> had it here for a while.  It hasn't been used much until now, but we recently
> had a user who wnated to mail encrypted text and asked if this could be built
> in directly into mail.  ENCRYPT generates mail-like headers, which potentially
> allows decryption on the fly, and might lend itself to incorporation into a
> mail package.
>
> Any thoughts on whether this might be something you would consider for the
> PMDF user agent, or whether other mailers might support encryption (or
> security-enhanced mail, as ENCRYPT calls it).

We have every intention of supporting privacy enhanced mail (PEM) with many of the
frills (message integrity checks, non-repudiation of origin).  However, like
most everyone else, we've been waiting for the PEM working group of the IETF
to come to some sort of closure on their standards work.  This closure now
seems to be nearing and we'll begin looking into adding PEM support to PMDF.

Dan
From: pern@db1.cc.rochester.edu (Jack Pernice)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF V4.1 and Jnet V3.6
Date: 15 Dec 92 00:09:25 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 19:09:25 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSB8L2A2PU8ZKABO@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"D.Nash@utexas.EDU"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


We installed JNET V3.6, and TCPNJE V1.2 (WIN driver) on an 8 node cluster
on 12/12/92.  We're running PMDF V4.1-12.  The JNET V3.6 installation does
not replace LMD.COM.  We're using LMD.COM that came with PMDF and all seems
to be just fine.

We have quite a bit of mail traffic through our system.  If there were any
problems, I think we would have encountered them by now.

----------
Jack Pernice				 BitNet:    PERN@UORDBV
VMS Systems				 InterNet:  pern@db1.cc.rochester.edu
University of Rochester			 Voice:     (716) 275-7160
Rochester, NY  14620
USA
Newsgroups: vmsnet.mail.pmdf
Subject: Max size of PMDF.cnf?
From: s.ross@cgnet.com
Date: 17 Dec 1992 17:48:33 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Dec 1992 17:48:33 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSFIWXNSAQ8WW40U@INNOSOFT.COM>
X-Vms-To: IN%"info-pmdf@innosoft.com"
X-Vms-Cc: KNOVAK
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

PMDF hacker types:

I added a few trivial lines to my PMDF.cnf file yesterday, without putting
in any blank lines, and immediately, I could not send anything through
PMDF using IN% from VMSmail!  The error message is shown below.

We have PMDF 4.1-13 and our PMDF.cnf file is NOT compiled.  The file was
731  lines before I added anything.

Is there a limit to how large PMDF.cnf can be?

It seems like a good idea to compile PMDF.cnf anyway, but I wanted to
check to see if this error is indicative of any other problem.

Has anyone seen this before?


MAIL> se
To:     in%k.novak-ms
%PMDF-E-FOPN, File open error
-PMDF-I-TEXT, no room in pool for alias test-l-expand -- line #6184 in file PMDF
_ALIAS_FILE

MAIL>

Thanks in advance!
Steve Ross
CGNET Services International
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mailserv subscriptions
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 18 Dec 1992 14:01:22 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Dec 1992 14:01:22 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSGPC73MVM90N5A9@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"TIHOR@ACFcluster.NYU.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Huh?

I merely explained one such case where using the Reply-to: instead of the
From: address for automatic list subscriptions will get you into trouble.
I can provide you with more examples of how using the Reply-to: address
can get you into deep trouble.

> A user phil sends mail from pole.nyu.edu his workstation but wants
> all his mail to go towards mail.nyu.edu from which it is redirected.
> The mailer on his workstation does not support forging the From: address.

There is no need to forge the From: address.  He can simple use the command

    SUBSCRIBE <list> <address>

and specify the address to be subscribed.

Dan
Newsgroups: vmsnet.mail.pmdf
From: daven@vx.cis.umn.edu (David Nieters)
Subject: Using customer-supplied routine substitutions
News-Software: VAX/VMS VNEWS 1.41    
Organization: University of Minnesota CIS
Distribution: usa
Date: Tue, 15 Dec 1992 20:17:00 GMT

I am trying to use a customer-supplied routine substitution as described
in section 3.2.4.7.3 on page 3-15 of the 4.1 PMDF managers manual.

I'm able to get my routine called just fine, and I print out the argument,
and what I am returning, but when I try to do a
	PMDF TEST/REWRITE/CONFIG=xxx.cnf
it seems to completely ignore the string that I return and just use
whatever it sent me.  I AM returning a -1 when I want it to do the
substitution.  Has anyone had any success with this?  If so, can I
look at your source?  Or am I doing something obviously wrong?

David Nieters
University of Minnesota
daven@vx.acs.umn.edu
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF V4.1 and Jnet V3.6
From: "Donald L. Nash" <d.nash@utexas.edu>
Date: 14 Dec 1992 16:40:40 -0600 (CST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 16:40:40 -0600 (CST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSB5JLIK0I8ZLBAS@YMIR.CLAREMONT.EDU>
X-Vms-To: in%"info-pmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Now that Jnet V3.6 has hit the streets, has anyone tried it with PMDF V4.1?
Jnet's version of LMD.COM has changed substantially since V3.5, so I'd like
to get some word on if/how well PMDF's LMD.COM works with Jnet V3.6.

I haven't poured over it deeply, but it looks like the new LMD.COM has
support (possibly undocumented, I couldn't find it mentioned in the release
notes), for using an alternate mail delivery procedure.  Hmmm, might be
something handy for PMDF to take advantage of if it becomes officially
acknowlegded by Wingra, since it would mean that PMDF wouldn't have to
replace LMD.COM, and people like me wouldn't have to worry about changes to
LMD.COM every time we upgrade Jnet.

                                Donald L. Nash

Internet:  D.Nash@utexas.edu    The University of Texas System
BITNET:    DON@THENIC           Office of Telecommunication Services
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Help: How to get mail deliver messages for internet nodes?
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 17 Dec 1992 11:46:02 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Dec 1992 11:46:02 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSF6BZ5P5E90MY4Q@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"OPERATOR%WFEB2.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Dan already answered this; I merely want to add a couple of extra points.

If delivery receipts are an unworkable solution, the best we could possibly
do is to inform users when mail leaves the local system. We could implement
this if you think it is useful. However, I must emphasize that this in and
of itself means nothing other than what I said -- just because the message
has left the local system does not mean it has been delivered. It may be
stuck on an intermediate system or it may be stuck on the target host waiting
for final delivery. Messages can sit in queues of this sort for days or weeks
and this happens fairly frequently.

BITNET is actually not materially different in this regard. You do get
notifications as messages move from one intermediate system to the next, and
this is totally impossible to do in the Internet. (Not hard, impossible. It
would require changing the software on around a million machines. Impossible
isn't strong enough, actually.) But BITNET doesn't really give you
notification of final delivery in most cases, especially when a gateway
to the Internet is involved.

In summary, your users were depending on a facility that's really entirely
illusory. Any claim that those messages represent a guarantee of final
delivery is bogus. These users are now faced with reality (not a pretty sight)
and there's precious little you can do to shield them from it.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Mailserv subscriptions
From: Stephen Tihor <tihor@acfcluster.nyu.edu>
Date: 18 Dec 1992 02:23:03 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Dec 1992 02:23:03 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSFV48H64Y90N1J1@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

One of our mailing list maintainers reports that SUBSCRIBE seems to be using
the From: address rather than the Reply-To address.  I can see some logic
for that but I suspect that the latter might be a better choice.   Does the
pseudo-standard specify or is the a clear logic for using the one?
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Adding a worldwide-known "alias" ?
From: "Kevin V. Carosso" <kvc@summer.innosoft.com>
Date: 14 Dec 1992 21:32:51 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 21:32:51 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSBOVOKV368ZLQ4D@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"JLW%PSULIAS.BITNET@ymir.claremont.edu"
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

You've got it mostly right.  Add a rule to PMDF to remap the bogus address to
your official-local-host name, as you said:

        !Currently this rule is in the file:
        psulias.psu.edu $U@psulias.bitnet
        !Should I add this one to do it all?
        lias.psu.edu    $U@psulias.bitnet

The purpose of the rule is to make sure your PMDF recognizes anything with the
other name and delivers it locally.  Without the rule, your PMDF will put it
back out on the network and it will go nowhere.

> What do I need to tell my DNS manager?  "Add an MX record for the address
> 'lias.psu.edu' pointing to the same IP address as 'psulias.psu.edu' currently
> points to" ?

Almost right, except that an MX record does not point at an IP address, it
points at a name. In your case you want it to point at "psulias.psu.edu".

	/Kevin Carosso
	 Innosoft
Newsgroups: vmsnet.mail.pmdf
Subject: Organization:-header and mail sent to host::in%"..."
From: Bob Tinkelman <bob@camb.com>
Date: 12 Dec 1992 18:41:43 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Dec 1992 18:41:43 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS8F3K52MA8WW2OO@INNOSOFT.COM>
X-Vms-To: IN%"info-pmdf"
X-Vms-Cc: TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

We share our Ethernet with another organization.  They sometimes
send Internet mail from their systems by addressing it
	To: OurSystem:in%"..."
I had defined PMDF_ORGANIZATION as a system wide logical, and,
as a result, their mail goes out with our organization name.

I can remove the system wide logical and use sylogin.com to define
PMDF_ORGANIZATION in the process tables instead.  That will result
in no Organization:-header for them.  While that's an improvement,
I was wondering if there was a recommended way to have this header
set depending on the originating DECnet node.
--
Bob Tinkelman <bob@camb.com>
From: kraftjoel@bvc.edu
Newsgroups: vmsnet.mail.pmdf
Subject: Second l channel?
Date: 14 Dec 92 11:12:28 CST
Organization: Buena Vista College, Storm Lake, IA

In order to make mail look "nicer" for our users, we currently use the
"headeromit" keyword on our l channel.  I have recently found the need to have
headers on mail sent to some accounts (most notably the account that receives
mail that is to be posted to news).  I would like to set up an additional
"l" channel that is identical to normal l except that the headers are included
on messages.  I have tried to make a new channel using the MAIL_ prefix name on
the channel, but any delivery on that channel crashes with this error:

%MAIL-E-ERRACTRNS, error activating transport HEADERS
%LIB-E-ACTIMAGE, error activating image $1$DUA0:[SYS2.SYSCOMMON.][SYSLIB]HEADERS
-RMS-E-FNF, file not found

I need to do this with a separate channel so that the activity to this channel
can be tracked in the logfile.  I have no problem with making entries in
aliases. for the accounts that need to have headers...

Thanks,
Joel D. Kraft
System Manager
Buena Vista College
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mailserv subscriptions
From: Stephen Tihor <tihor@acfcluster.nyu.edu>
Date: 18 Dec 1992 18:21:14 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Dec 1992 18:21:14 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSGS65Y83690N5MN@YMIR.CLAREMONT.EDU>
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

Once I get 4.2 up I will tell him to do that until then I need to used
the hacked mailserv that ignores address parameter.
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Stuck msgs in queue for local channel
From: Bob Tinkelman <bob@camb.com>
Date: 15 Dec 1992 14:51:21 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Dec 1992 14:51:21 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSCDY2HZEQ8WW1SV@INNOSOFT.COM>
X-Vms-To: IN%"NED@INNOSOFT.COM"
X-Vms-Cc: IN%INFO-PMDF,TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> > A dump of the queued msg shows lots of envelope destination addresses
> > of the form node::user.  This surprised me.  Is it an indication that
> > I did something wrong in setting up the list?
>
> I could not say without knowing what you did and how you did the conversion.

The system used to have logicals defined of the form
	$ define /system dis$xxx "@distribution_dir:xxx.dis"
and users would send to mail destination called dis$xxx (without typing an
@-sign).  The distribution files were indexed files with lines of the form
	node::user

We left the files indexed files intact (and thanks, Ned, for the change
that allowed us to access indexed files), removed the logicals, and for
each did:
	$ pmdf forward dis$xxx <file-spec-for-list
	$ mail
	Mail> set forward /user=dis$xxx in%dis$xxx

Would the fact that we used PMDF FORWARD rather than the alias file cause
us problems?
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Bad or missing to address
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 11 Dec 1992 09:52:04 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Dec 1992 09:52:04 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS6OM1BNZ68ZKRDG@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KNAPKE@Butler.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> In the last three or four days I have gotten a few bounced messages that
> are bounced because of a bad or missing to address.  I know this has been
> a topic before, but I don't recall the outcome.

Can you send a copy of one of these bounced messages to service@innosoft.com?
We need a little more context before we can answer the question.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Organization:-header and mail sent to host::in%"..."
From: Ned Freed <ned@innosoft.com>
Date: 12 Dec 1992 17:22:56 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Dec 1992 17:22:56 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS8IN8UZ028ZL8QZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"bob@camb.com"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

There's no built-in way to set this header depending on DECnet connection.
It would be trivial to set/override this as part of DECnet proxy login,
however. In the absence of a clear definition for or reasonable use of
this header we don't plan to provide elaborate mechanisms for setting it.

				Ned
From: bob@camb.com (Bob Tinkelman)
Newsgroups: vmsnet.mail.pmdf
Subject: Stuck msgs in queue for local channel
Date: 15 Dec 92 15:40:00 GMT
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Dec 1992 11:40:00 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSC7A84YLE90MTJL@INNOSOFT.COM>
X-Vms-To: IN%INFO-PMDF
X-Vms-Cc: TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

We converted a very large VMSmail distribution list (one with 100s of
entries) into a PMDF list by defining a PMDF alias that pointed to
an the existing file.  [It's maintained by a complex set of programs
that I didn't want to touch.]  The mailing list consists of single
lines of the format node::usename.

A mail msg to this list hung for over 24 hours.  When we killed the
job the last lines were
	$   mail /protocol=pmdf_mailshr
	%MAIL-E-NOSUCHUSR, no such user XXXXX at node XXXXX
(with actual user name and node)

First Question:

A dump of the queued msg shows lots of envelope destination addresses
of the form node::user.  This surprised me.  Is it an indication that
I did something wrong in setting up the list?

Second Question:

I know there is a bug in the Mail-11 protocol which gets triggered
when distinct distribution list entries (distinct on the local node)
getting collapsed into common addresses based on forwarding at
destination nodes.  Could this bug explain the msg getting hung?
If so, is there a recommended method to avoid the problem or at least
reduce the likelyhood of its occurance?  Finally, is there someway to
place a timeout on delivery through VMSmail?  I'd be willing to take
responsibility for maintaining the value of a locally specified
time-out value if that would be appropriate.
--
Bob Tinkelman <bob@camb.com>
Newsgroups: vmsnet.mail.pmdf
Subject: RE: DELIVER query - return message to sender
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 11 Dec 1992 10:22:33 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Dec 1992 10:22:33 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS6PNTWEB68ZL34T@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ccvj@misty.latrobe.edu.au"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I'd like to have a message automatically forwarded to people when I am
> away.  I have come up with the following rather unwieldly interpretation
> of DELIVER - is there a better way of doing it?  I fiddled with QFROM
> and QQFROM but went crosseyed with """s.   Have I missed an obvious flag
> for replying?

Use

   $ mail/subject="I am on holiday" hols.txt "''QFROM'"

Also, a word of warning.  You need to somehow log each address you
automatically send a message to and then ensure that you do not subsequently
send another automatic message to that address.  Otherwise, you may find
yourself generating a mail loop or two.  (E.g., you get a message from a
mailing list, you post hols.txt to the list, you get you're posting back, you
post hols.txt to the list, etc.)

Dan