User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20060909 FreeBSD/i386 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20060909 FreeBSD/i386 Firefox/184.108.40.206 One of my nightly scripts sends out an email with an "Update" alert at the very bottom. Unfortunately, it's rather dumb, so it doesn't modify the subject or anything - it will detect if something needs my attention, and output this phrase as the second-to-last line in the cron email. I set up a mail filter to detect when this phrase occurs (since it doesn't happen every time), but it seems to have trouble when the data preceding the message is over a certain length (approx. 2kb) The filter is: Match any; Body contains "** ADDRESSBOOK UPDATED **"; move to New Addressbook folder The emails don't have attachments, they're just textual output (output from a "diff", in this case), but if they are over 2kb the match doesn't seem to occur. Because the Thunderbird size listing is ... shall we say ... inaccurate, I can't nail down an exact byte threshhold that this occurs at. It seems that one or two "2kb" messages have matched properly, but several 2kb ones have failed, and one 5kb one failed - there haven't been any in between that range that I can test with. Reproducible: Sometimes Steps to Reproduce: 1. Create a message filter on "body contains" to move a message based on a string 2. Receive an email with 2 or 3 kb of text *before* the string occurs Actual Results: The message doesn't seem to move. Expected Results: The message should move to the desired folder. This is with Thunderbird 220.127.116.11, 20060909.
Kevin, imap or pop? are you on version 2 yet?
no response from reporter => incomplete
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 1.5
It's under POP3, and 18.104.22.168 at the moment (Fedora Core 6). However, I modified the script that is sending the message, so it's no longer a concern.
You need to log in before you can comment on or make changes to this bug.