HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MAC@gvg34.gvg.tek.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 14 Aug 92 01:35:27 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Install bug
X-To:         MAC@gvg34.gvg.tek.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Accounts of the form [nnn,0] have implicit privileges -- GRPPRV, I believe.
It is a very bad idea for the PMDF account to have such access; it is
certainly not needed and it can lead to trouble. We therefore don't allow
the use of an account of this sort as the PMDF account.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MITCHELL%UTHSCSA.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 12 Aug 92 19:20:43 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: two minor points
X-To:         MITCHELL@UTHSCSA, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> I hate to sound retrograde, but there are probably some sites that would
> prefer non-multipart notices.  Many people here won't have MIME-speaking
> UAs in the near future.  Novice users looking at these things sometimes
> despair before noticing that they contain readable information!

Well, the use of multipart messages for such bounce notices is
the direction being taken by the various concerns trying to standardize
the format of bounces and other error notifications.  So, it is safe to
assume that everyone will be seeing more of these (multipart error messages)
in the future.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"andrewr@itd.adelaide.edu.au"
X-VMS-Cc: IN%"info-pmdf@innosoft.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 13 Aug 92 14:41:14 GMT
From:         "David J. Knapke 317/283-9420"
              <KNAPKE%BUTLERU.bitnet@UICVM.UIC.EDU>
Subject:      RE: Mail User agents
X-To:         andrewr@itd.adelaide.edu.au
X-cc:         info-pmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l


>+ cc:Mail looked pretty good as well, but we are not sure how we are going to
>+ serve it to close to 400 Macs.  On the DOS side, its easy, we have Novell

>        We use Novell servers, as they appear as AppleShare File
>Servers, so you have both Mac's and PC's accessing the same post
>office sitting on the Novell server.

You certainly cannot connect 350-400 mac's to a file server.  The cost
of installing 3 (100 Mac users per server) additional Novell file servers
would be slightly prohibitive.

David J. Knapke                       Knapke@ButlerU.BITNET
Computer Center                          Assistant Director
Butler University                     Information Resources
Indianapolis, IN  46208                      (317) 283-9420
USA                                     Fax: (317) 283-9740
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",IN%"INFO-PMDF-REQUEST@INNOSOFT.COM"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 20:11:37 GMT
From:         SERENE_RC@CORNING.COM
Subject:      REMOVE FROM DISTRIBUTION LIST....
X-To:         INFO-PMDF@YMIR, INFO-PMDF-REQUEST@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l

PLEASE REMOVE MY NAME FROM YOU DISTRIBUTION LIST AT THIS TIME.

THANKS..   REGIS C. SERENE
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: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 01:32:49 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Changing To: header on alias list
X-To:         cvm@NAUVAX.UCC.NAU.EDU, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

There should be no reason to put the actual recipient in the To: header.
This information is available in the message envelope up until the instant
of final delivery, and all the mechanisms that need this information can
reference it. Once the message is delivered it is abundantly clear who it
is to and this information becomes superfluous.

So the answer is "no, there is no way to do this because there is no reasn
we know of to work this way". If you have a reason for wanting things to
work differently please elaborate on it further and we'll see what we can
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%"info-pmdf@ymir.claremont.edu"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 21 Aug 92 20:55:34 GMT
From:         "Cheri Weaver..Information Technology...849-2850"
              <WEAVER@SHERIDANC.ON.CA>
Subject:      pmdf-mr
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l


One of the questions asked during the configuration of pmdf-mr
is:  Convert WPS-PLUS to ASCII ?  I chose NO because I had already
answered yes to a similar question from the installation of V3.0 of
ALLIN1.  The question was "do you want outgoing WPS-PLUS docs converted
to ASCII?

I assumed that it is the same function, but if so why does PMDF offer
it if ALLIN1 already does it.

Is this one of those cases where it isn't getting done quite right
and I should be letting PMDF do the converts?  :-)

Thanks for any help
Cheri
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"coleve@cc.uvcc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 21:46:24 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Problem with printer channel?
X-To:         coleve@cc.uvcc.edu, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>> Apart from the fact that I will have to move to AVPL pairs (it would have
>> been nice to default mailboxes that are not AVPL pairs to just 'Attention:'),
>> I assume this other behaviour is most definitely a bug in the printer channel
   .
>
>  I'm trying a rewrite rule like:
>     HARDCOPY.UVCC.EDU        /AT=$U@HARDCOPY.UVCC.EDU
>
> seems to do the job...

Sure, that will work provided you don't mind rendering illegal all formerly
legal printer channel addresses.  The legal address

   "/at=Dan Newman/ms=broom closet/"@hardcopy.uvcc.edu

