HDTenEightyP/NetNews huggingface dataset:
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Changing To: header on alias list
Date: 17 Aug 92 23:50:33 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Aug 1992 16:50:33 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNP1EKHEW295NFX4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

There should be no reason to put the actual recipient in the To: header.
This information is available in the message envelope up until the instant
of final delivery, and all the mechanisms that need this information can
reference it. Once the message is delivered it is abundantly clear who it
is to and this information becomes superfluous.

So the answer is "no, there is no way to do this because there is no reasn
we know of to work this way". If you have a reason for wanting things to
work differently please elaborate on it further and we'll see what we can
do.

				Ned
From: ned@innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Channel Keyword "logging" and BITNET_DOMAINS.COM
Date: 17 Aug 92 18:47:14 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Aug 1992 10:47:14 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNOOQ38CS295NF54@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"JLW%PSULIAS.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Setting logging on the various channels produced by BITNET_DOMAINS.COM is
trivial if you use the defaults feature of PMDF. See section 3.2.5.7 (page
3-51) in the V4.1 manual for details. The defaults feature is also available
and documented in V4.0 in section 3.2.5.8 on page 3-42.

This mechanism is preferrabled to having BITNET_DOMAINS.COM put stuff on
every single channel it produces.

				Ned
From: ghc@vger.niddk.nih.gov (Gerson H Cohen)
Newsgroups: vmsnet.mail.pmdf
Subject: WAIS and GOPHER
Date: 20 Aug 92 22:02:45 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 18:02:45 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNT4IVWHZ695NSPS@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF
X-Vms-Cc: GHC
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I have recently been made aware of WAIS and GOPHER and am trying to get
them on my system.  I have been able to find and impliment Gopher as it
was fortunately coded for VMS with MultiNet in mind.  WAIS is another
story.  Has anyone seen or does anyone have a copy of this for MultiNet?

Gerson Cohen

-
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
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: question (thanks). More question
Date: 20 Aug 92 16:43:37 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 08:43:37 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNSRVLU6PY95NQPW@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"wdw3@cunixb.cc.columbia.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


 I run PMDF on a two-node VAXcluster. Each node has a valid internet host
> name. PMDF images are loaded on both nodes but there is only one cluster-
> wide MAIL$BATCH queue. I want different local host appear on the return
> address when people send mail from different node. So I create a PMDF.CNF
> for each node with the host name for l channel pointing to each node. This
> works fine when I send mail from the node on which the MAIL$BATCH is running.
> But when I send mail from the other node, the local host name apprears twice
> in the return address, like
> 	From: user@localhost@localhost
> Any idea how this happen? Or is there other better way to do this? Thanks.

The user@localhost@localhost sounds like you have something misconfigured.
I'll leave that for Ned to answer.

Now, if you want to run as though you have two distinct machines then you need
two distinct PMDF configurations (separate PMDF_ROOT:[TABLE] and
PMDF_ROOT:[QUEUE...] directories), and a way of ensuring that mail processing
for host A runs on host A and not host B.  This means two separate MAIL$BATCH
queues.  (Yes, you'll have to use different names for them and edit the proper
pieces of PMDF_STARTUP.COM and PMDF_SUBMIT_JOBS.COM so as to relflect these
changed queued names.)

Now, my questionfor you is, if there is the same SYSUAF and mail profile for
the two hosts, then why do you want to distinguish between the two systems
in the first place?

If you can distinguish on a per user basis whether their address should
always be user@hosta or user@hostb, thene there is another approach which
you can take which involves only a single PMDF configuration.  This approach
involves the use of the address reversal database.

Dan
From: d.nash@utexas.edu (Donald L. Nash)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: two minor points
Date: 12 Aug 92 19:20:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Aug 1992 13:20 -0600 (CST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNHQFE27QQ94E1KR@YMIR.CLAREMONT.EDU>
X-Vms-To: in%"info-pmdf@ymir.claremont.edu"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I'm inclined to agree with Scott on the matter of multipart bounce-o-grams.
Until we get MIME-compliant user agents, receiving multipart messages can be
annoying and/or confusing.  I don't think it is particularly fair to tell
people to just get used to it because that's the way it is.  However, I can
also understand Innosoft's position of wanting to get a MIME-compliant MTA
deployed as soon as possible.  If the much-heralded Innosoft MIME user agent
had shipped with PMDF V4.1 then I wouldn't have a problem with any of this.
But as the situation currently stands, it doesn't seem to make much sense to
send MIME messages if there aren't any MIME user agents to deal with them,
and there aren't any such agents for VMS (are there?).  Since V4.1 didn't
ship with the MIME user agent, I would like to have seen a setting which
would disable the use of MIME in bounce-o-grams (and maybe elsewhere).  This
would allow sites to ease into MIME as the user agents become available,
rather than forcing them to deal with MIME messages (and the "junk" they
contain), without a good user agent.  But I guess it's too late to retrofit
this into V4.1, and hopefully the Innosoft user agent will be available
before V4.2 comes out.

There, I'm glad I got that off my chest.  And lest anyone get confused and
think otherwise, let me say that I have nothing but good things to say about
Innosoft.  This whole MIME fracas is *minor* compared to the good stuff that
Innosoft has done for us.  Between their active participation in the IETF to
advance the state of the e-mail art and their contribution of real, working
code to implement that art, they have made significant contributions to the
Internet in general and to us poor VMS folks in particular.  It's nice to
see that Unix isn't always at the vanguard of progress.  Great work, guys!

                                ++Don Nash

The University of Texas System              Internet:  D.Nash@utexas.edu
Office of Telecommunication Services        BITNET:    DON@THENIC
From: kvc@summer.innosoft.com (Kevin V. Carosso)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mail User agents
Date: 13 Aug 92 16:56:40 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Aug 1992 08:56:40 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNIZNRCEFM94E4UD@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KNAPKE%BUTLERU.bitnet@UICVM.UIC.EDU"
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> You certainly cannot connect 350-400 mac's to a file server.  The cost
> of installing 3 (100 Mac users per server) additional Novell file servers
> would be slightly prohibitive.

This is the major reason in my mind why the PC mail solutions are all inadequate.
They all try to base the mail transport on file services, which simply cannot
scale adequately.  With mail services you need connectivity to millions of
hosts, not dozens.  SMTP based on a host to host wire protocol easily handles
a million hosts today (Internet).  Try doing that if SMTP were replaced with
something like BSMTP on NFS.  And even if you did it, who'd manage the
100,000 post offices? In a worldwide network it could never work.  A large
multi-national corporation isn't much different.

Most of the PC mail packages can interconnect post offices with a wire protocol,
but the narrow-minded designers chose proprietary protocols -- mainly designed
to run over dial-up lines.  Just try getting information on anything at that
level (the level at which we would prefer to speak to the things).

	/Kevin Carosso
	 Innosoft
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: listserv WELCOME message
Date: 15 Aug 1992 22:02:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Aug 1992 15:02:00 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNM50XMISY95N6O4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SROSS@CGNET.COM"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

It's a bug.  The welcome message code was added at the last minute to
satisfy a particular application; it was not tested very well as a result
of this. This problem will be rectified in a subsequent release of PMDF.

				Ned
From: kvc@summer.innosoft.com (Kevin V. Carosso)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: TCP/IP Services for VMS V2.0 and PMDF
Date: 21 Aug 92 06:04:05 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 22:04:05 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNTJ77Y34295NSJC@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"fineberg@wupost.wustl.edu"
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>  Just a quickie:
>	Has anyone used pmdf 4.x and UCX 2.0?
> We just got the new UCX in here at our campus ESL and I want to know
> if it is safe to use it...

It should work fine, you just have to disable the SMTP server that comes with
UCX.  I don't recall the details (we don't have it yet) but you need to remove
the UCX SMTP server from INETD.  Don't put the PMDF server in there, we haven't
modified it to work under INETD yet, just use START_UCX_SMTPD.COM as you did
with previous versions of UCX.

	/Kevin Carosso
	 Innosoft
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF-FAX installation and [ghostscript]fontmap.
Date: 21 Aug 92 17:06:17 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Aug 1992 09:06:17 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNU6ERLOZ695NV5D@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

in V4.2 we'll make the installation dio what we do with things like master.com:
rename the previous master.com to master.old.

