Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove hardcoded [email protected] address for amazon ses verification mail #381

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

steam0r
Copy link

@steam0r steam0r commented Feb 7, 2025

this solves /issues/370 by removing a hardcoded email address

tried to make it close to what is being done in emails.ex, hope thats fine

@wmnnd
Copy link
Contributor

wmnnd commented Feb 8, 2025

Thanks for taking a look at this! However, I don’t think this is the right way to go about this.

If you want to be able to customize the verification From email, that should happen in the settings for the Shared Sender. It doesn't really make sense to tie it to the system mailer.

@steam0r
Copy link
Author

steam0r commented Feb 10, 2025

Thanks for taking a look at this! However, I don’t think this is the right way to go about this.

If you want to be able to customize the verification From email, that should happen in the settings for the Shared Sender. It doesn't really make sense to tie it to the system mailer.

i just tried to make it somehow work, adding this to the settings of the shared sender seems like a good idea,
i was trying to mimic what the default sender does, sorry if this does not make much sense. but with the hardcoding
in it currently is not possible to use sas at all...or i am not getting it.

@wmnnd
Copy link
Contributor

wmnnd commented Feb 10, 2025

The system mailer (which is used to send things like the registration confirmation email or password reset emails) is configured with environment variables because there can only be one system mailer.

Shared Senders, on the other hand, are configured through the interface. A single instance of Keila could have multiple shared senders. Because of this, everything related to them, should be configured in the interface and not with an environment variable - just like all other properties of the shared sender (like server, password, etc).

@steam0r
Copy link
Author

steam0r commented Feb 10, 2025

would it then be possible to simply use the from address here, or does this need an extra field?

Bildschirmfoto 2025-02-10 um 14 00 18

@wmnnd
Copy link
Contributor

wmnnd commented Feb 10, 2025

Oh, so you're trying to just set up a regular SES Sender, not using a Shared Sender?

Edit: Hmm … but that doesn’t make sense since if you're just setting up a regular Sender with SES, there's no confirmation email. Could you try explaining a bit more what exactly you're trying to do?

@steam0r
Copy link
Author

steam0r commented Feb 13, 2025

so, i think setting up a "non shared" sender with ses works. when i set up a shared sed sender and use that in a project, the frontend tells me:

Bildschirmfoto 2025-02-13 um 19 12 40

and then results in this:

Bildschirmfoto 2025-02-13 um 19 13 14

and this logentry on the server:

Bildschirmfoto 2025-02-13 um 19 13 36

which, i guess, is the server sending with a hardcoded from-email that is not verified at SES...and can't be.
so i searched for the hardcoding and looked at what the other sender so and hence my PR.

am i doing something wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants