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: Saved Messages Header
* Patrick Shanahan [2013-01-30 11:40:05 -0500]: > * Ed [01-30-13 10:48]: > > How do I strip the headers when I save a message ? > > I know of no *mutt* specific facility, but rebinding to script > which would perform the actions you wish would be possible. Note: I > believe the resulting mail would be *unread*. Ok, what you need to do is when in the pager view, press 'v' to view attachments and it will list the mime parts of the mail. So if you just want to save the text part of the mail, you use the arrow keys to select the text/plain part, for example, and the press 's' to save and at the bottom it will ask you where to save the file; i.e. ~/patricksresponse. Then when you use another terminal and use cat or less on the file it will show you just the mail itself, no headers. This code was inherited from mail(1) I believe as it has the same ability to save messages without headers, for example diff files or code files and scripts that you want to save, obviously you wouldn't need the headers with those types of mail. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Saved Messages Header
On Jan 31, James Griffin wrote: > Ok, what you need to do is when in the pager view, press 'v' to > view attachments and it will list the mime parts of the mail. So > if you just want to save the text part of the mail, you use the > arrow keys to select the text/plain part, for example, and the press > 's' to save and at the bottom it will ask you where to save the > file; i.e. ~/patricksresponse. Then when you use another terminal > and use cat or less on the file it will show you just the mail > itself, no headers. This code was inherited from mail(1) I believe > as it has the same ability to save messages without headers, for > example diff files or code files and scripts that you want to save, > obviously you wouldn't need the headers with those types of mail. Thank you, just what I was looking for. Works well. Ed
Re: headers in mail vs forward vs bounce
On Wed, Jan 30, 2013 at 01:42:14PM -0600, Luis Mochan wrote: Of course, in this example Amavis rejected the message, but it seems it did so for a good reason, as the message had this strange characters \303\241. So I guess the problem is my configuration of mutt (or mutt itself). That is the utf-8 encoding of: U+00E1 á c3 a1 LATIN SMALL LETTER A WITH ACUTE I just checked the source code, and it does look like the Resent-To addresses are RFC2047-encoded at sendlib.c:2614
Re: headers in mail vs forward vs bounce
On Fri, Feb 01, 2013 at 04:06:42AM +, Michael Elkins wrote: On Wed, Jan 30, 2013 at 01:42:14PM -0600, Luis Mochan wrote: Of course, in this example Amavis rejected the message, but it seems it did so for a good reason, as the message had this strange characters \303\241. So I guess the problem is my configuration of mutt (or mutt itself). That is the utf-8 encoding of: U+00E1 á c3 a1 LATIN SMALL LETTER A WITH ACUTE I just checked the source code, and it does look like the Resent-To addresses are RFC2047-encoded at sendlib.c:2614 I just did a test and it does appear that Mutt is properly encoding the header: Resent-To: Luis =?iso-8859-1?Q?Moch=E1n?= me
Re: headers in mail vs forward vs bounce
On Fri, Feb 01, 2013 at 04:10:52AM +, Michael Elkins wrote: I just did a test and it does appear that Mutt is properly encoding the header: Resent-To: Luis =?iso-8859-1?Q?Moch=E1n?= This is change that fixed the above problem. It looks like the package of mutt you are using doesn't include this fix. http://dev.mutt.org/hg/mutt/rev/b574d6f9f532 changeset: 6183:b574d6f9f532 branch: HEAD user:Michael Elkins date:Mon Jun 20 16:39:27 2011 -0700 summary: rfc2047 encode recipient list in resent-to header field. closes #3512