will be rewritten to the illegal address

   /AT="/at=Dan Newman/ms=broom closet/"@HARDCOPY.UVCC.EDU

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Fri, 21 Aug 92 21:08:03 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: PMDF-FAX installation and [ghostscript]fontmap.
X-To:         bob@camb.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>> in V4.2 we'll make the installation dio what we do with things like
>> master.com: rename the previous master.com to master.old.
>
> Thanks.  That'll be an improvement.  But using the case of master.com
> as an analogy, there you have made changes to avoid the necessity of
> user editing of the command file.  Is there a way that you could do
> the same thing here?

You're taking this up with the wrong people.  The people to disucess this
with are the Ghostscript people.  Sure, I could make PMDF-FAX specific
changes to Ghostscript, but this is one area I absolutely refuse to mess with
unless it is absolutely necessary to (Ghostscript's initialization files).

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"@mr.lilly.com:ipmdf%ymir.claremont.edu@in""
          @mr.lilly.com:ipmdf%ymir.claremont.edu@in"
Autoforwarded: false
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Importance: normal
Priority: non-urgent
Sensitivity: Private
UA-content-id: 11686A890800
X-Hop-count: 2
Date:         Thu, 13 Aug 92 16:41:16 GMT
From:         "Brett E. Bowman" <BOWMAN_BRETT_E@LILLY.COM>
Subject:      RE: two minor points
X-To:         "@mr.lilly.com:ipmdf%ymir.claremont.edu@in"
              <ipmdf%ymir.claremont.edu@in>
Newsgroups: bit.listserv.pmdf-l

Here at Lilly, we have been piloting Mailworks as a "mail solution".  I really
like receiving the Postmaster's bounce messages via MIME and PMDF-MR so that I
get the message as an attachment.  It is very convenient.  Thanks go to
Innosoft for getting this implemented.
                                                Brett E. Bowman
                                                Postmaster
                                                Eli Lilly & Company
                                                BOWMAN_BRETT_E@LILLY.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF
X-VMS-Cc: GHC
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 21 Aug 92 02:28:52 GMT
From:         Gerson H Cohen <GHC@VGER.NIDDK.NIH.GOV>
Subject:      WAIS and GOPHER
X-To:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

I have recently been made aware of WAIS and GOPHER and am trying to get
them on my system.  I have been able to find and impliment Gopher as it
was fortunately coded for VMS with MultiNet in mind.  WAIS is another
story.  Has anyone seen or does anyone have a copy of this for MultiNet?

Gerson Cohen

-
Dr Gerson H Cohen
National Institutes of Health
Bldg 2, Room 312
Bethesda, MD  20892
'Phone: (301)496-4295
Internet: ghc@vger.niddk.nih.gov
BITNet:   ghc@nihklmb
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
Date:         Thu, 20 Aug 92 19:52:26 GMT
From:         Robin Goldstone <robin_goldstone@MACGATE.CSUCHICO.EDU>
Subject:      deliver and 'vacation' processing
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

I have never used DELIVER before and I though I would experiment around with it
to set up a simple "vacation" process, such that whenever anyone sends mail to
my account, they would get a message back saying I am on vacation.  My
MAIL.DELIVERY looks like this:

* * * A L DELIVER.LOG
* * * A E @VACATION.COM
* * * A D

The first line is for debugging purposes. The second line invokes a DCL program
which sends the vacation message back to the user.  The third line delivers the
message to the mailbox.

I am having trouble with my VACATION.COM procedure.  All I want it to do is
send a message back to the user.  It looks like this:

$ MAIL VACATION.TXT 'FROM'

The problem is the value of the symbol 'FROM' which DELIVER creates.  According
to the DELIVER.LOG file, the symbol looks like this:
$ FROM == "IN%""RGOLDSTONE@oavax.csuchico.edu""  ""Robin Goldstone"""

When I try to do:
$ MAIL VACATION.TXT 'FROM'
I get the error:
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
 \"Robin Goldstone"\

I know this is a quote problem.  If I do:
$ mail vacation.txt "IN%""RGOLDSTONE@oavax.csuchico.edu""  ""Robin Goldstone"""
it works fine.  So somewhere some quotes are getting stripped.  DCL and quotes
always gives me fits.  Can someone tell me what is happening and how I can fix
it?

Also, another problem.  The last line of MAIL.DELIVERY is:
* * * A D
which causes the message to be delivered "normally."  However, I noticed that
the delivered message has a header on it.  I have the 'headeromit' keyword on
my 'l' channel, but DELIVER seems to be ignoring this.  Is this a bug?

Robin Goldstone, CSU Chico
From: tkslen@ubvms.cc.buffalo.edu (Lenny Miceli)
Newsgroups: bit.listserv.pmdf-l
Subject: vms v5.5-1 and pmdf v4.1-1 problems.
Date: 13 Aug 92 14:17:57 GMT
Reply-To: tkslen@ubvms.cc.buffalo.edu (Lenny Miceli)
Organization: SUNY at Buffalo, Systems group


I am upgrading to vms v5.5-1 and pmdf v4.1-1 this monday.  Does anyone know of
any problems/gotchas with the combination of these two?

Thanks,
  Lenny Miceli
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.bitnet"
X-VMS-Cc: MIKE
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 21 Aug 92 20:21:04 GMT
From:         "Mike Hannon; UCD Physics; (916)-752-4966" <MIKE@UCDHEP>
Subject:      Mail delivery stopped
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

Greetings.  We're using PMDF V3.2 on a VMS 5.4-2 VAXstation 3100 model 76.  We
seem to be having problems with mail delivery.  We run Multinet V3.0 as our
TCP/IP and Jnet V3.5.  The problems may or may not have come upon us suddenly.

I noticed yesterday that I had very few network mail messages, considering all
the mailing lists I'm on.  Also, one of our users complained that he had not
received Internet mail that he sent to himself from an outside site.  At that
time the VAX had been up for about 153 days, so I figured that this was no big
deal.  I.e., s**t happens, very large buffers eventually fill up, etc., etc.
So I rebooted the VAX, expecting to clear up the problem.  The reboot didn't
help.

I have been receiving and sending Internet, Bitnet, and HEPnet mail on a daily
basis from and to sites all over the world, so I had no reason to expect
problems with PMDF.  But I noticed that PMDF_ROOT:[QUEUE.L] had over 1700 files
in it, so I executed the command:

                        $ @pmdf_root:[exe]master L

This caused me to get hundreds of mail messages, some dated as long ago as May
of this year.  Apparently a large number of messages also went out over the net.

I continued to test, and messages did not get delivered unless I executed
MASTER.COM by hand.  I then did:

                        $ @sys$startup:pmdf_submit_jobs

This caused messages to be processed, but only at the default time interval of
four hours.  I now have this job run automatically every half hour, by setting
the logical name PMDF_POST_INTERVAL to 00:30:00.  This is tolerable, I guess,
but I'm pretty sure I didn't do that before.

We seem to be on very shaky ground with a system which we count on to be
reliable, and I don't know why (maybe we're not in Kansas any more?).  Can
anybody help with this.  The only change in the system files that I can recall
that I made lately was to put the following at the start of SYLOGIN.COM:

