Article View: comp.mail.mush
Article #556A problem and a clarification
From: Mark Sirota
Date: Tue, 23 Oct 1990 18:54
Date: Tue, 23 Oct 1990 18:54
34 lines
2415 bytes
2415 bytes
I'm using Mush 7.1.2 7/11/90, and recently came across a problem I was
unable to solve within Mush.
There's no way to save a mailbox and leave the N flag on some message. Or
if there is, I can't find it. You can certainly use the flags command to
set the flags as you wish, but if you exit using "quit" (q), then it will
change them all to "Unread". If you exit using "exit" (x), then the changes
you've made with the flags command don't get saved. I've worked around this
problem and will probably never come across it again, but I'd be interested
in seeing any solutions within Mush.
Also, the README indicates that NO_COMMAS must be defined when using the
sendmail.cf from SunOS 4.1. I have tracked down precisely what the problem
is, I think... I feel that it's a bug in sendmail. Specifically, it's the
use of the 'R' option (e.g. "OR" in the sendmail.cf or -oR on the command
line) on a machine that mounts /var/spool/mail by NFS (e.g. any client).
What seems to be happening is that for clients, all mail is directed to the
server. This is done by taking the envelope To: addresses that are passed
by Mush as "user1@host1, user2@host2, user3@host3" on the sendmail command
line, and directing these to the server. Unfortunately, sendmail parses
these incorrectly, and ends up treating the commas as part of the address,
so it will bounce with the error "<user1@host1,>... Host unknown".
Again, the bug is in sendmail. Mush brings out the problem by passing the
commas in on the command line, which (I think) should work, and only fails
on clients with the R option set. I have reported this bug to Sun. In the
meantime, yeah, you've gotta compile with -DNO_COMMAS if you use the R
option on machines who mount /var/spool/mail from another machine by NFS.
--
Mark Sirota - University of Rochester Computing Center, Rochester NY
Internet: msir@cc.rochester.edu
Bitnet: msir@uordbv.bitnet
UUCP: {decvax,harvard,ames,rutgers}!rochester!ur-cc!msir
Technical Details
Message-ID:
<10011@ur-cc.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!rochester!uhura.cc.rochester.edu!sulu.cc.rochester.edu!msirShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!rochester!uhura.cc.rochester.edu!sulu.cc.rochester.edu!msir From: msir@sulu.cc.rochester.edu (Mark Sirota) Newsgroups: comp.mail.mush Subject: A problem and a clarification Message-ID: <10011@ur-cc.UUCP> Date: 23 Oct 90 18:54:14 GMT Sender: news@uhura.cc.rochester.edu Reply-To: Mark Sirota <msir@cc.rochester.edu> Lines: 34