textfields should be less than 1000 chars...

VERIFIED INVALID

Status

SeaMonkey
MailNews: Account Configuration
P3
minor
VERIFIED INVALID
18 years ago
14 years ago

People

(Reporter: Henrik Gemal, Assigned: Alec Flett)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

18 years ago
I know that not alot of people are affected by this bug, but anyways: It seems 
that fx newsserver only allow header lines to be 1000 chars.

If this user fx enters 1000 chars in the "Your Name", "Email Address", 
"Reply-To" or "Organisation" field in the Account Settings the From header(Your 
Name + Email Address) or other header when sending mails will be too long and 
the user will be presented with some strange sending error whenever the user 
tries to post something.

Couldn't we just limit the number of chars the user are allow to enter in the in 
textarea of the xul (am-main.xul) file. Something like MAXLENGTH="100". Doesn't 
textfields support this?
(Assignee)

Comment 1

18 years ago
sure, would be nice
Status: NEW → ASSIGNED
Target Milestone: --- → Future
(Reporter)

Comment 2

18 years ago
Created attachment 10446 [details] [diff] [review]
Limit textfields to 400
(Reporter)

Updated

18 years ago
Keywords: patch
(Assignee)

Comment 3

18 years ago
gemal, I want to find out if there are RFCs on header length, so we aren't 
arbitrarily limiting people.

Comment 4

18 years ago
alec, any word?
(Assignee)

Comment 5

18 years ago
RFC822 does not impose any limit on the length of any header (and in fact says 
"this RFC does not impose such a limit" when referring to "long" headers.
There are also no limits expressed in RFC850 (exchange of USENET messages) or 
RFC977 (NNTP)

So I'm marking this invalid.

if the "fx" newsserver has problems, then it's a bug on the newsserver.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID

Comment 6

18 years ago
vrfy invalid
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.