HDTenEightyP/NetNews huggingface dataset:
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: SMTP and Long Lines Supported ?
Date: 5 Nov 92 06:32:24 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Nov 1992 22:32:24 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQRQDFDPHE8ZFMUZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"roseberry@taney.uscghq.uscg.mil"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Dan's response is right on the money -- however, I wanted to add a couple
of additional comments.

The restriction in VMS MAIL is due to the way the MAIL-11 protocol is set up
and handled. It would be easy for DEC to fix; they simply have not done so.
In any case, if you don't use MAIL-11 (VMS MAIL's protocol over DECnet links)
there is no line length restriction and PMDF will happily deliver those long
lines to you. But if you use MAIL-11 there is no way for PMDF to know when
it will be used. In this case MIME encodings are the best solution to the
problem. And messages that never pass through VMS MAIL will never see the
restriction -- PMDF's SMTP implementation will handle 1000 character lines
quite nicely. Our SMTP doesn't produce longer lines (since they don't
interoperate well) and I believe it will wrap lines longer than 1000 characters
if it receives them over SMTP.

Generally speaking, PMDF can accomodate per-channel line length restrictions.
For example, if you have an incompliant SMTP implementation that cannot
handle long lines you can set up a special channel for that connection that
forces MIME encodings on messages longer than whatever limit you set.

Although PMDF's SMTP can handle long lines it does network reads and writes
blocked at 256 characters or so. This has no effect on line length since
SMTP rides on top of a stream protocol. However, in some cases it is nice to
be able to use larger block sizes to improve efficiency. As such, we've made
a bunch of changes in the next release so that larger block sizes are
supported (up to 1024 characters per block). The actual line length restriction
is set depending on the transport so only those transport that support larger
blocking factors can take advantage of this (most TCP/IP implementations can,
for example). We've also implementing SMTP streaming (or pipelining) where
SMTP commands are batched and sent in groups. This has to be used carefully
since some versions of sendmail don't like it. However, when used between
cooperating sites and over high-latency links it can improve throughput
dramatically.

					Ned
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Undocumented entry in mail.log?
Date: 12 Nov 92 19:36:02 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Nov 1992 12:36:02 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR2BV5BZB68ZGKG9@YMIR.CLAREMONT.EDU>
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

> I fond the following in mail.log and was wondering how to interpret?
>
> 11-NOV-1992 12:06:49 mailserv     120646120649 S 0 DMPM@mc.duke.edu sub chgadm-l
>     chgadm@mc.duke.edu 3.48
>
> I do not find anything about an S entry in the docs.

The "S" entry means "success".

Dan
From: dank@blacks.jpl.nasa.gov
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Does PMDF support SMTP source routing?
Date: 6 Nov 92 20:12:38 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 12:12:38 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: dank@blacks.jpl.nasa.gov, IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTXOTZNCY8ZEQ7Q@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"DAN@INNOSOFT.COM"  "Daniel C. Newman"
X-Vms-Cc: IN%"dank@blacks.jpl.nasa.gov", IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Thanks for the explanation!
I'm glad to hear I can continue to rely on the source routing probe
in my Horton auto-email-directory-database-gathering daemon
(this is a shameless plug; Horton can be got via anonymous FTP
 from punisher.caltech.edu in pub/dank/horton.  It runs under Unix
 (or OpenVMS?) and silently gathers e-mail address info for everybody
 in a domain, then makes it available via whois and ph).
- Dan K.
Newsgroups: vmsnet.mail.pmdf
Subject: Forcing lowercase usernames
From: "Jim Lovsey, MEC, (614)221-8005" <lovsey@mec.ohio.gov>
Date: 11 Nov 1992 23:37:18 -0500 (EST)
Organization: Metropolitan Educational Council
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Nov 1992 23:37:18 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR1EE3KL1U8ZGT9S@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


I recently setup a uucp connection to a Unix host that is really picky
about case.  I added a lowercase rewrite rule for them, something like:

unixhost  $u@unixhost

I swapped a few test messages with them and all was well.  Since the
people that really wanted to exchange mail with the new Unix host are my
A1 neighbors, I logged into their machine and sent a test message from
All-in-One.  PMDF-MR did it's magic and things looked fine.  A few minutes
later, bounced message.  I looked at the headers and low-and-behold, it
read   USER@unixhost.  Message Router evidently feels it has a civic duty
to uppercase everything.  Since I had foolishly already told the A1 people
that this was working, I needed to fix this up in a hurry, so I added the
unixhost uppercase usernames to the general database and substituted the
lowercase name.  They only have five or six users so this was easy to do.
I had entries like:

FRED	fred
BOB	bob

I then changed the rewrite rule to:

unixhost  $($u)@unixhost

