You can set the Recipient address to the submitter of the form, but not the Reply-To address. In our case, the Reply-To is the field we really want that option available on.
We're using Amazon SES, and like many other transactional email providers, they require the From address to be from a verified domain name. So the only way to allow clients to simply press Reply on a form notification and have it get to the submitter of the form, we need to use the Reply-To address.
Should the option be available for Reply To like it is for Recipient, or was it left out for a reason?
Comments
Comment #2
replicaobscuraComment #3
scott_euser commentedMakes sense, thanks for raising - will add to my to do list but as always would be happy if someone is willing to contribute a patch to help.
Comment #4
replicaobscuraI'll likely have a patch for this today, will submit here once I do.
Comment #5
nikathoneI am not quite sure if this what @bmcclure wanted but here is a patch which allow to send to the message entity sender mail base field. In case you wanted the same thing may the title should be updated to something like
Comment #6
nikathoneOops submitted wrong patch. Here is a good one
Comment #7
nikathoneWrong one again here is a new one.
Comment #8
replicaobscuraThat looks good to me! Currently it won't apply with the Translations patch I'm also using (and also I don't think will be necessary with that patch anymore, as it shares the same set of options as the Recipient Type field), however based on the patch file it seems to do exactly what I was looking for.
Comment #9
scott_euser commentedThanks both!
I've committed this to the 8.x-1.x-translatable-entities branch I am working on which I will eventually merge in, but I am still writing tests and refactoring to make sure it's stable before I merge it into the dev branch and release it. At that point the commit message will appear here in this issue but for now you can find the commit here.
Comment #10
replicaobscuraIs there a reason to have the to and reply_to use different switch options in the code like you've currently got them in the translations branch? It seems to me they both could be handled in essentially the same way, since they both can take any email address, and one can just take multiple values while the other only allows a single value. Might be something I'm missing there, but just curious.
Additionally, currently getTo() uses 'submitter' while getReplyTo() uses 'sender', but both are doing the same thing. If that code ultimately won't be combined, should one of those references possibly be renamed?
Comment #11
scott_euser commentedMakes sense, yeah besides the multiple vs single, they are the same, I'll refactor
Comment #13
scott_euser commentedThis is now committed to the dev branch. Thanks!