All users were logged out of Bugzilla on October 13th, 2018

ExtractProxyInfo not honoring permitHttp flag! [was: IMAP port "disabled for security reasons"]

RESOLVED FIXED in mozilla1.4beta

Status

()

P1
critical
RESOLVED FIXED
16 years ago
16 years ago

People

(Reporter: bugzilla, Assigned: darin.moz)

Tracking

({regression})

Trunk
mozilla1.4beta
x86
Windows XP
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030418
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030418

When I try to load a message on an IMAP server, I get a dialog box stating
access to the port has been disabled for security reasons, followed by an IMAP
connection error dialog.
I tried overriding the protection by adding port 143 to
network.security.ports.banned.override, and then I got "This request was not
recognized. Perform a trace." in the message area, possibly from my proxy, which
would be even more bizarre.

Reproducible: Always

Steps to Reproduce:
1. Click on an IMAP account's inbox
2. Click on a message

Actual Results:  
See above

Expected Results:  
Display the message body :)

Comment 1

16 years ago
I'm guessing your imap server wants you to use SSL - just configure your imap
server account settings in Mozilla to use SSL. I don't think this is a client
bug - i think your server administrator just turned off access to IMAP on the
default, non-SSL port. I could be wrong, but that's what it sounds like.
(Reporter)

Comment 2

16 years ago
No, I really think it's a bug. I've got 2 IMAP accounts and the problem occurred
on both. I switched back to an older nightly now, and they're both working
properly again.

Comment 3

16 years ago
yes, sorry, that is Mozilla code giving you that error message, but it's not the
IMAP code. Do you have other ports disallowed? There must be something about
your configuration that's special since the vast majority of users don't need to
do anything with network.security.ports.banned.override - The IMAP code allows
IMAP to be run on any port. Do you have port 143 on your banned list? Perhaps
the necko code that handles overriding banned ports is broken...

Comment 4

16 years ago
I've been having the same problems since the proxy-auto-config failover changes
were committed but nobody else was able to reproduce.  I see the problem on both
Solaris and Linux with an proxy.pac file referenced by a file: url.  If the
default result is DIRECT then imap works, if it points to a PROXY then imap urls
are sent to the http proxy which gets confused.  This is a serious regression.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 5

16 years ago
I've never changed anything to the banned ports except the override I mentioned
earlier on, but I removed that one again. As far as I know, my port
configuration is normal. But I _am_ using a proxy through PAC.
(Assignee)

Comment 6

16 years ago
-> me
Assignee: bienvenu → darin
Severity: major → critical
Component: Networking: IMAP → Networking
Flags: blocking1.4b?
Keywords: regression
Priority: -- → P1
Product: MailNews → Browser
Target Milestone: --- → mozilla1.4beta

Updated

16 years ago
QA Contact: gchan → benc
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED
Summary: IMAP port "disabled for security reasons" → ExtractProxyInfo not honoring permitHttp flag! [was: IMAP port "disabled for security reasons"]
(Assignee)

Comment 7

16 years ago
Created attachment 120991 [details] [diff] [review]
v1 patch

left out a very important check!!
(Assignee)

Updated

16 years ago
Attachment #120991 - Flags: superreview?(alecf)
Attachment #120991 - Flags: review?(gordon)

Comment 8

16 years ago
Comment on attachment 120991 [details] [diff] [review]
v1 patch

r=gordon
Attachment #120991 - Flags: review?(gordon) → review+
(Assignee)

Updated

16 years ago
Attachment #120991 - Flags: superreview?(alecf) → superreview?(bzbarsky)
Attachment #120991 - Flags: superreview?(bzbarsky) → superreview+
(Assignee)

Comment 9

16 years ago
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Updated

16 years ago
Flags: blocking1.4b?
You need to log in before you can comment on or make changes to this bug.