608031 - Multiple Account Restriction same server and user name too restrictive

Status: RESOLVED DUPLICATE of bug 226303

(Thunderbird :: Account Manager, defect)

Description

[Kevin Raymond]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101012 Firefox/3.6.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5

Hey Guys,

Very nice program, I feel compelled to let you know on the problem I am having. I use ssh tunnels to be able to access my emails form anywhere, so I specify the different servers by different ports in the account creation, the ip is always localhost. For example, 

server 1 is IP 127.0.0.1 port 10143 directs me to IMAP1
server 1 is IP 127.0.0.1 port 10343 directs me to IMAP2

on both servers, I have an account kraymond. I would like to set up the two of them within the same Thunderbird profile, this probably requires changing the qa authentication is managed within the accounts. A pair of username@server would not be enough to identify a password, the combination of  user@server:port would be needed.

Reproducible: Always

Steps to Reproduce:
1. create an account for an imap server, using username user
2. create an account for an imap server at the same ip but a different port with the same user. This second account ceration will be blocked by a message box that reads: An account with that user name and server already exists. Please enter a different user name and/or server name.
Actual Results:  
Second account creation prevented

Expected Results:  
create a second account for the same server with the same user name

this is not security issue, just functionality for advanced network people who play with ports

Comment 1

[Ludovic Hirlimann [:Usul]]

This looks a lot like 303542.

Comment 2

[WADA:World Anti-bad-Duping Agency]

dup of 226303.

As multiple server part of username@server can be defined in hosts file for same IP address of 127.0.0.1, you can create accounts of username@serverA/port=A, username@serverB/port=B, ... on Tb by serverA=127.0.0.1, serverB=127.1.1, ... in hosts file, unless SSL related issue occurs by it.