Closed edzillion closed 6 years ago
I have realised that the problem here has something to do with the domain settings - aws seems to think it's controlling them but when I look up the records it seems to show the old (namecheap) settings.
https://viewdns.info/dnsrecord/?domain=joincircles.net
The domain has been moved, but I notice that the nameservers are still the old ones:
Name servers
dns1.registrar-servers.com
dns2.registrar-servers.com
I am going to update these as a next step once I figure out what they should be :confused:
ok that seems to have fixed it. joincircles.net is properly redirecting to www.joincircles.net and all the other dns weirdness is gone.
I have retry'd the DKIM validation and we'll see how long it takes.
DKIM validation completed successfully.
So I went in and realised I had never added a MX record to the DNS settings for joincircles.net - so mails weren't even hitting the endpoint.
So added a MX record like so:
10 smtp.amazon.host
So the lamda function which forwards mails is working and the important piece is the config
block:
var defaultConfig = {
fromEmail: "*****@joincircles.net",
subjectPrefix: "",
emailBucket: "*****",
emailKeyPrefix: "",
forwardMapping: {
"example@joincircles.net": [
"example@gmail.com"
],
"example2@joincircles.net": [
"example2@gmail.com"
],
"@joincircles.net": [
"catchallemail@gmail.com"
]
}
};
If you need to add an email you will need to add an extra entry in the forwardMapping
block
AWS has lots of spam filtering and blacklists etc but this setup is somewhat susceptible to abuse as all emails to non-existent addresses are forwarded to the catch-all email. Perhaps we can change this if there is a lot of spam.
OK I am going to close this as it is working as expected. I have added a wiki page to document how to add a new email here:
Since we've moved the domain to route53 we need to setup email forwarders for the joincircles.net domain. I am following the tutorial here, which seems to be the best way to do this.
alternative, similar tutorial here