Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Virtual Identity #346

Closed
dotancohen opened this issue Jul 24, 2011 · 7 comments
Closed

Support for Virtual Identity #346

dotancohen opened this issue Jul 24, 2011 · 7 comments

Comments

@dotancohen
Copy link

The terrific extension Virtual Identity allows users to use a catchall email address at his own domain, and assign a custom email address to each contact. Among the extension's features is that when replying to a message the From field of the reply will be set to the value of the To field of the original message.

Thunderbird Conversations does not support the use of Virtual Identity for replies, in either the quickreply interface or when opening the reply in a Compose window. In both cases, the To address of the original message is put in a CC field of the reply. Please integrate support for Virtual Identity in Conversation View.

To reproduce:

  1. Install both Virtual Identity and Thunderbird Conversations.
  2. Receive and email addressed to an address for which you do not have an Identity configured.
  3. Click Reply

It can be seen that the original To address is now in the CC field, and the To field is set to a configured identity.

@dotancohen
Copy link
Author

Here is the corresponding Virtual Identity feature request, so that the devs may collaborate:
https://www.absorb.it/virtual-id/ticket/333

@protz
Copy link
Collaborator

protz commented Jul 24, 2011

Dotan,

I understand that you're enthusiastic about thunderbird conversations,
and I'm very glad about it :-). Thanks! However, I can't fix every
Thunderbird extension in the wild out there. I've blogged about this:
can you just point author extension authors to
http://blog.xulforum.org/index.php?post/2010/11/27/Thunderbird-Conversations-plugins
and point them to some sort of meta-bug called "conversation plugin
API" or something? I'd appreciate if you could close all these single
bugs and create a more important one about improving the API. That
would allow me to focus on the important point and feel like you want
me to fix all these extensions :-).

thanks,

jonathan

On Sun 24 Jul 2011 05:26:11 PM CEST, dotancohen wrote:

The terrific extension Virtual Identity allows users to use a catchall email address at his own domain, and assign a custom email address to each contact. Among the extension's features is that when replying to a message the From field of the reply will be set to the value of the To field of the original message.

Thunderbird Conversations does not support the use of Virtual Identity for replies, in either the quickreply interface or when opening the reply in a Compose window. In both cases, the To address of the original message is put in a CC field of the reply. Please integrate support for Virtual Identity in Conversation View.

To reproduce:

  1. Install both Virtual Identity and Thunderbird Conversations.
  2. Receive and email addressed to an address for which you do not have an Identity configured.
  3. Click Reply

It can be seen that the original To address is now in the CC field, and the To field is set to a configured identity.

@protz
Copy link
Collaborator

protz commented Jul 24, 2011

I meant not feel like...

On Sun 24 Jul 2011 11:01:47 PM CEST, Jonathan Protzenko wrote:

Dotan,

I understand that you're enthusiastic about thunderbird conversations,
and I'm very glad about it :-). Thanks! However, I can't fix every
Thunderbird extension in the wild out there. I've blogged about this:
can you just point author extension authors to
http://blog.xulforum.org/index.php?post/2010/11/27/Thunderbird-Conversations-plugins
and point them to some sort of meta-bug called "conversation plugin API"
or something? I'd appreciate if you could close all these single bugs
and create a more important one about improving the API. That would
allow me to focus on the important point and feel like you want me to
fix all these extensions :-).

thanks,

jonathan

On Sun 24 Jul 2011 05:26:11 PM CEST, dotancohen wrote:

The terrific extension Virtual Identity allows users to use a catchall
email address at his own domain, and assign a custom email address to
each contact. Among the extension's features is that when replying to
a message the From field of the reply will be set to the value of the
To field of the original message.

Thunderbird Conversations does not support the use of Virtual Identity
for replies, in either the quickreply interface or when opening the
reply in a Compose window. In both cases, the To address of the
original message is put in a CC field of the reply. Please integrate
support for Virtual Identity in Conversation View.

To reproduce:

  1. Install both Virtual Identity and Thunderbird Conversations.
  2. Receive and email addressed to an address for which you do not have
    an Identity configured.
  3. Click Reply

It can be seen that the original To address is now in the CC field,
and the To field is set to a configured identity.

@protz
Copy link
Collaborator

protz commented Jul 25, 2011

Closing as this seems to have been fixed on the other side

@protz protz closed this as completed Jul 25, 2011
@dotancohen
Copy link
Author

No problem, I thought that you might want the information about incompatible extensions here in the issue tracker.
considering that Conversations greatly affects how many other extensions interact with Thunderbird I think that it is prudent to have a record of the problems somewhere, so I've made a Wiki page on the subject:
https://github.com/protz/GMail-Conversation-View/wiki/IncompatibleAddons

Of course, I do not expect you to fix all the world's extensions! However I think that each incompatibility warrants a separate issue so that the other extensions' authors also have a point of contact with Thunderbird Conversations, a place to exclaim which hooks and features they need to make their extension compatible. I will take it upon myself to monitor these threads and close them when the extension works or to ping you when the extension's author mentions a hook that he needs.

In the end it's your call. Should I monitor the issues for updates to the other extensions' needs for hooks or just not file them here until after the other extension mentions a need? Should I continue updating the Wiki page or should I delete it?

You know that I appreciate your work and I don't expect anything. I file the issues to help, as that benefits us both.

@protz
Copy link
Collaborator

protz commented Jul 25, 2011

The wiki page is an excellent idea! I think it's much better suited
than issues on the bug tracker. The problem is these issues get easily
buried by other issues, and I think the wiki page is a much better
format.

On Mon 25 Jul 2011 03:46:51 PM CEST, dotancohen wrote:

No problem, I thought that you might want the information about incompatible extensions here in the issue tracker.
considering that Conversations greatly affects how many other extensions interact with Thunderbird I think that it is prudent to have a record of the problems somewhere, so I've made a Wiki page on the subject:

Of course, I do not expect you to fix all the world's extensions! However I think that each incompatibility warrants a separate issue so that the other extensions' authors also have a point of contact with Thunderbird Conversations, a place to exclaim which hooks and features they need to make their extension compatible. I will take it upon myself to monitor these threads and close them when the extension works or to ping you when the extension's author mentions a hook that he needs.
Thanks! I appreciate your help.

In the end it's your call. Should I monitor the issues for updates to the other extensions' needs for hooks or just not file them here until after the other extension mentions a need? Should I continue updating the Wiki page or should I delete it?
Updating the wiki page is great. You can even point to it from the main
wiki page. I'd love if you could monitor other issues on remote bug
trackers, and then, when people express the need for additional API
hooks, and only then, create an issue. The problem I have with the two
issues you created is that there's nothing "actionable" on them, and
nothing I can do about the issue.

You know that I appreciate your work and I don't expect anything. I file the issues to help, as that benefits us both.
And I appreciate that. Thanks again!

@dotancohen
Copy link
Author

Will, do. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants