Closed
Bug 490985
Opened 16 years ago
Closed 15 years ago
[autoconfig] Unable to find the incoming server after changing from IMAP to POP3
Categories
(Thunderbird :: Account Manager, defect)
Thunderbird
Account Manager
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 3.0b4
People
(Reporter: Nomis101, Assigned: bwinton)
References
Details
(Whiteboard: [no l10n impact])
Attachments
(1 file)
(deleted),
patch
|
philor
:
review+
Bienvenu
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; de-de) AppleWebKit/528.16 (KHTML, like Gecko) Version/4.0 Safari/528.16
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090430 Shredder/3.1a1pre
If you create a new account with autoconfig, than the default is IMAP. If you change this to POP3 and click "Go", than the incoming server could not be found. I've tested this with my web.de and my arcor.de account.
Reproducible: Always
Steps to Reproduce:
1. Complete the account informations and click the "Next" button.
2. Wait until the account informations are received
3. Click the "Edit" button and change "IMAP" to "POP3"
4. Click the "Go" button and wait.
--> The incoming server doesn't change and you get the message "Could not automatically configure incoming server, still trying for outgoing server."
5. Type now in the incoming server by hand (under "receiving") and click "Go".
--> Now you will get the "Your configuration details have been found!"
Blocks: autoconfig
Comment 1•16 years ago
|
||
Huh, I thought we had a _userChangedIncomingHostname to match the ones for protocol/port/sockettype, but apparently I dreamed that.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-thunderbird3?
Version: unspecified → Trunk
Updated•16 years ago
|
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Updated•15 years ago
|
Whiteboard: [no l10n impact]
Updated•15 years ago
|
Assignee: nobody → bwinton
Target Milestone: --- → Thunderbird 3.0b4
Assignee | ||
Comment 2•15 years ago
|
||
Yeah, it looks like we don't have that variable because I don't think we have a way to re-try to guess the hostname without re-trying everything else.
I'll add that functionality in, but it looks like this bug is going to take longer than I had originally hoped. (I'm mentioning this in case the drivers want to take it in to consideration when they're deciding on which bugs should be fixed for 3.0b4, as well as to find out if I'm missing something.)
Thanks,
Blake.
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•15 years ago
|
||
Yeah, I think I was tired when I wrote that last comment. I found a fairly straightforward way, I believe. Sure, I needed to keep around a little more info, but it didn't end up being that hard.
Thanks,
Blake.
Attachment #397312 -
Flags: review?(philringnalda)
Assignee | ||
Updated•15 years ago
|
Whiteboard: [no l10n impact] → [no l10n impact][needs review philor]
Updated•15 years ago
|
Attachment #397312 -
Flags: superreview?(bienvenu)
Attachment #397312 -
Flags: review?(philringnalda)
Attachment #397312 -
Flags: review+
Comment 4•15 years ago
|
||
Comment on attachment 397312 [details] [diff] [review]
A first cut at the patch.
Looks reasonable to me.
Assignee | ||
Updated•15 years ago
|
Whiteboard: [no l10n impact][needs review philor] → [no l10n impact][needs superreview bienvenu]
Comment 5•15 years ago
|
||
Comment on attachment 397312 [details] [diff] [review]
A first cut at the patch.
me too.
Attachment #397312 -
Flags: superreview?(bienvenu) → superreview+
Updated•15 years ago
|
Whiteboard: [no l10n impact][needs superreview bienvenu] → [no l10n impact]
Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
Comment 6•15 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•