61493 - migrate custom headers

Status: VERIFIED FIXED

(MailNews Core :: Profile Migration, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

I'm pretty sure it isn't working since we don't support custom headers (for
search or filters) yet.

this bug is just a place holder for now.

Comment 1

[laurel]

Just for reference: bug 16902 is main custom header bug.

Comment 2

[(not reading, please use [e-mail] instead)]

migration bugs to racham

Comment 3

[(not reading, please use [e-mail] instead)]

over to naving.

I think the custom header pref hasn't changed, and now that we support custom 
headers, this is fixed.

Comment 4

[Navin Gupta]

yes this is fixed. 

Comment 5

[laurel]

Using may20, only OK for windows -- used win98:
Custom headers migrated, show up in prefs.js, Search Messages UI, Filters UI in
dropdown and with existing filters using custom headers.


Not OK: Linux has existing problem reported in bug 107648.  Migrated custom
headers are not separated and can't be removed (We parse headers based on a
colon ": ", 4.x unix didn't use a colon, but used a space " " instead.)  Said
clumped headers will not appear in existing filters; the criteria gets reset to
default Subject. Said  headers appear as one selection in Search UI and Filter
UI dropdowns.

Am going to test mac again, but I assume it will exhibit the same problem since
4.x mac used a space instead of colon as separator in the custom headers pref line.

So, should I mark this reopened since it really only works in a usable fashion
for Windows? Or will we rely on bug 107468 as the open (and minused) issue?

Comment 6

[Navin Gupta]

let us mark this verified. We will rely on bug 107468 for open (minused) issue. 

Comment 7

[laurel]

Yes, same on Mac using may21 branch.
Marking this verified per naving.