Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don’t use a GUI mailer, so I can’t help you there.

    mutt [mutt.org] is an excellent choice for a terminal mailer. It does all you require and much more. Beware, though:

    • The defaults aren’t overly useful, so you’ll have to wade through the configuration.
    • It’s purely a MUA and does no filtering or delivery duties. You’ll probably want to configure fetchmail+procmail to pick up your mail.
    • This goes so far as to not include SMTP-talking facilities; you’ll need something that works roughly like a sendmail on your system, and the easiest way to get that is ESMTP [sourceforge.net] or maybe nullmailer [untroubled.org], both of which are trivial to install and set up.

    It’s a bit daunting to begin with, but once you have a set of dotfiles that suits your tastes, it rocks.

    As for the clients being aware of each other, that will be easy so long as they don’t use proprietary mailbox formats. mutt has no particular preference for where the mailboxen are stored and can read the mbox, MH and Maildir formats – ie anything that’s common in Unix.

    If you’re using fetchmail to pull your mail, you’ll also want to have the GUI mailer simply read the local mailboxen instead of fetching mail itself.

    I recommend this anyway, because a fetchmail+procmail configuration makes it easy to temporarily or permanently move duties between machines, and it also makes it possible to change mailers to your heart’s content without ever losing your filtering ruleset.