* On 2002.05.02, in <[EMAIL PROTECTED]>, * "V K" <[EMAIL PROTECTED]> wrote: > > Hi, i'm a pine user, but i want to know if mutt can > > handle many pop accounts?, > > Not really, or rather, depends. > > Mutt isn't designed to download mail, use fetchmail etc for this, but it
It is; this is just not the focus. Maybe this is a semantic quibble, not sure, but mutt can in fact download mail from POP servers. > does allow to view a remote pop box. fetchmail is fine. It allows this too. > As for sending mail, features are a bit lacking. The only 2 options are > 1) use local sendmail to deliver (not necessarily desirable with > multiple pop accounts as the mail will then originate from your own > local machine, not from the pop account), and 2) pipe into a program. > I'd like to know too what is suitable to read email from stdin and send > it off via remote relay (i.e. a pop account). http://freshmeat.net/search/?q=smtp+client§ion=projects > I've also been looking at how to handle multiple pop boxes and sender > identities, but support for that in mutt is rather on the lousy side > (unless there are feature I haven't heard of yet). "Lousy" is a subjective term. $ cat .muttrc-pop1 set pop_user=user1 set pop_host=server1 $ cat .muttrc-pop2 set pop_user=user2 set pop_host=server2 $ grep fetch .muttrc macro index "+pop1" "<enter-command>source ~/.muttrc-pop1<enter><fetch-mail>" macro index "+pop2" "<enter-command>source ~/.muttrc-pop2<enter><fetch-mail>" I just made that up on the spot, but it should be close. > Oh yes, in 1) above the mail will come from the pop account if the > local sendmail is setup to use that smart relay - hardly useful for > multiple pop accounts as one can't select on a per-mail basis which > smart relay sendmail is to use. Hypothetically: message-hook . "set sendmail='/usr/lib/sendmail -oi -oem'" message-hook "~t user1@pop1" "set sendmail='smtp-relay --relay=smtp1'" message-hook "~t user2@pop2" "set sendmail='smtp-relay --relay=smtp2'" -- -D. [EMAIL PROTECTED] NSIT University of Chicago
