HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.mx
Subject: Routing mail
From: "Herve GILIBERT, Universite de St-ETIENNE."
Date: Mon, 09 Nov 1992 11:52:02 +0100
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

Thanks to everybody for the numerous replies I got, but I didn't get any
solution, I think I didn't express myself correctly, so I'll ask my question
in a more general way :
Many nodes (generaly workstations) on my domain (not only my cluster) are often
unreachable, I'd like mails sent to those nodes, from the outside world, not to
be immediatly bounced to the sender but to be "buffered" into my MX node and
localy tried (for ie 48 hours) until the target node becomes reachable or
bounced to the sender if it doesn't becomes in operation after 48 hours.
The differents solutions I tried using MX RRs and define path command causes
mails looping from and to the MX node.
Does anybody has implemented a solution and can send me his MX RRs and DEF path
commands ?
Thanks in advance.
Herve
---------------------------------------------------------------------
                Herve GILIBERT                          UUUU     UUUU
                Universite Jean Monnet St-Etienne       UUUU     UUUU
                23,Rue du Dr. P. Michelon               UUUU     UUUU
                42023 ST ETIENNE Cedex 2                UUUU     UUUU
Tel : 33 77 42 15 79                                    UUUU     UUUU
Fax : 33 77 42 15 75                                    UUUU     UUUU
RFC822: gilibert@univ-st-etienne.fr                      UUUUUUUUUUU
DECNET: 51.31::gilibert                                   UUUUUUUUU
From: Irv Eisen <irv@ccstat.mc.duke.edu>
Newsgroups: vmsnet.mail.mx
Subject: RE: New mail announcement broadcast to users should be clusterwide
Date: Wed, 11 Nov 1992 14:10:57 EST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

<We have installed MX3.1C on VMS 5.5-1 .
<The MX processes are running only on our boot node in the LAVC cluster.
<The new mail flag in UAF is set correctly, but the broadcast is sent only
<to the logged in terminals of the corresponding user at the boot node and not
<to this user clusterwide as what is expected like VMS mail. This is very
<annoying, because our users should'nt log in on the boot server of course.
<
<Is that already a known problem? I'm new in this newsgroup.
<
<Thanks, Heribert

You need to define the logical MAIL$SYSTEM_FLAGS to 3. This "Directs MAIL
to set the cluster breakthrough flag when issuing the $BRJTHRU service to
notify the recipient of new mail. This flag is only used in VAXcluster
system and, typically, only in homogeneous VAXclusters (in other word, flag
1 is also set)." Use the qualifiers /system and /exec.

See the discussion in the Mail manual Chapter 9, System Management and Mail,
page 14 for all the options.

=========================================================================
| Irv Eisen, Systems Manager      Bitnet  : EISEN001@DUKEMC             |
| Cancer Center                   Internet: IRV@CCSTAT.MC.DUKE.EDU      |
| Box 3958                                                              |
| Duke University Medical Center  Voice   : (919) 286-7774              |
| Durham, NC 27710                Fax     : (919) 286-3956              |
=========================================================================

Newsgroups: vmsnet.mail.mx
From: madison@tgv.com (Matt Madison)
Subject: Re: smtp server/null addresses
Reply-To: madison@tgv.com
Organization: The Foundation for Dinner Peas
Date: Mon, 9 Nov 1992 19:34:12 GMT

In article <009635A4.F4B7E700.6638@MNSMC1>, sysmail@MNSMC1.MNSMC.EDU writes:
>220 MNSMC1.MNSMC.EDU MX V3.1C SMTP SERVER READY AT MON, 09 NOV 1992 10:21:03
>sam: HELO sam.mnsmc.edu
>250 Hello, sam.mnsmc.edu
>sam: Mail from: <>
                ^-------------this is the problem

>501 Invalid Address: <>
>sam: 501, unexpected response from remote smtp server 501

There should be no blank between the colon and the left angle-bracket.

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
From: <ac932@medina.freenet.edu>
Newsgroups: vmsnet.mail.mx
Subject: HELP
Date: Thu, 5 Nov 92 18:23:39 -0500
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List


HELP
Newsgroups: vmsnet.mail.mx
From: madison@tgv.com (Matt Madison)
Subject: Re: VMS MAIL personal names / From: lines
Reply-To: madison@tgv.com
Organization: The Foundation for Dinner Peas
Date: Tue, 10 Nov 1992 18:05:17 GMT

In article <1dnuj5INN3ep@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>In article <0096365E.615FEA60.12219@EIMONI.TUWIEN.AC.AT>, "Franz Schoenbauer,Computer Science,Vienna,Austria, +43-1-58801-4126" writes:
>>I'm using MX V3.1C, VMS 5.5-1 and i have set a personal name in
>>VMS-mail. When i send a message out it appears as
>>
>>From: "Franz Schoenbauer,Computer Science,Vienna,Austria, +43-1-58801-4126"
>                         ^                ^      ^
>>      <system@EIMONI.TUWIEN.AC.AT>
>
>>at the unix box. Is this a valid from line ?
>
>No.  The commas aren't allowed.  The basic format is fine, but you can't use
>special characters ("(",  ")",  "<",  ">",  "@", ",",  ";",  ":",  "\",  ".", 
>"[",  "]", or the quote character (") itself) in your personal name.

Uh, actually the answer is Yes.  MX_MAILSHR scans your VMS MAIL personal name
and quotes it if it contains one of the "specials", as it did in the above
From: line.  That makes it OK.

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
From: Larry Horn <hornlo@okra.millsaps.edu>
Newsgroups: vmsnet.mail.mx
Subject: RE: New mail announcement broadcast to users should be clusterwide
Date: Wed, 11 Nov 1992 12:56:56 CST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List


>The new mail flag in UAF is set correctly, but the broadcast is sent only

In your system startup command file(s):

    $ define/system/exec  MAIL$SYSTEM_FLAGS 7
                                                1: homogeneous cluster,
                                                2: cluster breakthru,
                                                4: time in notification
                                               ---
                                                7

This is in the MX docs.  Also, see Digital's docs for details.
MAIL$SYSTEM_FLAGS must have 1 and/or 2 [I don't recall for sure] set
(and reflect reality <grin>) for all nodes to be notified.

- ---------------------------------- signed: 11-NOV-1992 12:54 C*T (USA) --- -
    Larry Horn / Millsaps College / Jackson, MS / hornlo@okra.millsaps.edu
- -------------------------------------------------------------------------- -
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: vmsnet.mail.mx
Subject: RE: Mail routing
Date: 9 Nov 1992 20:33:16 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <00963368.088EF3C0.26171@CCVAX.CCS.CSUS.EDU>, "John F. Sandhoff" <syssand@CCVAX.CCS.CSUS.EDU> writes:
=>> I'd like to have E-mails sent to any node on my domain to be routed
=>> through my MX node called STROPH.
=
=> What's called for are a list of the exceptions, known only to stroph, where
=> the name server isn't used.
=>
=> DEFINE PATH "node1"                    SMTP/ROUTE="node1.univ-st-etienne.fr"
=> DEFINE PATH "node1.univ-st-etienne.fr" SMTP/ROUTE="node1.univ-st-etienne.fr"
=
=Almost. You need to define all possible names as LOCAL. For example, on
=my cluster of five CPU's here's a snippet of MCP SHOW:
=
=Domain-to-path mappings:
=  Domain="ccvax1.ccs.csus.edu", Path=Local
=  Domain="ccvax1.csus.edu", Path=Local
=  Domain="ccvax1", Path=Local
=  Domain="[130.86.89.1]", Path=Local
=  Domain="ccvax2.ccs.csus.edu", Path=Local
=  Domain="ccvax2.csus.edu", Path=Local
=  Domain="ccvax2", Path=Local
=  Domain="[130.86.89.2]", Path=Local
=
=I then use MX records in the Domain Name Service config file to point all
=of these machines (ccvax1, ccvax2...) to the actual machine running the
=SMTP_Server.
=
=And as was mentioned, ORDER IS IMPORTANT. These must come before the
=wildcards!

Either you or I misunderstand his problem.  As I understand it,
NODE1.UNIV-ST-ETIENNE.FR is NOT clustered with STROPH, so it CAN'T be a local
delivery.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
Newsgroups: vmsnet.mail.mx
From: DAHMS@ifk20.mach.uni-karlsruhe.de (Heribert Dahms)
Subject: New mail announcement broadcast to users should be clusterwide
Organization: University of Karlsruhe, FRG (Dept. of Mechanical Engineering)
Date: Wed, 11 Nov 1992 16:50:31 GMT
X-News-Reader: VMS NEWS 1.20

We have installed MX3.1C on VMS 5.5-1 .
The MX processes are running only on our boot node in the LAVC cluster.
The new mail flag in UAF is set correctly, but the broadcast is sent only
to the logged in terminals of the corresponding user at the boot node and not
to this user clusterwide as what is expected like VMS mail. This is very
annoying, because our users should'nt log in on the boot server of course.

Is that already a known problem? I'm new in this newsgroup.

Thanks, Heribert
Newsgroups: vmsnet.mail.misc
From: nreadwin@micrognosis.co.uk (Neil Readwin)
Subject: Anyone using A1MAIL/UMC?
Organization: Micrognosis, London, UK.
Date: Thu, 12 Nov 1992 13:14:19 GMT

Is anyone out there using UMC to gateway stuff into A1MAIL? If so, do you
want to swap horror stories about how brain-damaged it is :-)
-- 
 Phone: +44 71 815 5283  E-mail: nreadwin@micrognosis.co.uk
 Anything is a cause for sorrow that my mind or body has made
From: dmpm%dukemc.bitnet@ymir.claremont.edu (James Dryfoos- Postmaster)
Newsgroups: vmsnet.mail.pmdf
Subject: Very large alias and reverse databases?
Date: 11 Nov 92 19:00:34 GMT
Organization: Duke University Medical Center, Durham NC, USA
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Nov 1992 14:00:34 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR0UACWNGI8ZGRCZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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
   =======================================================================
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Additional mailing list security
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 13 Nov 1992 00:04:28 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Nov 1992 00:04:28 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR2ZW9N2UQ8ZH1SM@YMIR.CLAREMONT.EDU>
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

Yup, some of that was added after the manuals went to press. It depends on
the generation of manuals you have. The Bookreader materials are, as always,
the most current. (Just like DEC manuals, come to think of it.)

				Ned
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: SMTP and Long Lines Supported ?
Date: 5 Nov 92 05:01:33 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Nov 1992 22:01:33 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQRPA98BKI8ZFHJL@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

>	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: shah.khatri@asu.edu
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Help setting up mailing lists
Date: 12 Nov 92 20:41:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Nov 1992 13:41:00 -0700 (MST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR2C5UTTUA8ZGXTM@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
X-Mailer: Microsoft Mail V3.0


Thanks, Dan!

 ----------
>From: Daniel C. Newman
>To: Shah.Khatri; IPMDF
>Subject: Re: Help setting up mailing lists
>Date: Wed, Nov 11, 1992 12:03PM
>
>> We have a news server with newsgroups such as email.msmail.appletalk.
I'd
>> like to create MAILSERV mailing lists with the same name, as far as the
user
>> is concerned.
>>
>> If I create .DIS files by replacing periods with underscores, users also
>> will have to replace periods with underscores when they SUBSCRIBE.
>>
>> Can the mapping file be used to change the command sent to MAILSERV?  For
>> instance, map SUBSCRIBE EMAIL.MSMAIL.APPLETALK ... to SUBSCRIBE
>> EMAIL-MSMAIL-APPLETALK ...?
>
>For the time being, you're only option is to change the list names.  We'll
>look
>into adding for 4.2 a mapping table to map list names to mailing list file
>names.
>
>Note that the source to MAILSERV ships with PMDF.  Some simple code
additions
>will allow periods in list names to be translated to hyphens.  In a
separate
>message I'll send you such a modified version of MAILSERV.  The
translations
>are hard-coded and do not use mapping tables.
>
>Dan
>
From: laue%vtcc1.bitnet@ymir.claremont.edu (Eliza Lau)
Newsgroups: vmsnet.mail.pmdf
Subject: How to reroute bitnet mail to a unix machine
Date: 6 Nov 92 15:05:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 10:05 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTMLE23368ZFXI6@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

We just installed PMDF 4.1 on VTCC1, our campus's hub for VMS bitnet mail.
One of the VMS nodes on campus, VTMATH, will be replaced by a Unix machine.
I want to define VTMATH as an alias for VTCC1 in JNET and reconfigure PMDF to
route all the bitnet mail going to VTMATH to their new location math.vt.edu.

Please tell me which of the following rewrite rules should I put in PMDF.CNF:

VTMATH                                  $U@math.vt.edu
VTMATH.BITNET                           $U@math.vt.edu

*OR*

VTMATH                                  $U%math.vt.edu@mtcp-daemon
VTMATH.BITNET                           $U%math.vt.edu@mtcp-daemon

------------------------------------------------------------------------------
 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
------------------------------------------------------------------------------
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Compatibility of VMS 5.5 with other software
Date: 13 Nov 92 16:31:52 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Nov 1992 09:31:52 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR3JQ3UIXE8ZGTQ9@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"a866700@hp9000.csc.cuhk.hk"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> We're running VMS 5.3-1 on a VAXcluster consists of MicroVAX 3400,
> MicroVAX II, and 3 x MicroVAX 2000.  They also have PMDF 4.0, Jnet 3.5,
> and UCX 1.3a running on.  We'll upgrade to VMS 5.5 and UCX 2.0 (TCP/IP
> for VMS) shortly, but I wonder if there's any incompatibility with these
> software after the upgrade, and if there's any problem with the system
> after the upgrade.

PMDF V4.0 will run just fine with VMS 5.5.  With UCX 2.0 you will want to
turn off the new UCX SMTP server and leave PMDF's running.

Dan
From: mvbr@se.alcbel.be
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF-MR request
Date: 13 Nov 92 13:25:45 GMT
Reply-To: mvbr@se.alcbel.be
Organization: Alcatel Bell Telephone
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Nov 1992 13:25:45 +0000 (GMT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Return-Path: guest@se
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR3K3ZOTYQ8ZFQYH@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"alcbel-list-pmdf@alcbel.UUCP"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT



--
We want to use PMDF-MR to be able to exchange mail
between BMEMO users on MVS and VMSMAIL/Unixmail users via Digitals Mailbus
concept.
I assume installing PMDF-MR will not be so difficult. Most problems will
probably occur in setting up the correct configuration file. Can anyone
provide me with an example to realize this ? If required, I can give more info
on the configuration.
Greetings
-----------------------------------------------------------
Marc Verbruggen                 tel : 03.240.94.19
Alcatel Bell Telephone          fax : 03.240.99.50
F. Wellesplein 1                email : mvbr@se.alcbel.be
B-2018 Antwerp
Belgium

"System Manager's Headaches Are Not Cured With Aspirin,
 There Is A Better Way ..."
From: johnson@northeastern.edu (I am only an egg.)
Newsgroups: vmsnet.mail.pmdf
Subject: New Mail Interface
Date: 6 Nov 92 18:38:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 13:38 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQTUB34EPE8ZFYHV@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
X-Vms-Cc: JOHNSON
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


     Hi.

     At an INTEROP last year Dan told me that INNOSOFT was working on a
replacement mailer for VMS that (as I recall)

     o  used the existing VMS mail files and structure

     o  had all the fuctionallity of the existinf VMS mail interface

     o  would accept addresses DECNET or Internet form, with or
        without IN% and do the right thing with them

     I offered to BETA same and am still MORE than willing.  My users
don't like IN%.

     Is it close to BETA yet?  Please, please, please.

Chris Johnson
Northeastern University.
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF protocol error
From: "Jos Joosten, AGRONET Netwerkbeheer" <j.joosten@tfdl.agro.nl>
Date: 05 Nov 1992 11:09 +0100 (MET)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 05 Nov 1992 11:09 +0100 (MET)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQRY155H8Y8ZFKGS@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
X-Vms-Cc: GROOTHEEST,JOOSTEN
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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.
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: New Mail Interface
Date: 6 Nov 92 21:50:50 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Nov 1992 14:50:50 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GQU2TU0F028ZFVXO@YMIR.CLAREMONT.EDU>
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