HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Thu, 5 Nov 92 06:57:29 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: SMTP and Long Lines Supported ?
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Thu, 5 Nov 92 06:22:56 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: SMTP and Long Lines Supported ?
Newsgroups: bit.listserv.pmdf-l

>       We have an odd UNISYS system that has SMTP and sends some
>       very long lines of text in the mail message.  My understanding
>       is that any SMTP package should be able to handle lines as
>       long as 1000 characters.
>
>       MX won't support over about 250 characters per line.
>
>       Will PMDF support up to 1000 characters ?

PMDF will support lines as long as 1000 characters (and longer).  Note,
however, that there are some restrictions with VMS MAIL: under the right
conditions, you can not have lines longer than 255 characters in messages
passing into/through VMS MAIL.  PMDF has a couple of ways of working around
this VMS MAIL limitation (either wrap the lines or use MIME encodings).

If you wish, you can contact sales@innosoft.com to arrange for an evaluation
copy of PMDF.

Dan
From: D.Nash@UTEXAS.EDU (Donald L. Nash)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: Two unrelated questions
Date: 5 Nov 92 23:28:11 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir.claremont.edu"
X-VMS-Cc: GROOTHEEST,JOOSTEN
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 5 Nov 92 10:30:55 GMT
From:         "Jos Joosten, AGRONET Netwerkbeheer" <J.JOOSTEN@TFDL.AGRO.NL>
Subject:      PMDF protocol error
Newsgroups: bit.listserv.pmdf-l

The VMS-mail-limit of 255 characters is not the problem !!!

I  put a mail into a save_set, mailed it through VMS-mail (foreign) to
another  PMDF-WEP-system  with no problems (VMS V5.5-1), restored  the
save_set  and editted the PMDF-mail-file so that it would deliver this
mail to  me.
Using  the  command, "$ MAIL/PROT=PMDF_MAILSHR 'filename'",  delivered
the mail correctly.   The same PMDF V3.1 version is used here.

Furthermore,  I  was not able to find a file that had  strings  longer
than appr. 80 characters.

Regards,

Jos Joosten.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"C.Chaundy@its.unimelb.EDU.AU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 12 Nov 92 07:59:10 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Additional mailing list security
Newsgroups: bit.listserv.pmdf-l

The functionality to restrict the people who can mail to a given list was
added in V4.1. You can restrict the ability to post to a list of addresses
or a mapping or both. See the material on positional parameters for mailing
list (section 3.3.2 or thereabouts).

As for anonymous postings, as far as I can tell this isn't a mailing
list function; it should be the job of a special PMDF channel. And
while I've never seen one yet it shouldn't be too hard to write one.
Arranging for replies to anonymous postings is harder, but again should
not be too hard to do with a bidirectional database.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"J.JOOSTEN@TFDL.AGRO.NL"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 5 Nov 92 11:50:11 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: PMDF protocol error
Newsgroups: bit.listserv.pmdf-l

> The VMS-mail-limit of 255 characters is not the problem !!!

That remains to be seen. See below.

> I  put a mail into a save_set, mailed it through VMS-mail (foreign) to
> another  PMDF-WEP-system  with no problems (VMS V5.5-1), restored  the
> save_set  and editted the PMDF-mail-file so that it would deliver this
> mail to  me.
> Using  the  command, "$ MAIL/PROT=PMDF_MAILSHR 'filename'",  delivered
> the mail correctly.   The same PMDF V3.1 version is used here.

Delivering the mail to yourself on the local node proves absolutely nothing. In
particular, the line length limitation in VMS MAIL only applies when delivering
messages to remote MAIL-11 users.

Avoiding the network transfer is not the issue either. Since the error is being
reported from the local channel all indications are that the message made it to
the final PMDF system just fine. You are avoiding a network transfer which, as
far as I can tell, has absolutely nothing to do with the problem at hand.

> Furthermore,  I  was not able to find a file that had  strings  longer
> than appr. 80 characters.

I don't know what this means. Do you mean that your sample message had no long
lines in it? If so, this is all the more reason for your test to have worked
out fine. The issue is what's in the message that's failing on the system where
it is failing.

Despite the fact that PMDF V3.1 is totally obsolete and hence we don't support
it at all, I'm willing to try and help you figure out what's happening here.

First of all, it is absolutely imperative that you be able to isolate the exact
message file that is failing on the exact system where the problem is
happening. Nothing else will suffice. Once you have obtained a copy of this
message please send it to me and I check it out.

Second, you should enable slave_debug on your l channel. This will produce
a more detailed trace in the L_MASTER.LOG file. Please send that to me as well.

Third, please check all the recipient addresses in the message and determine
whether or not they are local. These addresses appear on the second and
subsequent lines of the message file. A line containing two control-a
characters separates the recipient list from the message header. At a
minimum you should check each of the recipient with a SHOW FORW/USER=
command in VMS MAIL and see if forwarding is set for any of them.

