Closed
Bug 280335
Opened 20 years ago
Closed 20 years ago
Forwarding messages returns twice with more recipients
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nubian, Assigned: mscott)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 See this: http://www.nubian.sk/maybe_bug.png when i forward message (inline), more recipients, with or without attachments, mail will come to recipient twice (original message, witch was to me arrived and message, witch i edit in message compose window) Reproducible: Always
Comment 1•20 years ago
|
||
This bug report is difficult to understand. The screenshot shows two messages that have arrived in your Inbox, each with a different Subject: text. They must have been sent with two separate Send actions. Is the problem that you have *two* messages like that, or that you have *any* messages like that? If the problem is that you are receiving *any* copy of the message: when you initially Forward the message, does your email address appear in the address headers at the top of the compose window? Perhaps with a BCC:? If so, you apparently have multiple identities defined, one of which has been configured to always BCC yourself -- because (presumably) you're forwarding a message that was sent to that identity, that identity is used as the "From:" account for the message, and the BCC is added. You can check this by looking at the Account Settings for that account; there is a Manage Identities button which opens a dialog letting you view, edit and delete the identities. If this solves your problem, please mark this bug: Resolved | Invalid If not, please provide more information.
Comment 2•20 years ago
|
||
No response from reporter; =>Invalid
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•