Matthew Darwin Reporter
	Description • 22 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

If you use the "Account Wizard" to add a new IMAP or POP account, trying to type
in an IPv6 address (with the [] or without, it doesn't matter) into the
"Incoming Server" is not accepted.

An error dialog "Please enter a valid hostname" is presented.

If you add the server by using it's DNS name, it is added ok and works.

Reproducible: Always

Steps to Reproduce:
1. Edit > Mail&Newsgroup Account Settings 
2. Click Add Account
3. Next, Next
4. Type an IPv6 address into "Incoming Server" (e.g "::1" or "[::1]")
5. Press Next

	Boying Lu
	Comment 2 • 20 years ago

Comment on attachment 161443 [details] [diff] [review]
a proposal

Can you give r? Thanks

	Boying Lu
	Comment 3 • 20 years ago

Comment on attachment 161443 [details] [diff] [review]
a proposal

Can you give r? Thanks

	Matthew Darwin Reporter
	Comment 4 • 20 years ago

Problem still occurs in Thunderbird version 1.0 (20050116)

	Boris Zbarsky [:bzbarsky]
	Comment 5 • 20 years ago

Comment on attachment 161443 [details] [diff] [review]
a proposal

I can't review patches to this module -- I'm not a peer for it.

	neil@parkwaycc.co.uk
	Comment 6 • 20 years ago

Comment on attachment 161443 [details] [diff] [review]
a proposal

Well, this patch doesn't address the issue in the bug, nor do I know enough
about IPv6.

	Gervase Markham [:gerv]
	Comment 7 • 19 years ago

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/

	Matthew Darwin Reporter
	Comment 8 • 19 years ago

This still ocurrs in Thunderbird version 1.0.2 (20050602).  Do not close this.

	Jo Hermans
	Comment 9 • 19 years ago

(In reply to comment #8)
> This still ocurrs in Thunderbird version 1.0.2 (20050602).  Do not close this.

And in Thunderbrid 1.5 beta 1 ?

	Derek Morr
	Comment 10 • 17 years ago

This bug is still in Thunderbird 2.0.0.9 (20071031) and 3.0a1pre (2008010703).

	Nikolay Shopik
	Comment 11 • 17 years ago

exist in version 3.0a1pre (2008040903)

	J.M.Roth
	Comment 13 • 15 years ago

(fails for SMTP server address too)

	Thomas Ahlblom
	Comment 16 • 13 years ago

Reproduced (tested with an IPv6 only IMAP server):
Mozilla/5.0 (X11; Linux x86_64; rv:10.0a1) Gecko/20111106 Thunderbird/10.0a1

Nowadays the IPv6 address input gets accepted, but Thunderbird mangles it so it doesn't work.

Is there a wellknown work around for this bug, or how comes there isn't more hullabaloo regarding this issue?

	johann
	Comment 17 • 12 years ago

please see Bug 795113 which deals with two (2) aspects of IPv6 mailserver account problems for SM/TB. these apsects are addressed separately in the two (2) bugs, infra.

Bug 199391 seems to deal with the basic code problem in that IPv6 will not work for server accounts: sending via SMTP on (usually) 465 and collecting via IMAP on 143/993 -- i am familiar with both. it also claims that POP3 is equally affected, but i do not deal with this protocol.

Bug 551675 seems to indicate that the Bug 199391 problem (now going on 10 years old) does not offer an IPv4 fall-back after failing on the mozilla-preferred IPv6. one would conclude from this indication that DNS of the account's server name has an IPv4 MX in addition to the IPv6 (is multi-homed). this can be verified as demonstrated in Bug 795113.

hopefully, these bugs can be consolidated into Bug 795113 and someone will finally resolve all of the issues.

thank you,

	:aceman
	Comment 19 • 7 years ago

Is this still a problem?
We support IPV6 addresses in our server hostname sanity checker https://dxr.mozilla.org/comm-central/rev/058aa6495c2db7c13eac1e23c74d2354bf9d6355/mailnews/base/util/hostnameUtils.jsm#183
and we even have a unit test to check ::1 passes as valid (https://dxr.mozilla.org/comm-central/rev/058aa6495c2db7c13eac1e23c74d2354bf9d6355/mailnews/base/test/unit/test_hostnameUtils.js#53) .

It was said in comment 16 that TB accepts the address, but mangles it into being unusable. I do not use IPV6 to test this so I'd need to hear more about the mangling. Also it is strange that users do not report this more. It may be that all mail servers still have an alternative IPv4 address (or users just use a proper hostname instead of hardcoding IP).

	ishtar
	Comment 20 • 7 years ago

I just found this while googling "Thunderbird add IPv6 account". Server in question is private so I cannot copy/paste the information publicly, but it does not have an IPv4 address associated with the DNS, only IPv6.

$ host 6.domain.com
6.domain.com has IPv6 address 2001:xxx:xxxx:xxx:xxxx:::2
6.domain.com mail is handled by 10 6.domain.com.

Thunderbird will not add the account. It fails with:
Thunderbird failed to find the settings for your account.

Setting the IPv6 IP instead of the host name results in the same error.

The only way I got it to work was to temporarily point an IPv4 address to the system, put the v4 IP in the configuration box, re-test, then change it back to 6.domain.com and save; finally remove the temp v4 IP.

Not sure if it's relevant to this bug, apologies if it's not.