$       VERIFY = 'F$VERIFY(0)
$       MODE = F$MODE ()
$       IF (MODE .NES. "INTERACTIVE") .AND. (MODE .NES. "BATCH") THEN EXIT

Previously I had not turned off verify, and I had tested only for MODE equal to
NETWORK for the exit.  The above was added to allow users to rlogin to the VAX
from our Ultrix systems.

Thanks.

                                        - Mike
-----------
Mike Hannon                                 mike@ucdhep     (Bitnet)
ucdhep::mike             (HEPnet)           42385::mike     (HEPnet)
mike@ucdhep.ucdavis.edu  (Internet)         916-752-4966    (Telephone)
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@innosoft.com"
X-VMS-Cc: SROSS
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 13 Aug 92 23:54:31 GMT
From:         SROSS@CGNET.COM
Subject:      listserv WELCOME message
X-To:         info-pmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l

I have been experimenting with the listserver software provided with
PMDF4.1-10.  I set up a list using the procedure described in the manual.

When I issue the command:   SUB TEST-L somebodyelse@cgnet.com
and "somebodyelse" is not the userid that I'm sending the request from,
the Welcome message gets automatically sent TO MY ACCOUNT and
NOT TO SOMEBODYELSE.  The subcription confirmation, however, does
get sent to both addresses.

Is this the intended functionality?

-Steve Ross, CGNET Services International
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"dsroberts@beckman.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 21 Aug 92 17:51:10 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Deliver and MM-32
X-To:         dsroberts@beckman.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> We just noticed a problem with this today.  DELIVER seems to have stopped
> working with MultiNet MM as of PMDF 4.1.  Perhaps a logical needs to be set or
> something?

If it was working before and has now stopped, then someone has probably changed
something on your system (e.g., gotten rid of the batch queue for DELIVER
processing, cut over to the PMDF Process Symbiont and not set up a queue other
than MAIL$BATCH for DELIVER processing to occur in, defined one of the MultiNet
or PMDF logicals which inhibit delivery of any mail to MM, set a PMDF switch
in the PMDF_ option file to inhibit any delivery to MultiNet MM).  The bottom
line is that if it was working before and isn't now, it probably means that
somebody changed something on your system.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ip_boss@degsyd.syd.deg.csiro.au"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>
Date:         Mon, 17 Aug 92 10:21:23 GMT
From:         John C Klensin <KLENSIN@INFOODS.MIT.EDU>
Subject:      RE: Mail User agents
X-To:         ip_boss@degsyd.syd.deg.csiro.au
X-cc:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

