Question
Setup a "mail.xxx.com" in Digital Ocean (when xxx.com's hosting server is located in Amazon S3)
- Posted on January 1, 2015
Asked by merubuntu
Hi guys. I’ll try to explain as detailed as possible.
- I own a Namecheap domain. And it’s web server is located in Amazon S3 and all directions xxx.com and www.xxx.com are routed with Amazon Route53.
- The point is: my customer wants a corporative mail ( @xxx.com) which server is now placed in DigitalOcean (ubuntu 14.xx).
The point is that my last step is to register the mail.xxx.com domain and point that domain to my IP DigitalOceans’s mail server.
But when I apply that action automatically it creates three “NS” records (which the digital oceans by-default-nameservers) and one “A” record (pointing to the IP). At this time I also created in Amazon Route53 a new “record set” of type MMX with the “mail.xxx.com” route and pointing to the three DigitalOcean “NS” directions.
Finally when I make a ping or trace mail.xxx.com it has no results in return.
I’m a little bit frustrated. In case you can help us, I would appreciate it.
Thanks in advance.
R.R.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Ok @freshscaped now this is my answer.
The problem was that, while I was following this guide -which is very similar to this other one my error was in the virtual_aliases table.
Its use was not meaningful for me until the explanation I read was clear:
“This lets you forward mail from one email address to another. This command will create a table called virtual_aliases. It has an id field, a domain_id field which will associate each entry with a domain, a source field for the original email address, and a destination field for the target email address”
Ok, so an alias account is not saved in the server, just used to forward all their incoming messages to (i) another @example.com account or (ii) any other mail. Be careful because in case you put an account that is not considered as an alias type, none of their incoming messages will be stored in the server.
Two days of hard thinking… #WhyME!!! Thanks for your support.
Raul you are very close to having a secure, stable, viable mail server. Try to log in with a couple of client accounts then run ‘tail -n 50 /var/log/syslog’. See if there is anything which gives you a strong clue and read back through the comments on the tutorial if anything looks familiar. Otherwise, post the outcome on something like pastebin.com and let us have a look by posting the link here…
@freshscaped thanks again.
Let me say that for now I send mails (for Yahoo, Google, Outlook). Listening on port 587 for SMTP I send mails from @xxxx.com account to N acounts. :)
But for IMAP case, I do not have a clear reason why I cannot receive any mails from other accounts (Outlook, Gmail, Yahoo, etc.) to my @xxxx.com account.
I checked mail.err (empty) and mail.log report me this:
Hope anyone can help me. Thanks! R2