Email via Amazon SES - which domain to verfy?
-
If I understand you correctly, this is the answer: I followed your docs:
https://docs.cloudron.io/email/#amazon-sesand SES docs:
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.html -
If I understand you correctly, this is the answer: I followed your docs:
https://docs.cloudron.io/email/#amazon-sesand SES docs:
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.htmlIn SES, my domian is verified but not my DKIM because your docs say that I should not do that.
Result is 100% of the mails I send bounce.
My main aim - or my fist stumbling block - is that I want to use a mailing list. So any of 10 users should send via a mailing list, sending from their private mail.
-
In SES, my domian is verified but not my DKIM because your docs say that I should not do that.
Result is 100% of the mails I send bounce.
My main aim - or my fist stumbling block - is that I want to use a mailing list. So any of 10 users should send via a mailing list, sending from their private mail.
@andxclfor the mail setup may indeed just hang on one wrong detail. I will follow up on the support system and see what I can make out by looking at the server itself. I would not be able to check SES from that, but lets see. AWS is often quite complex and hard to get right in comparison with other providers. For mail rely we ourselves use postmark, which worked flawlessly since we started using it years ago.
-
@andxclfor the mail setup may indeed just hang on one wrong detail. I will follow up on the support system and see what I can make out by looking at the server itself. I would not be able to check SES from that, but lets see. AWS is often quite complex and hard to get right in comparison with other providers. For mail rely we ourselves use postmark, which worked flawlessly since we started using it years ago.
-
@andxclfor the mail setup may indeed just hang on one wrong detail. I will follow up on the support system and see what I can make out by looking at the server itself. I would not be able to check SES from that, but lets see. AWS is often quite complex and hard to get right in comparison with other providers. For mail rely we ourselves use postmark, which worked flawlessly since we started using it years ago.
-
Ok, doing SendGrid now. Stuck at SMPT.
Not sure about what you say in SMPT settings:
"Cloudron richtet einen SPF-Eintrag nicht automatisch ein."Then on the link given by you, SendGrid says:
"When you complete Domain Authentication, automated security is enabled by default. Automated security handles your SPF and DKIM records for you."I have done automatic domain authentication and it is verified. Then I entered the SendGrid API in Cloudron. However, SendGrid cannot verify my SMTP credentials:
"Hmm, we haven't seen your email yet."Should I give it time?
-
Ok, doing SendGrid now. Stuck at SMPT.
Not sure about what you say in SMPT settings:
"Cloudron richtet einen SPF-Eintrag nicht automatisch ein."Then on the link given by you, SendGrid says:
"When you complete Domain Authentication, automated security is enabled by default. Automated security handles your SPF and DKIM records for you."I have done automatic domain authentication and it is verified. Then I entered the SendGrid API in Cloudron. However, SendGrid cannot verify my SMTP credentials:
"Hmm, we haven't seen your email yet."Should I give it time?
-
@andxclfor the SMTP credentials for sendgrid should work right away, since that should not be related to any DNS changes as such. The port would also be unchanged. Can you double check the sendgrid credentials?
-
@andxclfor ok, maybe you can send one of them to us via support@cloudron.io and if remote support is still enabled, I can debug this directly on your server.
-
@andxclfor ok, maybe you can send one of them to us via support@cloudron.io and if remote support is still enabled, I can debug this directly on your server.
-
Have you made sure DNS settings for previous mail settings have been all removed from the domain's DNS, before you've tried another approach? And, sometimes it takes awhile for the DNS settings to work. If you've been trying this, and that, and changing settings in the DNS, then it could just need a bit of time for the most recent to propogate.
