[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Should I Abandon Mutt and Exim4?



On Tue, Jan 17, 2006 at 12:03:20AM +1300, Chris Bannister wrote:
} On Thu, Jan 12, 2006 at 06:41:52PM -0500, Gregory Seidman wrote:
} > 1) procmail -- I still don't properly understand how to write my own
} >                recipes; all of mine are cut and paste or modified from cut
} >                and paste
} 
} Have a look at the procmail-lib package.

Very interesting. I'll dig through it.

} > 2) exim4 w/ maildir -- This took some digging to figure out, but it's a
} >                        matter of the line I mentioned in the previous post
} >                        in the /etc/exim4/update-exim4.conf.conf and running
} >                        update-exim4.conf && /etc/init.d/exim4 reload. The
} >                        line is: dc_localdelivery='maildir_home'
} 
} Ahh! What happens if you don't have it, considering in 
} .muttrc:
} 	set mbox_type=Maildir

Largely irrelevant and, in this case, undesirable since mbox_type only
affects creating new mailboxes. There are only three situations in which I
store emails:

1) To IMAP (in my muttrc, = expands to an IMAP account, which happens to be
   on my local box), so mbox_type doesn't matter

2) To my not-yet-trained-on spam folder, which already exists as a Maildir.

3) To my trained-on spam archives, which are mbox files of 500 messages
   each (and gzipped later).

Of these, only the third has mutt creating new mailboxes, and I want mbox
for that.

} and/or in 
} 
} .procmailrc:
} 	:0     # note - not :0: - no need for locking on maildir
} 	* ^Resent-Sender.*debian-user-request@lists.debian.org
} 	IN-debian-user/   # and note '/' after directory 
} 	                  # for maildir
} 
} or does
} 
} 	dc_localdelivery='maildir_home'
} 
} allow for no .procmailrc?

No, maildir_home is fine with a .procmailrc and, indeed, for my own mail I
do not need the exim4 Maildir setting. My wife's mail, however, goes right
into her Maildir without passing through either spamassassin or procmail
(she uses MacOS X's Mail.app's spam filtering, which works sufficiently
well for her).

[...]
} > 5) spamassassin user_prefs -- I shouldn't discount this, since I had
} >                               developed it over the course of years on a
} >                               system someone else administered, but it was
} >                               incremental improvements.
} 
} Ummm ... spamassassin AND fetchmail?
} 
} Is not spamassassin only useful if you are operating a smarthost, which
} if you are using fetchmail you won't be?

Okay, here's how mail flows from outside to the mailbox(es) I read:

POP server --> fetchmail --> exim4 --> procmail (calls spamc) --> Maildir

Mail coming from my system does, of course, go through my ISP's SMTP
server, which is used by exim4 as a smarthost.

} Chris.
--Greg



Reply to: