Feature request: Save recipients in email templates

mbjboon82 commented

2026-10-20 17:56:46 +00:00

Email templates currently save a subject and body, but they do not appear to save the recipient fields (To, Cc and Bcc).
For recurring emails, such as sending invoices, it would be useful to save the recipient together with the subject and body.

Proposed solution:

Extend email templates to optionally include:
To — one or more email addresses
Cc — optional recipients
Bcc — optional recipients

When inserting a template into a draft, populate these recipient fields alongside the subject and body.
Templates without saved recipients should continue to work exactly as they do now.

Thank you for iHasMail!

Email templates currently save a subject and body, but they do not appear to save the recipient fields (To, Cc and Bcc). For recurring emails, such as sending invoices, it would be useful to save the recipient together with the subject and body. **Proposed solution:** Extend email templates to optionally include: To — one or more email addresses Cc — optional recipients Bcc — optional recipients When inserting a template into a draft, populate these recipient fields alongside the subject and body. Templates without saved recipients should continue to work exactly as they do now. Thank you for iHasMail!

jcoffey-dev referenced this issue from a commit

2026-10-20 20:35:19 +00:00

Templates remember who they're for

jcoffey-dev referenced this issue from a commit

2026-10-20 20:35:22 +00:00

Templates remember who they're for

jcoffey-dev referenced a pull request that will close this issue

2026-10-20 20:35:40 +00:00

Interface refresh, smarter composer, and templates that remember recipients #59

jcoffey-dev referenced this issue from inbuxa/inbuxa-webmail

2026-10-20 20:35:40 +00:00

Templates remember who they're for #72

jcoffey-dev commented

2026-10-20 20:37:19 +00:00

Owner

Thanks @mbjboon82, good idea. I'm going to add saved To, Cc and Bcc to templates as a new feature. Templates without recipients will keep working exactly as they do now. It'll ship with a round of layout and graphics improvements I'm backporting from inbuxa-webmail.

A heads up on where ihasmail is going: apart from bug fixes, this will be one of the last big updates. Buried in the Stalwart web UI commits I found a licensing change that comes with version 2.0, and they seem to be closing off more of the project over time. My console has nearly fully diverged from theirs, and the server is at about 30%. I am focusing on full divergence, and at that point the two will be fully distinct products making support increasingly difficult as I will be developing against an entirely different code base.

Thanks @mbjboon82, good idea. I'm going to add saved To, Cc and Bcc to templates as a new feature. Templates without recipients will keep working exactly as they do now. It'll ship with a round of layout and graphics improvements I'm backporting from inbuxa-webmail. A heads up on where ihasmail is going: apart from bug fixes, this will be one of the last big updates. Buried in the Stalwart web UI commits I found a licensing change that comes with version 2.0, and they seem to be closing off more of the project over time. My console has nearly fully diverged from theirs, and the server is at about 30%. I am focusing on full divergence, and at that point the two will be fully distinct products making support increasingly difficult as I will be developing against an entirely different code base.

jcoffey-dev closed this issue

2026-10-20 20:51:58 +00:00

jcoffey-dev commented

2026-10-20 20:54:34 +00:00

Owner

Thanks @mbjboon82! This is merged now (#59). A template can carry To, Cc and Bcc, and inserting it adds those recipients alongside any already on the message. Templates without recipients work as before.

It will be in the next release, together with an interface refresh (#59, #60).

Thanks @mbjboon82! This is merged now (#59). A template can carry To, Cc and Bcc, and inserting it adds those recipients alongside any already on the message. Templates without recipients work as before. It will be in the next release, together with an interface refresh (#59, #60).

mbjboon82 commented

2026-10-20 21:03:09 +00:00

Author

Cool, thanks again for your work!

I have little server knowledge and i went to a self- maintained server for my websites and e-mail just recently (2 months ago).
Very exited to have my websites and Stalwart up and running by myself and after trying Bulwark i found ihasmail working better mainly because of the speed of implementing improvements.

I will migrate to Inbuxa in the future (couple of months i think) but for now that is a really big gap for me to overcome.
A bit scared about server bugs also :-)
But very understandable that you want to focus on your own products and codebase!

Cool, thanks again for your work! I have little server knowledge and i went to a self- maintained server for my websites and e-mail just recently (2 months ago). Very exited to have my websites and Stalwart up and running by myself and after trying Bulwark i found ihasmail working better mainly because of the speed of implementing improvements. I will migrate to Inbuxa in the future (couple of months i think) but for now that is a really big gap for me to overcome. A bit scared about server bugs also :-) But very understandable that you want to focus on your own products and codebase!

jcoffey-dev commented

2026-10-20 21:08:15 +00:00

Owner

it's more about not wanting to have to constantly step around a license trap with the dual licensing schema used by upstream.

Feature request: Save recipients in email templates #58