Closed Bug 136398 Opened 22 years ago Closed 14 years ago

Address book groups don't follow Composition preferences

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bugzilla, Unassigned)

Details

I set up an address book group containing some address book cards where
preferred format is HTML, and a card where preferred format is Plain Text.   In
the message composition options I set "Send in both plain text and HTML" (if not
all recipients can receive HTML).  
   When sending to this group (and using HTML formatting) the message sends in
plain text format.  If I change the Plain Text card to HTML, then the message
sends HTML (as it should).  If I change the Plain Text card to Unknown, the
message is sent multipart/alternative (as it should).

What needs to be fixed:  If sending to a list containing both HTML and
Plain-Text recipients, and if the preference is set to send both HTML and plain
text if not all recipients are capable of receiving HTML, the message should be
sent in multipart/alternative and not plain text.
Joel, what build ID are you reporting this against?

Can you still reproduce the problem using a current build?
Sorry, I was out of town the past couple weeks.   Do you still want me to 
test this?
Joel, yes. Thanks.
This still occurs for me on 1.0.0+ 2002051808.
Confirmed using FizzillaMach/2003021203.

1. Create a Mailing List with two members, one which prefers to receive HTML,
and one Plain Text
2. In Preferences/Mail & Newsgroups/Send Format, select the "Send the message in
both plain text and HTML (larger message size)" option
3. Send a message the text "foo" italicized.

The message is sent as plain text "/foo" only and is not sent as both plain text
and HTML as specified.
Severity: minor → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
mass re-assign.
Assignee: racham → sspitzer
Product: Browser → Seamonkey
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.