<<< Date Index >>>     <<< Thread Index >>>

Re: procmail with mutt



* Michelle Konzack <linux4michelle@xxxxxxxxxx> [2006-01-17 16:35 +0100]:
> Am 2006-01-14 00:27:11, schrieb Nicolas Rachinsky:
> 
> > He does _not_ deliver to a maildir (that could work). Instead he's
> 
> right, because it is "mh"

It isn't. It's just a directory containing files which happen to
contain mails.


>From man procmailrc:
| If  it  is  a directory, the mail will be delivered to a newly created,
| guaranteed to be unique file named $MSGPREFIX* in the specified direc-
| tory. 

He was doing that.

| If  the  mailbox name ends in "/.", then this directory is pre-
| sumed to be an MH folder; i.e., procmail will use the  next number  it
| finds  available.

Not that.

> Not right, because mutt CAN read mailbox, maildir AND mh
> 
> What about reading the mutt manual?
>
> set mbox_type=mh        # set it to mbox, maildir or mh

You should have done that.

   Mutt supports reading and writing of four different mailbox formats:
   mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there
                                                   ^
   is no need to use a flag for different mailbox types. When creating
   new mailboxes, Mutt uses the default specified with the $mbox_type
   variable.

According to the descriptions of the different types following the
above paragraph, none of these formats is just a directory of
arbitrarily named files.

If he had created a mh folder, mutt should have opened it (without any
need to set mbox_type, which is only used to set the type of folders
created by mutt).

Nicolas

-- 
http://www.rachinsky.de/nicolas