Finally, if you have installed a new version of VMS or VAX PSI you may have
introduced some bugs into VMS MAIL. Please indicate if you have done this.

Send the results of all this to service@innosoft.com. (This is not a topic of
any real interest to the info-pmdf list.) I'm still betting on a line length
problem.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DMPM%DUKEMC.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 12 Nov 92 21:57:05 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Undocumented entry in mail.log?
Newsgroups: bit.listserv.pmdf-l

> 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: NED@SIGURD.INNOSOFT.COM (Ned Freed)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: New Mail Interface
Date: 6 Nov 92 23:20:39 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"JOHNSON@northeastern.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

We're hard at work on the new interface now. We hope to have it in alpha test
fairly soon and we hope it will make it into our next release. There will be
a general announcement of its alpha test status on this list once we get
that far.

It is unfortunate that other project got in the way (like our API, PMDF-X400,
the Novell MHS channel, POPx and IMAP, etc. etc. etc.) but that's the way it
goes...

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 11 Nov 92 19:50:35 GMT
From:         "James Dryfoos- Postmaster" <DMPM@DUKEMC.BITNET>
Subject:      Very large alias and reverse databases?
Newsgroups: bit.listserv.pmdf-l

Will PMDF handle an alias and reversal database starting
at about 5,000 entries and possibly growing to 20,000?

What kind of problems might I run into?

What we are trying to do is allow everyone at the Medical Center
to have a single id in the form of id@mc.duke.edu
As most users are not on the PMDF node (not even a VMS system),
I want to rewrite the outgoing address into the normalized form using
the reverse databse and then use the alias to direct it to
the appropriate channel.  For example,

Outgoing:       user%node@mc.duke.edu becomes id@mc.duke.edu
Incoming:       id@mc.duke.edu user%node@channel

If there is a better way of doing this I would not mind hearing it.
We already maintain the databse needed to generate this info and
in fact already perform the equiv of the above.  We however want to
move it to PMDF if possible.

-Jim

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

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Thu, 5 Nov 92 00:36:41 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Trouble sending smtp mail from pmdf to a pc gateway running
              S-Bridge
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Mailer: ELM [version 2.3 PL11]
Date:         Thu, 5 Nov 92 21:20:46 GMT
From:         Mike Carter <carter@CRUNCH.COLORADO.EDU>
Subject:      Mail Server Software -- Survey
Newsgroups: bit.listserv.pmdf-l

My site is in the process of evaluating mail server software packages.  Our
end goal is to consolidate most of our (500) mailing lists with some mail
server.  We have lists of all types on many of our platforms and adminstration
has become a nightmare.  We support many of these lists with PMDF MAILSERV and
are mostly happy with it but don't want to overlook any other products out
there.

As a note to Ned, Kevin, Dan, et al:  What is in the future for MAILSERV?
Additional functionality like moderation of messages, moderation of sub/unsub,
etc?

If your site runs any type of mailing list server, please take a moment to
fill out this survey and return it to me (carter@crunch.Colorado.EDU)

1)  What mailing list server software do you run?

        a) BITnet LISTSERV
        b) Unix Listserv (from BU, Anastasios Kotsikonas)
        c) PMDF MAILSERV
        d) Unix Majordomo (from Brent Chapman)
        e) VMSLSV (as discussed on VMSLSV-L)
        f) Homebrew (please let me know what platform)
        g) Other public domain or 3rd party software (please let me know where
           you got it, cost, etc.)

2)  How many mailing lists do you support through your mailing list server?

3)  Are you happy with the features of the server(s) you run?  If not, what
    is missing?

4)  Would you recommend your server software to other sites?

5)  Is your server software RFC 822 compliant?


--

                                - Mike
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
X-VMS-Cc: GROOTHEEST,JOOSTEN
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 4 Nov 92 17:53:35 GMT
Comments:     This message was sent with PMDF 3.2
From:         J.JOOSTEN@TFDL.AGRO.NL
Subject:      PMDF protocol error
Newsgroups: bit.listserv.pmdf-l

I have the following problem, and I'm desperate...

I'm using PMDF V3.1 on a system running VMS V5.4-2.
Whenever the job "PMDF delivery" starts, the PMDF-files in the directory
PMDF_ROOT:[QUEUE.L] can not be delivered.    Using the "$ SET VERIFY" it
appears that during the execution of the command:

   $ mail/prot=pmdf_mailshr ce15e930903fc00705.00

in PMDF_ROOT:[EXE]MASTER.COM you get the following error-message:

   %PMDF-W-V5DETECT, MAIL CNCT block not found -- assuming VMS V5
   %MAIL-E-OPENOUT, error opening  as output
   -RMS-F-RFM, invalid record format

