Skip to main content
Solved

Why no Reply-To Header Functionality?

  • May 23, 2025
  • 0 replies
  • 205 views

Forum|alt.badge.img+3

I have a client that receives donation inquiries via a webform that posts to Quickbase and sends individual notifications to the relevant client personnel. Their prior system was through their website hosting vendor, which sent an e-mail to a shared e-mail account. However, the vendor's e-mail protocol included a Reply-To header that allowed them to reply to the e-mail address of the donor rather than the generic notify@ account that sent the email.

For those that are unfamiliar, email clients use the Reply-To header to pre-populate the "To" field when a user clicks "Reply." If the Reply-To header is not present, the client will typically default to the "From" address. As best I can tell, Quickbase's e-mail protocol and notifications do not support Reply-To, which is a major headache for this use case where I would like the Reply-To value to be the e-mail address of the donor submitting the form.

Does anyone know why Quickbase does not support Reply-To or if it is on the roadmap?

Also, what do you think the best workaround options are as of today?

Best answer by MarkShnierYou

Yes, I believe it is due to Quickbase not wanting to be used as a spam engine, so the FROM has to be from a registered user.

The Juiced Add on called Courier has more flexibility to use the value of any field as the Reply To. 

MarkShnierYou
Forum|alt.badge.img+24

In fact the FROM setting on a Notification becomes the Reply To.   Try triggering an Old Style Notification or New Style Customer Email and select a FROM from the dropdown.