Using build 20000104 on win98,mac and linux and in the process of verifying bug 21457 it was found that characters following and including @ are stripped from the entered SMTP user name. According to Seth, we should leave those characters displayed, but strip them when sending. Example if firstname.lastname@example.org is entered or migrated as the SMTP user name when you close then open Account setup you will only see foobar as the username. 1. Launch Messenger 2. Select Account Setup from the Edit menu 3. Select the Outgoing SMPT server and change the user name so it has an @xyz.com at the end of the users name. OK the Account Setup dialog 4. Open Account Setup again and notice the @xyz.com has been stripped from the name.
QA Contact: lchiang → esther
Summary: Characters stripped from SMTP user name → Characters stripped from SMTP user name
Status: NEW → ASSIGNED
Target Milestone: M13
data loss, marking m13. accepting.
Priority: P3 → P1
Target Milestone: M13 → M14
marking p1. (m14 p1 are m13 bugs that I want to fix first, but are not m13 blockers)
I remember in 4.x we intentionally stripped "@netscape.com" from POP/IMAP server user names. Eventually, this behavior was put on a pref -- something like mail.allow_at_sign_in_user_name. I'm not sure we did that for SMTP user names, but maybe we did...
Summary: Characters stripped from SMTP user name → "@domain.com" stripped from SMTP user name
since this is data loss, I want to fix it for beta1.
Putting on PDT- radar for beta1. phil approved, please see him if you have questions.
Target Milestone: M14 → M15
moving all m14 to m15.
moving to m16. I have *got* to fix this eventually. I suck.
Target Milestone: M15 → M16
Don't suck, fix. Marking nsbeta2.
Keywords: beta1 → nsbeta2
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Mozilla should not be stripping "@domain.com" from userids anywhere in any protocol. Usernames are not for the client to interpret, they are for the server to interpret according to the server's policy. Because of the 4.x behavior, you may want to strip "@domain.com" from userids during 4.x profile migration. If a user enters "@domain.com" through the Mozilla interface, however, it should be sent over protocol.
Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may pull this for PR2.
Due to slip in schedule, moving this bug from [6/01] to [Will be minus on 6/15] for fix deadline.
Whiteboard: [nsbeta2+][6/01] → [nsbeta2+][Will be minus on 6/15]
fixed. sorry it took me so long.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Using build 2000-06-26 on win98, mac and linux this is fixed. Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.