Closed Bug 245004 Opened 21 years ago Closed 21 years ago

can't create a return-address-only account (same login name conflicts with existing acct)

Categories

(Thunderbird :: Account Manager, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 44863

People

(Reporter: lists, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Galeon/1.3.14 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Galeon/1.3.14 I can't believe I'm the only person who has this issue (I've scoured the existing bugs but could find nothing). I'm a sysadmin who often needs to send messages as postmaster@, and I subscribe to a number of lists with a special lists@ address (for filing purposes and spam tracking). Neither of these accounts is "real" (meaning, they don't have a physical mailbox, they just come into my normal account), but they need to be distinct when sending. I currently use evolution, which I seriously dislike, but it has the ability to create a "return address only" account (I got around this lack in older mail clients by creating a never-checked POP account clone of my main account). It's a godsend. Other than that, I don't like evolution (it's slow and buggy). When I tried to use mozilla mail and thunderbird, I figured that they'd have options like this. Not only do they not have a return-address-only account, but I can't even fake it with a POP account because it complains when the same login/server pair are entered into another account. Reproducible: Always Steps to Reproduce: 1. Create an account 2. Create another account, with a different return address, but the same server and login name Actual Results: Get an error complaining about a duplicate login/server pair. Expected Results: It might warn me, but let me create the account, anyway, because I know what I'm doing.
*** This bug has been marked as a duplicate of 44863 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.