* Rocco Rutte pd...@gmx.net [2009-04-28 05:02 -0500]:
It would be nice if you could keep an eye on database file sizes. If
the db libraries don't reuse freed space (either by deleted or updated
entries), then we get a growing db file.
I'm running HEAD with your patch, and am running the
Hi,
* David J. Weller-Fahy wrote:
I have been using it, IMAP only as well, since the 18th of April, and
have had no problems.
I've got the Go to include it the mainline, thanks to everybody for
testing.
It would be nice if you could keep an eye on database file sizes. If the
db libraries
* Kyle Wheeler kyle-m...@memoryhole.net [2009-04-23 12:01 -0500]:
I'm using it since a few days (no imap, only local Maildir), no
problem so far.
I've been using it for a few days now too, with IMAP only, and it
seems to work fine for me.
I have been using it, IMAP only as well, since the
Hi,
* Kyle Wheeler wrote:
On Saturday, April 18 at 10:43 AM, quoth Paul E Condon:
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
Hi,
* Kyle Wheeler wrote:
On Saturday, April 18 at 02:12 PM, quoth Paul E Condon:
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.
I doubt it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 19 at 02:26 PM, quoth Rocco Rutte:
The problem with hcache is (currently, without the patch attached to
ticket #2942) that it's written only once when initially parsing the
message. Thus, if the date is Epoch upon first parse,
Hi,
* Kyle Wheeler wrote:
On Sunday, April 19 at 02:26 PM, quoth Rocco Rutte:
The problem with hcache is (currently, without the patch attached to
ticket #2942) that it's written only once when initially parsing the
message. Thus, if the date is Epoch upon first parse, it'll be that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, April 19 at 04:07 PM, quoth Rocco Rutte:
* Kyle Wheeler wrote:
On Sunday, April 19 at 02:26 PM, quoth Rocco Rutte:
The problem with hcache is (currently, without the patch attached to
ticket #2942) that it's written only once when
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
-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
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
-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
12 matches
Mail list logo