Dabn
From: robin_goldstone@macgate.csuchico.edu (Robin Goldstone)
Newsgroups: vmsnet.mail.pmdf
Subject: deliver and 'vacation' processing
Date: 20 Aug 92 08:41:16 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 08:41:16 +0000 (U)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNSROECDR095NQPW@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I have never used DELIVER before and I though I would experiment around with it
to set up a simple "vacation" process, such that whenever anyone sends mail to
my account, they would get a message back saying I am on vacation.  My
MAIL.DELIVERY looks like this:

* * * A L DELIVER.LOG
* * * A E @VACATION.COM
* * * A D

The first line is for debugging purposes. The second line invokes a DCL program
which sends the vacation message back to the user.  The third line delivers the
message to the mailbox.

I am having trouble with my VACATION.COM procedure.  All I want it to do is
send a message back to the user.  It looks like this:

$ MAIL VACATION.TXT 'FROM'

The problem is the value of the symbol 'FROM' which DELIVER creates.  According
to the DELIVER.LOG file, the symbol looks like this:
$ FROM == "IN%""RGOLDSTONE@oavax.csuchico.edu""  ""Robin Goldstone"""

When I try to do:
$ MAIL VACATION.TXT 'FROM'
I get the error:
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
 \"Robin Goldstone"\

I know this is a quote problem.  If I do:
$ mail vacation.txt "IN%""RGOLDSTONE@oavax.csuchico.edu""  ""Robin Goldstone"""
it works fine.  So somewhere some quotes are getting stripped.  DCL and quotes
always gives me fits.  Can someone tell me what is happening and how I can fix
it?

Also, another problem.  The last line of MAIL.DELIVERY is:
* * * A D
which causes the message to be delivered "normally."  However, I noticed that
the delivered message has a header on it.  I have the 'headeromit' keyword on
my 'l' channel, but DELIVER seems to be ignoring this.  Is this a bug?

Robin Goldstone, CSU Chico
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Install bug
Date: 11 Aug 92 19:34:51 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Aug 1992 12:34:51 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNJGSE2NYQ94E8VC@YMIR.CLAREMONT.EDU>
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

Accounts of the form [nnn,0] have implicit privileges -- GRPPRV, I believe.
It is a very bad idea for the PMDF account to have such access; it is
certainly not needed and it can lead to trouble. We therefore don't allow
the use of an account of this sort as the PMDF account.

				Ned
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: two minor points
Date: 12 Aug 92 23:32:02 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Aug 1992 16:32:02 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNI1AMGCMA94E1K3@YMIR.CLAREMONT.EDU>
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

One additional note on all this...

The precise format of returned messages is still very much up in the air.
Modulo MIME the format is pretty well set; it is fairly obvious what you
need and MIME addresses it very nicely.

What is still missing is the precise structure of the first part of the
message. That is, there needs to be a standardized format for error messages
that is both human readable (i.e. explains clearly what went wrong) as well
as machine readable (a program can deal with these things). This format has
not been defined yet, but there is work underway to do so.

Of course the act of retrofitting this into PMDF is much less than the work
needed to get things to be in MIME format. If all goes well the standard
format for the error report will also make gatewaying to X.400 very
easy, although X.400's inability to handle return-with-content in many
places may make such conversion rather problematic.

				Ned
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Deliver and MM-32
Date: 20 Aug 92 16:32:21 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 08:32:21 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNSRIQYKOI95NQPW@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"PAVER@Maximillion.mcc.com"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Does DELIVER work with MM-32 under PMDF 4.1? I read the manual, but
> it only talks about using Deliver with VMS mail.

DELIVER works with VMS MAIL and MultiNet V3.1 MM.  It does not work with
any other version of MM.  The support for MultiNet MM was new to PMDF V4.1
and MultiNet V3.1

Dan
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: question
Date: 19 Aug 92 02:17:21 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Aug 1992 18:17:21 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNQIR8IBK295NL84@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"wdw3@cunixb.cc.columbia.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Is it possible for a machine that only has internet connection to send
> mail to .bitnet address using PMDF alone (without Jnet) through
> gateway machines?

    Sure.  In fact, CONFIGURE.COM automatically puts in a rewrite rule to do
this using CUNYVM.CUNY.EDU as the Internet/BITNET gateway.  A lot of sites
then change this to use a some local Internet/BITNET gateway instead.

    If you do not have such a rewrite rule already, then just add the following
rewrite rule to your PMDF.CNF file:

