We want to send emails through our webapp. Users of the app provide their email adresses. In some cases, we want to send transactional email from the webapp, using the current user as a sender.
Does using the User's name and email adress in the email
from header affect email deliverability reputation?
Are there any other (bad) consquences, we should be aware of?
adding details about the use case:
- Say PersonA uses our app on myapp.com
- PersonA verified his email adress personA@example.com with a confirmation email we send him (he clicked a unique url in the email he got).
- Using the app, PersonA can invite other people to do something (attend an event for example)
- If PersonA invites PersonB we want to send an email, to let PersonB know that he has been invited. To do so, we would like to send an email from personA@example.com to PersonB.
- Having a sender header with myapp.com is totally fine. But PersonB should see see "PersonA ".
We are not going to send hundreds of emails like that. But we would like to create some trust when PersonB sees, that his good old friend PersonA invited him, not a stupid "email@example.com" he never heard about.