Closed
Bug 167944
Opened 22 years ago
Closed 22 years ago
Customized headers troubles with mozilla 1.0.1 (but not with 1.0 !!)
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: fl, Assigned: naving)
Details
After update from 1.0 to 1.0.1 mozilla-mail does write nonsense custom-headers to prefs.js and the imap-server blocks any attempt to get mails with bogus headers. Maybe someone broke the "rules.dat" parser? Content of user.js (the same line from prefs.js was removed with editor): user_pref("mailnews.customHeaders", "Delivered-To: List-Post: Newsgroup: \ Newsgroups: Precedence: Received: Reply-To: Sender: list-post: X-BeenThere: \ X-Loop: X-Mailing-List: X-Mailinglist: X-Orcpt: X-Virus-To:"); After mozilla-mail 1.0.1 ran see prefs.js: user_pref("mailnews.customHeaders", "Delivered-To: List-Post: Newsgroup: \ Newsgroups: Precedence: Received: Reply-To: Sender: list-post: X-BeenThere: \ X-Loop: X-Mailing-List: X-Mailinglist: X-Orcpt: X-Virus-To:: OR ("); FIX: remove the "customHeader" line from prefs.js and downgrade to 1.0 and all is fine again. "rules.dat" file available on request.
Assignee | ||
Comment 2•22 years ago
|
||
Could you try latest nightly trunk builds and see if it works for you ? thx.
Reporter | ||
Comment 3•22 years ago
|
||
tried nightly build Mozilla 1.2a Mozilla/5.0 (X11; U; Linux i586; ast-ES; rv:1.2a) Gecko/20020912 Now it shows up an alert dialog that one of my custom headers contains an invalid character. BUT I can not find any such invalid character. Can I mail you my rules.dat so you can try it?
Assignee | ||
Comment 4•22 years ago
|
||
yes, you can mail it to me. Did you edit your prefs.js to remove OR (
Reporter | ||
Comment 5•22 years ago
|
||
rules.dat will come in private mail prefs.js is clean: # grep mailnews.customHeaders prefs.js user_pref("mailnews.customHeaders", "Delivered-To: List-Post: Newsgroup: \ Newsgroups: Precedence: Received: Reply-To: Sender: list-post: X-BeenThere: \ X-Loop: X-Mailing-List: X-Mailinglist: X-Orcpt: X-Virus-To:");
Assignee | ||
Comment 6•22 years ago
|
||
Thanks, will take a look.
Assignee | ||
Comment 7•22 years ago
|
||
One of your rules has 'OR (' as header. Do you know how that happened ? description="Linux Kernel Mailing List" type="1" action="Move to folder" actionValue="imap://fl@mail.fl.priv.at/Ablage/1999/Mailing Listen/Linux-Kernel" condition="OR (from,contains,linux-kernel@vger.rutgers.edu) OR (to or cc,contains,linux-kernel@vger.rutgers.edu) OR (from,contains,owner-linux-kernel@vger.rutgers.edu) OR (OR (,contains,owner-linux-kernel@vger.rutgers.edu)"
Reporter | ||
Comment 8•22 years ago
|
||
Not really, but I had troubles some time ago maybe when testing mozilla 1.1a or the like. This rule was converted by netscape 6.2.something from my netscape 4.7 settings. After converting my rules and addressbooks with netscape 6.x I changed to mozilla. Never changed that rule in the last two years or so. As you can see I was on the linux kernel list in 1999 and before. Sorry but because of the long rule I overlooked the occurance of the second OR (. So now mozilla 1.0.1 does build up the list of custom headers from the rules.dat file, doesn't it? Now I'll try mozilla 1.0.1 with a cleaned rules.dat. I'll clean all headers from prefs.js and user.js to see if it is working the way it should.
Reporter | ||
Comment 9•22 years ago
|
||
OK, now it works. When I have a look at the mailrule file from netscape 4.7x (still there, who knows when you need it :) the rule look like below. So somewhere in the converting from ns4.7x to mozilla it happend. But I can swear that I can tell you where it happend. description="Linux Kernel Mailing List" type="1" action="Move to folder" actionValue="//imap:Ablage/1999/Mailing Listen/Linux-Kernel" condition=" OR (from,contains,linux-kernel@vger.rutgers.edu) OR (to or CC,contains,linux-kernel@vger.rutgers.edu) OR (from,contains,owner-linux-kernel@vger.rutgers.edu) OR (\"Sender\",contains,owner-linux-kernel@vger.rutgers.edu)"
Comment 10•22 years ago
|
||
Reporter: Can we resolve this bug then?
Reporter | ||
Comment 11•22 years ago
|
||
As I can not swear when this happend I can not tell you which mozilla version did corrupt the rule in question. I suggest bringing up the rule with the error if the user presses a "show rule" button and not only showing that there is an error in one of the rules. Emphasizing the part of the rule that breaks would be nice too :)
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•