.BITNET             $U@$H$D@cunyvm.cuny.edu

> Sorry if this is FAQ.

No problem.

>  BTW is there a FAQ for this group?

Unfortunately not.  Some frequent _problems_ can be found in the Troubleshooting
& Maintenance chapter of the System Manager's Guide.  I'll give some thought
again to putting together a FAQ.  However, everyone should understand that we,
Innosoft, are more than happy to answer questions (even if some of them do
exasperate us at times ;-)  If you feel that your question is a FAQ and would
rather not trouble the whole world (info-pmdf) with it, then you can post to
service@innosoft.com which is read by just Innosoft personnel, call us at
+1 714 624 7907, drop us a FAX at +1 714 621 5319, or catch us at Walter's
(the coffee shop on 4th and Yale).

Dan
From: smith%nyumed.bitnet@ymir.claremont.edu
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Error in queueing bounced message.
Date: 16 Aug 92 12:59:53 GMT
Organization: NYU Medical Center, 550 First Ave., New York, 10016
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Aug 1992 08:59:53 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNN0FM5VUA95NBQB@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"Ned Freed <NED@INNOSOFT.COM>",in%"ipmdf@ymir.bitnet"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


Thanks for the analysis.  Yes, indeed 'nyu-medical.nyu.edu' is illegal (but
probably shouldn't be, but that is another matter).  My problem was that the
MR_LOCAL channel was not delivering what appeared to be a reasonable address.
I will be upgrading to V4.1-10 tomorrw, so with luck this will not recur.

Thanks again.
From: dsroberts@beckman.com
Newsgroups: vmsnet.mail.pmdf
Subject: Re: Deliver and MM-32
Date: 20 Aug 92 21:46:33 GMT
Organization: Beckman Instruments

In article <714322258.880000.PAVER@Maximillion.mcc.com>, paver@maximillion.mcc.com (Bob Paver) writes:
> Does DELIVER work with MM-32 under PMDF 4.1? I read the manual, but
> it only talks about using Deliver with VMS mail.
> 
> Thanks,
> 
> Bob
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Bob Paver  ---->  paver@mcc.com  OR  cs.utexas.edu!milano!paver
> 
> Microelectronics and Computer Technology Corp (MCC)
> 3500 West Balcones Center Drive
> Austin, Texas 78759-6509             (512) 338-3316

We just noticed a problem with this today.  DELIVER seems to have stopped
working with MultiNet MM as of PMDF 4.1.  Perhaps a logical needs to be set or
something?
-- 
   Don Roberts                   Internet:  don@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   People are as happy as they decide to be - A. Lincoln
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: two minor points
Date: 12 Aug 92 18:22:05 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Aug 1992 10:22:05 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNHOECVRQQ94E1DK@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"MITCHELL%UTHSCSA.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I hate to sound retrograde, but there are probably some sites that would
> prefer non-multipart notices.  Many people here won't have MIME-speaking
> UAs in the near future.  Novice users looking at these things sometimes
> despair before noticing that they contain readable information!

Well, the use of multipart messages for such bounce notices is
the direction being taken by the various concerns trying to standardize
the format of bounces and other error notifications.  So, it is safe to
assume that everyone will be seeing more of these (multipart error messages)
in the future.

Dan
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: deliver and 'vacation' processing
Date: 22 Aug 92 00:37:59 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Aug 1992 17:37:59 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNUO9AELWI95NWV4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KLENSIN@INFOODS.MIT.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

The single best way to filter out list addresses from vacation processing
is to use subaddressing on the address you use to subscribe to the list.


For example, when I subscribed to the ietf mailing list, I told them to
put me down under the address ned+list-ietf@innosoft.com. This gets back to
me just fine, and I can use DELIVER to filter things based on the envelope
To: address, which is ALWAYS this address for mail coming from this
particular list.

I use a different subaddress for each list. Not only does this give me
a guaranteed way to do vacation processing right, it also gives me a way
to file messages from lists to selected folders automatically. I do this
sometimes for lists I'm not actively involved with.

All this requires some foresight since you have to use a subaddress at
the time you subscribe (or ask that your subscription be changed to a
subaddress later). But it is the only way I know of that works correctly;
in general the behavior of list exploders is just too unpredictable to make
any other scheme practical.

				Ned