Eh, I tried Mutt and I really don't have the patience to work with
something like that. Plus I archive all of my mail, so having Icedove do
it for me automatically makes things so much easier in the end.
Maybe I'll try out Mutt at some future date or when I'm forced to use it
(Since I know how to configure it, should X die I can still talk on the
mailing list), otherwise I really have no need to force myself to use
it. I don't mind not getting geek creds.

Divorcing the task of *getting* mail from *reading* mail is a very
useful endeavor, though. For example, you upgrade your system
tonight and it borks X, or even Icedove. Then what? You're boned.
Sure, all your email is in standard mbox files, but in Icedove
directory trees. Most aggravating to import into Mutt for the 3
days that X is hosed.

I have fetchmail, postfix & maildrop to grab and filter mails into
IMAP folders, and use courier-imap to fetch them. Both Icedove and
Mutt (and Sylpheed and Evolution and KMail, etc) all understand
IMAP. So, if something borks X (or if I go away for the weekend),
I'm still getting my mail and can read it from the console.

Geeky, yes, but practical. My wife's box runs XP, but my box grabs
and filters her email. Win-Tbird reads it from across the LAN.

Do you mean that you have all of your mailboxes synced with one another?
I'd love to be able to do that with Mutt and Icedove if possible. Any
chance you have a URL to a walkthrough/HowTo on how to do something like
that?

No, no, no.

ONE mail folder tree shared by *all* MUAs. That is the beauty of
the IMAP protocol.

Re: Very disturbing feature in icedove... in the same file Inbox.... clearly visible and present from mutt.... I had implemented icedove in my system to make it ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...(Debian-User)