HDTenEightyP/NetNews huggingface dataset:
From: DAN@INNOSOFT.COM (Daniel C. Newman)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: PMDF 3.2 - job enqueue error
Date: 18 Nov 92 21:47:29 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"gomide%BRFAPQ.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

> I'm running pmdf 3.2 with VMS 5.4-2. When a new mail arrives, pmdf
> enqueues another job on the corresponding queue, without recognizing
> that there are already other jobs for the same channel pending on that
> queue. This creates a big overhead of JOB CONTROL. Is there a patch to
> correct this? For reasons not stated here I can not install pmdf 4.x
> right now.

     Support to do this was added to PMDF V3.0.  There are two possibilities as
to what might be going wrong here.  But first an explanation as to how PMDF
submits batch jobs:

(1) If the process has SYSPRV & CMKRNL privileges (required by $SNDJBC) PMDF
    first checks to see if there already is pending job and if not then submits
    a batch job with $SNDJBC.  The $GETQUI call to check for a pending job
    requires either SYSPRV or OPER privileges.

(2) If the process lacks SYSPRV or CMKRNL then PMDF cannout use $SNDJBC to
    submit the batch job.  It resorts to spawning a subprocess which submits
    the job using the DCL SUBMIT command.  In this case, no check is made to
    see if there already is a pending batch job.

     Now, from within VMS MAIL, (1) should always be used since the necessary
privileges are made available by PMDF's protected shareable image PMDFDISP.EXE.
If this image isn't properly installed then none of your users would be able to
send any PMDF mail whatsoever from within VMS MAIL.  I suspect, therefore, that
you are not seeing superfluous jobs queued from VMS MAIL.  You can double check
this by doing the following:

       $ STOP/QUEUE/NEXT MAIL$BATCH
       $ MAIL/SUBJECT="Test 1" SYS$LOGIN:LOGIN.COM IN%SYSTEM
       $ MAIL/SUBJECT="Test 2" SYS$LOGIN:LOGIN.COM IN%SYSTEM
       $ SHOW QUEUE/FULL/ALL MAIL$BATCH

Do you see one or two pending L channel jobs in the MAIL$BATCH queue?

     My guess is that the superfluous pending jobs are being created by PMDF
channel programs which are running under an account which lacks either SYSPRV
or CMKRNL or both and is therefore following (2) above.  To isolate this
problem, you'll have to determine which all accounts may be running PMDF
channels and what privileges that they have.  (For instance, do you use
DECnet, PhoneNet, or PSI channels and if so does your PMDF server account
lack these privileges?)

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"jobes@mayo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 00:39:18 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: "Illegal host/domain name" errors
Newsgroups: bit.listserv.pmdf-l

I'd have to see the errors in question, and in particular where they
occurred, before I could possibly comment on why they happened. Generally
speaking, this sort of thing usually occurs as a result of nameserver
glitching, and is unrelated to resource starvation issues.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"BOWMAN_BRETT_E@LILLY.COM"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 00:17:31 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Working with MR "flags" like sensitivity in PMDF-MR
Newsgroups: bit.listserv.pmdf-l

> Our company is evaluating migrating users to DEC's Mailworks.  We currently us
   e
> a gateway machine to connect to the Internet and exchange mail between the
> Internet and our internal mail network using PMDF and PMDF-MR.
>
> We have a mechanism in place to control who can send messages out onto the
> Internet.  Before people can get access, them are required to read and
> acknowledge a statement about use of the Internet and about not sending
> confidential information over it.  For the most part, this system seems to wor
   k
> fairly well.  However, we occasionally have people who are "authorized" that
> "accidentally" send messages to the wrong address (Internet rather than
> intra-company).
>
> A1Mail has a feature of being able to specify a "Sensitivity" for a message.
> Are there any plans for PMDF-MR to be able to do something with this flag?
> (Such as only allowing messages where sensitivity is not COMPANY_CONFIDENTAIL
> to be sent out onto the Internet.)  We are looking at starting to use PMDF for
> some of the internal mail routing, also, so it would be best if something coul
   d
> be applied based upon the routing rather than just applying to everything
> coming through PMDF-MR.

While I cannot speak as to planned uses for the Sensitivity flag (that's Ned's
ballicwick), I thought I'd point out that PMDF V4.1-10 and later has a mapping
table which allows you to control who can send to where (source channel, source
address, destination channel, destination address).  This, of course, doesn't
prevent authorized people from accidentally sending company-confidential
material out to the Internet, but it does add another degree of control
to your present system.  That may or may not be interesting to you.  Since this
was added as an interim feature (requested by a customer) it is not in the
printed documentation.  It's also not in the on-line 4.1 docs.  If you're
interested I can send you the relevant documentation.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"BOWMAN_BRETT_E@LILLY.COM"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 00:10:17 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Working with MR "flags" like sensitivity in PMDF-MR
Newsgroups: bit.listserv.pmdf-l

