Volker -- ...and then V K said... % % > Hi, i'm a pine user, but i want to know if mutt can % > handle many pop accounts?, % % Not really, or rather, depends.
Heh :-) % % Mutt isn't designed to download mail, use fetchmail etc for this, but it % does allow to view a remote pop box. fetchmail is fine. Right. Let fetchmail or something else *designed* to download mail do it and leave handling the messages locally to mutt. % % 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 You mean the problem of setting the sender and having the possible warning flag, right? I figure this because I also figure you have to know about $from and my_hdr settings. If not, though, they are probably your magic answer. If you want to hide your machine info entirely, then you probably can't use mutt for this; the first (well, bottom-most) Received: header will have your machine in it as you hand off to the smarthost. I think that a message sent out via Eudora or the like will also have the originating machine's identity in it, though (yep; just confirmed it by checking a message from my wife), so you haven't lost anything by using mutt. Even a webmail message will probably have a Posted-From: header or the like, unless you put up your own webmail server and then you're back to your machine and ... % 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). Isn't this what ssmtp does, or even sendmail as you mention below? % % 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). Aha! Perhaps you haven't, then. Using hooks you can control who you appear to be. Even if you don't want to bother with hooks, using $alternates to tell mutt what all of your addresses are and then setting $reverse_reply will generally have you sending out mail as the right person, based on to whom it was sent. I like hooks, though, for their control: [zero] [7:17am] ~> grep 'send-hook.*my_hdr.*From' .mutt/muttrc* .mutt/muttrc:send-hook . my_hdr From: [EMAIL PROTECTED] (David T-G) ... .mutt/muttrc:send-hook mutt my_hdr From: [EMAIL PROTECTED] (David T-G) .mutt/muttrc:send-hook qmail my_hdr From: [EMAIL PROTECTED] (David T-G) .mutt/muttrc:send-hook vim my_hdr From: [EMAIL PROTECTED] (David T-G) ... .mutt/muttrc.bulbs:send-hook . my_hdr From: [EMAIL PROTECTED] (David T-G, KotLBJL) # who am i? .mutt/muttrc.choice:send-hook . my_hdr From: [EMAIL PROTECTED] (Choice Consulting) ... % % 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. Bah. Use an account-hook or folder-hook or whatnot to change $sendmail to point to whatever it takes to go to a particular relay. Since ssmtp is so lightweight, even if there's no way to pass the smarthost on the command line it seems a good choice because you could just compile a copy for every smarthost you want to use. % % Volker % % -- % Volker Kuhlmann is possibly list0570 with the domain in header % http://volker.orcon.net.nz/ Please do not CC list postings to me. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg27843/pgp00000.pgp
Description: PGP signature
