[arch-general] Email via mutt+offlineimap+msmtp
Hi, I am trying to send and receive emaisl using mutt. I am using offlineimap to download and store all my emails from two of my gmail accounts. I have followed the following two guides [1] [2] to setup my configuration. My problem is that when I try to compose an email, mutt automatically chooses my second email account to send mails from whereas I want my first account to be the one from which mails are sent by default. In my config files I have named my first email account for both imap and smtp as well as for my local mail dir "mkakati" and my second one "papul". So mutt chooses papul account to send mails from everytime i compose an email. Basically what I want is that I want the mkakati account to be the one from which emails are sent. Also I would like to be able to choose from which email account I wantr to send mails. I have folder-hooks setup so that it changes to from field according to the folder (i.e account) I am in. But that doesn't seem to be working properly. have provided links to my offlineimaprc, muttrc, msmtprc and some other files below. offlineimaprc http://codepad.org/6Sptj5DE msmtp.rc http://codepad.org/wFuRZOKM muttrc http://codepad.org/Rn7plSRp mkakati.muttrc http://codepad.org/KvQn3Gri papul.muttrc http://codepad.org/ppYti2KS [1] http://pbrisbin.com/posts/two_accounts_in_mutt [2] http://pbrisbin.com/posts/mutt_gmail_offlineimap
The 07/01/12, Madhurya Kakati wrote:
I am trying to send and receive emaisl using mutt. I am using offlineimap to download and store all my emails from two of my gmail accounts.
I use the same tools but msmtp. To not have to play with more than one account in a mutt session I have one mutt configuration file per account (and a global configuration sourced from them for configuration not dedicated to an account). Other than that, I've written a very small wrapper called "emails" that takes care of launching each mutt session in a screen window. So, each account have its own window in screen. Today, I use 3 unrelated mail accounts but I had 5 accounts handled this way some time ago. It's the easiest and most scalable configuration I've found. -- Nicolas Sebrecht
Mailed just to say that all of my problems have been resolved. It was a weird bug with mutt. --
Excerpts from Madhurya Kakati's message of Fri Jan 13 07:23:43 +0100 2012:
Mailed just to say that all of my problems have been resolved. It was a weird bug with mutt.
Yeah like, adding "Re:" on every fucking message and not using In-reply-to or References tag, and break my fucking threads. No offense :) -- With the best regards, Alfredo Palhares
On 01/13/12 at 08:55am, Alfredo Palhares wrote:
Excerpts from Madhurya Kakati's message of Fri Jan 13 07:23:43 +0100 2012:
Mailed just to say that all of my problems have been resolved. It was a weird bug with mutt.
Yeah like, adding "Re:" on every fucking message and not using In-reply-to or References tag, and break my fucking threads. No offense :)
-- With the best regards, Alfredo Palhares Sorry for that. How do I configure mutt to use In-reply-to instead of adding Re: to the subject?(if it is possible to do so.) --
It would appear that on Jan 13, Madhurya Kakati did say:
On 01/13/12 at 08:55am, Alfredo Palhares wrote:
Excerpts from Madhurya Kakati's message of Fri Jan 13 07:23:43 +0100 2012:
Mailed just to say that all of my problems have been resolved. It was a weird bug with mutt.
Yeah like, adding "Re:" on every fucking message and not using In-reply-to or References tag, and break my fucking threads. No offense :)
Sorry for that. How do I configure mutt to use In-reply-to instead of adding Re: to the subject?(if it is possible to do so.)
Pardon me for jumping in here, but if mutt isn't smart enough to automatically use In-Reply-To: and/or References: headers on replies? Or likes to add extra Re: (IE: Re: Re: Re:) to the subject header line? {All of which is news to me BTW...} Then I gotta ask, "why use it?" If it's because it runs in the console, then my real question is have you tried alpine? It certainly does use those thread friendly Message-ID: based reply headers and seldom {if ever} adds any redundant "Re:" tags to the "Subject:" header line. It's also highly configurable with a comprehensive built in help system. It can use local Linux mail spool and/or remote IMAP folders (or even pop inboxes). It can be configured to use local sendmail or remote SMTP servers. And it also does NNTP... It comes with it's own editor/composer but can easily be configured to use your choice of alternate editors (I use vim with it)... Just a thought... -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@ttlc.net>>
On Fri, Jan 13, 2012 at 08:33:36AM -0500, Joe(theWordy)Philbrook wrote:
It would appear that on Jan 13, Madhurya Kakati did say:
On 01/13/12 at 08:55am, Alfredo Palhares wrote:
Excerpts from Madhurya Kakati's message of Fri Jan 13 07:23:43 +0100 2012:
Mailed just to say that all of my problems have been resolved. It was a weird bug with mutt.
Yeah like, adding "Re:" on every fucking message and not using In-reply-to or References tag, and break my fucking threads. No offense :)
Sorry for that. How do I configure mutt to use In-reply-to instead of adding Re: to the subject?(if it is possible to do so.)
Pardon me for jumping in here, but if mutt isn't smart enough to automatically use In-Reply-To: and/or References: headers on replies? Or likes to add extra Re: (IE: Re: Re: Re:) to the subject header line? {All of which is news to me BTW...} Then I gotta ask, "why use it?"
It *does* add In-Reply-To and References by default. It does *not* add extra "Re:"s if one is already present. (It *does*, however, add "Re:" if it has not been added yet; *all* mail programs do that.) -- Mantas M.
On Fri, Jan 13, 2012 at 05:14:13PM +0200, Mantas M. wrote:
On Fri, Jan 13, 2012 at 08:33:36AM -0500, Joe(theWordy)Philbrook wrote:
Pardon me for jumping in here, but if mutt isn't smart enough to automatically use In-Reply-To: and/or References: headers on replies? Or likes to add extra Re: (IE: Re: Re: Re:) to the subject header line? {All of which is news to me BTW...} Then I gotta ask, "why use it?"
It *does* add In-Reply-To and References by default. It does *not* add extra "Re:"s if one is already present. (It *does*, however, add "Re:" if it has not been added yet; *all* mail programs do that.)
+1 Also, @ Joe Philbrook Firstly, Alpine isn't maintained anymore. Secondly, mutt is much more configurable and more help is available for it on the net. Before using mutt, i had tried alpine, but didn't like it much (mainly because text based mail interfaces were new and strange to me, due to switching from gmail's interface). But, then i found that it wasn't being developed anymore, and i don't like to use outdated software, especially which require interaction with the internet. Configuring mutt was a pain, but well worth it. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
On 2012-01-13 17:56, gt wrote:
Firstly, Alpine isn't maintained anymore.
There is a fork "re-alpine", though. -- Mantas M.
On Fri, Jan 13, 2012 at 07:14:38PM +0200, Mantas M. wrote:
On 2012-01-13 17:56, gt wrote:
Firstly, Alpine isn't maintained anymore.
There is a fork "re-alpine", though.
Yeah, I know of that, but i heard of it, after i got hooked to mutt :) -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
It would appear that on Jan 13, gt did say:
On Fri, Jan 13, 2012 at 05:14:13PM +0200, Mantas M. wrote:
On Fri, Jan 13, 2012 at 08:33:36AM -0500, Joe(theWordy)Philbrook wrote:
Pardon me for jumping in here, but if mutt isn't smart enough to automatically use In-Reply-To: and/or References: headers on replies? Or likes to add extra Re: (IE: Re: Re: Re:) to the subject header line? {All of which is news to me BTW...} Then I gotta ask, "why use it?"
It *does* add In-Reply-To and References by default. It does *not* add extra "Re:"s if one is already present. (It *does*, however, add "Re:" if it has not been added yet; *all* mail programs do that.)
+1
I'm glad to hear it. Not being a mutt user I didn't know for sure... I hadn't noticed the beginning of this thread. But it appeared that Madhurya Kakati didn't know how to get mutt to do those things when he responded to Alfredo Palhares' somewhat impolite complaint about those things... Hence I offered an alternative.
Also, @ Joe Philbrook
Firstly, Alpine isn't maintained anymore.
see below...
Secondly, mutt is much more configurable and more help is available for it on the net.
I'm glad to know that. If alpine, re-alpine, or some future fork of them should stop being viable to me. learning to use mutt might be my only alternative to giving up on email altogether. (I have yet to find a GUI client I can stomach...)
Configuring mutt was a pain, but well worth it.
I did once consider mutt but I was having a problem with getting it configured to suit my needs... And by then I was already hooked on most of alpine's user interface. It would appear that on Jan 13, gt did also say:
On Fri, Jan 13, 2012 at 07:14:38PM +0200, Mantas M. wrote:
On 2012-01-13 17:56, gt wrote:
Firstly, Alpine isn't maintained anymore.
There is a fork "re-alpine", though. Yeah, I know of that, but i heard of it, after i got hooked to mutt :)
And I note that as a multi-boot/multi-Linux-distribution user That the "alpine" packages found in at least some of the distro's repositories appears to be compiled from re-alpine sources since If I understand it right, the last official Uwash alpine version was 2.00 yet for example: ~ UnderTree =-> pacman -Ss alpine extra/re-alpine 2.02-3 [installed] The continuation of the Alpine email client from University of Washington ~ UnderTree =-> Since I tend to stick with package manager installed software, I can't tell you how pleased I was when I 1st noticed that some pacman -Syu had upgraded my Arch installation's alpine beyond version 2.00... ;-) -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@ttlc.net>>
On Sun, Jan 15, 2012 at 01:19:29AM -0500, Joe(theWordy)Philbrook wrote:
-- snip --
And I note that as a multi-boot/multi-Linux-distribution user That the "alpine" packages found in at least some of the distro's repositories appears to be compiled from re-alpine sources since If I understand it right, the last official Uwash alpine version was 2.00 yet for example:
~ UnderTree =-> pacman -Ss alpine extra/re-alpine 2.02-3 [installed] The continuation of the Alpine email client from University of Washington ~ UnderTree =->
Since I tend to stick with package manager installed software, I can't tell you how pleased I was when I 1st noticed that some pacman -Syu had upgraded my Arch installation's alpine beyond version 2.00... ;-)
But they (upstream) should change the useragent to re-alpine instead of alpine. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
On Sun, 2012-01-15 at 01:19 -0500, Joe(theWordy)Philbrook wrote:
And I note that as a multi-boot/multi-Linux-distribution user That the "alpine" packages found in at least some of the distro's repositories appears to be compiled from re-alpine sources since If I understand it right, the last official Uwash alpine version was 2.00 yet for example:
~ UnderTree =-> pacman -Ss alpine extra/re-alpine 2.02-3 [installed] The continuation of the Alpine email client from University of Washington ~ UnderTree =->
Since I tend to stick with package manager installed software, I can't tell you how pleased I was when I 1st noticed that some pacman -Syu had upgraded my Arch installation's alpine beyond version 2.00... ;-)
I don't understand why that much people are using MUAs without a GUI, anyway, a penfriend is blind, reading braille, a good reason to use a GUI free MUA. An Email I received yesterday was written with User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) Debian testing and unstable are at 2.02-3 too. I don't think that Alpin will be dropped by major distros. - Ralf
It would appear that on Jan 15, Ralf Madorf did say:
I don't understand why that much people are using MUAs without a GUI, anyway, a penfriend is blind, reading braille, a good reason to use a GUI free MUA.
And a good reason to support email standards that are still friendly to plain-text clients... My original reason for liking alpine had to do with having gotten used to pine with a Unix login I had with a former employer... That plus NOT having good mouse manipulation skills (I feel a little like a 3yr old trying to color within the lines...) Along with NOT wanting my email client to automatically fetching content from the web (If I decide I "want" to actually view some stinking HTML mail the way the sender want's me to I can choose to pipe it through Firefox...) And then there have been a few times when I've managed to break something X needs, and having access to all my email resources from the console was then a wonderful thing.
An Email I received yesterday was written with User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) Debian testing and unstable are at 2.02-3 too. I don't think that Alpin will be dropped by major distros.
I'm happy to agree. -- | ~^~ ~^~ | <*> <*> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
On Sun, Jan 15, 2012 at 11:15:50AM +0100, Ralf Madorf wrote:
I don't understand why that much people are using MUAs without a GUI, anyway, a penfriend is blind, reading braille, a good reason to use a GUI free MUA. An Email I received yesterday was written with User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) Debian testing and unstable are at 2.02-3 too. I don't think that Alpin will be dropped by major distros.
My reason for switching to a text based mail client (from gmail) was that i had to use 32kbps internet for a while. Loading gmail was a pain, and looking for options, i found alpine and mutt. Now, text interfaces are my preference, firstly because my computer is an old p4 with 1 gig of ram. And secondly, they fit nicely into tmux (earlier screen). -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
participants (7)
-
Alfredo Palhares
-
gt
-
Joe(theWordy)Philbrook
-
Madhurya Kakati
-
Mantas M.
-
Nicolas Sebrecht
-
Ralf Madorf