the FAPI recieves the contact request (user's name, mail, phone and message)
and sends a request to the MessageAPI including the user input and other meta info, e.g. which mail template to take for that mail
PROBLEM: the FAPI seems NOT to include the user's mail as reply_to into the request
CONSEQUENCE: an entry owner recieves an email, which has the requesting user's mail in the mail text, but not set as reply-to parameter and therefore the native answer-function of the mail client would send a mail to "bot@afeefa.de" instead of to the user mail
when a user contacts an entry over our FE
the FAPI recieves the contact request (user's name, mail, phone and message)
and sends a request to the MessageAPI including the user input and other meta info, e.g. which mail template to take for that mail
PROBLEM: the FAPI seems NOT to include the user's
mailasreply_tointo the requestCONSEQUENCE: an entry owner recieves an email, which has the requesting user's mail in the mail text, but not set as reply-to parameter and therefore the native answer-function of the mail client would send a mail to "bot@afeefa.de" instead of to the user mail