HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Second l channel?
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 14 Dec 1992 11:08:54 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 11:08:54 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSAY64APKY8ZLN3I@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"kraftjoel@bvc.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

Use a d or dn_ channel for a second local channel.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: mail without sender?
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 11 Dec 1992 09:49:55 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Dec 1992 09:49:55 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GS6OJCC0PU8ZL0N5@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"92636828s%csghsg5a.bitnet@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>  	Is it possible to send an email with VMS Mail without the
>        email-address of the sender being included in that mail?

Well, there's two things you might be asking for here: the ability to send mail
anonymously or the ability to have a mailing list which supports anonymous
postings.  The latter is something we've thought about adding support for
but it has never made it high enough on our priority list.  (Just let us know
and we'll look more seriously into implementing it.)  The former, the ability
to anonymously send mail, is violates all sorts of standards and spirits of the
standards and I do not see us ever supporting it.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Queued mail messages.
From: "Kevin V. Carosso" <kvc@summer.innosoft.com>
Date: 14 Dec 1992 20:05:47 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 20:05:47 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSBGWQU2WI8ZLMBE@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"FLEP@NET.CCD.BNL.GOV",
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>	When ever I look at the mail queues, with @pmdf_root:[exe]qm
>	all I see are mail messages with sizes and dates. What I would
>	like to know is why a particular message is queued. The "postmaster"
>	sometimes receives copies of mail to various users stating his
>	mail sent is queued for three days and will continue to be queued
>	for "n" more days, the question is WHY is this particular
>	message being queued and resent. Often the user wants to know.

All messages are queued.  That is the first thing that happens to them.  I
think the question you are asking is "how can I see why a message has not been
dequeued".  That is "why hasn't it left the queue and gone to wherever it
is supposed to go".

Currently the only way to answer that question is to look at the .LOG file for
the channel in PMDF_ROOT:[LOG] (for example, if queued in [QUEUE.MTCP_LOCAL]
look in MTCP_LOCAL_MASTER.LOG.  You should see error messages in there that
occur when the channel program processes the messages.  Enabling "master_debug"
for the channel by adding that keyword to the channel definition line in
PMDF_ROOT:[TABLE]PMDF.CNF may provide additional information around the error
to help figure out the problem.

In PMDF V4.2 we improve this a lot by logging the failures with the message.

	/Kevin Carosso
	 Innosoft
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Address reversal data base
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 15 Dec 1992 13:10:20 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Dec 1992 13:10:20 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSCGOXFI2Q8ZLTGP@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"bthomas@drifter.uwyo.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> How does one go about getting a default reversal mapping in the
> reversal data base similar to the "*" mapping in the directory
> data base. I would like not to have to put all users on other systems
> using PMDF as a mail forwarder into the reversal file if I can help it.
> I get the idea from the manual this is done with the REVERSE keyword
> but I have tried several varations on using it and none have worked.

The address reversal database does not support wild card operations; it's too
much of a performance lose in that situation.  (The directory channel can be
argued to support them since use of the directory channel in the first place
is an implicit statement that performance is not an issue.)

The reverse keyword is not what you need to be using; it merely controls
whether or not the reversal mechansims are used for a particular channel.
What you need to be looking at is the REVERSE mapping.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: talking about MCI, how about a SprintMail PMDF interface?
From: Ken Harris <harris@si-bas.si.com>
Date: 16 Dec 1992 22:02:09 +0000 (GMT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Dec 1992 22:02:09 +0000 (GMT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSECC9QOYQ90MUSQ@YMIR.CLAREMONT.EDU>
X-Vms-To: MAILGATE::"@si.com:info-pmdf@ymir.claremont.edu"
X-Vms-Cc: HARRIS
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>
> does PMDF have a way to talk directly to mcimail?
>
> --
> --- bob pasker
> ---- rbp@netcom.com

Going further... does PMDF have a way to talk to SprintMail?  We are hoping to
become a X.400 PRMD off TMAILUK (Sprint aka Telemail, in the UK) but in the
meantime are using the PC Sprintmail package via dial-up to access mailboxes on
the SprintMail host.  Lotus have a cc:Mail to SprintMail gateway product that
uses cc:Mail import/export much like the PMDF to cc:Mail gateway but it's
pricey and does not support binary attachments (strange because the cc:Mail to
MCI mail gateway DOES).  Looks like it would need a combination of the PMDF
cc:Mail gateway code plus some dialling code from PhoneNet and some...

Any ideas?  BTW the Lotus product SEEMS to only need ONE mailbox on SprintMail
to serve multiple real local users; sounds clever.

Ken
________________________________________________________________________________
Ken Harris                                         | Tel: +44-256-349422
Smiths Industries Aerospace                        | Fax: +44-256-844434
Basingstoke RG22 6HP                               | PSI: 234225600152::HARRIS
UK                                                 | harris@si-bas.si.com
Newsgroups: vmsnet.mail.pmdf
From: rbp@netcom.com (Bob Pasker)
Subject: MCI mail PDMF interface?
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 12 Dec 1992 04:58:34 GMT

does PMDF have a way to talk directly to mcimail? 

-- 
--- bob pasker
---- rbp@netcom.com
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Help: How to get mail deliver messages for internet nodes?
Date: 17 Dec 92 16:50:53 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Dec 1992 09:50:53 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSF2BTQ5V690MXIG@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

> We are on both Bitnet and Internet.  Before we joined Internet last month, we
> can receive messages dislayed on the screen shown where the mail has been
> delivered.  After I adding a channel and installing the slave program
> PMDF_ROOT:[EXE]MTCP_SLAVE.EXE to act as TGV MultiNet's SMTP server, now I can
> receive deliver messages only when the mail's destination is a BITNET node.
> Some of my users REALLY sit in front of the terminal until they saw their mails
> been delivered to the destination.  That feature is very important to them.
> Can anyone tell me if it is possible to get the deliver messages for all the
> addresses(not only Bitnet)?  Is there some kind of switch I need to set?
> Thank you very much for your help.

The SMTP (the Internet's mail transport) does not support this "feature" nor
does PMDF's SMTP client implement any sort of mechanism whereby a broadcast can
be sent to a local user after their mail has been delivered to a remote SMTP
server.  If your users really want to get delivery confirmations, they can
request a delivery receipt when they send the message.  Note, however, that not
all mailers will generate delivery receipts (i.e., recognize delivery receipt
requests) and thus a negative confirmation does not mean that the message has
not yet been delivered.  These delivery reports come back in the form of a mail
message and are generated by the remote mailer.

Now for a warning: your users can really deluge your system with mail when they
use delivery receipts without thinking about what they're doing.  For instance,
accidentally post to a large mailing list (e.g., info-vax) with a delivery
receipt request and they may receive 10 of thousands of delivery reports.  Not
only will this flood their mailbox, it can flood your system.

See Section 2.1.10 in the V4.1 PMDF System Manager's Guide for a discussion
on how to request delivery receipts.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mailserv subscriptions
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 18 Dec 1992 09:02:36 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Dec 1992 09:02:36 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSGEWL95W290N3AJ@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

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

Ned might have a different take on this; I just want to toss in my two bits.

I've seen mailers & user agents which always put all From:, To:, and Cc:
addresses onto the Reply-to: line.  There's nothing inherently wrong with
doing so.  However, this is a case where you would certainly not want to
use the Reply-to: address.  The last thing you want to do is to automatically
subscribe the list to itself!

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF V4.1 and Jnet V3.6
From: dan@toe.towson.edu
Date: 16 Dec 1992 08:31:03 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Dec 1992 08:31:03 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSDF41L8MA8ZKI7T@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

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.
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PX25_master hangs (PMDF 4.0)
From: Ned Freed <ned@innosoft.com>
Date: 16 Dec 1992 10:09:54 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Dec 1992 10:09:54 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSDOOF2VLU8ZLQHL@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ROLFF@enterprise.eurokom.ie"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

This is the first we've heard of any such problem; many sites are using
this channel successfully and as far as I know you're the first one to
report this.

Without additional logging information from the channel there's nothing
we can do to diagnose this further. I would also recommend upgrading to
V4.1; we no longer support V4.0. There were some changes in V4.1 that
might have corrected this problem, but there's no way to be sure.

			Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Queued mail messages.
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 14 Dec 1992 09:30:23 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 09:30:23 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSAUPY5ARM8ZL8WV@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"FLEP@NET.CCD.BNL.GOV"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> How can I find out WHY a mail message is being queued??

We need a little more context in order to answer this question in a meaningful
way.  I.e., does the same message keep on appearing on your system as a new
message; is there a message looping around on your system; are there messages
seemingly appearing from nowhere; etc.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF Installs in a Heterogeneous VAX Cluster
From: Jim Greenberg <greenbjb%snyoneva.bitnet@ymir.claremont.edu>
Date: 15 Dec 1992 10:09:41 -0400 (EDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Dec 1992 10:09:41 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSC431JVYQ8ZKF8W@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
X-Vms-Cc: WILSONEH
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

PMDFers,

Section 1.3.2 of the PMDF manual explains how to install PMDF on two nodes in
a heterogeneous cluster.  I think I understand it but want to make sure.

I currently have PMDF running on one node no problems.  I now want to install
it on the other, each having their own QUEUE, LOG, TABLE, etc. directories.
In fact, they will be on different disks. I realize I could share the EXE
directory but don't know how if PMDF_ROOT has to point to a different place
on each node. So lets say I will have two of those also.

I now have the PMDF startup files in my SYS$COMMON:[000000.SYS$STARTUP] dir
from the first install.  This points the PMDF_ROOT to the correct place for
the current install.  When I install the second node, won't it will overwrite
(create a new version) of this file since the nodes share a common startup
disk.  Don't I have to break up the startup so the two startups are in
specific not common areas?

The manual says the startup files will be installed in the specific areas but
that is not what appears to have happened with my first install.  Did I miss
something?

Does it sound like I know what I'm doing? Anything else to worry about?

Jim Greenberg
SUNY College at Oneonta

"Someone lifted the Lorax away."
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Second l channel?
From: "Kevin V. Carosso" <kvc@summer.innosoft.com>
Date: 14 Dec 1992 22:15:56 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Dec 1992 22:15:56 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSBLFSJJWY8ZLMIW@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KRAFTJOEL@bvc.edu"
X-Vms-Cc: info-pmdf,ned
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Okay, this is close, but when trying this I see that the "d" channels parse
> the user@host format in its entirety interpreting the host as a decnet node
> name, while the "l" channel will strip off the "@host" portion.  What is
> the best way to set up the rewrite rules in our homogeneous cluster (which
> shares the PMDF configuration) to get the decnet hostname to work properly.
> I'd prefer not to write a rule for each node to get it to work out
> properly.

Sorry, I should've included the rewrite rules to use.  I just set up a working
"headeromit" channel for alternate local delivery as follows:

    ! Rewrite rules for the local host/VAXcluster
    !
    SUMMER                                  $U@SUMMER.INNOSOFT.COM
    SUMMER.innosoft.com                     $U@SUMMER.INNOSOFT.COM
    SUNDAY                                  $U@SUMMER.INNOSOFT.COM
    SUNDAY.innosoft.com                     $U@SUMMER.INNOSOFT.COM
    !
    ! Special channel for "headeromit" on local delivery
    !
    NOHEAD.SUMMER.INNOSOFT.COM              $U%SUMMER@NOHEAD-MAIL
        .
        .
        .
    l nox_env_to
    SUMMER.INNOSOFT.COM

    d_noheaders nox_env_to headeromit
    NOHEAD-MAIL

The trick here is the "$U%SUMMER@NOHEAD-MAIL" rewrite.  SUMMER is a DECnet node
name within the local cluster.  With MAIL$SYSTEM_FLAGS set correctly for a
homogeneous cluster (7 in my cluster), the node prefix SUMMER:: will be stripped
by VMS MAIL.

> May I also suggest adding support for multiple "l" channels...

I'll have to let our architect (Ned) comment on this one.  Functionally it would
be the same as the alternate "d_" channel.  Perhaps it could short-circuit the
need to count on VMS MAIL to strip the local NODE:: prefix.  I don't know the
details involved, however.

	/Kevin Carosso
	 Innosoft
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Sending small msgs before large ones
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 10 Dec 1992 11:09:17 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 10 Dec 1992 11:09:17 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSFMIBN65E90N0R3@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

PMDF already supports the sending of small messages before large ones.
It does it automatically, as a matter of fact. It is implicit in the way
the queue cache is implemented.

We're adding some additional functionality in PMDF V4.2 in this area as
well that's tied into the SMTP extensions for message size negotiation.
This will provide you with the ability to specifically block the transfer
of messages larger than some size, as well as providing for the case of
simply holding large messages.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Using [auth_list] positional parameter
From: Bob Tinkelman <bob@camb.com>
Date: 20 Dec 1992 23:03:21 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Dec 1992 23:03:21 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: TINKELMAN@DECUS.Org
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSJUKHKSUQ8WW5IC@INNOSOFT.COM>
X-Vms-To: in%"info-pmdf@innosoft.com"
X-Vms-Cc: TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I'm trying to use the [auth_ilst] positional parameter to restrict
posting to a list.

From the alias file:

> ! Mailing_List.Aliases
> !
> comcom-l:		comcom-list
> comcom-list:		comcom-forward
> comcom-x:		<pmdf_mailserv_mail_dir:comcom-list.dis,\
> 			[auth_list] pmdf_mailserv_mail_dir:comcom-list.dis,\
> 			comcom-l-owner,*,*,comcom-l-owner
> comcom-owner:		postmaster,comcom-sec
> comcom-sec:		gerland

VMSmail forwarding addresses:
	comcom-x -> in%comcom-x
	comcom-forward -> in%comcom-x

Mail that is sent from an address not in the named file is not delivered
to the list, as expected.  However, it's not bounced to the originator
either.  It just sits in the queue and gets retried laster.  The log file
shows:

> $   mail/protocol=pmdf_mailshr
> %PMDF-E-HOST, Illegal host/domain in address "COMCOM-X"
> -PMDF-I-TEXT, you are not allowed to use this list: COMCOM-X@DECUS.Org

I don't remember what version of PMDF was first supposed to support this
feature.  Should this work under 4.1-11?

If the PMDF version is not the problem, what do you suggest I look at to
figure out the problem?
Newsgroups: vmsnet.mail.pmdf
Subject: Address reversal data base
From: bthomas@drifter.uwyo.edu
Date: 15 Dec 1992 13:58:25 -0700
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Dec 1992 13:58:25 -0700
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSCG8RUJCY8ZKH88@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


How does one go about getting a default reversal mapping in the
reversal data base similar to the "*" mapping in the directory
data base. I would like not to have to put all users on other systems
using PMDF as a mail forwarder into the reversal file if I can help it.
I get the idea from the manual this is done with the REVERSE keyword
but I have tried several varations on using it and none have worked.

Thanks

-------------------------------------------------------------------------------
|   ####   ###  ##    |   Brad Thomas                                         |
|   ####   ###  ##    |   System Programmer                                   |
|   ####   ###  ##    |   Network Development Group                           |
|   ####   ###  ##    |   University of Wyoming                               |
|    ###    #   #     |   Bthomas@Outlaw.UWyo.Edu                             |
|     ###### ###      |   bthomas@drifter.uwyo.edu                            |
-------------------------------------------------------------------------------
Newsgroups: vmsnet.mail.pmdf
Subject: PX25_master hangs (PMDF 4.0)
From: Anders Rolff <rolff@enterprise.eurokom.ie>
Date: 16 Dec 1992 11:58:09 +0000 (WET)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Dec 1992 11:58:09 +0000 (WET)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSDBQK4PTE8WW3WE@INNOSOFT.COM>
X-Vms-To: in%"info-pmdf@innosoft.com"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Hello!

I have noticed several times that the PX25_master program hangs (for hours).
As an effect of this, that particular channel is blocked so no messages
will be delivered. When I manually kill the process, and manually re-run
the queue it works fine.

Is there a known workaround for this problem?

Thanks,

Anders.