16.58 KB, text/plain
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla Thunderbird 0.4 (20031205) Particulars: TB 0.4 (20031205) Win98SE ( 250megs ram ) Mail Server = RH8.0+QMail+Vpop using virtual domains ( my own server ) Problem: PMV in DBIENG.DLL Result: TB Crash Most Probable cause: Extreme length of subject: header in e-mail message ( exceeding 4000 char ). This may be having causes in the routines for display and the routines for building the .msf files. Best Fix Opinion Hard limit on subject: header buffer <= char(254) Narative: Opened t-bird to retrieve messages, message retrieval going fine, PMV occurs and choices are Ignore/Close. Review of screen output shows message with waht appears to be several overwritten subject lines as the last message retrieved., tb shuts down. Attempted TB restart and immediate PMV occurs. Delete inbox & inbox.msf Restart TB message retrieved until message with excessive header reached, TB PMV's Get on the mail server, mv *.* /hold from Maildir. Restart TB. TB Restarts but behaves quirkily can will not retrieve. Shutdown TB, Delete popstate file and restart TB retrieves new mail, but does not display or run filters. After deleteing both inbox & inbox.msf several times and restarting TB _something_ shakes out and system behaves normally again. grep'd the mail in /hold found two message files with long subject lines, review of messages shows one with a subject: header length of 4733 bytes, then other 5432 bytes. Both of these message are SPAM with spoofed addresses and sender ID's. Reproducible: Always Steps to Reproduce: 1. receive and e-mail message with a subject: header of like 4K 2. 3. Actual Results: PMV in DBIENG.DLL, system crash Expected Results: Hard limit on subject: header buffer <= char(254) I have an offending message file ( inbox format ) that I can send for testing.
Created attachment 139578 [details] This is a segment of the inbox file that causes the crash use this file to validate the bug.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.