© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f399f05
demo site
(Get the code!)
> Nonetheless, I see this issue with 1.5.0.12, exactly as described.
> Specifically, with the "Received" header, which must be defined as a custom
> header as it is not (for some inexplicable reason) included among the standard
> headers.
The reason that this bug was re-activated is because of broken IMAP Server Search functions. "Some people" complained that "after the fact" filtering was broken and it turned out that the reason that it was broken is that the IMAP search functions were not implemented or not implemented correctly.
Probably the best way to solve this issue, is not to use the IMAP search functions but to cache the headers in the .MSF databases then let Thunderbird do rest. And, I agree with the statement:
> It would be nice to have an option to store headers but not body locally,
> wouldn't it?
Because some users might be limited by disk drive space.
Until there is a fix, I will do "after the fact filter" one of two ways... since I am the admin of the one of the servers. I have created a folder called
"- temp" so that I can easily move the messages I want filter into that folder. I will create a filter based upon the message. Since my IMAP server stores email in individual files, I then can at the OS level move the files from the temp folder back to the Inbox folder. Now Thunderbird thinks it is a new message and run the filter as if it was new mail. On the server that I don't have admin rights to, I use the offline function.
George