Article View: comp.sys.masscomp
Article #120Re: Mailx on System 5
From: dale chayes
Date: Wed, 02 Mar 1988 16:04
Date: Wed, 02 Mar 1988 16:04
18 lines
1225 bytes
1225 bytes
In article <451@penguin.UUCP>, jac@penguin.UUCP (James Carter) writes: > .... a 3B1 and SVR3 .. having trouble with Mailx > [after] responding .... mailx will skip > the next sequential message This is problem also occurs with the Masscomp version of mailx. As far as I can tell, this is not something the user can control, and without source, it will be a bit tough to resolve. Our approach is to find a better mailer. We are looking at MMDF and MUSH as possible solutions. -- Dale Chayes Lamont-Doherty Geological Observatory of Columbia University usmail: Route 9W, Palisades, N.Y. 10964 voice: (914) 359-2900 extension 434 fax: (914) 359-6817 usnet: ...philabs!lamont!dale
Technical Details
Message-ID:
<3346@soma.bcm.tmc.edu>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!nuchat!uhnix1!soma!masscomp-requestReferences:
<451@penguin.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!nuchat!uhnix1!soma!masscomp-request From: dalesys@lamont.ldgo.columbia.edu (dale chayes) Newsgroups: comp.sys.masscomp Subject: Re: Mailx on System 5 Message-ID: <3346@soma.bcm.tmc.edu> Date: 2 Mar 88 16:04:20 GMT References: <451@penguin.UUCP> Sender: masscomp@soma.bcm.tmc.edu Organization: Lamont-Doherty Geological Observatory N.Y. Lines: 17 Keywords: Mailx Sys5 Summary: mailx bug? happens on Masscomp's too, you are not alone Approved: masscomp@soma.bcm.tmc.edu Status: R