Closed Bug 281226 Opened 20 years ago Closed 19 years ago

Port field could be wider

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
All
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: rado, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; sk-SK; rv:1.8a6) Gecko/20050111
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; sk-SK; rv:1.8a6) Gecko/20050111

This would be useful for users that setup an SSH tunel from local port for
example 55555 to remote mail server. And, hopefully, there is a place on the
form to make the field a little wider, so it would show up to 5 digits. (I
believe maximum port number is 65535?)

Reproducible: Always
*** Bug 281227 has been marked as a duplicate of this bug. ***
Version: unspecified → Trunk
The port fields for SMTP, POP and IMAP all are wide enough for five digits.
(I'm looking at Moz 1.8b2-0309, which has the rewritten SMTP server interface, 
and running under Win2K.)

Is there a field I've missed, or should this bug be   Resolved | WorksForMe  ?
I tried version 20050318 under Windows 98. Yes you can input 5 digits into all
fields. But none field shows them all. The field Port under redesined SMTP
interface shows app. 4, the field under Server settings (all POP / IMAP / News)
shows only 3. The only field wide enough is the SMTP Port field in TB 1.0.

Other problem is, that it s possible to input port number like 123456789 (or
even number like 123456790123456790, which overflows to be stored as
-350287872). Is that a real port number? (maybe on IPV6?)
On my system (Windows 2000, Large Fonts, Qute theme for TB and Orbit theme for 
Mozilla) the fields *are* all wide enough to show five digits, even more in the 
case of SMTP.

You opened this bug with "OS=All" -- are you actually seeing this problem on 
multiple platforms?  What theme(s) are you using?
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.