Unsolved Email via Amazon SES - which domain to verfy?
-
As per this:
https://docs.cloudron.io/email/#amazon-sesWhich domain or domains should I verify with SES and which email address/addresses?
Only my.example.com? Or every-app.example.com? Or mailserver.example.com?
Only admin@example.com and newsletter@example.com? Surely not each and every email address individually!?
Thank you
-
@andxclfor in this case you would verify the domain example.com via the procedure described at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.html
All email FROM addresses, also from mails sent from apps would be something@example.com so that should suffice.
-
Thank you @nebulon for your exceedingly quick reply!
I did as explained and in SES my root domain is shown as verified. But still get bounces, so I must have done something wrong.
I assume it is either the MX record on the wrong mail from domain.
Or what about DKIM? The docs seem to say that I do not have to configure them, so in SES those are shown as not-verified - is that correct?
-
@andxclfor can you check the status tab for that domain in the mail view? The DNS records are only setup automatically if you have an automated DNS backend configured for that domain, otherwise the status tab will show you the expected values.
Also you can manually check with your nameserver to see if the DNS values are there. Sometimes those things take some time to be synced all over. -
I am totally lost. I have tried for 6 weeks now setting up SES, but it never works. Yes, the first 4 weeks it was my mistake.
I really appreciate your help but I do not know what I could do. I see two options, either cancel Cloudron, or use another email service.
-
@andxclfor Can you post the links for the instructions you’ve been following please? I’ve found setting up SES can be tricky because you need to sometimes mix and match different tutorials to get the big picture of all that is needed. If you post the main sites you’ve used thus far to get set up, I can follow them myself and see what’s up.
-
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 -
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.
-
@nebulon You are very welcome to go onto all and any server!
-
@nebulon And, I don't have to use SES. I'll look into Postmark or Sendgrid
-
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?
-
.. or change the port?
I am on 587
-
@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?
-
@nebulon I have now tried three API keys. All no success.
-
@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.
-
@nebulon Thank you. Email sent, remote support is active.
-
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.
