Re: INBOX message count in sidebar
On 24-07-2023 21:41, Will Yardley wrote: > On Mon, Jul 24, 2023 at 10:18:37PM +0200, Mikhail Nidze via Mutt-users wrote: > > The problem was in *folder* and *spoolfile* variables incorrectly set. > > The correct ones are: > > > > set folder = "imaps://imap.mail.me.com:993" > > set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX" > > BTW, Kevin's response may have hinted at this a bit, but you can use + > or = before so that you don't have to repeat the imaps:// part, e.g., > > set folder="imaps://imap.example.com/" > set spoolfile=+INBOX > set postponed=+Drafts Thanks, I tried that too. In this case $spoolfile will be expanded to "imaps://imap.mail.me.com:993/INBOX", i.e. without *my_account* part and that doesn't work. In fact, fetching mail will still work as it used to, but sidebar will show "INDEX 0". The only solution I've found so far is to set $folder without *my_account* part and $spoolfile with one. -- Best regards, Mikhail.
Re: INBOX message count in sidebar
On 25-07-2023 10:53, Kevin J. McCarthy wrote: > I see you solved your problem, but also note the mailboxes command doesn't > use an assignment syntax. The '=' will be interpreted as a mailbox shortcut > for $folder. Just use: > > mailboxes -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX" Oh, my mistake! Thank you, Kevin! Fixed that. Haven't noticed it since the mail still worked. Can it be because $folder is set *after* the mailboxes command in my config (my guess)? -- Best regards, Mikhail.
Re: INBOX message count in sidebar
On Mon, Jul 24, 2023 at 10:18:37PM +0200, Mikhail Nidze via Mutt-users wrote: > The problem was in *folder* and *spoolfile* variables incorrectly set. > The correct ones are: > > set folder = "imaps://imap.mail.me.com:993" > set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX" BTW, Kevin's response may have hinted at this a bit, but you can use + or = before so that you don't have to repeat the imaps:// part, e.g., set folder="imaps://imap.example.com/" set spoolfile=+INBOX set postponed=+Drafts # or, Gmail style w/ label prefix on folder name set postponed="+[Gmail]/Drafts" /w w
Re: INBOX message count in sidebar
On Mon, Jul 24, 2023 at 07:22:29PM +0200, Mikhail Nidze via Mutt-users wrote: My mailboxes are set like this: mailboxes = -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX" I see you solved your problem, but also note the mailboxes command doesn't use an assignment syntax. The '=' will be interpreted as a mailbox shortcut for $folder. Just use: mailboxes -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: INBOX message count in sidebar
Update: The problem was in *folder* and *spoolfile* variables incorrectly set. The correct ones are: set folder = "imaps://imap.mail.me.com:993" set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX" Now INBOX shows message count correctly in sidebar. Problem solved. -- Best regards, Mikhail.
INBOX message count in sidebar
Hi all. My mutt is configured to fetch mail from single IMAP account with several folders set with *mailboxes ...*. All folders are shown in sidebar: sidebar_format = '%B%?F? [%F]?%* %?N?%N/?%S' The problem is INBOX folder doesn't show message count in sidebar "%S" column after program start, i.e. when I start mutt INBOX always shows "INBOX 0" (of course, INBOX is not empty and all messages are shown in index/main window). Other folders show correct number of messages in sidebar. If I re-enter INBOX (press y, then select INBOX) the message count for INBOX appears correctly. What can be a problem here? Can this be solved? I use Mutt 2.2.10. My mailboxes are set like this: mailboxes = -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX" mailboxes = -label "SENT" "imaps://my_acco...@imap.mail.me.com/Sent Messages" mailboxes = -label "DRAFTS" "imaps://my_acco...@imap.mail.me.com/Drafts" mailboxes = -label "JUNK" "imaps://my_acco...@imap.mail.me.com/Junk" mailboxes = -label "ARCHIVE" "imaps://my_acco...@imap.mail.me.com/Archive" mailboxes = -label "TRASH""imaps://my_acco...@imap.mail.me.com/Deleted Messages" Variables are: set folder = "imaps://my_acco...@imap.mail.me.com:993" set spoolfile = "+INBOX" set postponed = "+Drafts" set record = "+Sent Messages" set trash = "+Deleted Messages" -- Best regards, Mikhail.
Re: How to remove the gap between the status bar and the INBOX
On 2023-04-03 09:42:35, Kevin J. McCarthy wrote: > On Mon, Apr 03, 2023 at 12:03:12PM +0800, Sadeep Madurange wrote: > > Yes, a minimum reproducing muttrc (see attached for the screenshot - > > the gap between status bar and the word "INBOX" on the left): > > > > set imap_user=x...@asciimx.com > > set imap_pass=`pass show email` > > set folder=imaps://imap.example.com:993 > > set from=sad...@asciimx.com > > set spoolfile=+INBOX > > mailboxes = +INBOX > > The mailboxes command is not an assignment. Change the above line to just: > mailboxes +INBOX That was it, thanks! -- Regards, Sadeep PGP: 103BF9E3E750BF7E signature.asc Description: PGP signature
Re: How to remove the gap between the status bar and the INBOX
On Mon, Apr 03, 2023 at 12:03:12PM +0800, Sadeep Madurange wrote: Yes, a minimum reproducing muttrc (see attached for the screenshot - the gap between status bar and the word "INBOX" on the left): set imap_user=x...@asciimx.com set imap_pass=`pass show email` set folder=imaps://imap.example.com:993 set from=sad...@asciimx.com set spoolfile=+INBOX mailboxes = +INBOX The mailboxes command is not an assignment. Change the above line to just: mailboxes +INBOX -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: How to remove the gap between the status bar and the INBOX
On 2023-04-01 09:53:33, Kevin J. McCarthy wrote: > On Sat, Apr 01, 2023 at 05:48:41PM +0800, Sadeep Madurange wrote: > > I just switched to mutt from neomutt. There is a gap of one row between > > the status row and the first folder (i.e., INBOX) in the sidebar. Can I > > remove that? > > To make sure I understand, you have $status_on_top set, and there is a blank > line inside the sidebar at the top, before the first folder is listed; but > not in the index. Is that correct? > > That's not expected behavior, and I'm not seeing it in my testing. Can you > create a minimum reproducing muttrc? Yes, a minimum reproducing muttrc (see attached for the screenshot - the gap between status bar and the word "INBOX" on the left): set imap_user=x...@asciimx.com set imap_pass=`pass show email` set folder=imaps://imap.example.com:993 set from=sad...@asciimx.com set spoolfile=+INBOX mailboxes = +INBOX set sidebar_visible=yes Also, I'm using urxvt with xcompmgr for transparency with the following Xresources configuration: URxvt.depth: 32 URxvt.background: rgba://0200/c800 URxvt.foreground: #28fe14 URxvt.cursorColor: #28fe14 URxvt.scrollBar: false URxvt.cursorBlink: true URxvt.cursorUnderline: false URxvt.internalBorder: 10 URxvt.font: xft:Dejavu Sans Mono:size=16 -- Regards, Sadeep PGP: 103BF9E3E750BF7E signature.asc Description: PGP signature
Re: How to remove the gap between the status bar and the INBOX
On Sat Apr01'23 05:48:41PM, Sadeep Madurange wrote: > From: Sadeep Madurange > Date: Sat, 1 Apr 2023 17:48:41 +0800 > To: mutt-users@mutt.org > Subject: How to remove the gap between the status bar and the INBOX > > I just switched to mutt from neomutt. There is a gap of one row between > the status row and the first folder (i.e., INBOX) in the sidebar. Can I > remove that? > > -- > Regards, > Sadeep > PGP: 103BF9E3E750BF7E Can you send a screenshot? Ranjan
Re: How to remove the gap between the status bar and the INBOX
On Sat, Apr 01, 2023 at 05:48:41PM +0800, Sadeep Madurange wrote: I just switched to mutt from neomutt. There is a gap of one row between the status row and the first folder (i.e., INBOX) in the sidebar. Can I remove that? To make sure I understand, you have $status_on_top set, and there is a blank line inside the sidebar at the top, before the first folder is listed; but not in the index. Is that correct? That's not expected behavior, and I'm not seeing it in my testing. Can you create a minimum reproducing muttrc? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
How to remove the gap between the status bar and the INBOX
I just switched to mutt from neomutt. There is a gap of one row between the status row and the first folder (i.e., INBOX) in the sidebar. Can I remove that? -- Regards, Sadeep PGP: 103BF9E3E750BF7E signature.asc Description: PGP signature
Re: Selecting INBOX... problem
> What debug level are you using? Try at least level 3, in this case. I tried first level 2 then 5. The last line remained the same. The problem resolved after I found one forgotten Mutt instance in a paused state. After killing it another stuck Mutt woke and gave a read error. After restarting Mutt it accessed Gmail just fine. I presume the problem was caused by Mutt blocking its own header cache. In the debug log the next event after selecting Inbox refers to header cache: [2023-02-02 02:17:21] 4> a0005 STATUS "[Gmail]/Drafts" (MESSAGES) a0006 SELECT "INBOX" [2023-02-02 02:17:21] mboxcache: hcache uidvalidity 1, uidnext 4489, modseq 0 [2023-02-02 02:17:21] 4< * STATUS "[Gmail]/Drafts" (MESSAGES 0) Jarkko Lavinen
Re: Selecting INBOX... problem
On Wed, Feb 01, 2023 at 07:50:40PM +0200, Jarkko Lavinen wrote: Using debug I see 'a0006 SELECT "INBOX"' as the last message. What debug level are you using? Try at least level 3, in this case. After sending the SELECT command, Mutt tries to read some values, such as UIDVALIDITY, from the header cache and should generate some debug output (at level 3) if they exist. After that it tries to read the response from the server. You may also want to try trimming your muttrc down to the bare minimum, just to see if you can get it to work from a starting point. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Selecting INBOX... problem
I cannot access Gmail with Mutt (2.2.9) any more. After "Selecting INBOX..." nothing happens. Tried also 1.10.1. The same message and behaviour. The problem appeared just few days ago and before this accessing Gmail has worked for years once authenticated. I haven't changed my .muttrc for 6 weeks and the config file has worked since until the problem appeared. Using "./mutt_oauth2.py token -t -v" says all authentications succeed. I can read gmail using Thunderbird so it doesn't seem to have any problem accessing Gmail. Using debug I see 'a0006 SELECT "INBOX"' as the last message. Jarkko Lavinen
Selecting INBOX... problem
I cannot access Gmail with Mutt (2.2.9) any more. After "Selecting INBOX..." nothing happens. Tried also 1.10.1. The same message and behaviour. The problem appeared just few days ago and before this accessing Gmail has worked for years once authenticated. I haven't changed my .muttrc for 6 weeks and the condig file has worked some 4-5 weeks since until the problem appeared. Using "./mutt_oauth2.py token -t -v" says all authentications succeed. I can read gmail using Thunderbird so it doesn't seem to have any problem accessing Gmail. Using debug I see 'a0006 SELECT "INBOX"' as the last message. Jarkko Lavinen
Re: No Messages in Hotmail Inbox
On Sat, Aug 14, 2021 at 09:10:25AM +1000, Cameron Simpson wrote: > > I created my Hotmail account through mutt-wizard. Previously I > > created Gmail and GMX accounts successfully. But this time I find no > > messages in Hotmail Inbox, though I have thousands of emails in > > Hotmail. Here are the steps I did. > I'm assuming mutt-wizard and "mw" are from here: > > https://muttwizard.com/ > https://github.com/LukeSmithxyz/mutt-wizard Also, since mw requires neomutt, this is probably not the correct place to ask for help. /w
Re: No Messages in Hotmail Inbox
On 12Aug2021 12:01, chalao.adda wrote: >Hello, > >I created my Hotmail account through mutt-wizard. Previously I created Gmail >and GMX accounts successfully. But this time I find no messages in Hotmail >Inbox, though I have thousands of emails in Hotmail. Here are the steps I did. > >gpg --full-generate-key >pass init j**@hotmail.com >mw -a j**@hotmail.com >mw -y j**@hotmail.com >Now when I run neomutt, I find no messages in Inbox. I'm assuming mutt-wizard and "mw" are from here: https://muttwizard.com/ https://github.com/LukeSmithxyz/mutt-wizard and that "pass" is this: https://www.passwordstore.org/ It seems to me that "mw -y" syncs all your email to local storage. Are you sure your neomutt is pointing at the local storage and not your IMAP mailbox? Maybe it is only showing "new" messages? Just guessing vaguely here. >Also when I run mbsync -a , it says, >C: 3/3 B: 52/52 F: +2/2 *2/2 #0/0 N: +8/8 *0/0 #0/0an INBOX? That seems like a similar symptom. Cheers, Cameron Simpson
No Messages in Hotmail Inbox
Hello, I created my Hotmail account through mutt-wizard. Previously I created Gmail and GMX accounts successfully. But this time I find no messages in Hotmail Inbox, though I have thousands of emails in Hotmail. Here are the steps I did. gpg --full-generate-key pass init j**@hotmail.com mw -a j**@hotmail.com mw -y j**@hotmail.com Now when I run neomutt, I find no messages in Inbox. Also when I run mbsync -a , it says, C: 3/3 B: 52/52 F: +2/2 *2/2 #0/0 N: +8/8 *0/0 #0/0an INBOX? Please help. Thanks.
Re: Retrieve inbox contents and email body
* Julius Hamilton [2021-07-07 22:57]: > Unfortunately, I have been trying to get going with some simple tools like > grepmail and mail and I can't find an answer to a simple question I > have. I recommend that you re-phrase the simple question. How I have understood, you wish to see if there are some emails on the remote IMAP server related to specific recipient or sender. Is it? -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
Re: Retrieve inbox contents and email body
* Jon LaBadie [2021-07-08 08:37]: > > Could anyone provide me with some simple steps to download my Gmail inbox > > to my filesystem as a mailbox, so that I could grepmail through it? I did > > read that the mailbox could be saved to var/mail or just $HOME. In either > > case I think grepmail can search for it and find it. > > Didn't know, I have google send my gmail to my home account. > > I expected you could just select the desired gmail messages and download > them. Found out you can only do single messages that way. > > Asking google how to do it got me to takeout.google.com. Google lets > you download all your data throught "takeout". Its a little clumsy, > but if you deselect all and reselect just "mail", you can download > all your gmail (trash, spam, and archive included :)). - Use Google IMAP server - Use `movemail' or `fetchmail' or `imapsync' to synchronize with computer -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
Re: Retrieve inbox contents and email body
On Wed, Jul 07, 2021 at 09:56:10PM +0200, Julius Hamilton wrote: Unfortunately, I have been trying to get going with some simple tools like grepmail and mail and I can't find an answer to a simple question I have. How are these tools configured? It seems like grepmail looks in mailbox directories already saved in your filesystem, instead of there being some kind of configuration file or .rc file where you put in your IMAP and SMTP info. So I would need to already have downloaded a mailbox onto my system. Well the manpage you read says a required argument to grepmail is "file(s)". That sounds local to me. Could anyone provide me with some simple steps to download my Gmail inbox to my filesystem as a mailbox, so that I could grepmail through it? I did read that the mailbox could be saved to var/mail or just $HOME. In either case I think grepmail can search for it and find it. Didn't know, I have google send my gmail to my home account. I expected you could just select the desired gmail messages and download them. Found out you can only do single messages that way. Asking google how to do it got me to takeout.google.com. Google lets you download all your data throught "takeout". Its a little clumsy, but if you deselect all and reselect just "mail", you can download all your gmail (trash, spam, and archive included :)). jl -- Jon H. LaBadie mut...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: Retrieve inbox contents and email body
* Julius Hamilton [2021-07-07 22:57]: > Could anyone provide me with some simple steps to download my Gmail inbox > to my filesystem as a mailbox, so that I could grepmail through it? I did > read that the mailbox could be saved to var/mail or just $HOME. In either > case I think grepmail can search for it and find it. I use the program `movemail' from GNU Mailutils package to download it offline. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
Re: Retrieve inbox contents and email body
> I would like to retrieve the contents of my inbox - the emails' > metadata, sender, subject, date - to stdout, rather than by opening > an application. Can Mutt dump the inbox page? Does it have any way > to return to stdout information about the inbox? Or should I use a > different tool for this? This doesn't entirely do what you want, and it doesn't involve mutt; however, the command frm -s new /var/mail/$(whoami) will output the "From" and "Subject" lines of all unread messages in /var/mail/$(whoami) to standard output. Or, if you just want the "From" lines: frm -f From -s new /var/mail/$(whoami) There is documentation here: https://mailutils.org/manual/mailutils.txt As I recall, the OP was interested in being notified upon arrival of a response to an e-mail he sent. For this, perhaps for ((;;)) ; do sleep 60 ; frm -f From -s new /var/mail/$(whoami) ; done is suitable to check for a response every minute. This can of course be modified to display only e-mails from a particular sender: for ((;;)) ; do sleep 60 ; frm -f From -s new /var/mail/$(whoami) | egrep -n -e 'friend@example\.org' ; done Best regards, Greg Marks signature.asc Description: PGP signature
Re: Retrieve inbox contents and email body
12021/04/27 06:64.00 ನಲ್ಲಿ, Julius Hamilton ಬರೆದರು: > Unfortunately, I have been trying to get going with some simple tools like > grepmail and mail and I can't find an answer to a simple question I have. > > How are these tools configured? It seems like grepmail looks in mailbox > directories already saved in your filesystem, instead of there being some kind > of configuration file or .rc file where you put in your IMAP and SMTP info. So > I would need to already have downloaded a mailbox onto my system. I assume the > mail tool would permit that. But I have also not been able to find how to pass > my configuration information to mail. The docs seem to assume the information > is present as environmental variables, and it just shows commands you can call > to send mail, for example. > > Could anyone provide me with some simple steps to download my Gmail inbox to > my > filesystem as a mailbox, so that I could grepmail through it? I did read that > the mailbox could be saved to var/mail or just $HOME. In either case I think > grepmail can search for it and find it. > > Thanks very much and sorry for my simple confusion. Any help is really > appreciated. > > Best regards, > Julius I wrote this up a while back and it should be helpful: https://web.archive.org/web/20210121103233/https://chiraag.me/blog/2019/08/21/managing-multiple-email-accounts-with-mutt-and-fetchmail/ It's basically the same system I currently use with a bunch of different accounts from different providers. I'm more than happy to help debug and/or answer questions! Sincerely, Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Pronouns: he/him/his publickey - mailinglist@chiraag.me - b0c8d720.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Retrieve inbox contents and email body
Unfortunately, I have been trying to get going with some simple tools like grepmail and mail and I can't find an answer to a simple question I have. How are these tools configured? It seems like grepmail looks in mailbox directories already saved in your filesystem, instead of there being some kind of configuration file or .rc file where you put in your IMAP and SMTP info. So I would need to already have downloaded a mailbox onto my system. I assume the mail tool would permit that. But I have also not been able to find how to pass my configuration information to mail. The docs seem to assume the information is present as environmental variables, and it just shows commands you can call to send mail, for example. Could anyone provide me with some simple steps to download my Gmail inbox to my filesystem as a mailbox, so that I could grepmail through it? I did read that the mailbox could be saved to var/mail or just $HOME. In either case I think grepmail can search for it and find it. Thanks very much and sorry for my simple confusion. Any help is really appreciated. Best regards, Julius On Wed, Jul 7, 2021, 19:46 Jean Louis wrote: > * Julius Hamilton [2021-07-07 20:27]: > > Thanks. > > There is a lot of good stuff here to look into. > > I think I will try with grepmail first. > > I was wondering what the simplest way to send an email might be - the > > mentioned "mail" unix utility, perhaps? > > Mutt is the way. > > Use whatever you have available. If you have sendmail, you can echo > email message and use sendmail. > > You can connect to SMTP server and send email from command line by > using raw connection commands. > > Description : Swiss Army Knife SMTP; Command line SMTP testing, > including TLS and AUTH > URL : https://jetmore.org/john/code/swaks/ > > I am using GNU Mailutils' program `mail' so often, and I send emails > by using Emacs Lisp library and Common Lisp library for `mail': > > Emacs Lisp: rcd-mail.el package as bindings to GNU Mailutils "mail" program > > https://hyperscope.link/3/8/3/0/3/rcd-mail-el-GNU-Mailutils-mail-program.html > > I have tried using mutt as batch in the same manner, I could maybe > rewrite it for mutt. Mutt does some things in batch mode better than > `mail' maybe some features are missing. > > -- > Jean > > Take action in Free Software Foundation campaigns: > https://www.fsf.org/campaigns > > In support of Richard M. Stallman > https://stallmansupport.org/ >
Re: Retrieve inbox contents and email body
* Julius Hamilton [2021-07-07 20:27]: > Thanks. > There is a lot of good stuff here to look into. > I think I will try with grepmail first. > I was wondering what the simplest way to send an email might be - the > mentioned "mail" unix utility, perhaps? Mutt is the way. Use whatever you have available. If you have sendmail, you can echo email message and use sendmail. You can connect to SMTP server and send email from command line by using raw connection commands. Description : Swiss Army Knife SMTP; Command line SMTP testing, including TLS and AUTH URL : https://jetmore.org/john/code/swaks/ I am using GNU Mailutils' program `mail' so often, and I send emails by using Emacs Lisp library and Common Lisp library for `mail': Emacs Lisp: rcd-mail.el package as bindings to GNU Mailutils "mail" program https://hyperscope.link/3/8/3/0/3/rcd-mail-el-GNU-Mailutils-mail-program.html I have tried using mutt as batch in the same manner, I could maybe rewrite it for mutt. Mutt does some things in batch mode better than `mail' maybe some features are missing. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
Re: Retrieve inbox contents and email body
Thanks. There is a lot of good stuff here to look into. I think I will try with grepmail first. I was wondering what the simplest way to send an email might be - the mentioned "mail" unix utility, perhaps? Thanks very much, Julius On Tue, Jul 6, 2021, 19:33 Jon LaBadie wrote: > On Tue, Jul 06, 2021 at 06:19:54PM +0200, Julius Hamilton wrote: > >Thanks very much. > > > >I am now looking into using a Python IMAP library. > > > >However, I think there must be a way to just dump the contents of a Mutt > >page, and that could be an easier short-term solution. > >You mentioned there being a print function. > >Could you provide an example of using that to print the inbox to stdout? > It > >would have to be automatic, i.e. not requiring the user to actually open > >Mutt themselves and type the print command. So that leads me to the > >question of if this command can somehow be passed to mutt as a command > line > >option, or if there is some bash automation tool for calling it inside > Mutt > >anyway. > > > >The context is that I just would like to send emails and check for > >responses in a more precise and quick way than opening my inbox. I would > >like to have commands at my disposal when I am working on something to > just > >send an email directly and later check for responses to that email, or > >check for all new emails from a particular sender. That info would need to > >come back as the output of commands, to stdout. > > > >Thanks very much, > >Julius > > If looking at separate programs, what about "grepmail"? > > Ex.grepmail -h -B -e '^Subject: ' > > -h (grep only headers) > -B (print body with limited headers) > > jon > > -- > Jon H. LaBadie j...@labadie.us > 11226 South Shore Rd. (703) 787-0688 (H) > Reston, VA 20190 (703) 935-6720 (C) >
Re: Retrieve inbox contents and email body
On Wednesday, 07 July at 08:38, Jean Louis wrote: > > > The context is that I just would like to send emails and check for > > responses in a more precise and quick way than opening my inbox. I would > > like to have commands at my disposal when I am working on something to just > > send an email directly and later check for responses to that email, or > > check for all new emails from a particular sender. That info would need to > > come back as the output of commands, to stdout. > > How I understand it is that you wish to automatically verify the > existence at IMAP server of responses to particular email address. > > In almost every GNU/Linux distribution there shall be package with GNU > Mailutils https://www.mailutils.org and inside there is one program > named `from', that has among others the following option: > > -s, --sender=ADDRESS print only mail from addresses containing the > supplied string > > What is interesting is that it will work not only with local mail but > it can work with remote server. For help just write to > bug-mailut...@gnu.org mailing list even without subscription. > There's also mblaze which is a set of Unix utilities for processing and interacting with mail messages which are stored in maildir folders. > > -- > Jean > > Take action in Free Software Foundation campaigns: > https://www.fsf.org/campaigns > > In support of Richard M. Stallman > https://stallmansupport.org/ -- |\ _,,,---,,_ ZZZzz /,`.-'`'-. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_)
Re: Retrieve inbox contents and email body
> The context is that I just would like to send emails and check for > responses in a more precise and quick way than opening my inbox. I would > like to have commands at my disposal when I am working on something to just > send an email directly and later check for responses to that email, or > check for all new emails from a particular sender. That info would need to > come back as the output of commands, to stdout. How I understand it is that you wish to automatically verify the existence at IMAP server of responses to particular email address. In almost every GNU/Linux distribution there shall be package with GNU Mailutils https://www.mailutils.org and inside there is one program named `from', that has among others the following option: -s, --sender=ADDRESS print only mail from addresses containing the supplied string What is interesting is that it will work not only with local mail but it can work with remote server. For help just write to bug-mailut...@gnu.org mailing list even without subscription. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
Re: Retrieve inbox contents and email body
On 06Jul2021 18:19, Julius Hamilton wrote: >Thanks very much. >I am now looking into using a Python IMAP library. Note that imaplib from the Python standard library is only a low level wrapper for the protocol, not a fulling fledged "remote IMAP mailbox" tool (which you might expect to trweat it like a map or something). There are other IMAP modules in PyPI offering higher level access. >However, I think there must be a way to just dump the contents of a Mutt >page, and that could be an easier short-term solution. >You mentioned there being a print function. See the manual for "print", "print_command", "print_decode". The defaults are ok, except that you would want to set "print_command" to something like "cat" for the message to appear on stdout. A bit of experimentation reveals that is as good as , so something like this: mutt -e 'set wait_key=no; push ".cat"' -f YOUR_MBOX seems to work. Open mailbox, tag every message (or whatever subset you want), pipe through "cat", quit. This is all a bit of a hack - mutt is inherently an interactive programme and the above works my pushing keystrokes onto the input stream. Cheers, Cameron Simpson
Re: Retrieve inbox contents and email body
On Tue, Jul 06, 2021 at 06:19:54PM +0200, Julius Hamilton wrote: Thanks very much. I am now looking into using a Python IMAP library. However, I think there must be a way to just dump the contents of a Mutt page, and that could be an easier short-term solution. You mentioned there being a print function. Could you provide an example of using that to print the inbox to stdout? It would have to be automatic, i.e. not requiring the user to actually open Mutt themselves and type the print command. So that leads me to the question of if this command can somehow be passed to mutt as a command line option, or if there is some bash automation tool for calling it inside Mutt anyway. The context is that I just would like to send emails and check for responses in a more precise and quick way than opening my inbox. I would like to have commands at my disposal when I am working on something to just send an email directly and later check for responses to that email, or check for all new emails from a particular sender. That info would need to come back as the output of commands, to stdout. Thanks very much, Julius If looking at separate programs, what about "grepmail"? Ex.grepmail -h -B -e '^Subject: ' -h (grep only headers) -B (print body with limited headers) jon -- Jon H. LaBadie j...@labadie.us 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: Retrieve inbox contents and email body
Thanks very much. I am now looking into using a Python IMAP library. However, I think there must be a way to just dump the contents of a Mutt page, and that could be an easier short-term solution. You mentioned there being a print function. Could you provide an example of using that to print the inbox to stdout? It would have to be automatic, i.e. not requiring the user to actually open Mutt themselves and type the print command. So that leads me to the question of if this command can somehow be passed to mutt as a command line option, or if there is some bash automation tool for calling it inside Mutt anyway. The context is that I just would like to send emails and check for responses in a more precise and quick way than opening my inbox. I would like to have commands at my disposal when I am working on something to just send an email directly and later check for responses to that email, or check for all new emails from a particular sender. That info would need to come back as the output of commands, to stdout. Thanks very much, Julius On Tue, Jul 6, 2021, 00:44 Cameron Simpson wrote: > On 05Jul2021 19:19, Julius Hamilton wrote: > >I would like to retrieve the contents of my inbox - the emails' > >metadata, > >sender, subject, date - to stdout, rather than by opening an application. > >Can Mutt dump the inbox page? Does it have any way to return to stdout > >information about the inbox? Or should I use a different tool for this? > > I would use a different tool. Personally I'd write a little Python > programme to read you inbox (IMAP? Local mail folder?) and report. > > >I would also like to retrieve the body of a specific email in the same > way, > >to stdout. Do the emails have identifier tags by which they can be > >specified? Or, what would be a way to do this? > > All messages have a Message-ID: header which has a unique value per > message. Mutt's %i pattern operator matches message-ids. I suppose you > could invoke mutt from the command line this instructions to open the > message based on the message-id and "print" it, specifying the print > action as something which writes output. > > But again, if I'd already written the Python programme above (summarise > ths inbox) it would probably be easier to extend that to write out the > desired message. > > More context? There are probably already tools to do things like what > you suggest, even if they are not exact matches for what you ask for. > > Cheers, > Cameron Simpson >
Re: Retrieve inbox contents and email body
On 05Jul2021 19:19, Julius Hamilton wrote: >I would like to retrieve the contents of my inbox - the emails' >metadata, >sender, subject, date - to stdout, rather than by opening an application. >Can Mutt dump the inbox page? Does it have any way to return to stdout >information about the inbox? Or should I use a different tool for this? I would use a different tool. Personally I'd write a little Python programme to read you inbox (IMAP? Local mail folder?) and report. >I would also like to retrieve the body of a specific email in the same way, >to stdout. Do the emails have identifier tags by which they can be >specified? Or, what would be a way to do this? All messages have a Message-ID: header which has a unique value per message. Mutt's %i pattern operator matches message-ids. I suppose you could invoke mutt from the command line this instructions to open the message based on the message-id and "print" it, specifying the print action as something which writes output. But again, if I'd already written the Python programme above (summarise ths inbox) it would probably be easier to extend that to write out the desired message. More context? There are probably already tools to do things like what you suggest, even if they are not exact matches for what you ask for. Cheers, Cameron Simpson
Retrieve inbox contents and email body
Hey, I would like to retrieve the contents of my inbox - the emails' metadata, sender, subject, date - to stdout, rather than by opening an application. Can Mutt dump the inbox page? Does it have any way to return to stdout information about the inbox? Or should I use a different tool for this? I would also like to retrieve the body of a specific email in the same way, to stdout. Do the emails have identifier tags by which they can be specified? Or, what would be a way to do this? Thank you very much, Julius Hamilton
Re: Inbox folder doesn't work anymore
On Wed, May 08, 2019 at 01:24:29AM -0300, Luciano ES wrote: I have ~/Mail/inbox as correctly indicated in the line that was causing me trouble. Still a mystery. $folder specifies the default location for all your mailboxes. The first time you enter the browser, this will be where mutt looks. Subsequent times, it will change depending on the last folder selected. So by setting 'set folder="$HOME/Mail/inbox"' you have told mutt to look in there, at least the first time, when you open the browser. The problem is "$HOME/Mail/inbox" is a MH mailbox, in which you also appear to have other mailboxes: postponed-mail, sent-mail, and clAcc. I would suggest moving those mailboxes under "$HOME/Mail/" instead, using your shell or a file manager program. Then adjust: set folder="$HOME/Mail" set spoolfile="+inbox" set postponed="+postponed-mail" set record="+sent-mail" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Inbox folder doesn't work anymore
On Tue, 7 May 2019 22:59:51 -0400, Patrick Shanahan wrote:
> > set folder="$HOME/Mail/inbox"
> >
> > When that one line is commented out, the problem disappears.
> you can answer yourself, look at:
> ls -la ~/ |grep -i mail
> ls -la ~/{M,m}ail |grep -i inbox
>
> guessing, you actually have ~/Mail/Inbox or
> ~/mail/Inbox or
> ~/Mail/inbox
I have ~/Mail/inbox as correctly indicated in the line that was
causing me trouble. Still a mystery.
--
Luciano ES
>>
Re: Inbox folder doesn't work anymore
* Luciano ES [05-07-19 21:28]:
> I believe the problem has been fixed, though I don't really understand
> why... yet. I'll have to catch up with a lot of reading before I can
> really understand.
>
> I took a new approach and attacked my muttrc file rather than the
> inbox folder. I deleted about half of all lines in it and launched
> mutt and... Problem gone!
>
> So I restored all lines and repeated the elimination process a few
> times until I zeroed in on one line:
>
> set folder="$HOME/Mail/inbox"
>
> When that one line is commented out, the problem disappears.
>
> Please tell me why if you feel like it. Who knows why I even added
> it in the first place. Probably copied from some .muttrc file shared
> and spotted in the wild.
you can answer yourself, look at:
ls -la ~/ |grep -i mail
ls -la ~/{M,m}ail |grep -i inbox
guessing, you actually have ~/Mail/Inbox or
~/mail/Inbox or
~/Mail/inbox
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Re: Inbox folder doesn't work anymore
On 2019-05-07 22:12, Russell L. Harris wrote: > On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote: > > The problem is that the Inbox folder is empty. And it shouldn't be. > > I can inspect that directory say, with a file manager, and it's loaded > > with messages. > > Check two things: > > (1) The only maildirs or mboxes of which Mutt is aware are those which > are specified in .muttrc by the "mailboxes" command. This is not true, strictly speaking. The "mailboxes" command makes a folder available to switch with the "y" or "c-?" key sequences. But in response to the prompt after "c", you can enter a filename of any file or directory that is a valid folder - in a format that mutt knows about - and mutt will happily open it. And you can always start mutt like mutt -f /home/me/Mail/box even if that path is not in any mailboxes line. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
Re: Inbox folder doesn't work anymore
I believe the problem has been fixed, though I don't really understand why... yet. I'll have to catch up with a lot of reading before I can really understand. I took a new approach and attacked my muttrc file rather than the inbox folder. I deleted about half of all lines in it and launched mutt and... Problem gone! So I restored all lines and repeated the elimination process a few times until I zeroed in on one line: set folder="$HOME/Mail/inbox" When that one line is commented out, the problem disappears. Please tell me why if you feel like it. Who knows why I even added it in the first place. Probably copied from some .muttrc file shared and spotted in the wild. Mutt seems to be working again and I'll be reading docs and fine tuning it to my very specific tastes. I'll stick around so I get to read about the subject more often and keep learning. Feel free to add any comments you may feel like. They will be very welcome. Otherwise, thank you very much for all the attention. All the best, -- Luciano ES >>
Re: Inbox folder doesn't work anymore
On Tue, May 07, 2019 at 08:00:56PM -0300, Luciano ES wrote: I don't have any 'mailboxes' command in my .muttrc file. Not at all. I have this: set spoolfile="$HOME/Mail/inbox" I have a few folder-hooks though, and they all point to subdirectories of $HOME/Mail/inbox. Your problem may be that your system is running on defaults of which you are unaware, and that you need to use ".muttrc" to specify a few locations. As I said, if you do not use "folder" to specify a base for your mail repository, Mutt assumes the base is $HOME/Mail. You need to read the Mutt manual (and possibly other sources) to familiarize yourself with the typical usage of the following directories, all of which, in your case, are in Mail: "mbox", "postponed", "record", "spoolfile", "tmpdir". Each has an intended use. And the path of each should specified with a "mailboxes" command. In particular, "spoolfile" no longer serves the purpose it once did. In modern Linux systems the Mail Transfer Agent (Exim4) commonly delivers system-level messages to "spoolfile"; and some system utilities expect the format of "spoolfile" to be Mbox rather than Maildir. I suggest that you add to ".muttrc" the line "mailboxes $HOME/Mail/inbox" and specify "inbox" as "Maildir". Also, if the Mutt configuration variable "move" is true, Mutt automatically transfers a message from "spoolfile" to the location specified by the Mutt configuration variable "mbox" once the message has been read; this reduces clutter in "spoolfile". Regrettably, Mutt uses for this location variable the same name used for the format "mbox"; this is a source of confusion.
Re: Inbox folder doesn't work anymore
On 2019-05-07 19:00, Luciano ES wrote: I pasted the output of ls -AR here: https://pastebin.com/DihPtit2 Nothing jumps out at me as obviously invalid MH format, but it's clearly been modified and reused at least a couple times. There's extra stuff that's not normally present in MH format. For one, it looks like you renamed maildir's subdirectories tmp, new, and cur to xtmp, xnew, and xcur, but left them there, in what is now used as an MH directory. There are still about 900 messages in xcur, which would be inaccessible to anything expecting either maildir or MH format. Mutt might be trying and failing to interpret those subdirectories as subfolders -- failing because they're not either maildir or MH format. I suggest that you try to start over, make a new clean folder. Use something high-level -- maybe Mutt -- to copy the messages into a new place and leave all the other stuff behind. Then rename directories to end up with the new clean folder having the same old pathname.
Re: Inbox folder doesn't work anymore
On Tue, 7 May 2019 22:12:35 +, Russell L. Harris wrote: > (1) The only maildirs or mboxes of which Mutt is aware are those which > are specified in .muttrc by the "mailboxes" command. > (2) The base of the maildir or mbox structure is specified by the > "folder" command. If I recall correctly, Mutt assumes "~/Mail" if no > base is specified. I don't have any 'mailboxes' command in my .muttrc file. Not at all. I have this: set spoolfile="$HOME/Mail/inbox" I have a few folder-hooks though, and they all point to subdirectories of $HOME/Mail/inbox. On Tue, 7 May 2019 17:29:39 -0400, Kurt Hackenberg wrote: > On 2019-05-07 17:11, Luciano ES wrote: > > > I don't remember how I converted it. It was a very long time ago. > > Oh. But the problem just started a day or two ago? Then two questions: > > Did something change just before the problem started? If so, what? > > And, maybe you could show us the contents of that directory? Say, the > output of "ls -AR". The problem started years ago. I asked for help in a generic *nix forum and nobody had a clue so I gave up. I am trying to sort it out for good this time around. I'm making progress. :-) I just want to get rid of that glitch in the command. I pasted the output of ls -AR here: https://pastebin.com/DihPtit2 -- Luciano ES >>
Re: Inbox folder doesn't work anymore
On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote: The problem is that the Inbox folder is empty. And it shouldn't be. I can inspect that directory say, with a file manager, and it's loaded with messages. Check two things: (1) The only maildirs or mboxes of which Mutt is aware are those which are specified in .muttrc by the "mailboxes" command. (2) The base of the maildir or mbox structure is specified by the "folder" command. If I recall correctly, Mutt assumes "~/Mail" if no base is specified.
Re: Inbox folder doesn't work anymore
On 2019-05-07 17:11, Luciano ES wrote: I don't remember how I converted it. It was a very long time ago. Oh. But the problem just started a day or two ago? Then two questions: Did something change just before the problem started? If so, what? And, maybe you could show us the contents of that directory? Say, the output of "ls -AR".
Re: Inbox folder doesn't work anymore
On Tue, 7 May 2019 16:28:59 -0400, Kurt Hackenberg wrote: > On 2019-05-07 15:21, Luciano ES wrote: > > > Why does mutt show files rather than browse folders on every first > > attempt? It doesn't make sense. > > Because when you converted your inbox from maildir to MH format, you > didn't do it right. That's my current guess, anyway. > > How did you convert it, exactly? I don't remember how I converted it. It was a very long time ago. I'm not even sure I converted it. Maybe I just started the whole Mail content with MH since I used claws before mutt. Or maybe I imported them from Kmail, which I used some 15 years ago. I do have mail as old as that. Claws-mail can only import mbox so maybe I used mbox. Or maybe I converted from maildir to mbox then imported the resulting file into claws-mail. I don't know really. -- Luciano ES >>
Re: Inbox folder doesn't work anymore
On 2019-05-07 15:21, Luciano ES wrote: Why does mutt show files rather than browse folders on every first attempt? It doesn't make sense. Because when you converted your inbox from maildir to MH format, you didn't do it right. That's my current guess, anyway. How did you convert it, exactly?
Re: Inbox folder doesn't work anymore
On 2019-05-07, Luciano ES wrote: > By the way, does mutt support Gmail boxes now? It didn't when I still > used it. Please note that I am stuck with mutt 1.7.2 which is what > Debian stable provides. Yes. Mutt's IMAP support works great with Gmail's IMAP server (and has for many years). -- Grant Edwards grant.b.edwardsYow! Either CONFESS now or at we go to "PEOPLE'S COURT"!! gmail.com
Re: Inbox folder doesn't work anymore
On Tue, 7 May 2019 13:43:22 -0400, Kurt Hackenberg wrote:
> On 2019-05-07 12:13, Luciano ES wrote:
>
> >> Does the Inbox folder contain the standard maildir style
> >> directories: cur, new, tmp ? Unread messages should be inside
> >> 'new', read messages inside 'cur'.
> >>
> >
> > Hi. There used to be cur, new, tmp. There shouldn't be because it is
> > all MH. So I decided to delete them. Only Inbox had them. Sure
> > enough, now mutt can see the contents of Inbox.
>
> An MH folder is a directory containing a file for each message; the
> filenames are numbers. There's also, optionally, a file named
> ".mh_sequences" that contains one or two message attributes
> ("unseen", and Mutt adds "replied"), plus user-specified groupings of
> messages. I believe Mutt will not recognize this as an MH folder if
> the file .mh_sequences is absent. So that might be part of your
> problem.
>
> But maildir would probably be a better choice for your main inbox.
> Maildir does random access, concurrent access, and spooling of
> incoming messages. MH format does only random access. When you use MH
> format for your inbox, how is new incoming mail delivered?
I just poll pop3 boxes directly, mostly Gmail. I don't use procmail or
anything like that.
By the way, does mutt support Gmail boxes now? It didn't when I still
used it. Please note that I am stuck with mutt 1.7.2 which is what
Debian stable provides.
I love maildir, but the problem with maildir is that even if I go
back to mutt, I want to have something to fall back on if I have to.
I am going to need some time to relearn how to properly configure
mutt so it's nice and sweet again. The only MUA I can stand besides
mutt is claws-mail, which does not support maildir. There used to be
a plugin, but it is discontinued. Since mutt supports MH, I guess
I had better just stay put in relation to that. I'm just insecure
about the whole thing because it's behaving strangely. Why
does mutt show files rather than browse folders on every first
attempt? It doesn't make sense.
Thank you for your assistance.
--
Luciano ES
>>
Re: Inbox folder doesn't work anymore
On 2019-05-07 12:13, Luciano ES wrote:
Does the Inbox folder contain the standard maildir style directories:
cur, new, tmp ? Unread messages should be inside 'new', read messages
inside 'cur'.
Hi. There used to be cur, new, tmp. There shouldn't be because it is
all MH. So I decided to delete them. Only Inbox had them. Sure enough,
now mutt can see the contents of Inbox.
An MH folder is a directory containing a file for each message; the
filenames are numbers. There's also, optionally, a file named
".mh_sequences" that contains one or two message attributes ("unseen",
and Mutt adds "replied"), plus user-specified groupings of messages. I
believe Mutt will not recognize this as an MH folder if the file
.mh_sequences is absent. So that might be part of your problem.
But maildir would probably be a better choice for your main inbox.
Maildir does random access, concurrent access, and spooling of incoming
messages. MH format does only random access. When you use MH format for
your inbox, how is new incoming mail delivered?
Re: Inbox folder doesn't work anymore
On Mon, 6 May 2019 22:23:39 -0500, Jason wrote: > On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote: > > > > Then I tried to use it again, but it didn't quite work anymore. > > > > The problem is that the Inbox folder is empty. And it shouldn't be. > > I can inspect that directory say, with a file manager, and it's > > loaded with messages. In fact, I can view them all in claws-mail, > > the MUA I've been using since I had that problem. Mutt can't see > > them. Mutt always shows me an empty Inbox folder. > > > > It's just the Inbox folder. I can switch to any other folder and > > view all of their contents. Old and recent messages (received > > through claws-mail) are all there, not one is missing. Mutt can > > display them. It just can't see anything inside Inbox. > > >> > Does the Inbox folder contain the standard maildir style directories: > cur, new, tmp ? Unread messages should be inside 'new', read messages > inside 'cur'. > Hi. There used to be cur, new, tmp. There shouldn't be because it is all MH. So I decided to delete them. Only Inbox had them. Sure enough, now mutt can see the contents of Inbox. When I brought those folders back (I didn't delete them, I moved them) the Inbox would look empty again. So I moved them out again, and mutt could see the contents of Inbox again. But something strange has happened. When I pressed the key to change folder, mutt would show me a list of the files inside Inbox, including many messages but shown as files, all named after numbers. I couldn't open them. Then I would press the key to exit and mutt would exit altogether. That was yesterday, after I sent a message to this mailing list. Today, the behavior is a little different. I press the key to change folder and I get that strange file list. But now I exit and I just exit that screen and go back to the Inbox, and then the Inbox looks normal and I can browse and open messages. Then I press the key to change folder and I can browse them normally again. I have repeated the test and many times and I can confirm that pressing the key to change folder always gives me the weird file list on the first time, then I exit that screen and the 'change folder' key will show the folders normally again. Does that make sense? I believe something is broken, but I have no idea what. -- Luciano ES >>
Re: Inbox folder doesn't work anymore
On Tue, May 07, 2019 at 12:08:14AM -0300, Luciano ES wrote: > > Then I tried to use it again, but it didn't quite work anymore. > > The problem is that the Inbox folder is empty. And it shouldn't be. > I can inspect that directory say, with a file manager, and it's loaded > with messages. In fact, I can view them all in claws-mail, the MUA > I've been using since I had that problem. Mutt can't see them. Mutt > always shows me an empty Inbox folder. > > It's just the Inbox folder. I can switch to any other folder and view > all of their contents. Old and recent messages (received through > claws-mail) are all there, not one is missing. Mutt can display them. > It just can't see anything inside Inbox. > >> Does the Inbox folder contain the standard maildir style directories: cur, new, tmp ? Unread messages should be inside 'new', read messages inside 'cur'. -- Jason
Inbox folder doesn't work anymore
This is a very old problem. I used mutt a long time ago. I loved it. Then I stopped using it for a short while for some reason I can't even remember. Then I tried to use it again, but it didn't quite work anymore. The problem is that the Inbox folder is empty. And it shouldn't be. I can inspect that directory say, with a file manager, and it's loaded with messages. In fact, I can view them all in claws-mail, the MUA I've been using since I had that problem. Mutt can't see them. Mutt always shows me an empty Inbox folder. It's just the Inbox folder. I can switch to any other folder and view all of their contents. Old and recent messages (received through claws-mail) are all there, not one is missing. Mutt can display them. It just can't see anything inside Inbox. I would love to use mutt again, but I can't with that problem. Does anyone here have any clue about why that happens? Thanks a lot for any help. -- Luciano ES >>
Re: Saving sent e-mails in INBOX for better threading?
On 30Mar2019 15:34, Erik Christiansen wrote: On 29.03.19 13:37, Max Görner wrote: thank you everyone for the valuable replies. I am a bit relieved to learn that others follow similar approaches. I will try to Bcc all e-mails to myself. That sounds a bit less hacky than saving sent e-mails in the Inbox. Errr ... doesn't Bcc-ing yourself result in saving sent e-mails in the Inbox? And wasn't the original aim to thread both sides of an exchange in the one mailbox, for threading? Bccing yourself delivered the email to yourself which causes it to be fetches which causes it to be filed like other messages, so hopefully into the right mail folder. Cheers, Cameron Simpson
Re: Saving sent e-mails in INBOX for better threading?
On 30.03.19 09:37, Cameron Simpson wrote: > Aside: I sort new-to-top, the reverse of the default, because I like to see > the whole thread before replying. I found sorting conventionally got me > involved before I'd seen followon posts saying the same stuff I was saying. Hmmm ... that bears consideration. It definitely has its benefits. ... > I use notmuch to search email; I have a couple of handle shell scripts 9with > short names) to do lookups. Saving deciding _where_ to look - notmuch looks > everywhere and one just has to type an ok search. Then it opens the results > in mutt anyway for easy persual (the (l)imit keystroke is a grwat boon > here). Yes, something beyond mutt's search, and egrep, would be needed on one mammoth inbox. With archived mail in over a thousand mailboxes, those simple tools suffice amply, though. (Yeah, probably have to be slightly OCD to put in the effort of considered archiving, but search keys can be much looser.) > My "inbox" is supposed to be my "priority" categories: personal email, > family, banking. And unfortunately, nearly a bazillion other special > criteria. Still, lists email goes to its own folder. In contrast, priority is lost with the OP's one inbox. Pearls, spam, and general effluvia appear in reverse date order. When I return from a week on the farm, an important (legal) email could be at the tail end of over 1200 fresh mails. Even from one day to the next, it could be anywhere amongst over 200. With procmail hiving bulk traffic off to mailing list mailboxes, mutt presents the mailboxes in my chosen priority order: residue after filtering first. (They're unknowns, e.g. bank notices, council rates notices, ISP invoices, bills.); then family; finally the ML inboxes in order of interest. If time is short, the tail end misses out, but I don't miss anything important. And I don't have to fiddle any mutt display filters to twiddle that effect. If higher priority mail comes in while I'm burrowing in a ML inbox, then the next 'c' Change-Folder invocation in mutt takes me to that, for immediate attention. It works like a bought one. :-) Erik
Re: Saving sent e-mails in INBOX for better threading?
On 29.03.19 13:37, Max Görner wrote: > Dear list users, > > thank you everyone for the valuable replies. I am a bit relieved to learn that > others follow similar approaches. I will try to Bcc all e-mails to myself. > That sounds a bit less hacky than saving sent e-mails in the Inbox. Errr ... doesn't Bcc-ing yourself result in saving sent e-mails in the Inbox? And wasn't the original aim to thread both sides of an exchange in the one mailbox, for threading? And isn't long-term usability severely constrained by saving a chaotic panoply of disparate traffic in one increasingly entropic morass? (Apologies for the rhetorical query. It is intended to evoke deliberation.) Erik
Re: Saving sent e-mails in INBOX for better threading?
On 29Mar2019 18:21, Erik Christiansen wrote: On 28.03.19 13:24, Max Görner wrote: I am a very pleased Mutt user for several years now. However, I would love to have a threading similar to GMail, showing send and received messages in the same thread. I wonder whether one could just configure mutt such as to save all send messages to Inbox again. Of course, that would clutter the inbox severely, but a) I have a hook limiting the view to ~(~N|~F) already b) the cluttering might be counteracted by Mutt's threading capabilities. Display filtering of one enormous clutter had never occurred to me as a viable option. I do the following to reduce clutter: I sort folders threaded reverse (new stuff on top). And I push these commands on entry to a folder: # mark stuff I posted as read folder-hook . 'push ":set auto_tag=no~T~P~NN~T:set auto_tag=yes"' # collapse read threads folder-hook . 'push ""' folder-hook . 'push ":set collapse_unread=no"' To explain: First I mark anything new which I wrote (~P~N) as "read" - after all, I've seen it. This catches stuff from me via lists and anything I've run through my filing rules (email I sent gets filed like other email in my regime). Then I issue a to collapse _all_ threads to a single line each. And then issue ":set collapse_unread=no" to uncollapse threads with new messages. Between the collapsing and the thread sort, new threads with unread messages are at the top of my email view. Aside: I sort new-to-top, the reverse of the default, because I like to see the whole thread before replying. I found sorting conventionally got me involved before I'd seen followon posts saying the same stuff I was saying. There are various incoming mail filtering tools in any linux distro repository - the one I've used for decades is procmail. I've set it to stream incoming mail to a separate inbox for each mailing list, one for family, and the rest remain in /var/spool/mail/erik. On list mailboxes, record is just set to "sent", as the list server provides a copy of my mail for threading. A couple of hooks, folder and recipient, record to =family when required. So, yes, posts & replies thread nicely. I set $record to my "+spool-out" folder, which is monitored and cross files messages (like you, family to one box and so on). As you might imagine, inbound email lands in "+spool-in" which is also monitored and filed from there; that folder is post my crude prefilter for spam. To further reduce clutter, and highly optimise searches, I delete 95 - 99% of all list mail, My mutt "delete" keystrokes move the messages to parallel "archive" folders: "+mail" to "+O/mail", and "O" is a symlink to a per year directory which I flip each January. So I get "+OLD/2018/mail" etc, purely to control file size. and archive any pearls in topic-specific secondary mailboxes; there are 70 for mutt, 456 for LinuxCNC, and 1259 mailboxes in all. (When looking for a hint on vim scripting a few minutes ago, for a reply on another list, I only had to consider the subject lines of 205 posts in the mailbox vim_script, rather than who knows how many in the 104 vim mailboxes, let alone the umpty thousands if there were only one inbox. (I'm still amazed at the thought.) I use notmuch to search email; I have a couple of handle shell scripts 9with short names) to do lookups. Saving deciding _where_ to look - notmuch looks everywhere and one just has to type an ok search. Then it opens the results in mutt anyway for easy persual (the (l)imit keystroke is a grwat boon here). My "inbox" is supposed to be my "priority" categories: personal email, family, banking. And unfortunately, nearly a bazillion other special criteria. Still, lists email goes to its own folder. I group lists by topic. Several "python" lists land in "+python", mutt and other mail tech related lists in "+mail" and so forth. Cheers, Cameron Simpson
Re: Saving sent e-mails in INBOX for better threading?
On 28Mar2019 22:05, Gregor Zattler wrote: I send every email to me via Bcc: the incoming Bcc: copy is handled by the same procmail scripts as all email and therefore the email will go in the same folder(s). Admittedly I get duplicates this way, but I use procmail also as a duplicate filter an anyway mutt is great in searching/deletung duplicates too. I use a similar scheme (submit my own email to myself for filing) and also use mutt's $record setting. And I also get dups due to this practice. An alternative to stripping dups with procmail, which I find risky unless you keep a per folder db, is that you can have mutt strip the duplicates when you enter a folder: tag duplicated messages (the "~=" pattern) and delete. You can push that via a folder hook so it is automatic. Cheers, Cameron Simpson
Re: Saving sent e-mails in INBOX for better threading?
Dear list users, thank you everyone for the valuable replies. I am a bit relieved to learn that others follow similar approaches. I will try to Bcc all e-mails to myself. That sounds a bit less hacky than saving sent e-mails in the Inbox. Thank you for all the replies. Sincerely Max Görner signature.asc Description: PGP signature
Re: Saving sent e-mails in INBOX for better threading?
On 28.03.19 13:24, Max Görner wrote:
> Hello,
>
> I am a very pleased Mutt user for several years now. However, I would love to
> have a threading similar to GMail, showing send and received messages in the
> same thread.
>
> I wonder whether one could just configure mutt such as to save all send
> messages to Inbox again. Of course, that would clutter the inbox severely, but
>
> a) I have a hook limiting the view to ~(~N|~F) already
> b) the cluttering might be counteracted by Mutt's threading capabilities.
Display filtering of one enormous clutter had never occurred to me as a
viable option. There are various incoming mail filtering tools in any
linux distro repository - the one I've used for decades is procmail.
I've set it to stream incoming mail to a separate inbox for each mailing
list, one for family, and the rest remain in /var/spool/mail/erik.
On list mailboxes, record is just set to "sent", as the list server
provides a copy of my mail for threading. A couple of hooks, folder and
recipient, record to =family when required. So, yes, posts & replies
thread nicely.
To further reduce clutter, and highly optimise searches, I delete 95 -
99% of all list mail, and archive any pearls in topic-specific secondary
mailboxes; there are 70 for mutt, 456 for LinuxCNC, and 1259 mailboxes
in all. (When looking for a hint on vim scripting a few minutes ago, for
a reply on another list, I only had to consider the subject lines of 205
posts in the mailbox vim_script, rather than who knows how many in the
104 vim mailboxes, let alone the umpty thousands if there were only one
inbox. (I'm still amazed at the thought.)
Mutt's mailbox name completion is one aid to navigation to one of 456
mailboxes - type a couple of charcters, tab twice, and page/scroll down the
list then presented. I also have:
$ which mls
mls is a function
mls ()
{
ls -xF ~/mail/*$1*
}
which gives me a shortlist from the 1259, given a few topic-related
characters.
Erik
Re: Saving sent e-mails in INBOX for better threading?
Hi Max, * Max Görner [2019-03-28; 13:24]: > I wonder whether one could just configure mutt such as to save all send > messages to Inbox again. Of course, that would clutter the inbox severely, but > > a) I have a hook limiting the view to ~(~N|~F) already > b) the cluttering might be counteracted by Mutt's threading capabilities. > > Could some readers of this list please share their opinion/experiences with > me? I am tempted to just try out, but I am also a bit afraid of bad > consequences. I do this since years and would not want handle email without. It's so much easier to follow a thread if all messages are in the same folder. I send every email to me via Bcc: the incoming Bcc: copy is handled by the same procmail scripts as all email and therefore the email will go in the same folder(s). Admittedly I get duplicates this way, but I use procmail also as a duplicate filter an anyway mutt is great in searching/deletung duplicates too. Ciao; Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: Saving sent e-mails in INBOX for better threading?
On Thursday 28 March 2019 13:24, Max Görner put forth the proposition: > Hello, > > I am a very pleased Mutt user for several years now. However, I would love to > have a threading similar to GMail, showing send and received messages in the > same thread. > > I wonder whether one could just configure mutt such as to save all send > messages to Inbox again. Of course, that would clutter the inbox severely, but > > a) I have a hook limiting the view to ~(~N|~F) already > b) the cluttering might be counteracted by Mutt's threading capabilities. > > Could some readers of this list please share their opinion/experiences with > me? I am tempted to just try out, but I am also a bit afraid of bad > consequences. The way I do this is to set record=^ in ~/.muttrc so it saves in the same folder that the message was created and sent from: set record=^ And a hook which also has the setting in the sourced file: folder-hook .* source ~/.mutt/default Then I have other hooks when I want to use a different folder - mailing list messages get saved in =Sent, since the original message will go to the list folder anyway: folder-hook =Lists/* source ~/.mutt/listhook Containing: set record="=Sent" That way I can have things in various folders for family, friends etc. Best, Dave > > Sincerely > > Max Görner -- All I ask of life is a constant and exaggerated sense of my own importance.
Re: Saving sent e-mails in INBOX for better threading?
On Thu, Mar 28, 2019 at 13:24:22 +0100, Max Görner wrote: > I am a very pleased Mutt user for several years now. However, I would love to > have a threading similar to GMail, showing send and received messages in the > same thread. Well, GMail and Mutt threading is different. Mutt uses Message-Id and In-Reply-To headers. GMail guesses and does heuristics (personally, I find it far inferior). > I wonder whether one could just configure mutt such as to save all send > messages to Inbox again. Of course, that would clutter the inbox severely, but I do this with: set record = '=acct/INBOX' which saves outgoing messages to the account's INBOX. You can use `folder-hook` to reset the variable based on which account you're in. --Ben
Re: Saving sent e-mails in INBOX for better threading?
On Thu, 28 Mar 2019, at 13:32, Max Görner wrote: > Could some readers of this list please share their opinion/experiences with > me? As someone who is only using mutt's threaded view, it's terrific and achieves exactly the behaviour I want from a mail client. mutt's way of displaying threads -- at least with Unicode characters -- also looks very tidy. Collapsing, splitting, merging threads is also a very convenient feature to have, especially in cases where the conversation partner or software breaks threading by applying worst practices on every occasion. An issue is that when using multiple email clients, online IMAP must be used for all mailboxes (which I don't like -- I like to only pull IMAP to my local machine, which is the authoritative copy, and not push; also, I don't sync IMAP deletions from the server) OR you could just do it like I do, I BCC all outgoing emails to myself so I can have the same consistent inbox view from everywhere. Multiple clients in my case means: mutt at home with isync (pull only), webmail from everywhere else.
Saving sent e-mails in INBOX for better threading?
Hello, I am a very pleased Mutt user for several years now. However, I would love to have a threading similar to GMail, showing send and received messages in the same thread. I wonder whether one could just configure mutt such as to save all send messages to Inbox again. Of course, that would clutter the inbox severely, but a) I have a hook limiting the view to ~(~N|~F) already b) the cluttering might be counteracted by Mutt's threading capabilities. Could some readers of this list please share their opinion/experiences with me? I am tempted to just try out, but I am also a bit afraid of bad consequences. Sincerely Max Görner signature.asc Description: PGP signature
Macro for goto next in thread and then go back out to inbox
When reading long threads in mailing lists I often feel it might be convenient to have the following functionality in the pager: Instead of working my way through a thread using or I would like to press some key and it takes me to the next message in the thread like but when I reach the last mail in the thread and press again it takes me back out to the current inbox index. I'm pretty much a noob but I'm wondering if it might be possible to define this as a macro? Any help would be highly appreciated! -- Jonas Hedman XMPP:n...@jabber.at PGP Key: 0x5c3989e0616bb08c Fingerprint: 8F72 C5BE AAFA B4BA 8F46 9185 5C39 89E0 616B B08C signature.asc Description: Digital signature
Re: 100,000 messages, and counting., procmail mailinglist to new inbox recipe
Most importantly, there is a nice procmail recipe in that procmailrc that
creates list inboxes automatically
as soon as you sign up for a mailing list, procmail will create it as a new
inbox for you automatically... pretty cool
:0:
* ^((List-Id|X-(Mailing-)?List):(.*[<]\/[^>]*))
{
LISTID=$MATCH
:0:
* LISTID ?? ^\/[^@\.]*
lists/$MATCH
}one inbox for each mailig list, switch to them with 'c?'
- Original Message -
From: "Michael Ole Olsen"
To: "Michael Ole Olsen" ; ; "Alan
Mackenzie"
Sent: Monday, February 17, 2014 9:43 PM
Subject: Re: 100,000 messages, and counting.
https://svn.rlogin.dk/dotfiles/muttrc
https://svn.rlogin.dk/dotfiles/procmailrc
Some inspriation for many mboxes perhaps
Spamassassin,procmail for every mbox,priority mails etc.
Mutt watching each inbox, only alerting on new mails in those inboxes that
I care about
Send hooks / alternate identities etc. in muttrc (so by pressing 8 I
change to 'trading' mbox, and my email changes when I reply to certain
mails - ebay i.e., as they only allow you to reply from your ebay email)
by pressing 'v' when I send I can chose between 20+ emails I got and it
will use msmtp to send with, from those new emails after chosing
Had one mbox for facebook too, but unsubscribed from that..
facebook mbox... who wants that stuff in their regular inbox
Same goes for anything that has 'order','bestellung','invoice' in title,
goes into my 'trading' inbox so I don't have to have it floating in my
inbox
will get an announcement in mutt that I can press 'c' to change to trading
inbox and view the mail
Procmail is also nice for creating a 'p5911' priority title for your
emails
if you receive important emails, then they will never be sent into spam by
spamassassin if they have that in the title
Spamassassin feeds on my spam once a day, 500MB and learns from it, so
very few spam make it into my inbox, maybe 1 a day max
Procmail is very helpful with mutt, wouldn't be without it..
- Original Message -
From: "Michael Ole Olsen"
To: ; "Alan Mackenzie"
Sent: Monday, February 17, 2014 9:22 PM
Subject: Re: 100,000 messages, and counting.
Split between mailboxes and logrotate your mailboxes too(with a custom
script that checks size and does stuff to it)
I only got inbox of 5000, 150MB mailbox after 10+ years in mutt, but spam
is 500MB and "root" is 50k so I never open it, takes too long to open,
spam takes many seconds too
Maildir is really the best thing there is for large mailboxes, it only
opens headers usually, no need to read the whole file when opening the
mail box
I got maybe 30-40 mboxes, one for each mailing list, inbox, auction
sites(trading),sent,spam,root,work inbox,work inbox2 etc.
Mutt will watch those that you specify are important... no need to read
all mailinglists everyday(too much info)
make mutt watch those mboxes which are important and alert you so you can
change to them with 'c'
If you rotate your mailboxes you can write a custom script that greps all
rotated mailboxes too for finding your stuff
.. or you could just use Maildir, mbox is not good for large mboxes
If you don't use maildir you can keep upgrading servers/disks every year
to make it fast enough to open your mailboxes
but maildir only fetches headers, so much faster, it even caches headers,
reducing load time a lot
I use procmail to forward into different mailboxes, then I make mutt
watch those
Many inboxes, many emails in the same client, that is what mutt does well
(with send-hooks/folder-hooks)
Then I combine all my own emails into one inbox, but work emails/trading
stuff etc. into separate inboxes
I was switching to Maildir due to this problem you mention(mbox is not
good for large files unless you got plenty ram/fast disks)
unfortunately my inbox file must have been corrupted, so it could not be
converted... due to disk crashes
so now I am still with mbox 5 years later, even slower than before :)
- Original Message -
From: "Alan Mackenzie"
To:
Sent: Monday, February 17, 2014 8:58 PM
Subject: Re: 100,000 messages, and counting.
Hi, Bastian.
On Mon, Feb 17, 2014 at 08:42:16PM +0100, bastian-muttu...@t6l.de wrote:
On 17Feb14 18:50 +, Alan Mackenzie wrote:
> My inbox has now reached the grand total of 100,000 messages
> (_exactly_
> 100,000, coincidentally enough). This is partly a result of me
> being
> subscribed to too many mailing lists, and partly of me not getting
> around to clearing things out.
mbox or maildir?
mbox. I've never used maildir, but it strikes me that it would be
slower, not counting the initial 12s loading time.
> (Yes, I know I could do clever things to split incoming messages
> amongst
> several mailboxes, but I d
Mutt manual: %L w.r.t. group [Was: Inbox and Sent messages in one thread. How To? [Off topic question]]
On 06.12.13 11:22, Paul E Condon wrote: > On 20131206_210949, Erik Christiansen wrote: > > help when you are off in another mailbox, and suddenly decide to fling > > off a message. To let mutt catch that use case, and put any message to > > family in the right mailbox, I've settled on: > > > > fcc-save-hook '%L fam_grp' family > ^^ > Where is the use of '%L and other such magic documented? In mutt, press F1¹, then either search for %L (about the third hit includes the text "GROUP"), or go to section "3.1. Pattern Modifier". (It's the same place.) ... > Where is -group within an alias command documented? In the same manual. That's where I found it, after a bit of poking about. (I'm no mutt guru either. It took several dives into the doco before I'd fashioned the simple config which simply worked.) > Is this a unique feature? I don't know what other MUAs might have the feature. > Or are there other modifiers for alias? A little effort finds that in the F1 manual. > Documented where? If you've only been looking in http://www.mutt.org/doc/manual/, then that's perhaps a fair question. The 'F1' manual is infinitely superior w.r.t. ease of finding stuff. ¹ If F1 doesn't work for you, then you could manually zcat /usr/share/doc/mutt/manual.txt.gz Erik -- manual, n.: A unit of documentation. There are always three or more on a given item. One is on the shelf; someone has the others. The information you need is in the others. - Ray Simard
Re: Inbox and Sent messages in one thread. How To? [Off topic question]
My question is embedded in the quoted message, below: On 20131206_210949, Erik Christiansen wrote: ... remove text that's not relevant to my questions > help when you are off in another mailbox, and suddenly decide to fling > off a message. To let mutt catch that use case, and put any message to > family in the right mailbox, I've settled on: > > fcc-save-hook '%L fam_grp' family ^^ Where is the use of '%L and other such magic documented? I have found a magic code ~L. Is that 'the same thing'? If so why the substitution of % for ~ ? > > after setting up a group via the alias for each, e.g.: > > alias -group fam_grp jim jim@example.com > alias -group fam_grp joe joe@elephant.org Where is -group within an alias command documented? Is this a unique feature? Or are there other modifiers for alias? Documented where? > ... > > That is as far as I've been motivated to pursue the hunt for efficiency > and convenience, given the diminishing returns once the biggest bugbear > is a fading memory. > > Erik > > ¹ Chucking most outgoing mail into "sent" is a high entropy expedient, > useful only for last resort message recovery when your post didn't > make it to a list, I find. It pretty much scores -10 as storage of > half of multiple unrelated conversations with various parties, where > it's copy of outgoing mail is the only one. (But then, that's what > you've discovered, AIUI.) > > -- > For those with savings and fixed incomes, deflation is wonderful, but for > those > with debt, it is catastrophic since the value of the dollar repaid is greater > than the dollar borrowed. ... borrowers are ascendant and central banks are > working for them, not savers. In fact, savers are being plundered with super > low > interest in the name of promoting aggregate demand and maintaining inflation. > - > http://www.abc.net.au/news/2013-11-06/kohler-prices-want-to-fall-but-borrowers-wont-let-them/5072388 -- Paul E Condon pecon...@mesanetworks.net
Re: Inbox and Sent messages in one thread. How To?
On Fri, Dec 06, 2013 at 05:02:21AM +0400, Kirill Tkhai wrote: > Hi, > > I want to have a posibility to see inbox and sent messages together > in one thread. Is this possible without copying content of Sent folder > to Inbox? I may be misunderstanding something, but how about just BCCing yourself when you send a message? -pd
Re: Inbox and Sent messages in one thread. How To?
On 06Dec13 13:57 +0100, Suvayu Ali wrote: > On Thu, Dec 05, 2013 at 08:21:00PM -0500, Patrick Shanahan wrote: > > * Kirill Tkhai [12-05-13 20:05]: > > > I want to have a posibility to see inbox and sent messages together in > > > one thread. Is this possible without copying content of Sent folder to > > > Inbox? > > > > Leave the "sent" msgs in the inbox > > > > or insteadof "saving" outgoing post, copy them to the "Sent" directory and > > the original will remain in your inbox. > > > > If you do not want a copy of the "Sent" mail in your inbox, I believe you > > are outtaluck. mutt alone cannot deal with this, afaik. Mairix can help out here. It supports a search modus for e.g. the message-id of a mail. This normally returns a single mail, but adding the --threads switch also returns all mails of the thread this mail is related to. I am using Maildir (no imap, mbox, etc) In this case mairix works pretty efficient, as the search result is presented in a temporary % Maildir containing links to the real Mailfiles. The creation of this folder can be initiated from within mutt (with a look&feel like it is a mutt command). If interested in mairix and its integration into mutt, I could provide my config, which I copied from the net somewhere.
Re: Inbox and Sent messages in one thread. How To?
On Thu, Dec 05, 2013 at 08:21:00PM -0500, Patrick Shanahan wrote: > * Kirill Tkhai [12-05-13 20:05]: > > I want to have a posibility to see inbox and sent messages together in > > one thread. Is this possible without copying content of Sent folder to > > Inbox? > > Leave the "sent" msgs in the inbox > > or insteadof "saving" outgoing post, copy them to the "Sent" directory and > the original will remain in your inbox. > > If you do not want a copy of the "Sent" mail in your inbox, I believe you > are outtaluck. I would like to suggest try the Mutt fork Mutt-kz[1]. This integrates support for the Xapian based indexer Notmuch[2]. What the OP is asking can be achieved very easily using notmuch. In fact, the command does exactly that[3]. I can also provide a shell script (older than the command) that does something similar. The fork is maintained & developed actively and it is synced with recent Mutt developments quite regularly (e.g. changes from 1.5.22 was merged recently). Using notmuch simplifies a lot of similar problems, but the caveat is, it only works if your mailstore is in Maildir format. I have been using it for a little less than a year now, it has been performing remarkably well. Footnotes: [1] <https://github.com/karelzak/mutt-kz> [2] <http://notmuchmail.org/> [3] <https://github.com/karelzak/mutt-kz/blob/master/README.notmuch#L107> -- Suvayu Open source is the future. It sets us free.
Re: Inbox and Sent messages in one thread. How To?
On 06.12.13 05:02, Kirill Tkhai wrote: > I want to have a posibility to see inbox and sent messages together > in one thread. Is this possible without copying content of Sent folder > to Inbox? There are many ways to skin the message storage cat, all with some merit. (Except perhaps, for indiscriminate use of the "sent"¹ mailbox.) Perhaps you can take something from part of how my usage has evolved. Firstly, procmail is used to split incoming mail into a separate mailbox for each category, including maillists. (Trying to untangle mail from multiple lists in one inbox would be too depressingly burdensome to ever contemplate.) Mutt is made aware of the distinct mailboxes via the "mailboxes" config item. Since my own posts come back as list posts, both sides of the exchange appear intermixed as they should in the threads, without further effort. (That's 99% of the traffic handled) Other groupings might include e.g. family. But they don't don't come from a listserver, so one more simple procmail rule recognises them, and puts them into another mailbox. But how to ensure that mails to family also go in there, to take their place in threads? There is a mutt setting to save in the current folder instead of "sent", but that is no help when you are off in another mailbox, and suddenly decide to fling off a message. To let mutt catch that use case, and put any message to family in the right mailbox, I've settled on: fcc-save-hook '%L fam_grp' family after setting up a group via the alias for each, e.g.: alias -group fam_grp jim jim@example.com alias -group fam_grp joe joe@elephant.org ... That is as far as I've been motivated to pursue the hunt for efficiency and convenience, given the diminishing returns once the biggest bugbear is a fading memory. Erik ¹ Chucking most outgoing mail into "sent" is a high entropy expedient, useful only for last resort message recovery when your post didn't make it to a list, I find. It pretty much scores -10 as storage of half of multiple unrelated conversations with various parties, where it's copy of outgoing mail is the only one. (But then, that's what you've discovered, AIUI.) -- For those with savings and fixed incomes, deflation is wonderful, but for those with debt, it is catastrophic since the value of the dollar repaid is greater than the dollar borrowed. ... borrowers are ascendant and central banks are working for them, not savers. In fact, savers are being plundered with super low interest in the name of promoting aggregate demand and maintaining inflation. - http://www.abc.net.au/news/2013-11-06/kohler-prices-want-to-fall-but-borrowers-wont-let-them/5072388
Re: Inbox and Sent messages in one thread. How To?
* Kirill Tkhai [12-05-13 20:05]: > I want to have a posibility to see inbox and sent messages together in > one thread. Is this possible without copying content of Sent folder to > Inbox? Leave the "sent" msgs in the inbox or insteadof "saving" outgoing post, copy them to the "Sent" directory and the original will remain in your inbox. If you do not want a copy of the "Sent" mail in your inbox, I believe you are outtaluck. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Inbox and Sent messages in one thread. How To?
Hi, I want to have a posibility to see inbox and sent messages together in one thread. Is this possible without copying content of Sent folder to Inbox? Thanks, Kirill
Re: How to fetch inbox for a newly mutt client (gmail account)
On 2013-04-19, Paul Hoffman wrote: > On Fri, Apr 19, 2013 at 07:16:57PM +0300, Kevin Wilson wrote: >> Hi, >> I installed mutt of Fedora 18 and configured muttrc >> to my gmail account; I am able to send messages properly. >> However, the inbox is almost empty (5 messages) and I want to >> fetch previous messages (let's say >> 1000 or 2000) from my inbox of the gmail account >> >> How can I achieve this ? > > Probably by switching to the "All Mail" folder -- press c and enter >=[Gmail]/All Mail That won't work (at least it never has for me). Mutt doesn't allow you to enter mailbox names with spaces in them. It will, however, auto-complete names with spaces. To get to All Mail, you have to enter '=[Gmail]/All' and then hit [Tab] followed by [Enter]. -- Grant Edwards grant.b.edwardsYow! Didn't I buy a 1951 at Packard from you last March gmail.comin Cairo?
Re: How to fetch inbox for a newly mutt client (gmail account)
On Fri, Apr 19, 2013 at 07:16:57PM +0300, Kevin Wilson wrote: > Hi, > I installed mutt of Fedora 18 and configured muttrc > to my gmail account; I am able to send messages properly. > However, the inbox is almost empty (5 messages) and I want to > fetch previous messages (let's say > 1000 or 2000) from my inbox of the gmail account > > How can I achieve this ? Probably by switching to the "All Mail" folder -- press c and enter =[Gmail]/All Mail -- at least I assume that's where you want to get them from. Paul. -- Paul Hoffman
How to fetch inbox for a newly mutt client (gmail account)
Hi, I installed mutt of Fedora 18 and configured muttrc to my gmail account; I am able to send messages properly. However, the inbox is almost empty (5 messages) and I want to fetch previous messages (let's say 1000 or 2000) from my inbox of the gmail account How can I achieve this ? rgs Kevin
Re: Inbox not updated
* Patrice Levesque [2013-01-30 15:33:11 -0500]: > > > My problem is that all Maildir folders are updated automatically when a > > new email is received, but my Inbox doesn't show updates. To see new > > email I have to quit mutt and re-open it. > > > > What I'm doing wrong?. > > See this entry from the FAQ, might provide you a hint or two: > http://dev.mutt.org/trac/wiki/MuttFaq/Folder#Whyarenewflagsofmboxfolderswronginfolder-listview when you specify mailboxes to be checked for new mail, i.e. with the mailboxes command, make sure you have a line like this: mailboxes ! mailboxes =foo ... The '!' character is a shortcut for your spoolfile, and it should report new mail when it arrives. Before I set up an imap server I was using a similar set up, with /var/mail/$user in mbox format and other mailboxes in ~/Mail in Maildir format. I did not experience any issues with new mail not being registered/shown by mutt. There also could be another explanation - do you have any other programs running on your system that are checking mail that could mark the mailbox as "read", if you see what I mean. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Inbox not updated
On 2013-01-30 17:54:04 -0300, Leonardo M. Ramé wrote:
> On 2013-01-30 15:33:11 -0500, Patrice Levesque wrote:
> >
> > > My problem is that all Maildir folders are updated automatically when a
> > > new email is received, but my Inbox doesn't show updates. To see new
> > > email I have to quit mutt and re-open it.
> > >
> > > What I'm doing wrong?.
> >
> > See this entry from the FAQ, might provide you a hint or two:
> > http://dev.mutt.org/trac/wiki/MuttFaq/Folder#Whyarenewflagsofmboxfolderswronginfolder-listview
> >
> >
>
> Ok, so, basically the recommended way is to convert my inbox to Maildir.
> Now the question is how?.
>
This was easy:
1) Convert /var/spool/mail/me to Maildir using mb2md -m
2) Redefined the INBOX variable in ~/.procmailrc to
INBOX=$HOME/Maildir/.inbox/new # to store all incoming mail in that
folder.
3) Added this fields to ~/.muttrc
set timeout = 10# mutt 'presses' (like) a key for you
(while you're idle)
# each x sec to trigger the thing below.
set mail_check=5# mutt checks for new emails on every
keystroke
# but not more often than once in 5
seconds.
set spoolfile = "~/Maildir/.inbox" # mutt will open this folder at
# startup.
--
Leonardo M. Ramé
http://leonardorame.blogspot.com
Re: Inbox not updated
On 2013-01-30 15:33:11 -0500, Patrice Levesque wrote: > > > My problem is that all Maildir folders are updated automatically when a > > new email is received, but my Inbox doesn't show updates. To see new > > email I have to quit mutt and re-open it. > > > > What I'm doing wrong?. > > See this entry from the FAQ, might provide you a hint or two: > http://dev.mutt.org/trac/wiki/MuttFaq/Folder#Whyarenewflagsofmboxfolderswronginfolder-listview > > Ok, so, basically the recommended way is to convert my inbox to Maildir. Now the question is how?. -- Leonardo M. Ramé http://leonardorame.blogspot.com
Re: Inbox not updated
> My problem is that all Maildir folders are updated automatically when a > new email is received, but my Inbox doesn't show updates. To see new > email I have to quit mutt and re-open it. > > What I'm doing wrong?. See this entry from the FAQ, might provide you a hint or two: http://dev.mutt.org/trac/wiki/MuttFaq/Folder#Whyarenewflagsofmboxfolderswronginfolder-listview -- --|-- | Patrice Levesque http://ptaff.ca/ mutt.wa...@ptaff.ca | --|-- -- signature.asc Description: Digital signature
Inbox not updated
Hi, I'm using mutt 1.5.21 with sidebar patch from 20120829. I'm also using Fetchmail and Procmail to store my emails in different folders. My Inbox is directly read from /var/spool/mail/leonardo, which is an mbox file, while every other emails are stored in their respective Maildir folders. My problem is that all Maildir folders are updated automatically when a new email is received, but my Inbox doesn't show updates. To see new email I have to quit mutt and re-open it. What I'm doing wrong?. Regards, -- Leonardo M. Ramé http://leonardorame.blogspot.com
Re: maildir: No mailbox is open. - can't open inbox by default
[ Paolo Pisati wrote on Mon 8.Oct'12 at 20:57:41 +0200 ] > the leading dot came from a precooked config file for offlineimap that i > found around. > I removed the trailing / and indeed it didn't make any difference. > > If you want to see my entire mutt config, is here: > http://people.canonical.com/~ppisati/mutt/ in your muttrc you have 'c' mapped to the command ... in index and pager view. This will override the default behaviour of 'c' which would show/list the contents of $folder, in your case ~/Maildir. You could perhaps change that macro to bind 'y' to toggle your mailboxes. Try that first. Also, I think you can probably remove the leading '.' fromm your $record and $postponed Maildirs.
Re: maildir: No mailbox is open. - can't open inbox by default
On Mon, Oct 08, 2012 at 02:10:51PM +0100, Jamie Paul Griffin wrote: > > > > set mbox_type=Maildir > > set folder="~/Maildir/" > > set spoolfile=+inbox > > set mask="!^\\.[^.]" > > set record="+.Sent" > > set postponed="+.Drafts" > > > > set from="Foo Bar " > > set sendmail = "/usr/bin/msmtp -a gmail" > > what is the output from ls -a ~/Maildir [flag@newluxor ~]$ ls -a ~/Maildir/ . bak.sent cazzeggio gufilinux.arm linux.lkmllinux.patch linux.tegra openwrtpersonal.fatture personal.sky u-boot .. bak.spam drafts inbox linux.btrfs linux.mipslinux.pulllinux.tippandaboard personal.groupon queue bak.drafts bak.trash.Drafts jobslinux.cgroup linux.mmc linux.regression linux.usbpersonal personal.job sent bak.flaggedbeagleboard gdb linaro linux.kernel-newbies linux.netdev linux.samsung mutt personal.ags personal.pirelli .Sent bak.important canonicalgroupfuffa linux linux.kexec linux.omaplinux.sound openocd personal.casa personal.piva trash [flag@newluxor ~]$ > > Also, why do you have a leading '.' for your $record and $postponed > mailboxes. You don't need the '/' at the end of $folder=~/Maildir/ not that > it should make much difference. the leading dot came from a precooked config file for offlineimap that i found around. I removed the trailing / and indeed it didn't make any difference. If you want to see my entire mutt config, is here: http://people.canonical.com/~ppisati/mutt/ -- bye, p.
Re: maildir: No mailbox is open. - can't open inbox by default
[ Paolo Pisati wrote on Mon 8.Oct'12 at 14:26:49 +0200 ] > On Fri, Oct 05, 2012 at 05:03:06PM +0200, Paolo Pisati wrote: > > On Fri, Oct 05, 2012 at 12:39:42PM +0100, Jamie Paul Griffin wrote: > > > The problem is with your setting of $spoolfile. By default, mutt uses > > > ~/Mail for it's mailboxes. If you want to use ~/Maildir for your > > > mailboxes you need to specify $folder to ~/Maildir, which you have done. > > > But, you want ~/Maildir/inbox to be your spoolfile, so you need to put > > > this in muttrc > > > > > > set folder=~/Maildir > > > set spoolfile=+inbox > > > ... > > > > thanks, it worked. > > ok, but i've another problem now: > > whenever i press 'c' to change mailbox i get an empty screen (previously it > would show me the content > of ~/Maildir) and to get the list of mailboxes i either have to: > > -press TAB once > > or > > -press another time 'c', and when it shows "Chdir to: /home/flag/Maildir/" > press enter > > what could be wrong now? > > set mbox_type=Maildir > set folder="~/Maildir/" > set spoolfile=+inbox > set mask="!^\\.[^.]" > set record="+.Sent" > set postponed="+.Drafts" > > set from="Foo Bar " > set sendmail = "/usr/bin/msmtp -a gmail" what is the output from ls -a ~/Maildir Also, why do you have a leading '.' for your $record and $postponed mailboxes. You don't need the '/' at the end of $folder=~/Maildir/ not that it should make much difference.
Re: maildir: No mailbox is open. - can't open inbox by default
On Fri, Oct 05, 2012 at 05:03:06PM +0200, Paolo Pisati wrote: > On Fri, Oct 05, 2012 at 12:39:42PM +0100, Jamie Paul Griffin wrote: > > The problem is with your setting of $spoolfile. By default, mutt uses > > ~/Mail for it's mailboxes. If you want to use ~/Maildir for your mailboxes > > you need to specify $folder to ~/Maildir, which you have done. But, you > > want ~/Maildir/inbox to be your spoolfile, so you need to put this in muttrc > > > > set folder=~/Maildir > > set spoolfile=+inbox > > ... > > thanks, it worked. ok, but i've another problem now: whenever i press 'c' to change mailbox i get an empty screen (previously it would show me the content of ~/Maildir) and to get the list of mailboxes i either have to: -press TAB once or -press another time 'c', and when it shows "Chdir to: /home/flag/Maildir/" press enter what could be wrong now? set mbox_type=Maildir set folder="~/Maildir/" set spoolfile=+inbox set mask="!^\\.[^.]" set record="+.Sent" set postponed="+.Drafts" set from="Foo Bar " set sendmail = "/usr/bin/msmtp -a gmail" source ~/.mutt/mailboxes and ~/.mutt/mailboxes is a file created by offlineimap containing: mailboxes "+gmail/bak.drafts" "+gmail/bak.flagged" "+gmail/bak.important" "+gmail/bak.sent" "+gmail/bak.spam" "+gmail/bak.trash" "+gmail/beagleboard" "+gmail/canonical" "+gmail/cazzeggio" "+gmail/drafts" "+gmail/gdb" "+gmail/groupfuffa" "+gmail/gufi" "+gmail/inbox" "+gmail/jobs" "+gmail/linaro" "+gmail/linux" "+gmail/linux.arm" "+gmail/linux.btrfs" "+gmail/linux.cgroup" "+gmail/linux.kernel-newbies" "+gmail/linux.kexec" "+gmail/linux.lkml" "+gmail/linux.mips" "+gmail/linux.mmc" "+gmail/linux.netdev" "+gmail/linux.omap" "+gmail/linux.patch" "+gmail/linux.pull" "+gmail/linux.regression" "+gmail/linux.samsung" "+gmail/linux.sound" "+gmail/linux.tegra" "+gmail/linux.tip" "+gmail/linux.usb" "+gmail/mutt" "+gmail/openocd" "+gmail/openwrt" "+gmail/pandaboard" "+gmail/personal" "+gmail/personal.ags" "+gmail/personal.casa" "+gmail/personal.fatture" "+gmail/personal.groupon" "+gmail/personal.job" "+gmail/personal.pirelli" "+gmail/personal.piva" "+gmail/personal.sky" "+gmail/queue" "+gmail/sent" "+gmail/trash" "+gmail/u-boot" -- bye, p.
Re: maildir: No mailbox is open. - can't open inbox by default
On Fri, Oct 05, 2012 at 12:39:42PM +0100, Jamie Paul Griffin wrote: > The problem is with your setting of $spoolfile. By default, mutt uses ~/Mail > for it's mailboxes. If you want to use ~/Maildir for your mailboxes you need > to specify $folder to ~/Maildir, which you have done. But, you want > ~/Maildir/inbox to be your spoolfile, so you need to put this in muttrc > > set folder=~/Maildir > set spoolfile=+inbox > ... thanks, it worked. -- bye, p.
Re: maildir: No mailbox is open. - can't open inbox by default
[ Paolo Pisati wrote on Fri 5.Oct'12 at 13:23:25 +0200 ] > On Fri, Oct 5, 2012 at 1:16 PM, Patrick Shanahan wrote: > > > > try: mailboxes +/Maildir/inbox > > so what's the point of the variable folder? > > set folder="~/Maildir/" > > besides, when i press c? it displays all the mailboxes in ~/Maildir, > so the "root maildir directory" is correct. The problem is with your setting of $spoolfile. By default, mutt uses ~/Mail for it's mailboxes. If you want to use ~/Maildir for your mailboxes you need to specify $folder to ~/Maildir, which you have done. But, you want ~/Maildir/inbox to be your spoolfile, so you need to put this in muttrc set folder=~/Maildir set spoolfile=+inbox ... Then your spoolfile will be picked up by mutt. Or you could set the environment variable $MAIL in your shell's configuration file; for example: export MAIL=~/Maildir/inbox for bash MAIL=~/Maildir/inbox; export MAIL for ksh or sh setenv MAIL ~/Maildir/inbox for csh or tcsh.
Re: maildir: No mailbox is open. - can't open inbox by default
On Fri, Oct 5, 2012 at 1:16 PM, Patrick Shanahan wrote: > > try: mailboxes +/Maildir/inbox so what's the point of the variable folder? set folder="~/Maildir/" besides, when i press c? it displays all the mailboxes in ~/Maildir, so the "root maildir directory" is correct.
Re: maildir: No mailbox is open. - can't open inbox by default
* Paolo Pisati [10-05-12 07:11]: > I can't make mutt to open my ~/Maildir/inbox by default. ... > mailboxes +inbox try: mailboxes +/Maildir/inbox hth :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
maildir: No mailbox is open. - can't open inbox by default
I can't make mutt to open my ~/Maildir/inbox by default. mutt's status line: ---Mutt: (no mailbox) [Msgs:0 Inc:1]---(threads/date)(all)--- No mailbox is open. [flag@newluxor ~]$ ls -la ~/Maildir/inbox/ total 20 drwx-- 5 flag flag 4096 Sep 24 10:36 . drwxrwxr-x 53 flag flag 4096 Sep 24 10:36 .. drwx-- 2 flag flag 4096 Sep 24 23:53 cur drwx-- 2 flag flag 4096 Sep 24 23:53 new drwx-- 2 flag flag 4096 Sep 24 23:53 tmp [flag@newluxor ~]$ .muttrc: ... set mbox_type=Maildir set spoolfile="~/Maildir/" set folder="~/Maildir/" set mask="!^\\.[^.]" set record="+.Sent" set postponed="+.Drafts" mailboxes +inbox but the "funny" thing is that if i c?, navigate to inbox and press enter, i can see my emails!!! mutt's status line: ---Mutt: ~/Maildir/inbox [Msgs:28 New:2 5.0M]---(threads/date) what's wrong with my config?
Store responded messages into inbox
Hi, currently I store all my responses to ~/Maildir/sent-mail-2012, this directory is created automatically, because of this configuration: set record="=sent-mail-`date +%Y`" I would also like to store my responses in my Inbox, which is set this as this: set mbox="+.inbox-`date +%Y`" Without this, it's easy to lost the path in long email threads. I've read this can be done by creating some fcc-hook rules, but I don't now how. Regards, -- Leonardo M. Ramé http://leonardorame.blogspot.com
Using Mutt with Gmail with an effective filter of "in:inbox in:important" (ie. neither just important mail nor just the inbox)
Hello mutt users and discussers, Currently I am successfully seeing everything in my Inbox when I execute mutt but I don't want to see the entire Inbox. I pretty much have almost everything the way I want it otherwise though. I also don't want to see all Important mail regardless of if it's in the Inbox or not. I have approximately 65000 emails in my Important mailbox - for comparison I have about 21000 in my Sent mailbox. I have had a Gmail account for a very long time now and I use it for everything. Effectively I would like to have the contents of the search string "in:inbox in:important" in my mutt message listing when I open mutt. The applicable parts of my current muttrc look like this: set folder = imaps://imap.gmail.com:993 set spoolfile = imaps://imap.gmail.com:993/INBOX set postponed = "+[Gmail]/Drafts" set message_cachedir=~/.mutt/cache/bodies set header_cache=~/.mutt/cache/hcache set certificate_file=~/.mutt/certificates I've tried setting things up the following combinations but have had no luck thus far: set folder = imaps://imap.gmail.com:993/INBOX set spoolfile = "+[Gmail]/Important" set folder = imaps://imap.gmail.com:993 set spoolfile = "+[Gmail]/Important +[Gmail]/Inbox" ... and some other non-sense combinations that didn't work. Is what I'm attempting to do possible and how can I achieve it? Thanks for reading and pondering this predicament! :-D -- Landon pgpgLyHXhKBvs.pgp Description: PGP signature
Re: unified inbox
* Derek Martin [2011-02-27 18:11 -0800]: > On Thu, Feb 24, 2011 at 02:34:43PM -0600, Puneet Kishor wrote: > > There is much that I have to do to really get comfortable with mutt, but > > I think I am making slow but steady progress. One feature that really > > bothers me because of its absence is a unified mailbox. > > There isn't really any way to do this, except -- as others have said > already -- to get all your mail somehow delivered to the same folder. > ... > The easiest way to deal with multiple accounts with mutt is to deliver > mail from those accounts into specific folders, and use folder hooks > to set variables associated with the respective accounts upon entering > the folder. I was reading the above message when it occurred to me that using the hcache functions of mutt might be suitable to implementing a unified inbox functionality. For example, if you could define multiple inboxes and their aliases, and defined each to have the same aliase, then each accounts' messages would be stored in the same hcache directory, and thus displayed in the same the mail folder. Obviously, this is a rough draft and would need more work to be fully functional... but I think it might be useful and doable. Of course, it would need a patch (extensive) to implement... thoughts? -- dave [ please don't CC me ] pgpuy5sqyfvXT.pgp Description: PGP signature
Re: unified inbox
On Feb 28, 2011, at 8:15 AM, Derek Martin wrote: > On Mon, Feb 28, 2011 at 10:01:01AM +0100, Joost Kremers wrote: >>>>> I don't think having a specific feature in Mutt is necessary or >>>>> desirable to achieve this. You can easily have mail from multiple >>>>> accounts delivered to your mailspool using getmail or fetchmail. >>>> >>>> except that that downloads the mail to your local machine. >>> >>> Not if you run it on your IMAP server. >> >> but it still puts all your mail into a single mail box, which entirely >> defeats >> the purpose of a unified inbox. > > I don't see that at all... The purpose of having a unified inbox is > to present all of your new mail to you simultaneously. This does > exactly that. > Actually, a "unified inbox" (as provided by Apple Mail.app or Postbox) presents all my new mail in one view, however, the mail actually remains in separate inboxes behind the scenes. A column in the view tells me where the mail actually resides. That way, mail can remain in physically separate accounts/inboxes, but can be seen in one view. Postbox takes this a bit further by allowing the user to create arbitrary number of groups -- so I could see inbox1 and inbox2 in a virtual view called "work" and inbox3 and inbox4 in a virtual view called "gambling," if I so wanted. >>>> > lacking in some way or other. Unified inbox is something I > specifically DO NOT want, as it removes a certain amount of context > from the mail-handling process for me. > > .. As noted above, the context is provided by a column in the view. My unified inbox in Apple Mail looks like so -- Subject Date Recd Mailbox = ====== = Derek Martin 8:18 AMInbox - punk.kish Re: unified inbox -- Someone Else 7:14 AMInbox - punkish Re: logging in BC makes.. -- I hope the above doesn't come out garbled. In the view above, I can see emails from two inboxes (even as they remain in their respected inboxes). In addition, since 2 lines are devoted to each mail, I can see the subject below the sender's name. Actually, Sparrow, a new, Gmail-specific IMAP only client (soon to expand to other IMAPs also) even shows the first couple of lines from the message text as well. Rather useful. Additional Note: Part of the issue is that I haven't really understood how Mutt works. In true Unix philosophy, mutt is (was) designed to do only one thing (reading and replying to my mail), while other tools did other things. More and more, tools are doing one "conceptual" thing (working with my mail) even though behind the scenes it is doing many things. The user, me, is not worrying about what is happening behind the scenes. More and more programs don't even require the user to interact with the physical location and storage of the content (iPhoto, Mail, and more programs in the new iOS paradigm). You open the program and your content appears there. Even if mutt works with the IMAP server, my mail is actually "stored" (cached) in my mutt cache location. I would like that to continue, particularly since I don't trust any IMAP servers (Google could vanish tomorrow -- in fact, just yesterday there was a report of some users finding their emails had vanished -- Google was working on fixing it), but I also like the ubiquitous availability of IMAP. The solution, for me, is to use IMAP, but to sync all my email locally, so I can have the best of both worlds. Will get there soon hopefully. Thanks all. Puneet.
Re: unified inbox
On Mon, Feb 28, 2011 at 10:01:01AM +0100, Joost Kremers wrote: > > > > I don't think having a specific feature in Mutt is necessary or > > > > desirable to achieve this. You can easily have mail from multiple > > > > accounts delivered to your mailspool using getmail or fetchmail. > > > > > > except that that downloads the mail to your local machine. > > > > Not if you run it on your IMAP server. > > but it still puts all your mail into a single mail box, which entirely defeats > the purpose of a unified inbox. I don't see that at all... The purpose of having a unified inbox is to present all of your new mail to you simultaneously. This does exactly that. > > > mutt is really a one-mail-account kind of mail client. > > > > That's amusing... I've been using it with multiple accounts for over a > > decade. > > so have i, but you need to resort to some trickery to do that. either by > defining macros to change account info (server, username/password), or by > collecting the mail into a single mailbox, or (like me) by running multiple > instances of mutt within screen/tmux or in different tabs of one's terminal > emulator. it's certainly not as simple as: > > set imap_user[1] = "f...@bar.com" > set imap_pass[1] = "baz" > > set imap_user[2] = "f...@buz.com" > set imap_pass[2] = "baz2" No, it's much simpler. You simply need to understand how to configure Mutt. Just use URL syntax to define your mail folders, i.e.: mailboxes imap[s]://[username1[:password1]@]server1[:port][/path] mailboxes imap[s]://[username2[:password2]@]server2[:port][/path] [Of course, putting passwords in a config file is generally stupid... but mutt is flexible enough to let you be stupid.] Then, if need be, define folder hooks (or similar) to set your identities for sending mail, and such. This is hardly "trickery"; this is the standard way Mutt is configured to use multiple accounts (and to do many, many other things). > > > it would be nice if mutt were to gain the ability to > > > conveniently deal with multiple mail accounts within a single > > > instance, but it's up to the developers to decide if they want > > > to implement it. Mutt is extremely unconventional, by design... that is what gives it its power. However what you want is pretty simple. You may not prefer the way it works in Mutt, but that bit is your problem. ;-) > > Many would argue that it does that already, and much more flexibly > > than other clients do it. > > define "flexible" in this regard. See above. I think that's pretty flexible. With proper hooks defined, folder or otherwise, you can switch back and forth between multiple accounts seamlessly and effortlessly, without even needing to notice. I haven't used Thunderbird for any meaningful mail usage, so I can't really compare, sadly. Each time I tried it I found it lacking in some way or other. Unified inbox is something I specifically DO NOT want, as it removes a certain amount of context from the mail-handling process for me. -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpDxwqUZMhKW.pgp Description: PGP signature
Re: unified inbox
On Sun, Feb 27, 2011 at 08:08:49PM -0600, Derek Martin wrote: > On Sat, Feb 26, 2011 at 08:32:25PM +0100, Joost Kremers wrote: > > On Sat, Feb 26, 2011 at 01:29:21PM -0500, Logan Rathbone wrote: > > > On Thu, Feb 24, 2011 at 02:34:43PM -0600, Puneet Kishor wrote: > > > > So, since nothing is impossible in mutt, how can I get a unified inbox > > > > for my two accounts? > > > > > > I don't think having a specific feature in Mutt is necessary or > > > desirable to achieve this. You can easily have mail from multiple > > > accounts delivered to your mailspool using getmail or fetchmail. > > > > except that that downloads the mail to your local machine. > > Not if you run it on your IMAP server. but it still puts all your mail into a single mail box, which entirely defeats the purpose of a unified inbox. > > mutt is really a one-mail-account kind of mail client. > > That's amusing... I've been using it with multiple accounts for over a > decade. so have i, but you need to resort to some trickery to do that. either by defining macros to change account info (server, username/password), or by collecting the mail into a single mailbox, or (like me) by running multiple instances of mutt within screen/tmux or in different tabs of one's terminal emulator. it's certainly not as simple as: set imap_user[1] = "f...@bar.com" set imap_pass[1] = "baz" set imap_user[2] = "f...@buz.com" set imap_pass[2] = "baz2" > > it would be nice if mutt were to gain the ability to conveniently deal with > > multiple mail accounts within a single instance, but it's up to the > > developers > > to decide if they want to implement it. > > Many would argue that it does that already, and much more flexibly > than other clients do it. define "flexible" in this regard. i'm not aware of anything that mutt can do with multiple accounts that e.g. thunderbird cannot. (and there are things thunderbird can do, and mutt can't, such as the unified inbox, or easily copying messages from one IMAP server to another.) i would say that mutt is so flexible that it is possible to deal with multiple accounts in spite of the fact that it wasn't designed to do so. i mean, if thunderbird were designed to handle just one mail account, there would be no way to use it with more than one. -- Joost Kremers Life has its moments
Re: unified inbox
On Sat, Feb 26, 2011 at 02:53:44PM -0500, Logan Rathbone wrote: > Personally I prefer to use the right tool for the right job. > Thunderbird is a much better IMAP client than Mutt, so why not use > Thunderbird? How so? > I disagree; I think Mutt is more of a 'read mail from file' kind of mail > client. This whole concept of Mutt's directly accessing either the POP3 > or IMAP protocol is a relatively new feature to the client and Mutt > really wasn't originally designed to work that way. Uh huh... That's completely preposterous. > I really don't care for some of the features they've added into 1.5.x, > but I can see why some might see the features as attractive. I tried to > use Mutt as an IMAP client for awhile, but I threw away that approach > because I realized rather quickly that while Mutt may tolerate being > used in that way, it doesn't *want* to. Mutt 1.4 is ancient. It worked about as well as anything did with IMAP circa 2000... IMAP has seen numerous improvements since then, and in order to benefit from them you MUST use the 1.5 tree. Mutt's core IMAP functionality also improved greatly in the 1.5 tree. So if you're using 1.4, well, that's kind of retarded (literally)... Mutt 1.5 is about 9 years old... -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpMiF1KnREZq.pgp Description: PGP signature
Re: unified inbox
On Thu, Feb 24, 2011 at 02:34:43PM -0600, Puneet Kishor wrote: > There is much that I have to do to really get comfortable with mutt, but > I think I am making slow but steady progress. One feature that really > bothers me because of its absence is a unified mailbox. There isn't really any way to do this, except -- as others have said already -- to get all your mail somehow delivered to the same folder. There are many ways to accomplish this... If you have shell access to the server (and it's Unix-like), a .forward file will allow you to redirect all your mail elsewhere. The fetchmail program can be configured to fetch mail from numerous sources and store it all in one folder (this could be on an IMAP server... there isn't any technical reason this needs to be delivered to your desktop). This idea seems somewhat counter to the philosophy of Mutt, which one might summarize as "a place for everything, and everything in its place." Most people I have encountered who use Mutt and enjoy it specifically do not want a unified inbox, myself certainly included. I think it's fair to say that Mutt was not designed with this paradigm in mind... The easiest way to deal with multiple accounts with mutt is to deliver mail from those accounts into specific folders, and use folder hooks to set variables associated with the respective accounts upon entering the folder. Note that I said "easiest" -- it is in no way the only way to do that. > As is, with mutt, I am constantly flipping between one account to > another, and even though I have mapped the F1 and F2 keys to the > inboxes for the two accounts, it is a pain in the derierre. > Everytime mutt has to scan through the cache and rebuild the index > view. This is only a pain if you're keeping thousands of messages in your inbox (maybe hundreds with IMAP). You certainly can do that, but in many ways it would be more efficient to archive read mail into another folder, relegating your inbox for onlyl what that name implies: incoming items. You can, of course, run multiple copies of Mutt, each in a different folder. > So, since nothing is impossible in mutt, how can I get a unified > inbox for my two accounts? Many things are impossible in Mutt, and many other things are possible but hard or painful. In some cases, the folks on the list have struggled with the same problems you are encountering and can help provide solutions. But if you're committed to the speed and power of Mutt, yet can't find a solution to make a particular aspect of Mutt behave the way you want, it may sometimes be more fruitful to consider changing the way you think about and handle your mail. Mutt is fast and powerful, but it is definitely not for everyone. -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpfxvBYYw5HX.pgp Description: PGP signature
