You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks a lot for all your efforts in keeping signatureswitch alive, also for TB78! This addon really makes my live easier.
Thanks also for your recent new auto-switch feature! This made me think about another cool addition: I am using TB for private and for business purposes. emails from my business identity(s) should never ever contain one of my private signatures and the other way round because this can be very embarrassing. Would it be possible to have two different sets of signatures which one then can assign individually to the respective email identities. Again, I have been living without this for years but your new feature triggered this wish. I would not even dare to ask for a second level of auto-switching in which the addon would learn which signature to use for which recipient.
Again, thanks for all your continuous effort
PUKK
The text was updated successfully, but these errors were encountered:
Hi,
First of all, thanks a lot for all your efforts in keeping signatureswitch alive, also for TB78! This addon really makes my live easier.
Thanks also for your recent new auto-switch feature! This made me think about another cool addition: I am using TB for private and for business purposes. emails from my business identity(s) should never ever contain one of my private signatures and the other way round because this can be very embarrassing. Would it be possible to have two different sets of signatures which one then can assign individually to the respective email identities. Again, I have been living without this for years but your new feature triggered this wish. I would not even dare to ask for a second level of auto-switching in which the addon would learn which signature to use for which recipient.
Again, thanks for all your continuous effort
PUKK
The text was updated successfully, but these errors were encountered: