Difference between revisions of "MailFerret"
Jump to navigation
Jump to search
(→Current Status: 9/30) |
(→Current Status: wanted features) |
||
Line 9: | Line 9: | ||
So I guess I need to provide a way to store the raw timestamp when the parsing code says "huh?". | So I guess I need to provide a way to store the raw timestamp when the parsing code says "huh?". | ||
==Wanted Features== | |||
* Log of all messages received so I can be *sure* I didn't receive a message (and can find out where it went if I did -- deleted, manually filed, filed by filter, etc.) Log should be viewable by filter, i.e. what messages has this filter been applied to? | |||
* Temporary disablement of individual or all filters (without having to delete them) | |||
* Filters should indicate when they were last applied | |||
* Filters should be applicable automatically or on demand | |||
* Filters should be runnable on any folder (not just inbox) | |||
* Scripting extensions (like what Gimp has), triggerable by events: on receipt of mail, on deletion of mail, on use of filter, on calendar/timer event... |
Revision as of 14:04, 25 November 2005
This article is a stub requiring substantial initial content from Woozle. Although you may be able to help expand it, it is more likely that Woozle will have to finish setting up the initial content before it will make sense to anyone else.
Woozle: Projects: Software: HyperMail
Current Status
- 2005-09-30 Latest problem is that I've run into one of the limits of MS Access -- an error pops up when HyperMail tries to add new records, something like "database size limitation exceeded". The .mdb file is about a gigabyte; I tried compressing it, but Access just locked up... and the import isn't really anywhere near completion. So it's time to try another database engine. I have to set up a MySQL server on Camilla and see if I run into the same problem using Access as a front end connector, or if I have to somehow go directly (via ADO, maybe).
- 2005-05-11 The Mozilla/Thunderbird code is basically working, although very slowly... and I keep running into variations of the timestamp format. First it was a malformed timezone string: "+0-900" or maybe it was "-0+900", I forget... but then the latest is this one:
mi�, 06 ago 2003 05:52:52 -0400
So I guess I need to provide a way to store the raw timestamp when the parsing code says "huh?".
Wanted Features
- Log of all messages received so I can be *sure* I didn't receive a message (and can find out where it went if I did -- deleted, manually filed, filed by filter, etc.) Log should be viewable by filter, i.e. what messages has this filter been applied to?
- Temporary disablement of individual or all filters (without having to delete them)
- Filters should indicate when they were last applied
- Filters should be applicable automatically or on demand
- Filters should be runnable on any folder (not just inbox)
- Scripting extensions (like what Gimp has), triggerable by events: on receipt of mail, on deletion of mail, on use of filter, on calendar/timer event...