IMAP: Huge mail (117 attachments) gives me "S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively complex FETCH attribute list" error

NEW
Unassigned

Status

--
major
19 years ago
8 years ago

People

(Reporter: bugzilla, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [has protocol log])

Attachments

(2 attachments)

(Reporter)

Description

19 years ago
I have a mail that consist of 107 forwarded messages. When trying to read this 
mail I'm getting an error but in the UI and in the IMAP log:

1284[241bd08]: fep2.sprawl.dk:S-INBOX:SendData: 8 UID fetch 1182 (BODY[HEADER] 
BODY[1.MIME] BODY[2.MIME] BODY[2.1.MIME] BODY[2.1.HEADER] BODY[2.2.MIME] 
BODY[2.2.HEADER] BODY[2.3.MIME] BODY[2.3.HEAD
1284[241bd08]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively 
complex FETCH attribute list
(Reporter)

Comment 1

19 years ago
Created attachment 10149 [details]
Big mail that gives me error when reading...

Comment 2

19 years ago
are the forwards nested, or is it one msg with 107 attachments?

Updated

19 years ago
Severity: normal → major
QA Contact: lchiang → huang
Summary: Huge mail gives me "S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively complex FETCH attribute list" error → IMAP: Huge mail gives me "S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively complex FETCH attribute list" error
(Reporter)

Comment 3

19 years ago
I think that it's a mail with 107 attachments. At least in Outlook Express the 
attachment dropdown box contains 107 entries...
(Reporter)

Comment 4

19 years ago
The errors that I'm getting in alerts are:
"The current did not succeed. The mail server responded:Excessively complex 
FETCH attribute list"
and then right after I click OK:
"The current did not succeed. The mail server responded:FETCH could not complete 
for one or more messages"


The IMAP server log:
20000622 230413390+0200 fep2.sprawl.dk imapserv 15357 8 28 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=16 UID 
fetch 1132 (BODYSTRUCTURE):fromhost=193.163.158.4
20000622 230423101+0200 fep2.sprawl.dk imapserv 15357 8 28 
Warn;ImapCommandFailedReason(56/21) Excessively complex FETCH attribute 
list:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=17 UID 
fetch 1132 (BODY[HEADER] BODY[1.MIME] BODY[2.MIME] BODY[2.1.MIME] 
BODY[2.1.HEADER] BODY[2.2.MIME] BODY[2.2.HEADER] BODY[2.3.MIME] BODY[2.3.HEADER] 
BODY[2.4.MIME] BODY[2.4.HEADER] BODY[2.5.MIME] BODY[2.5.HEADER] BODY[2.6.MIME] 
BODY[2.6.HEADER] B:fromhost=193.163.158.4
20000622 232922193+0200 fep2.sprawl.dk imapserv 15357 8 28 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=18 UID 
fetch 1132 (BODY[0]):fromhost=193.163.158.4
20000622 232922194+0200 fep2.sprawl.dk imapserv 15357 8 28 
Warn;ImapCommandFailedReason(56/21) FETCH could not complete for one or more 
messages:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=18 UID 
fetch 1132 (BODY[0]):fromhost=193.163.158.4


Comment 5

19 years ago
right, this is a server "limitation". Does Netscape 4.5 or 4.7 have the same
problem?

Comment 6

19 years ago
Henrik, can you try to reproduce on Communicator 4.5 or 4.7 since you have that 
mail that consist of 107 forwarded messages?
(Reporter)

Comment 7

19 years ago
It works fine in Netscape 4.73.
The IMAP server is my software.com server...
(Reporter)

Comment 8

19 years ago
The IMAP server log when accessing the mail with Netscape 4.73:
20000623 092407976+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:from=<hege@fep2.sprawl.dk>:mss=back:port=5006:mbox=12321442661
:fldr=INBOX:msgid=<1000615153117.972@back.sprawl.dk>:size=353027:cmd=8 UID fetch 
1132 (UID RFC822.SIZE BODY[]<0.6144>):fromhost=193.88.13.34
20000623 092408115+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=9 UID fetch 
1132 (UID RFC822.SIZE BODY[]<6144.6144>):fromhost=193.88.13.34
20000623 092408212+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=10 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<12288.8192>):fromhost=193.88.13.34
20000623 092408396+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=11 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<20480.10240>):fromhost=193.88.13.34
20000623 092408582+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=12 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<30720.12288>):fromhost=193.88.13.34
20000623 092408767+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=13 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<43008.14336>):fromhost=193.88.13.34
20000623 092408968+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=14 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<57344.16384>):fromhost=193.88.13.34
20000623 092409162+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=15 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<73728.18432>):fromhost=193.88.13.34
20000623 092409427+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=16 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<92160.20480>):fromhost=193.88.13.34
20000623 092409674+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=17 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<112640.22528>):fromhost=193.88.13.34
20000623 092410013+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=18 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<135168.24576>):fromhost=193.88.13.34
20000623 092410317+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=19 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<159744.26624>):fromhost=193.88.13.34
20000623 092410527+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=20 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<186368.28672>):fromhost=193.88.13.34
20000623 092410611+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=21 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<215040.30720>):fromhost=193.88.13.34
20000623 092410685+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=22 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<245760.32768>):fromhost=193.88.13.34
20000623 092411069+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=23 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<278528.34816>):fromhost=193.88.13.34
20000623 092411458+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=24 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<313344.36864>):fromhost=193.88.13.34
20000623 092411908+0200 fep2.sprawl.dk imapserv 15357 8 31 Note;MsgTrace(65/26) 
retr:user=gemal01:mss=back:port=5006:mbox=12321442661:fldr=INBOX:cmd=25 UID 
fetch 1132 (UID RFC822.SIZE BODY[]<350208.2819>):fromhost=193.88.13.34
(Reporter)

Comment 9

19 years ago
I've now created an account on my IMAP server with the mail in the Inbox. 
Anybody who needs to test this can get login/password by emailing me 
(gemal@dk.net)...

Comment 10

19 years ago
I email to you already.

Comment 11

19 years ago
By using today's 06-26-09-M17 commercial build 
I got the same results as Henrik:

183[3579bd0]: fep2.sprawl.dk:NA:CreateNewLineFromSocket: * OK IMAP4 server 
(InterMail vM.4.01.02.00 201-229-116) ready Mon, 26 Jun 2000 19:58:12 +0200 (MET 
DST)
183[3579bd0]: fep2.sprawl.dk:NA:SendData: 1 capability
183[3579bd0]: fep2.sprawl.dk:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 
UIDPLUS
183[3579bd0]: fep2.sprawl.dk:NA:CreateNewLineFromSocket: 1 OK CAPABILITY 
completed
183[3579bd0]: fep2.sprawl.dk:NA:SendData: 2 login "mozilla" "netscape"
183[3579bd0]: fep2.sprawl.dk:NA:CreateNewLineFromSocket: 2 OK LOGIN completed
183[3579bd0]: fep2.sprawl.dk:A:SendData: 3 lsub "" "*"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * LSUB () "/" "INBOX"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * LSUB () "/" "SentMail"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * LSUB () "/" "Trash"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: 3 OK LSUB completed
183[3579bd0]: fep2.sprawl.dk:A:SendData: 4 list "" "INBOX"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * LIST () "/" "INBOX"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: 4 OK LIST completed
183[3579bd0]: fep2.sprawl.dk:A:SendData: 5 select "INBOX"
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * 2 EXISTS
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * OK [UIDVALIDITY 
961579650] UIDs valid
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * FLAGS (\Answered 
\Flagged \Deleted \Draft \Seen)
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * OK [PERMANENTFLAGS 
(\Answered \Flagged \Deleted \Draft \Seen)] Permanent flags
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: * 0 RECENT
183[3579bd0]: fep2.sprawl.dk:A:CreateNewLineFromSocket: 5 OK [READ-WRITE] SELECT 
completed
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SendData: 6 UID fetch 1:* (FLAGS)
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: * 1 FETCH (FLAGS 
(\Seen \Deleted) UID 1000)
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: * 2 FETCH (FLAGS 
() UID 1001)
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 6 OK UID FETCH 
completed
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SendData: 7 UID fetch 1001 (BODYSTRUCTURE)
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: * 2 FETCH 
(BODYSTRUCTURE (("text" "plain" ("charset" "US-ASCII") NIL NIL "7BIT" 71 
7)(("message" "rfc822" ("charset" "US-ASCII") "<Pine
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Charles Miller's 
message of "Tue, 5 Oct 1999 10:33:33 +0800" 
"<v6905iiib1.fsf@kechara.flame.org>") ("text" "plain" ("charset" "us-ascii
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) (({19}
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) (({19}
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) ((NIL NIL "coders" "sorcery.net")) NIL NIL NIL 
"<m11nbDU-0002sCC@vex.net>") ("text" "pla
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) (({19}
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) (({19}
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Liam "R." "E." 
Quin NIL "liam" "vex.vex.net")) ((NIL NIL "coders" "sorcery.net")) NIL NIL NIL 
"<m11rp5P-0002wPC@vex.net>") ("text" "pla
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 
<Pine.LNX.4.10.9912062019360.964-400000@mulcahy.demon.co.uk
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket:  > 
"<3.0.5.32.19991227215647.008fa520@atlantis.fukt.hk-r.se>") ("text" "plain" 
("charset" "us-ascii") NIL NIL "7BIT" 722 20) 43)("messa
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: Re: [coders]: fwd: 
[Aureus@xrgaming.net: couple of questions for
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket:  you] (("Mysidia" 
NIL "jmhess" "i-55.com")) (("Mysidia" NIL "jmhess" "i-55.com")) (("Mysidia" NIL 
"jmhess" "i-55.com")) (("Dafydd James
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 7 OK UID FETCH 
completed
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SendData: 8 UID fetch 1001 (BODY[HEADER] 
BODY[1.MIME] BODY[2.MIME] BODY[2.1.MIME] BODY[2.1.HEADER] BODY[2.2.MIME] 
BODY[2.2.HEADER] BODY[2.3.MIME] BODY[2.3.HEADE
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively 
complex FETCH attribute list
183[3579bd0]: fep2.sprawl.dk:S-INBOX:STREAM:OPEN Size: 195635: Begin Message 
Download Stream
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-MessageRFC822: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-MessageHeaders: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-Part-Inline: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SendData: 9 UID fetch 1001 (BODY[0])
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: * 2 FETCH (BODY[0] 
"" UID 1001)
183[3579bd0]: fep2.sprawl.dk:S-INBOX:CreateNewLineFromSocket: 9 NO FETCH could 
not complete for one or more messages
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-Multipart: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-Boundary: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-Boundary: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:SHELL:GENERATE-Boundary-Last: 0
183[3579bd0]: fep2.sprawl.dk:S-INBOX:STREAM:CLOSE: Normal Message End Download 
Stream

Comment 12

19 years ago
load balancing.
Assignee: mscott → bienvenu
Keywords: nsbeta3
Target Milestone: --- → M18

Comment 13

19 years ago
accepting
Status: NEW → ASSIGNED

Updated

18 years ago
Keywords: correctness

Comment 14

18 years ago
this did NOT work in netscape 4.72 - I'll try 4.74, or whatever the latest 
version is, but I'm afraid that if it does work in later versions, it's because 
other things are broken with mime parts on demand in 4.73 and later.
(Reporter)

Comment 15

18 years ago
What do you mean about not working? Do you mean you did or didn't get the error 
that I got?

Comment 16

18 years ago
I mean that 4.72, 4.74, and 6.0 give me the same error, the same one you got
with 6.0. I think that 6.0 is working the same as 4.7x, so I'm less worried
about this bug. I was worried that we were doing something differently by
accident in 6.0, but it doesn't look like we are.
(Reporter)

Comment 17

18 years ago
To be hornest I dont really understand your argumentation: If it didn't work in 
Netscape 4.74, lets make it work as bad in Mozilla?

Comment 18

18 years ago
the argument for not being so concerned about this bug is something as follows:

1. Mozilla should work at least as well as 4.7, and it does in this case.
2. This is a server limitation.
3. The message in question is fairly pathological.

My first priority is achieving parity with 4.7 in as many areas as possible.
After that comes being better than 4.7. We already are better than 4.7 in lots
of ways. If this was easy to fix, I'd fix it, but I don't know how to fix it
easily. I didn't write the mime parts on demand code in 4.7, so it's somewhat of
a mystery to me how it works. I just ported it to 6.0
(Reporter)

Comment 19

18 years ago
Answers/comments to your points:
1) It doesn't work....!
2) How can this be? OE loads the messages fine.
3) Still. It's not a fictional mail. I really got this one.

Comment 20

18 years ago
1. It's a question of priority. First, I need to fix the bugs in 6.0 that don't
occur in 4.x (with some leeway for seriousness of the bug - we have fixed bugs
in 6.0 that also occurred in 4.x, some with your very kind help.
2. We're sending legal protocol that the software.com server can't deal with
(but other servers, like NMS 4.0, can). OE is sending different protcool, but I
don't know exactly what protocol they're sending. The way we would fix this in
our client is to break up the multiple fetch requests for the 107 mime headers,
and we'd have to base this on whatever software.com's server's limit is.

3. True, but this is the first report I've heard of this, and 4.5 has been out
for close to 2 years now, so it's not *that* common :-)
(Reporter)

Comment 21

18 years ago
Outlook Express does the following:
000D UID FETCH 1:* (BODY.PEEK[HEADER.FIELDS (References X-Ref X-Priority 
X-MSMail-Priority X-MSOESRec Newsgroups)] ENVELOPE RFC822.SIZE UID FLAGS 
INTERNALDATE)
000E UID FETCH 1:1055 (UID FLAGS)
000F UID FETCH 1003 (BODY.PEEK[] UID)

The last command will return the entire message.

Comment 22

18 years ago
Mail triage is marking nsbeta3-
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future

Comment 23

18 years ago
adding mail3 keyword
Keywords: mail3

Comment 24

18 years ago
changing priorities
Priority: P3 → P2

Comment 25

18 years ago
marking nsbeta1- due to not affecting many users.
Keywords: nsbeta1-

Comment 26

16 years ago
*** Bug 158405 has been marked as a duplicate of this bug. ***

Updated

16 years ago
QA Contact: huang → gchan

Comment 27

15 years ago
When subscribing to Samba list (at www.samba.org) in digest form I get this bug 
every day ( Thunderbird version 0.3 rc 3). As there was no comment on this bug 
for over a year I should assume this bug has a very low priority ?
Thanks 
David de Leeuw
(Reporter)

Comment 28

15 years ago
please provide a mail protocol log:
http://mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
(Reporter)

Comment 29

15 years ago
I only see this on my "IMAP4 server (InterMail vM.5.01.06.04
201-253-122-130-104-20030726)" and not my "debian Cyrus IMAP4 v1.5.19"

I'm attaching the imap protocol log
Summary: IMAP: Huge mail gives me "S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively complex FETCH attribute list" error → IMAP: Huge mail (117 attachments) gives me "S-INBOX:CreateNewLineFromSocket: 8 BAD Excessively complex FETCH attribute list" error
(Reporter)

Comment 30

15 years ago
Created attachment 133262 [details]
imap log
(Reporter)

Updated

15 years ago
Attachment #133262 - Attachment mime type: application/octet-stream → text/plain
Product: MailNews → Core

Updated

10 years ago
Assignee: bienvenu → nobody
Status: ASSIGNED → NEW
QA Contact: grylchan → networking.imap
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core

Comment 31

8 years ago
Joe, possible for you to attempt to reproduce?
Keywords: qawanted
Priority: P2 → --
Whiteboard: [nsbeta3-]
Target Milestone: Future → ---

Comment 32

8 years ago
tested for grins with current trunk, ~150 attachments, and I get the error message.

Note: This is the ONLY open bug reporting this. And no reports in getsatisfaction.
Keywords: qawanted
Whiteboard: [has protocol log]
You need to log in before you can comment on or make changes to this bug.