>>      So the concept employed is that there is one central place
>> that stays up all day, and you can access from all over the place. The
>> problem now is that PC and Mac users expect a GUI as opposed to the
>>...
>That's why "store and forward" methods like POP have been very popular for
>PCs and MACs of late.  There some very nice looking POP client programs
>available to overcome the issue of not having your personal computer
>turned on all the time.

Jack,
  While not disagreeing with anything you've said, I think a
terminology clarification would be helpful before this discussion goes
down the path of a parallel discussion about these mail-receiving
protocols...
  Strictly speaking, one could easily construct "store and forward", and
a solution to the shut-off workstation problem with SMTP alone.  You
would set up MX records for the workstations that would deposit the mail
somewhere else if the workstation was off, e.g.,
     workstation MX 0  workstation
     workstation MX 10 postoffice
You would then set "postoffice" up with a channel (or equivalent) for
delivery to local workstations distinct from its channels for delivery
to the rest of the network.  And you would set a really aggressive retry
schedule on that channel s.t., when the workstation came up, it would
get its mail dumped on it in rather short order.  You'd be effectively
polling its SMTP port all the time, and delivering as soon as it came
up.

Is this a good idea?  Well, no, and for a number of reasons.  But it is
"store and forward".   POP et al., which depend on the workstation
announcing to the server that they have come up and then retrieving the
mail, are more like "store and fetch".
   --john

  Is th
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Columbia University
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:         Thu, 20 Aug 92 18:07:05 GMT
Comments:     Warning -- original Sender: tag was usenet@NEWS.COLUMBIA.EDU
From:         Wei Dong Wu <wdw3@CUNIXB.CC.COLUMBIA.EDU>
Subject:      RE: question (thanks). More question
X-To:         ipmdf-newsgate@mccall.UUCP
Newsgroups: bit.listserv.pmdf-l

Thanks Dan and Ned for your lightening fast answer to my question of sending
bitnet mail from a internet-only machine.
I run PMDF on a two-node VAXcluster. Each node has a valid internet host
name. PMDF images are loaded on both nodes but there is only one cluster-
wide MAIL$BATCH queue. I want different local host appear on the return
address when people send mail from different node. So I create a PMDF.CNF
for each node with the host name for l channel pointing to each node. This
works fine when I send mail from the node on which the MAIL$BATCH is running.
But when I send mail from the other node, the local host name apprears twice
in the return address, like
        From: user@localhost@localhost
Any idea how this happen? Or is there other better way to do this? Thanks.


Weidong Wu
wdw3@cunixb.cc.columbia.edu

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"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 13 Aug 92 06:01:19 GMT
From:         "David J. Knapke 317/283-9420" <KNAPKE@BUTLERU>
Subject:      Mail User agents
X-To:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

We finally making efforts (and aparently have money too, wow) to have a
complete mail solution.  We have both Macs and IBM compatibles on people's
desk, very few VTs.  We would like a mail system that generally stores mail
on a host, getting people to backup is not fun around here.

I have looked at a couple of packages, but have not found the product that
fits the mold here just yet.  Believe it or not, talking with Digital,
MailWorks (A1 mail) seems to be most intersting to us.  A couple of questions
that the Rep couldn't answer though, what transports/protocals can you run
with the MailWorks client (both environments)??

We also looked at QuickMail, yuuuuk!

cc:Mail looked pretty good as well, but we are not sure how we are going to
serve it to close to 400 Macs.  On the DOS side, its easy, we have Novell
servers.  There has been discussion of the cc:Mail channel in PMDF and how
to push mail back and forth, that sounds good but a little ruff as far as
the particulars of pushing the files back and forth.  Ned mentions MIME
translation into cc:Mail, but said there were problems with multi-part mail
(if I recall correclty).  That confuses me since cc:Mail had the ability to
have multiple enclosures, or am I missing something??

Other considerations, Ithink Eudora is out for spoofing reasons.  I'm looking
at MicroSoft Mail, which is not impressive if you want to have good clients for
both platforms.  They are basically two different products that have a
gateway that runs betweent them, pretty klunky looking so far.

Anything else someone could suggest?  I would certainly appreciate any
info to help us out.

I wonder if this will divert peoples attention away from fueding??
(Sorry, I couldn't resist.  I think that we are lucky to have, as
someone else pointed out, a vender that is sincerely concerned about
there niche product and standards that revolve around it.)



David J. Knapke                       Knapke@ButlerU.BITNET
Computer Center                          Assistant Director
Butler University                     Information Resources
Indianapolis, IN  46208                      (317) 283-9420
USA                                     Fax: (317) 283-9740
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU