Description of problem: When I compose a message thus: To: Some people: ; Bcc: dwmw2 ... Thunderbird refuses to send it, popping up a dialog box which (incorrectly) tells me: "Some people: ;" is not a valid address because it is not of the form user@host. You must correct it before sending the email. Version-Release number of selected component (if applicable): thunderbird-1.5.0.5-1.1.fc5 How reproducible: 100% Steps to Reproduce: 1. Compose mail with a group in recipient header. 2. Press 'send' Actual results: Thunderbird refuses to send perfectly valid mail. Expected results: Thunderbird sends mail. Additional info: http://www.ietf.org/rfc/rfc2822.txt §3.4 "Addresses occur in several message header fields to indicate senders and recipients of messages. An address may either be an individual mailbox, or a group of mailboxes." group = display-name ":" [mailbox-list / CFWS] ";" [CFWS]
This probably also affects FC6 -- would be good to get it fixed.
Fedora Core 5 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
We haven't got any reply to the last question about reproducability of the bug with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you have new information that would help us fix this bug, please reopen it with the additional information.
Reopening -- I believe this bug persists. It would be trivial for anyone who actually _uses_ thunderbird (unlike me) to confirm.
We found that this bug has been already registered in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=83521) and believe that it is more appropriate to let it be resolved upstream. Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report.