Re: Debian mutt-ng_0.0+20050831-1_i390.deb

On Sun, 11 Sep 2005 the mental interface of
Rocco Rutte told:

> Hi,
> 
> * Elimar Riesebieter [05-09-11 17:38:28 +0200] wrote:
> >On Sun, 11 Sep 2005 the mental interface of Peter J. Holzer told:
> >>On 2005-09-08 22:38:20 +0200, Elimar Riesebieter wrote:
> 
> >>> Why are your reading your mail in /var/spool/mail?
> 
> >>Because that's where the mailbox is on his system?
> 
> *LOL*
> 
> >Right, but it is just a spooldir with unreliable user rights.
> 
> In such cases it's the admins fault. Mailspools outside of $HOME
> have to be created with 0775 and root:mail and even better with
> the sticky bit set. I even saw 1777 for the dir and 0660
> ($user:mail) for the spools...

This seems to be nfs exported var/spools? Hey, come on, spooldirs are
always local and in networks the admins have to sort them in $MAIL or
provide them via imap. IMHO /var/mail is only for picking up mails.

> >It is recommended to sort local mail in $HOME/"whatever you
> >want". Tools like procmail or getmail or maildrop or ... are very
> >useful to do that.
> 
> But then you need enough storage for mail in $HOME. I've seen
> installations where $HOME and /var/mail came from different
> machines with huge disks. I even saw installations were there were
> quotas on $HOME but not on $MAIL so people were wrapping lots of
> data in MIME mails in $MAIL instead of $HOME (hint: with muttng
> one can define where to store postponed mails). The others, not
> me, of course ;-))

ACK, but in that case $MAIL has to be in a $HOME like
environment ;-)

Elimar


-- 
  You cannot propel yourself forward by
  patting yourself on the back.