bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

CAB Autocollection garbles addresses from non-mime messages

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Address Book & Contacts
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: marina, Unassigned)

Tracking

({intl})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
*** observed with 2002-04-19 trunk and branch ***
This bug will mostly effect international users, because when you click on a
"From"link in the body of the non-mime message before changing the charset the
sender name is displayed garbled and is getting added garbled into collected
addresses. This happens regardless of the option in Preferences |Mail&
Newsgroup|Addressing where all the checkboxes for collecting addresses from
incoming, outgoing and newsgroups are left unchecked. You do not have to click
Add to Address Book or Compose mail, just click on the From (or Reply to) link.
Screen shot to follow.
(Reporter)

Comment 1

17 years ago
Created attachment 80082 [details]
the screen shot to illustrate the problem. CAB with non-mime non-ascii sender name
(Reporter)

Comment 2

16 years ago
in the current build it's suffucient to select a message in the thread to add
the address into the CA, if i have a nomime message in chinese big5 the address
and the display will be enetered into CA as garbage 
Summary: CA: addresses get collected just by visiting the From link in the message body → CA: addresses get collected just by selecting them in the thread

Comment 3

16 years ago
QA contact to marina.
Keywords: intl
QA Contact: nbaca → marina
mass re-assign.
Assignee: racham → sspitzer

Comment 5

15 years ago
The problem of mail automatically collecting addresses against pref settings is
bug 180253.  The problem of addresses collected as garbage characters should
only now be an issue when mail.collect_email_address_incoming is set to true
(non-default setting).  That part, however, seems enough to keep the bug open as
a non-duplicate.
Updating summary; old summary:
CA: addresses get collected just by selecting them in the thread
Summary: CA: addresses get collected just by selecting them in the thread → CAB Autocollection garbles addresses from non-mime messages
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
QA Contact: marina → addressbook

Comment 6

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 7

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.