#104 closed defect (fixed)
Reply with 0.5.6 uses wrong names
| Reported by: | Owned by: | rene | |
|---|---|---|---|
| Version: | 0.5.6 | Keywords: | |
| Cc: |
Description
Thunderbird installed 0.5.6. Since then, when replying to an existing message, a virtual identity is constructed for the message which uses my address as the apparent user, but the sender of the original message as the mail address actually used.
Then, if I change this to myself by selecting a real mailing address, the original sender of the message is removed from the address fields.
Attachments (1)
Change History (7)
comment:1 Changed 14 years ago by
| Owner: | set to rene |
|---|
comment:2 Changed 14 years ago by
| Status: | new → assigned |
|---|
comment:3 Changed 14 years ago by
I had the same issue. Try disabling Smart Draft (uncheck "use Smart Draft" in the main tab of the Virtual Identity settings). If you have Thunderbird set to store sent messages in your inbox, Smart Draft doesn't seem to work properly becausrecipient (the sender of the message you're replying to in this case.
Virtual Identity should be modified to detect this case, either by checking whether the sent folder is the inbox, or by first checking the TO headers of the message being replied to before invoking Smart Draft.
comment:4 Changed 14 years ago by
Hi,
thanks for the additional information, currently busy I will have a look at it in a few days.
Regards, Rene
Changed 14 years ago by
| Attachment: | virtualidentity.debug added |
|---|
comment:5 Changed 14 years ago by
I attached the debug file, as requested.
I also confirmed what justin said earlier, that this problem does not occur when "SmartDrafts?" is turned off.
comment:6 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Hi,
thanks to your description it was easy to understand the problem. Never thought that the INBOX might be used to store sended mails, for sure it can :) Changed the extension in a way that it checks for 'received' headers, if none found assumes that it was a send mail. This will hopefully work in all cases now.
Fixed with [454], it will be great if you can check the current trunk snapshot if this fits your requierements.
Nice regards and thanks for the great help to make the extension better,
Rene
Hi,
maybe there is a configuration problem or a bug in the extension, hard to say. Please post a debug output (activate it in preferences) in a case when this problem occurs - check for confidential information (like email adresses) before posting here. Hope this will help me to understand what's going on...
Nice regards, Rene