PMDF-MR has always handled the Sensitivity: flag properly; it maps it
to a Sensitivity: header in accordance with RFC1327. We have not seen any
proposals, either as a standards-based effort or as a private extension
that map this information into any sort of real action. It would be trivial
to write a channel program that performs this sort of filtering. It is
possible that we'd consider adding support for Sensitivity: filtering to
PMDF proper as well. I'll have to think about it some, but it would be very very
easy to do.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@INNOSOFT.COM"
X-VMS-Cc: IN%"dryfo001@deneb.mc.duke.edu"  "James Dryfoos"
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 19 Nov 92 21:35:08 GMT
From:         "James D. Dryfoos" <dryfo001@DENEB.MC.DUKE.EDU>
Subject:      Alias, reply address problem.
Newsgroups: bit.listserv.pmdf-l


Below is an error I got replying to a message I received. I realize why I got
the error.  In PMDF on our vax (DUKEMC) I have put in an alias for dryfo001 and
pointed it to dryfo001@deneb.mc.duke.edu (my workstation).

This has worked fine for some time.  However, just found a case where it does
not.  Someone sent me mail from a Bitnet node (DUKEMVS) to dryfo001@dukemc.  My
alias forward sent it to me at deneb.mc.duke.edu, but the return address was
setup so that it would only work we replying through the PMDF system (which it
was not) -- i.e. user@node.bitnet.  Normal SMTP internet mail works fine as my
reply goes directly to the sender and not through PMDF.  I suspect I need a
rewrite rule or something to prevent this?  Am I doing something I am not
supposed to? On systems connected to the PMDF system, I want replies to go
through our Bitnet connection, but for cirumstances such as this, we need to go
through an SMTP/Bitnet gateway or back through the PMDF system?

Thanks in advance,

--Jim Dryfoos

---------- Forwarded message ----------
Date: Thu, 19 Nov 1992 11:06:53 -0500
From: MAILER-DAEMON@deneb.mc.duke.edu
To: dryfo001@deneb.mc.duke.edu
Subject: Returned mail: Host unknown

   ----- Transcript of session follows -----
550 dukemvs.bitnet (tcp)... 550 Host unknown
554 WEINER6@DUKEMVS.BITNET... 550 Host unknown (Authoritative answer from name s
   erver)

   ----- Unsent message follows -----
Date: Thu, 19 Nov 1992 11:03:39 -0500 (EST)
From: "James D. Dryfoos" <dryfo001>
Subject: Re: BBS access
To: WEINER6@DUKEMVS.BITNET
Message-Id: <Pine.3.05.9211191138.E933-b100000@deneb.mc.duke.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On 19 Nov 1992 WEINER6@DUKEMVS.BITNET wrote:

message deleted...
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"KVC@SUMMER.INNOSOFT.COM"  "Kevin V. Carosso"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"  "info-pmdf"
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary (ID H7xPOYSw470tG3oTBnn5Hw)"
X-Mailer: Microsoft Mail V3.0
Date:         Fri, 20 Nov 92 18:05:11 GMT
From:         Chris Michels <cvm@MSMAIL.UCC.NAU.EDU>
Subject:      RE: Bad return address
Newsgroups: bit.listserv.pmdf-l


--Boundary (ID H7xPOYSw470tG3oTBnn5Hw)--
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 05:23:30 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: Bad return address
Newsgroups: bit.listserv.pmdf-l

> I have a problem with MS-Mail not using the correct address when
> replying to a message from a POP3 client whose mail address is on our
> VAX.  I have a copy of the queued message on the VAX before it gets sent
> to the MS-Mail system.  All other machines that the POP client sends to,
> reply to CVM@NAUVAX.UCC.NAU.EDU.  The MS-Mail system replies to
> CVM@PC19.UCC.NAU.EDU.  Before I go to Microsoft or the MS-Mail
> discussion list, I need to know is what the first line in this file is
> used for.

The MS-Mail gateway is causing MS-Mail to use the envelope-from address
for replies rather than the header "From:" address.  This is not uncommon,
many UNIX mailers do the same sort of thing.  As Dan explained earlier,
the address on the "m;" line is the envelope-from address.  If you could
modify the MS-Mail itself or the MS-Mail gateway to use the header-from
preferentially, that might be a solution, but would hide the real problem.

I suspect the real problem actually lies with the POP3 client, which is
not putting a domain name on the envelope-from address when doing its
SMTP dialog.  I bet if you were to watch the SMTP dialog from that client
you would see something like:

   MAIL FROM:<cvm>

