155496 - error mesg about FETCH BODY.PEEK[HEADER.FIELDS pops up when setting up a customized header in Filters

Status: VERIFIED DUPLICATE of bug 107620

(MailNews Core :: Networking: IMAP, defect)

Description

[grylchan]

Using commercial trunk
2002-07-01-08-trunk/ NT 4.0
2002-07-02-08-trunk/ mac 9.2.2
2002-07-02-04-trunk/ linux 2.2

If I create a filter for a custom header,send myself a mesg
that will be filtered based on that custom header, whenever I do
a 'GetMsg', I instead get an error mesg:
   The current command did not succeed. the mail 
   server responded:Invalid field-name in UID 
   FETCH BODY.PEEK[HEADER.FIELDS. 

I ran into this problem trying to test bug 137994

I was trying to filter a mesg by creating a customized header.
These were the filters/customized headers I did:
  -'X-Accept-Language:' contains 'en-us, en' 
    move to folder sent on local folders. 
  -'User-Agent:' contains 'Mozilla/5.0'
    move to folder sent on local folders. 
  -'Received:' contains 'linzilla'
    move to folder 'x' on local folders

Steps to reproduce:
1.Create a imap mail account
2.Login
3.Go to filters
4.Click new button
5.Click on drop down menu item called subject
6.Select Custom
7.Add a custom header (like User Agent: or Received:)
8.Save filter
9.Comose a mesg that will be filtered based on your custom header
10.Send it to yourself
11.Do a Get Msgs
result: the error mesg appears and you don't actually receive the mesg
expected: to receive the mesg and no error mesg to appear

I assume I am doing customized headers correctly? Never did it before.
I am using Netscape mesg server 4.15 in case there is some setting
on the server I need to set up for custom headers?

Comment 1

[Karen Huang]

This might be dup of bug 153251 when I tried to narrow down problem with Sarah.
Still investigating.....

Comment 2

[David :Bienvenu]

yes, it looks like a dup - Sarah has a filter on a custom header, "/Received",
so it looks the same to me.

Comment 3

[David :Bienvenu]

my guess is that I broke this somehow so I'll look into it.

Comment 4

[grylchan]

Laurel pointed out when I was doing my custom headers
that I included the ':' when I shouldn't have.

I tested again on commercial trunk 2002070808 on linux 2.2
and I did not get the error mesg.

So maybe custom headers do work and user error?

Comment 5

[David :Bienvenu]

Oh, well, a user error that shouldn't have resulted in a program error, then.
Thx for the info. It sounds like the code we have that parses the custom headers
has a problem. I was afraid that I'd broken the custom header downloading in the
imap protocol code, but it doesn't sound as likely anymore.

Comment 6

[laurel]

We do have an old bug about the colon not being stripped (ui oriented) - bug
107620. I'm not sure about sairuh's input, though.

Comment 7

[Karen Huang]

From above Gary and Laurel's comments, I am thinking this bug should be dup of 
bug 107260.
Bug 153251 is different with this bug since when I worked with Sarah. She didn't 
put the colon for it......

Comment 8

[Karen Huang]

I mean this bug should be dup of bug 107620....

Comment 9

[David :Bienvenu]

dup of 107620 - I'll go add a comment to that bug.

*** This bug has been marked as a duplicate of 107620 ***

Comment 10

[laurel]

OK, marking verified as duplicate