Incorrect identity always coming out

[virtualidentity@…]

Hi,

I have VI installed on Thunderbird 2.0.12 with Nostalgy on an XP Pro box, post-SP2.

I have the following issues:

Rather than defaulting to the mailbox that it is in (mailbox foo), it instead defaults to mailbox fooey. I have similar behavior when replying, even when smart reply et cetera is off. I have used previous versions of VI, and wonder if that has contributed to the problem. Is there somewhere I can add/remove VI or amend the decision making??

Thunderbird 2.0.0.14 (2008042104; Windows NT 5.1)

• Nostalgy nostalgy@… 0.2.15
• Talkback talkback@… 2.0.0.9
• Virtual Identity {dddd428e-5ac8-4a81-9f78-276c734f75b8} 0.5.2

---

## v_identity: composeDialog reopened. (msgType 0) ## v_smtpSelector: clean ## v_identity: everything cleaned. ## v_identity: initSystemStage1. ## v_smtpSelector: selectUsedSMTPServer ## v_smtpSelector: setMenuToKey 'smtp3' ## v_smtpSelector: use SMTP from BaseIdentity?: smtp3 ## vI_msgIdentityClone: 'undefined' ## vI_msgIdentityClone: LoadIdentity? ## cleanupReplyTo ## vI_msgIdentityClone: copySelectedIdentity ## vI_msgIdentityClone: copySelectedIdentity MsgIdentityPopup?.doCommand() ## v_smtpSelector: setMenuToKey 'smtp3' ## v_identity: getAddress: address 'Jim Fooey <jim.fooey@…>' name 'Jim Fooey' email 'jim.fooey@…' ## vI_msgIdentityClone: matchingIdentity key id2 ## initReplyToFields identity.replyTo: ## initReplyToFields identity.replyTo: ## v_identity: initSystemStage2. ## vI_smartIdentity: msgComposeType = 0 ## vI_smartIdentity: can't get URI of former Message ## vI_smartIdentity: can't get Message Header of former Message. ## vI_storage: isMailingList 'archive@…' ## vI_storage: isMailList false. ## vI_rdfDatasource: readVIdentityFromRDF. ## vI_rdfDatasource: readVIdentityFromRDF found stored data. ## vI_rdfDatasource: email 'jim@…' ## vI_rdfDatasource: fullName 'Jim "Bud" Foo' ## vI_rdfDatasource: id 'id3' ## vI_rdfDatasource: smtp 'smtp2' ## vI_smartIdentity: add new address to result:Jim "Bud" Foo <jim@…> ## vI_storage: isMailingList ## vI_storage: isMailList false. ## vI_rdfDatasource: readVIdentityFromRDF. ## vI_smartIdentity: checked for stored VIdentities and found 1 address(es) ## vI_msgIdentityClone: addSeparatorToCloneMenu ## vI_msgIdentityClone: addIdentityToCloneMenu 'id3' using Virtual Identity as sender. ## vI_msgIdentityClone: setMenuToIdentity key id3 ## vI_msgIdentityClone: setMenuToIdentity MsgIdentityPopup_clone.doCommand() ## vI_msgIdentityClone: LoadIdentity? ## cleanupReplyTo ## vI_msgIdentityClone: copySelectedIdentity ## vI_msgIdentityClone: copySelectedIdentity MsgIdentityPopup?.doCommand() ## v_smtpSelector: setMenuToKey 'smtp4' ## v_identity: getAddress: address 'Jim "Bud" Foo <jim@…>' name 'Jim "Bud" Foo' email 'jim@…' ## vI_msgIdentityClone: matchingIdentity key id3 ## initReplyToFields identity.replyTo: ## v_smtpSelector: setMenuToKey 'smtp2' ## initReplyToFields setIdentity Jim "Bud" Foo <jim@…> ## v_identity: getAddress: address 'Jim "Bud" Foo <jim@…>' name 'Jim "Bud" Foo' email 'jim@…' ## v_identity: getAddress: address 'Jim "Bud" Foo <jim@…>' name 'Jim "Bud" Foo' email 'jim@…' ## v_identity: reopen done. ## v_identity: replace GenericSendMessage? (Virtual Identity activated) ## updateReplyTo replyToStoredLastValue=null ## vI_storage: awSetInputAndPopupValue 'addressCol2#2' ## vI_storage: field is a 'reply-to' or 'followup-to'. not searched. ## vI_storage: awSetInputAndPopupValue 'addressCol2#3' ## vI_storage: no recipient found, not checked. ## synchroneReplyTo ## vI_storage: awOnBlur 'addressCol2#2' ## vI_storage: field is a 'reply-to' or 'followup-to'. not searched. ## vI_storage: awOnBlur 'addressCol2#3' ## vI_storage: no recipient found, not checked. ## v_identity: getAddress: address 'Jim "Bud" Foo <jim@…>' name 'Jim "Bud" Foo' email 'jim@…'

[rene]

Hi,

seems like the log shows how you compose a new mail. It initially uses the default Identity ('Jim Fooey <jim.fooey@…>') Then it seems to recognize a recipient address ('archive@…') and he extensions searches the Storage for any related information about this address. It finds 'Jim "Bud" Foo <jim@…>' stored and sets the senders Identity to this address.

So, is this right that you composing a new mail to 'archive@…' or do I misread the log?

If, the only way to get rid of this is a little tricky, cause 0.5.2 does not contain an storage-editor yet and does not offer any option to stop using stored Identities. So, if you like, open the file virtualIdentity.rdf in your profiles folder and remove the contents from

<RDF:Description RDF:about="http://virtual-id.absorb.it/vIStorage/email/archive@foo.org"

till the

\>

while Thunderbird is not running.

Or, if you prefer it that way, you can test the pre-release 0.5.3pre7 of the extension, which contains an editor for the storage. Beside, if we are talking about a 'real' bug in 0.5.2, it might be already solved in 0.5.3pre.

Regards and thanks for the report, Rene

[virtualidentiy@…]

Hi,

archive is a bcc that thunderbird autopopulates (per a standard thunderbird setting), so that way I have a copy of my mail regardless of which mail client I am using. (in my "archive" account).

I'm happy to use the beta if it makes sense.

Regards, Jim

PS It would be nice if my mail address had asterisks on it on the web page.

[rene]

Hi,

thats really a problem. Never thought of the bcc case. Solved in [264], you can try version 0.5.3pre10 (download) which includes the bugfix.

Thanks for reporting, regards, Rene

PS: The problem with your email is a problem of Trac. Upcoming version will solve this and I will install this as soon as possible. Sorry.