To verify this, put "slave_debug" on your "mtcp_local" channel in your
PMDF configuration file, PMDF_ROOT:[TABLE]PMDF.CNF.  This will result in
a trace of the SMTP dialog in the log file PMDF_ROOT:[LOG]MTCP_LOCAL_SLAVE.LOG

This is not allowed, it is not supposed to put an address onto the network
without fully qualifying it.  PMDF accepts this broken address and does the
only thing it can to make it legal by adding a domain name.  It chooses to
use the domain name of the machine at the other end of the connection,
in this case the POP3 client.

Previous versions of PMDF added PMDF's local host name rather than that of
the other machine.  In your case this would be preferable.  I do not know if
this is settable, but Ned should know.

I think you may also be able to fix this by putting a rewrite rule in PMDF.CNF
that reads:

    pc19.ucc.nau.edu        NAUVAX.UCC.NAU.EDU

This unconditionally maps the PC's address to the local host address.  Since
you cannot send mail to the PC directly, this shouldn't interfere with
anything.  If you think about it, since the POP3 machine has to get its
mail on the server, this rewrite rule simply reflects reality.

Of course you probably should see about fixing the POP3 client to correctly
specify envelope-from addresses.  It should use the same thing it is using
in the header-from (which is set by the user of the PC).

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Washington University in Saint Louis, MO USA
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:         Sun, 15 Nov 92 03:19:03 -0600
From:         "Charles M. Fineberg" <fineberg@WUPOST.WUSTL.EDU>
Subject:      RE: Additional mailing list security
Newsgroups: bit.listserv.pmdf-l

c.chaundy@its.unimelb.edu.au writes:
>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?

Hmm.  When I read the 4.1 docs it seemed trivial to limit who could post
to a list, but allowing mailed list ownership didn't seem to be there at
all.  So what did my denseness ignore?  That is where in the manual is
the reference to controlling who may add and delete users?
        Charlie
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SYSMARK@minna.iit.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 23 Nov 92 19:21:47 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Sudden switchover to JNET protocol...
Newsgroups: bit.listserv.pmdf-l

One additional point. In order to restart PMDF to its proper role in handling
the delivery of Jnet mail you need to stop and restart processing for your
local link in JCP. This corresponds to using the STOP command (with the
local node as a parameter), waiting a bit, and then using the START command
(same parameter).

                                Ned
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, 19 Nov 92 02:39:20 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Memory leak in process symbiont?
Newsgroups: bit.listserv.pmdf-l

> We are using the PMDF process symbiont under V4.1-13 to run three PMDF
> server queues and have been having a problem where occasionally the queues
> stop.  The error messages that appear in the operator log file are:

This description sounds just like the bug which was fixed prior to -13.
The error messages you sent also support this conclusion.  Could it be that
when you put -13 up that you did not copy the latest version of the symbiont
to SYS$SYSTEM?  Or if you did, then is perhaps an older version of the
symbiont in a specific directory of SYS$SYSTEM overriding the newer version.

You can get the latest copy of the symbiont via anonymous FTP to
thor.innosoft.com.  Look in the [.pmdf_patches] subdirectory.  If you are
indeed using the latest version and still experiencing this problem, then
send e-mail to service@innosoft.com and we'll take it from there.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SETH@SPEECH.MIT.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 15:07:14 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Incoming notification From: prefix = SMTP%
Newsgroups: bit.listserv.pmdf-l

When you change TCP/IP packages you also have to reconfigure PMDF and the new
TCP/IP to make things work properly again... None of this is automatic. In
particular, you have to change your PMDF channels to be mtcp_* instead of
ctcp_* _and_ you have to configure the Multinet server process per the
documentation. Failure to do this will mean that Multinet will deliver its
own mail, bypassing PMDF and causing you to get SMTP% prefixes.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"martinez@iris-dcp.es"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 18 Nov 92 05:15:10 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Help: mapping file for VMS addresses
Newsgroups: bit.listserv.pmdf-l

> According to the manual, I have created a PMDF_MAPPING_FILE that reads
>
> ...
>
> PMDF-TO-VMSMAIL
>
>    PSI$%IBERPAC.*                        PSI$%ARTIX.$0$>
>
> ...

     There are two typos in the documentation.  First, notice how the second
paragraph of item 2. gives the table name as "PMDF-TO-VMSMAIL" although the
discussion is "VMSMAIL to PMDF" and the example table shows "VMSMAIL-TO-PMDF"?
Well, the correct table name is indeed "VMSMAIL-TO-PMDF".

     Now, notice how in the second paragraph the format

         channel_name|address

is given.  However, the example does not use this format.  Well, in this
regard the example is incorrect.

     So, your table should look like

       VMSMAIL-TO-PMDF

         d|PSI$%IBERPAC.*                 PSI%ARTIX.$0$>

Do not use "$%" in the right hand side.  It isn't obvious that you shouldn't
do this.  I'll look into making PMDF V4.2 treat $% and $* in the right hand
side as % and *.


     You can test your mapping as follows:

       $ pmdf test/mapping
       Enter mapping name: VMSMAIL-TO-PMDF
       Input string: d|PSI%IBERPAC.xxx
       Output string: PSI%ARTIX.xxx
       Output flags: [0,62]
       Input string: ^Z
       $

     Note that if you use a compiled configuration, then you must recompile
and reinstall before your mapping file (or changes to it) will be seen by PMDF.
If you have PMDF V4.1-6 or earlier, two bugs prevent you from being able to
use mapping files with compiled configurations.  If you have 4.1-7, then use
the command

       $ PMDF CNBUILD/OPTION

to compile your configuration.  If you have 4.1-8 or later, then none of these
problems affect you.  You can type out the file PMDF_ROOT:[EXE]IDENT.OPT to
determine which revision level of PMDF you have.  If you have 4.1-6 or earlier,
and are using a compiled configuration, then let me know and we will arrange
to get you an updated tape.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"fineberg@wupost.wustl.edu"
X-VMS-Cc: IN%"ipmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 17 Nov 92 15:25:23 +1000
Comments:     Warning -- original Sender: tag was
              CHRIS@UCSVC.UCS.UNIMELB.EDU.AU
From:         C.Chaundy@ITS.UNIMELB.EDU.AU
Subject:      RE: Additional mailing list security
Newsgroups: bit.listserv.pmdf-l

>Date: 15 Nov 1992 03:19:03 -0600
>From: fineberg@wupost.wustl.edu (Charles M. Fineberg)
>Subject: RE: Additional mailing list security
>
>c.chaundy@its.unimelb.edu.au writes:
>>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?
>
>Hmm.  When I read the 4.1 docs it seemed trivial to limit who could post
>to a list, but allowing mailed list ownership didn't seem to be there at
>all.  So what did my denseness ignore?  That is where in the manual is
>the reference to controlling who may add and delete users?

It did not get into the manuals, but was described in some mail from Dan
a few months back.  It is all done with the MAPPINGS. file for the name
MAILSERV_ACCESS (for MAILSERV commands with special characters such as
SEND/LIST, the slash is simply omitted).  BTW, controlling who can post
to lists did not make it into early printings of the manuals either :-(.

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)
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"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Vmsmail-To: NETMAIL"IPMDF@YMIR.CLAREMONT.EDU"
Date:         Fri, 20 Nov 92 03:20:42 GMT
From:         SETH@SPEECH.MIT.EDU
Subject:      Incoming notification From: prefix = SMTP%
Newsgroups: bit.listserv.pmdf-l

Hi,
        A while back I posted a note concerning occasional file
create errors of the following form:

%MAIL-E-SENDERR, error sending to user audiodev@cbgrle.mit.edu at
-PMDF-E-FCRT, File create error, Pascal status = 2, VMS statuses = 99684 and 0
-PMDF-I-TEXT, cannot create channel queue entry

        It turned out that we were mixing IN% and SMTP% protocols
in a given MAIL session. Simply requiring the use of only one
of these form solved the problem, but in hindsight brings up an
interesting question.

        Why would all incoming mail on a machine newly updated
from CMU TCP/IP to Multinet suddenly start using the SMTP prefix
on ALL incoming Internet mail? I don't seem able to determine the
cause of this change. As far as I know, it was nothing I did during
the switch from CMU to TGV code, at least knowingly... :-)


                                Thanks in advance,

                                                Seth Hall
                                                Systems Manager
                                                Speech and Sensory
                                                 Communications Groups
                                                MIT, Cambridge
From: DAN@INNOSOFT.COM (Daniel C. Newman)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: ccMail question
Date: 19 Nov 92 01:08: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%"MAC@gvg47.gvg.tek.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

> We are seeing some of the messages that PMDF leaves for ccMail to deliver
> that contain what looks like some form of line wrapping that uses the ``=''
> as the continuation character.  There message also appear to have hex
> quoting for some characters like maybe =20 means a space and maybe =9 means
> a tab.  I know this is a marginal description of the problem.  I will
> enclose a part of one of these message at the end of this message.  What is
> going on?  Any help greatly appreciated.

You're seeing line wrapping which uses the quoted printable MIME encoding.
The "=xx" means "ASCII character with hex value xx".  You see some =20 at
the end of lines because PMDF wrapped the line and was now afraid that if
it left a naked space at the end of the line some other mailer would strip
it away.  The =9 are tabs.

Send your PMDF.CNF to service@innosoft.com and some sort of indication as
to how this message originally entered PMDF.  It probably came in on some
channel with a "linelength" keyword specified.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU