fritz@cit-vlsi.Caltech.Edu (fritz nordby) (01/07/89)
In a UNIX mailbox, the first line of each message is a postmark beginning with the 5 characters "From ". Inc seems to want to remove this line from messages when reading from a unix mailbox. Is there some way to preserve this line? Perhaps inc could put it in as a "Unix-From:" header line? I've poked around a bit, but I can't seem to find any way to keep this line around. Anybody out there have any suggestions? Fritz Nordby. fritz@vlsi.caltech.edu cit-vax!cit-vlsi!fritz
wisner@killer.DALLAS.TX.US (Bill Wisner) (01/08/89)
If MH is compiled with the RPATHS configuration option defined, the envelope information contained in the From_ line will be put into a Return-Path: line.
allbery@ncoast.UUCP (Brandon S. Allbery) (01/14/89)
As quoted from <9038@cit-vax.Caltech.Edu> by fritz@cit-vlsi.Caltech.Edu (fritz nordby): +--------------- | In a UNIX mailbox, the first line of each message is a postmark | beginning with the 5 characters "From ". Inc seems to want to | remove this line from messages when reading from a unix mailbox. | Is there some way to preserve this line? Perhaps inc could put | it in as a "Unix-From:" header line? I've poked around a bit, +--------------- 2@ncoast:1 % comp -help syntax: comp [+folder] [msg] [switches] switches are: -draftfolder +folder -draftmessage msg -nodraftfolder -editor editor -noedit -file file -form formfile -[no]use -whatnowproc program -nowhatnowproc -(help) version: MH 6.5 #45[UCI] (nrtc-gremlin) of Tue Jul 8 11:38:00 PDT 1986 options: [SYS5] [MORE='"/usr/plx/more"'] [NDIR] [BERK] [OVERHEAD] [RPATHS] [BANG] [ISI] [WHATNOW] [SENDMTS] 2@ncoast:2 % _ The RPATHS option (I think; manuals aren't online) tells inc to save the From_ line as a Return-Path: header. Check the MH configuration manual for the correct option. ++Brandon -- Brandon S. Allbery, comp.sources.misc moderator and one admin of ncoast PA UN*X uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu ncoast is registering as "ncoast.org" -- watch for the official announcement! Send comp.sources.misc submissions to comp-sources-misc@<backbone>.
strike@pixel (strike) (01/01/91)
Can anyone tell me why inc has to be setuid? Martin Streicher CONVEX
dce@smsc.sony.com (David Elliott) (01/01/91)
In article <9012312114.AA15911@pixel.convex.com> strike@pixel (strike) writes: >Can anyone tell me why inc has to be setuid? Well, you don't say what kind of system you are using, but on some systems (especially when using diskless workstations) you can only do locking by creating a lock file. On those systems, you either have to make the lock directory mode 01777 (that is, 777 with the sticky bit on, which again depends on the system type) or disable locking in inc.
dcm@baldur.dell.com (Dave McCracken) (01/02/91)
strike@pixel (strike) writes: >Can anyone tell me why inc has to be setuid? I don't know exactly what kind of system you are using, but on most, if not all, flavors of SYSV the mailboxes are protected by only allowing group mail to have access to the /usr/mail directory. This is not a problem for just reading the mail, but most tools then turn around and delete your mail file after they have read it, which requires the program to be in group mail to get write access to the directory. -- Dave McCracken dcm@dell.dell.com (512) 343-3720 Dell Computer 9505 Arboretum Blvd Austin, TX 78759-7299
jik@PIT-MANAGER.MIT.EDU ("Jonathan I. Kamens") (01/03/91)
Another reason inc has to be setuid is if you use the RPOP protocol, which requires the program doing the mail retrieval to bind to a reserved port. Only the superuser can bind to a reserved port (which is, after all, why it's called "reserved" :-), so inc has to run as root. Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8085 Home: 617-782-0710