This message will also be found in the file PMDF_ROOT:[LOG]L_MASTER.LOG .
This error is reproducable by issueing the above command !   All files
remain on the directory PMDF_ROOT:[QUEUE.L]
I already reinstalled PMDF, checked diskquota, file-protections, file-
ownerships, etc., but nothing helps !

Is there anyone who expirienced the same problem out there !!!

Regards,

Jos Joosten,
AGROnet Network-management,
TFDL Wageningen,
The Netherlands.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"J.JOOSTEN@TFDL.AGRO.NL"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 4 Nov 92 19:05:27 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: PMDF protocol error
Newsgroups: bit.listserv.pmdf-l

You have encountered a VMS MAIL restriction here. VMS MAIL does not like
lines longer than 255 characters coming in from a foreign protocol interface.

PMDF ha been enhanced in subsequent versions to deal with this problem. First
of all, later versions don't hang the entire queues when something like
this happens. Second, a linelength channel keyword was added to force
automatic wrapping of long lines on the L and D channels. Third, MIME
support was added so that long lines could be folded and unfolded later.

None of these features are present in PMDF V3.1, however. You will have to
upgrade to a newer version of PMDF (V4.0 or later) to fix this. In the
meantime your only recourse is to delete the offending message.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: University at Buffalo
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 13 Nov 92 01:15:38 GMT
Comments:     Warning -- original Sender: tag was NETNEWS@AMERICAN.EDU
From:         tkslen@UBVMSB.CC.BUFFALO.EDU
Subject:      BN_SLAVE error while deleting a file.
Newsgroups: bit.listserv.pmdf-l

I sometimes get the following error message in LMD.COM:

$ run pmdf_root:[exe]bn_slave.exe
%PAS-F-ERRDURCLO, error during CLOSE
  File "JNETFILE"  Filename "JAN_TMPROOT:[SYS]JMAILER.TXT;2"
-RMS-E-MKD, ACP could not mark file for deletion
-SYSTEM-W-ACCONFLICT, file access conflict
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000509C0  000509C0
                                                           0004B2A5  0004B2A5
                                                           0004B0A1  0004B0A1
                                                           00091182  00091182
BN_SLAVE        BN_SLAVE                         4104      0000149D  00003B09

Everytime I get this message the incremental or full backups are running on
that disk.  I do not use /ignore=interlock on either style of backup.  But I
do use the /record qualifier.  Before I call Jnet support I want to make sure
that it is their problem.  I feel it could be yours though, because BN_SLAVE
is actually trying to delete the file and since backup is either accessing the
directory or file for a second or two, BN_SLAVE is not being allowed to delete
it.  So, since you can't delete it you exit out of BN_SLAVE because you think
something is wrong.  If I am right, can you modify BN_SLAVE such that if this
error occurs you wait a couple seconds and try to delete it again or some other
logic so you do not exit BN_SLAVE.
I would like this to be resolved because this happens at least once
or twice a week.  You would think the window for this error occuring would be
very small, but at a large site like this where mail is constantly coming in
and being delivered and backups are done daily, it occurs a reasonable amount.

Thanks,
  Lenny Miceli
From: tkslen@ubvmsb.cc.buffalo.edu (Lenny Miceli)
Newsgroups: bit.listserv.pmdf-l
Subject: BN_SLAVE error while deleting a file.
Date: 12 Nov 92 16:25:00 GMT
Organization: University at Buffalo
News-Software: VAX/VMS VNEWS 1.41

I sometimes get the following error message in LMD.COM:

$ run pmdf_root:[exe]bn_slave.exe
%PAS-F-ERRDURCLO, error during CLOSE
  File "JNETFILE"  Filename "JAN_TMPROOT:[SYS]JMAILER.TXT;2"
-RMS-E-MKD, ACP could not mark file for deletion
-SYSTEM-W-ACCONFLICT, file access conflict
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000509C0  000509C0
                                                           0004B2A5  0004B2A5
                                                           0004B0A1  0004B0A1
                                                           00091182  00091182
BN_SLAVE        BN_SLAVE                         4104      0000149D  00003B09

Everytime I get this message the incremental or full backups are running on
that disk.  I do not use /ignore=interlock on either style of backup.  But I
do use the /record qualifier.  Before I call Jnet support I want to make sure
that it is their problem.  I feel it could be yours though, because BN_SLAVE
is actually trying to delete the file and since backup is either accessing the
directory or file for a second or two, BN_SLAVE is not being allowed to delete
it.  So, since you can't delete it you exit out of BN_SLAVE because you think
something is wrong.  If I am right, can you modify BN_SLAVE such that if this
error occurs you wait a couple seconds and try to delete it again or some other
logic so you do not exit BN_SLAVE.
I would like this to be resolved because this happens at least once
or twice a week.  You would think the window for this error occuring would be
very small, but at a large site like this where mail is constantly coming in
and being delivered and backups are done daily, it occurs a reasonable amount.

Thanks,
  Lenny Miceli