This worked like a charm but there must be a better way to handle this.
Suggestions?

Thanks,

--- Jim

+-----------------------------------------------------------------------------+
+ Jim Lovsey, System Administrator        Internet: lovsey@mec.ohio.gov       +
+ Metropolitan Educational Council                  lovsey.j@oecn.ohio.gov    +
+ Ohio Educational Computer Network         BITNET: lovsey@ohstpy             +
+ 180 E. Engler Street                        UUCP: mecsys!lovsey             +
+ Columbus, Ohio 43215                Voice: (614)221-8005 FAX: (614)221-6050 +
+-----------------------------------------------------------------------------+
From: d.nash@utexas.edu (Donald L. Nash)
Newsgroups: vmsnet.mail.pmdf
Subject: Two unrelated questions
Date: 5 Nov 92 21:38:35 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 05 Nov 1992 15:38:35 -0600 (CST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQSM1ESZTU8ZFS73@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

I'm having an odd problem with MAILSERV under V4.1-10.  Everything seems to
work OK except for the DIRECTORY command.  I've defined
PMDF_MAILSERV_FILES_DIR to be "DUB0:[ANONYMOUS.ROOT.]", but the DIR command
fails with this error:

	No files found in command: dir *.*;*
	Use the HELP command to get a list of legal MAILSERV commands.

The screwy thing is that the SEND command *does* work.  I can use MAILSERV to
retrieve stuff from that directory, I just can't list anything.  I enabled
master_debug on the mailserv channel and got this:

Debugging enabled.
  Command limit set to 2147483647
  Maximum blocks per message set to 2147483647
  Maximum lines per message set to 2147483647
  MAILSERV reply address is: mailserv-reply@nic.the.net

Starting processing of PMDF_ROOT:[QUEUE.mailserv]ZZ01GQSOK7FHES00005M.00
  Message is from: D.Nash@utexas.edu
  Command: dir *.*;*
  CLI$DCL_PARSE returned status of 196609
Processing DIRECTORY command.
  Directory specification: *.*;*
  CLI$DISPATCH returned status of 0
  Making response header.
  Closing the output message.
  Finished with this message.

Not very informative, huh?  This one's got me stumped, so I'd appreciate some
enlightenment.

On a totally different subject, we have a mail host here which serves the
utexas.edu domain.  People who are registered with this mail host have mail
addresses of the form "F.Last@utexas.edu", and mail to this address will be
forwarded to their "real" mailbox (for example, D.Nash@utexas.edu gets
forwarded to don@nic.the.net, which is where I receive all my mail).  I have
a few users on my VAX (myself included), who have been registered with the
mail host.  I'd like to be able to recognize these addresses in PMDF and
deliver them locally rather than forwarding them to the mail host and getting
them right back again.  The problem is, I don't know how to do this.  I know
that I can set up a directory channel domain for utexas.edu, but that will
capture all utexas.edu addresses and I only want to capture three of them.
Is this possible?  If so, how is it done?

				Thanks,

                                ++Don Nash

Internet:  D.Nash@utexas.edu    The University of Texas System
BITNET:    DON@THENIC           Office of Telecommunication Services
From: postmaster@osu.edu
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Does PMDF support SMTP source routing?
Date: 6 Nov 92 20:25:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 15:25 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTXWL7BW28ZG02G@YMIR.CLAREMONT.EDU>
X-Organization: Academic Computing Services, The Ohio State University
X-Vms-To: IN%"dank@blacks.jpl.nasa.gov"
X-Vms-Cc: IN%"ipmdf@ymir.claremont.edu",STEELE
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I will let others explain to you what PMDF does and doesn't do.

I am responding to your posting to file a STRONG OBJECTION to what you are
doing! There is already enough junk traffic on the Internet without more
people designing automatons to troll for information that isn't desired
by anyone. There are probably 1,000 systems on this campus alone running
mailers, and I don't particularly want you probing them all to find out
how they're configured. Please reconsider what you're doing!
 -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
Gregory (Greg) E. Steele              Postmaster@osu.edu
Network Engineer                      (Internet):ges+@osu.edu
The Ohio State University             (BITNET): GES+@OHSTMAIL
Academic Computing Services
1971 Neil Avenue - Rm 406             Voice: 614-292-4843
Columbus, OHio  43210-1210            FAX:   614-292-7081
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Does PMDF support SMTP source routing?
Date: 6 Nov 92 18:51:48 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 11:51:48 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTWMFEQIQ8ZEVR2@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"dank@blacks.jpl.nasa.gov"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I'm trying to do an automatic mail probe to see if mail systems are
> well-configured.  The acid test is to see whether the system can route
> mail thru itself back to me via source routing, i.e.
>     mail @host2:myself@myhost

PMDF supports source routes in their fullest generality:

      @h1,@h2,...,@hn:user@host

> However, sometimes when I try this, I get errors like
>
> From: PMDF Mail Server <postmaster@portia.caltech.edu>
> Subject: Undeliverable mail: temporarily unable to deliver
>
> Your message could not be delivered to:
>
>     horton%punisher.caltech.edu@ORIENT
>
> Your message has been enqueued and undeliverable for 6 days.
> The mail system will continue to try to deliver your message
> for an additional 6 days.
>
> Is this because PMDF can't handle source routing?

No, this is because PORTIA.CALTECH.EDU has been unable to make a connection to
the host ORIENT.

Also, I believe, for technical reasons Valerie Okinawa has gone to great pains
to force the conversion of source routes to percent hacks on VMS systems at
Cal Tech.  I seem to recall that she had problems with other machines which
wouldn't accept source routes.

Dan
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: forwarding mail for testing
Date: 13 Nov 92 17:07:40 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Nov 1992 10:07:40 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR3KZU3QAA8ZFR5L@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

> I am trying to evaluate MS-Mail.  To help do this I would like to have
> all mail that is sent to my VMS mail account also sent to my MS-Mail
> account. I am currently using the W action of deliver to do this, but it
> does not keep the original headers intact.  Any suggestions on how I can
> accomplish this?  I use deliver for other purposes also.  Could I
> eliminate the W action in my MAIL.DELIVERY file, change my forwarding
> address in VMS mail to be: in%"~cvm,cvm@msmail.ucc.nau.edu" and still
> have deliver work?

Use the P action instead of W or F.  The problem with W and F is that they
use VMS MAIL to forward the message and this is too much of a disruption to
the headers.  If you use the P action, then PMDF SEND will be used instead
of VMS MAIL:

  * * * A P "cvm@msmail.ucc.nau.edu"

Dan
From: dank@blacks.jpl.nasa.gov
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Does PMDF support SMTP source routing?
Date: 6 Nov 92 20:47:44 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 12:47:44 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: dank@blacks.jpl.nasa.gov, ipmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTYSN6P4Y8ZG09B@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"Postmaster@osu.edu"
X-Vms-Cc: IN%"dank@blacks.jpl.nasa.gov", IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Greg writes:
>I am responding to your posting to file a STRONG OBJECTION to what you are
>doing! There is already enough junk traffic on the Internet without more
>people designing automatons to troll for information that isn't desired
>by anyone. There are probably 1,000 systems on this campus alone running
>mailers, and I don't particularly want you probing them all to find out
>how they're configured. Please reconsider what you're doing!
>Gregory (Greg) E. Steele              Postmaster@osu.edu
>Network Engineer                      (Internet):ges+@osu.edu
>The Ohio State University             (BITNET): GES+@OHSTMAIL
>Academic Computing Services
>1971 Neil Avenue - Rm 406             Voice: 614-292-4843
>Columbus, OHio  43210-1210            FAX:   614-292-7081

Hmm.  Let me try to allay your fears.
I share your concern about junk traffic on the Internet, but Horton
does not go offsite, so it does not put any traffic on the backbone at all.
Horton does indeed troll for information- but in a very controlled way.
It is only intended for use by network administrators to create an e-mail
database for their *own* network.
It is not intended to look outside the subdomain.
I believe it is less invasive than Netfind, an e-mail lookup tool
which is run directly by users instead of by a single administrator.

Who would want to run Horton?  Any network administrator wanting to set up a
whois server but not wanting to collect and maintain the database by hand.
It is already in use by ten or twenty sites around the world, including
horton.caltech.edu; try whois /host=horton.caltech.edu searchkey
to see what its database looks like.
- Dan Kegel
From: d.nash@utexas.edu (Donald L. Nash)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Two unrelated questions
Date: 5 Nov 92 22:38:03 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 05 Nov 1992 16:38:03 -0600 (CST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQSO3MKTEA8ZFQKR@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

Portia Shao <PORTIA@INNOSOFT.COM> wrote:

>>I'm having an odd problem with MAILSERV under V4.1-10.  Everything seems to
>>work OK except for the DIRECTORY command.  I've defined
>>PMDF_MAILSERV_FILES_DIR to be "DUB0:[ANONYMOUS.ROOT.]", but the DIR command
>>fails with this error:
>
>try DIRECTORY [*...]*.* instead

Thanks!  That did it.  The only problem is that it doesn't show anything in
the top-level directoy, DUB0:[ANONYMOUS.ROOT].  This is ony a minor
annoyance, which I can overcome easily enough.

				++Don
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Trouble sending smtp mail from pmdf to a pc gateway running
Date: 4 Nov 92 23:35:38 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Nov 1992 15:35:38 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQRBSNW66Q8ZFLFZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"BURKE%jcvaxa.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

The log indicates that the other side of the connection is vanishing in the
middle of the transaction. When I try this particular system with a test
message I have no problems with it at all. It probably has something to do
with the particular message you are trying to send.

					Ned
Newsgroups: vmsnet.mail.pmdf
From: dank@blacks.jpl.nasa.gov (Daniel R. Kegel)
Subject: Does PMDF support SMTP source routing?
Organization: Image Analysis Systems Group, JPL
Date: Fri, 6 Nov 1992 18:39:27 GMT

Hi,
I'm trying to do an automatic mail probe to see if mail systems are
well-configured.  The acid test is to see whether the system can route
mail thru itself back to me via source routing, i.e.
    mail @host2:myself@myhost

However, sometimes when I try this, I get errors like

From: PMDF Mail Server <postmaster@portia.caltech.edu>
Subject: Undeliverable mail: temporarily unable to deliver

Your message could not be delivered to: 

    horton%punisher.caltech.edu@ORIENT

Your message has been enqueued and undeliverable for 6 days.
The mail system will continue to try to deliver your message
for an additional 6 days.

Is this because PMDF can't handle source routing?
- Dan K. (dank@blacks.jpl.nasa.gov)
From: goodwin%smcvax.bitnet@ymir.claremont.edu (Dave Goodwin)
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF & MultiNet
Date: 13 Nov 92 13:48:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Nov 1992 09:48 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR3E6GGSGY8ZGXMR@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.bitnet"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

We are in the midst of getting ourselves connected to the Internet, and
have just installed TGV's MultiNet 3.1.  I have PMDF 4.1 ready to install,
but I'd like some advice and feedback from the net first.  Here's the
situation I need to handle:

Our site will remain on Bitnet for a while, with a separate 9.6k line to
each of two other nodes.  We will have a 56k line to our Internet neighbor
with nobody else downstream from us.  We currently use PMDF 3.1(?) on our
Bitnet system, along with Jnet.  This runs on a VAX 3400 with VMS 5.4-2.
Currently all users read their mail on a single node, although I will
be changing this later to use Decnet channels to direct mail to other
nodes internally.  We also have a couple of UNIX workstations which will
eventually get their mail sent directly to them.

Now the questions:

1.  Does anyone have opinions on the advisability of using MultiNet MM
    instead of VMS Mail?  It seems more capable on the surface, but there
    will be the training issue.  Also, I know we can let PMDF deliver to
    both mail agents depending on the existence of the Multinet mail files.
    I'm interested in the experiences of other MultiNet sites.

2.  During PMDF configuration, will the auto-config program be able to
    setup the configuration I need, or will I need to do it manually?
    I'm a bit uncertain about the choices to make concerning what
    systems are gateways, and to/from whom.  Any hints or trouble spots
    to watch would be appreciated.

Thanks in advance....
===========================================================================
Dave Goodwin                                   |
Assistant Director, Academic Computing         | We're all kinds of animals
-----------------------------------------------| coming here.
BitNet   : Goodwin@SMCVAX                      |
Ma Bell  : (802)654-2220                       | Occasional Demons, too.
US Mail  : Saint Michael's College             |
           Winooski Park, Colchester, VT 05439 |           -Jethro Tull
Ham Radio: N1HRO @ W1KOO.#NWVT.VT.USA.NA       |
===========================================================================
Newsgroups: vmsnet.mail.pmdf
Subject: Additional mailing list security
From: c.chaundy@its.unimelb.edu.au
Date: 12 Nov 1992 18:02:28 +1000
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Nov 1992 18:02:28 +1000
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR1JJ9GYGI8ZFRQZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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?

Also, is it possible to go futher and totally hide the address that
made the posting to the list?

Thanks in advance, Chris Chaundy (Technical Manager, Networks)

Information Technology Services, Thomas Cherry Building,
The University of Melbourne, Parkville, Victoria 3052 Australia
Phone:    +61 3 344 7045                Fax:   +61 3 347 4803
Internet: C.Chaundy@its.unimelb.EDU.AU 	(X.121 505233430003)
From: laue%vtcc1.bitnet@ymir.claremont.edu (Eliza Lau)
Newsgroups: vmsnet.mail.pmdf
Subject: How to subscribe to this group
Date: 5 Nov 92 17:11:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 05 Nov 1992 12:11 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQSCP4GHWY8ZFPE5@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Original_To: BITNET%"info-pmdf@ymir"
Original_Cc: LAUE

I am new to PMDF. Can someone tell me how to subscribe to info-pmdf?  I tried
sending a subscribe message to listserv@ymir but got an error message.
Please reply through email.  Thanks in advance.

------------------------------------------------------------------------------
 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
------------------------------------------------------------------------------