fixing email dates
I have a number of malformed emails that I want to save in an archive. Before I archive them I want to make the dates right. Now they appear in Mutt with the date: 1970-01-01 00:00:00. I know what this date is, and from other records, I can assign a more honest date to each of them. I had thought that I could edit into the email a Date: header with the correct date, but that doesn't seem to work, for me. I still get the Unix Epoch in the index display. I have editted in both Date: and Delivery-date: headers. I can see them when I open an email and visually read the headers. But I want that date to appear in the index as well. Where does Mutt get the date that it displays in 'index-format'? What is the correct format for that date? What does Mutt do with emails for which it cannot parse the date? Is there a secret database somewhere in which Mutt keeps what it thinks it the real date? Etc. Etc... I'm using Maildir format for all by emails. TIA -- Paul E Condon pecon...@mesanetworks.net
a puzzlement
I just posted a question about dates on emails. When I exited Mutt after sending it I noticed a feature of Mutt that has long puzzled me and I decided to ask what about it: When Mutt closes, it invariable issues the message: Mailbox is unchanged. This message regardless of how much or how little work I have done. Once I got it after I deleted 20,000 emails from a single mailbox, or maybe I misunderstand what a mailbox is. Anyway, what does this message mean? Should I ever expect to see a different message? Why is it there? I'm puzzled TIA -- Paul E Condon pecon...@mesanetworks.net
Re: a puzzlement
On Sat, Apr 18, 2009 at 10:53:39AM -0600, Paul E Condon wrote: I just posted a question about dates on emails. When I exited Mutt after sending it I noticed a feature of Mutt that has long puzzled me and I decided to ask what about it: When Mutt closes, it invariable issues the message: Mailbox is unchanged. If you delete some message, it will say something like '1 deleted, 100 kept'. -- Zhengquan
Re: a puzzlement
* On 18 Apr 2009, Paul E Condon wrote: When Mutt closes, it invariable issues the message: Mailbox is unchanged. Do you sync-mailbox before you quit or exit? Mailbox is unchanged means that no messages were changed since the last sync. (It doesn't count changes since startup, just changes to the current context; and the context is reset whenever you sync.) -- -D.d...@uchicago.eduNSITUniversity of Chicago
Re: Color problem for mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, April 18 at 10:27 AM, quoth He Wen: i wanna know how to highlight a specific field of a index item, for example, the date field? There's no good way, unfortunately. There may be a patch out there somewhere that allows you to do it, but in standard mutt... nope. I thought that maybe you could do it by changing your $index_format to include color-changing commands... but that gets passed through iconv (apparently), so the ansi color commands get masked out by question marks. ~Kyle - -- Victory goes to the player who makes the next-to-last mistake. -- Chessmaster Savielly Gricorievitch Tatrtak -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAknqGPkACgkQBkIOoMqOI17C4gCgyxyJqBsbMDNILBDYLtqc9kgM fZoAnjruMjvxe12g33/lXhJ7Vq56YJXf =GgtR -END PGP SIGNATURE-
Re: a puzzlement
On 2009-04-18_12:05:51, David Champion wrote: * On 18 Apr 2009, Paul E Condon wrote: When Mutt closes, it invariable issues the message: Mailbox is unchanged. Do you sync-mailbox before you quit or exit? Mailbox is unchanged means that no messages were changed since the last sync. (It doesn't count changes since startup, just changes to the current context; and the context is reset whenever you sync.) What is a sync in this context? Is it something I should be doing? I thought Mutt did what I think of as sync without my asking. I just did a string search on 'sync-mailbox' in the Mutt info page and got no hits. Where is it documented? -- Paul E Condon pecon...@mesanetworks.net
Re: fixing email dates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, April 18 at 10:43 AM, quoth Paul E Condon: I had thought that I could edit into the email a Date: header with the correct date, Yup, that's the way to do it. Let me guess: you edited the message outside of mutt, and you use header caching. When you relaunched mutt, it didn't think the message had changed, since the filename was the same (which is an assumption it makes about Maildir messages), so it simply used the cached value of the Date header when rendering the index list. but that doesn't seem to work, for me. I still get the Unix Epoch in the index display. I have editted in both Date: and Delivery-date: headers. I can see them when I open an email and visually read the headers. But I want that date to appear in the index as well. That date also gets stored in the header cache. Where does Mutt get the date that it displays in 'index-format'? It gets it from the Date header. What is the correct format for that date? It's the format specified in section 5 of RFC 822. http://www.ietf.org/rfc/rfc0822.txt What does Mutt do with emails for which it cannot parse the date? It uses the epoch. Is there a secret database somewhere in which Mutt keeps what it thinks it the real date? Etc. Etc... Nope. But mutt can cache the date header (if you told it to). ~Kyle - -- In all matters of opinion, our adversaries are insane. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAknqHOUACgkQBkIOoMqOI14F+QCgvoVD5kJPxIMZwyF2rhJZciUu EyAAmwXnf4Gz8uzGNG9qiHfyRBuy+75/ =Hh8l -END PGP SIGNATURE-
Re: a puzzlement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, April 18 at 12:29 PM, quoth Paul E Condon: What is a sync in this context? Essentially, when mutt opens a mailbox, it builds a picture of the mailbox's state in memory. When you mark messages as deleted, this is done in memory, rather than immediately to disk (this is to speed up common use, and also to make it possible to undelete messages to some extent). When you sync, the changes from memory are written to disk. A sync normally happens when you close a mailbox, but can be triggered earlier. Is it something I should be doing? Generally, it's something you already do whenever you close a mailbox. I thought Mutt did what I think of as sync without my asking. It does. But it does it whenever you close a mailbox (e.g. by changing to a different one). I just did a string search on 'sync-mailbox' in the Mutt info page and got no hits. Where is it documented? It's documented in the manual: http://www.mutt.org/doc/devel/manual.html, though it doesn't go into great detail... it really just alludes to the synchronization. ~Kyle - -- University politics are vicious precisely because the stakes are so small. -- Henry Kissinger -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAknqHz0ACgkQBkIOoMqOI17LpwCgqrngAsKWDx7IcIMpG1NyXrjI /QYAoJ3aJrzECbdl4nOcLSmxnpLWaE94 =5hDX -END PGP SIGNATURE-
Re: Color problem for mutt
Hi, * He Wen schrieb am Samstag, den 18. April 2009: i wanna know how to highlight a specific field of a index item, for example, the date field? Here is the Indexcolor Patch: http://greek0.net/mutt.html Andreas
Re: fixing email dates
On 2009-04-18_13:33:09, Kyle Wheeler wrote: On Saturday, April 18 at 10:43 AM, quoth Paul E Condon: I had thought that I could edit into the email a Date: header with the correct date, Yup, that's the way to do it. Let me guess: you edited the message outside of mutt, and you use header caching. When you relaunched mutt, it didn't think the message had changed, since the filename was the same (which is an assumption it makes about Maildir messages), so it simply used the cached value of the Date header when rendering the index list. but that doesn't seem to work, for me. I still get the Unix Epoch in the index display. I have editted in both Date: and Delivery-date: headers. I can see them when I open an email and visually read the headers. But I want that date to appear in the index as well. That date also gets stored in the header cache. Where does Mutt get the date that it displays in 'index-format'? It gets it from the Date header. What is the correct format for that date? It's the format specified in section 5 of RFC 822. http://www.ietf.org/rfc/rfc0822.txt What does Mutt do with emails for which it cannot parse the date? It uses the epoch. Is there a secret database somewhere in which Mutt keeps what it thinks it the real date? Etc. Etc... Nope. But mutt can cache the date header (if you told it to). OK, header cache is the mysterious something that was stopping me. How do I empty the header cache and force a reload from disk? Preferably without exiting Mutt, so that I can check my work as I go. -- Paul E Condon pecon...@mesanetworks.net
Re: fixing email dates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, April 18 at 02:12 PM, quoth Paul E Condon: Nope. But mutt can cache the date header (if you told it to). OK, header cache is the mysterious something that was stopping me. Hardly mysterious... header caching isn't turned on by default, so if it's enabled, YOU enabled it. How do I empty the header cache and force a reload from disk? Essentially, by deleting it and relaunching mutt. Preferably without exiting Mutt, so that I can check my work as I go. You can't do it without exiting mutt, BUT there's a better way to edit messages. Edit the message FROM WITHIN MUTT (i.e. with the edit-message function, which is bound to the e key by default). Mutt will launch your $editor for editing the message. When you do it that way, mutt knows that the contents of the message changed and need to be re-parsed. ~Kyle - -- The truth is that there are no things for which men will make such herculean efforts as the things of which they know they are unworthy. -- G. K. Chesterton -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAknqOAcACgkQBkIOoMqOI15bogCfRF1Z2oYL6xgFBZCGYDxh/O0a WFwAn0zxGvhmRJe3dPWddTo466jp6ERz =hrHy -END PGP SIGNATURE-
pop-last=yes isn't working?
Hi All, I am accessing my pop via smtp and everything is working fine. Whenever i download mail, it asks if i want to delete them from the server. If i don't the next time i check, mutt has downlaoded them again. If i DO remove them from the server, my phone, or web access cannot find those mails. I read through the docs and set the pop_last = yes, thinking this would force mutt not to redownload messages it already has downloaded. When i tried this however, it doesn't seem to make difference. Can anyone shed some light on this? Thanks, Russ
Re: a puzzlement
On 2009-04-18_13:43:09, Kyle Wheeler wrote: On Saturday, April 18 at 12:29 PM, quoth Paul E Condon: What is a sync in this context? Essentially, when mutt opens a mailbox, it builds a picture of the mailbox's state in memory. When you mark messages as deleted, this is done in memory, rather than immediately to disk (this is to speed up common use, and also to make it possible to undelete messages to some extent). When you sync, the changes from memory are written to disk. A sync normally happens when you close a mailbox, but can be triggered earlier. Is it something I should be doing? Generally, it's something you already do whenever you close a mailbox. I thought Mutt did what I think of as sync without my asking. It does. But it does it whenever you close a mailbox (e.g. by changing to a different one). I just did a string search on 'sync-mailbox' in the Mutt info page and got no hits. Where is it documented? It's documented in the manual: http://www.mutt.org/doc/devel/manual.html, though it doesn't go into great detail... it really just alludes to the synchronization. I found my problem. I wasn't using header cacheing, but I also wasn't getting RFC2822 date format correct. So, naturally I kept getting Epoch. Thanks and sorry about having an annoying way of expressing myself. -- Paul E Condon pecon...@mesanetworks.net
