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.

Sign up for GitHub

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

Jump to bottom

%recipient% should use reply-to header if present when replying #166

Closed
RealRaven2000 opened this issue Jan 20, 2022 · 2 comments
Closed

%recipient% should use reply-to header if present when replying #166

RealRaven2000 opened this issue Jan 20, 2022 · 2 comments
Assignees
@RealRaven2000
Labels
enhancement

Comments

@RealRaven2000
Copy link
Owner

RealRaven2000 commented Jan 20, 2022 •
edited
Loading

When using the %recipient% field in a reply, this is replaced with the %to% variable internally when replying to an email. However it should be set to the final recipient (reply-to) when that field was set in the original email.
@RealRaven2000 RealRaven2000 self-assigned this Jan 20, 2022
@RealRaven2000 RealRaven2000 changed the title %recipient% should us reply-to header id present when replying %recipient% should use reply-to header id present when replying Jan 20, 2022
@RealRaven2000 RealRaven2000 changed the title %recipient% should use reply-to header id present when replying %recipient% should use reply-to header if present when replying Jan 20, 2022
@RealRaven2000
Copy link
Owner Author

RealRaven2000 commented Jan 20, 2022 •
edited
Loading

Test versions with a quick fix:

Tb 68: smartTemplate-fx-2.18pre4.zip
Tb 78-91: smartTemplate-fx-3.9.1pre2.zip

to test, as always download the zip file, then drag it (without unpacking) into Thunderbird Add-ons Manager.

@RealRaven2000
Copy link
Owner Author

Implemented in 3.10.1 - released on 04/Feb/2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RealRaven2000 RealRaven2000

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RealRaven2000