All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
MxRoute - outgoing only for custom domain I own (but not hosted at MxRoute)
ypmLA77zcs
Member
I've been searching everywhere for the last few days, to determine if my use case is compliant with MxRoute's policies. Couldn't find anything exactly matching it, so thought I'd ask the knowledgeable users here instead...
I have a lifetime account with MxRoute (DirectAdmin), and would like to use it only for their unrivalled ability to get emails to land in big brothers' inbox. For various reasons (storage size being one of them) I would like to host the domain user account / mailbox elsewhere.
So I own my-domain.com, and its DNS MX records point to the big-storage.com mail servers so any incoming email is stored there. So at this point, MxRoute knows nothing about my-domain.com. How do I configure things in MxRoute DirectAdmin account, so I can use MxRoute's SMTP server without being rejected and / or my account suspended? This will strictly be used for personal email sending, absolutely no commercial / transactional activity.
Thanks in advance everyone
Comments
add to your domain's dns mxroute's spf and dkim after adding it to directadmin, create a mailbox for outgoing mail, point the mail client sending mail to the mxroute server you're assigned and it'll relay via it
If their terms don't exclude this use case, it would seemingly indicate it is permitted. @jar
From what you're describing it sounds like you want to use MXRoute for the purpose other people might use MailChannels.
This is in addition to another domain I have at MxRoute for which I have a full mailbox both receiving and sending
Thanks, I did all this and stumbled upon the following roadblock: I was trying to use Cloudflare Email Routing as a forwarder and MxRoute says the following in their Important Account Information email - "Even if not using our MX records, sending domains are required to have at least one MX record to send from MXroute. Otherwise you cannot receive bounce emails". So once I added one more MX record to DNS in Cloudflare, Email Forwarding started complaining that DNS is misconfigured and disabled itself (this after actually forwarding the first test email).
So question for @jar - how critical is it that I add MxRoute MX record to the sending domain DNS records? Is it really required even if I rarely send from there?
TIA
Add the mx record at a higher priority (the lower priority gets picked first) to satisfy that requirement ig
You don't need to add the MX records for MXroute, actually. They just need to have Cloudflare E-mail Forwarding's (or any other provider's) MX records.
Additional to this, you want to go to
E-mail Manager>E-mail Routing, and uncheck "Use this server to handle my e-mails. If not, change the MX records and uncheck this option." then save.It just needs to be an MX record to some server that hosts your email. I believe you already have that covered with this statement:
It doesn't need to point to us, pointing elsewhere is fine. It just needs to point somewhere, sending from domains that have no MX record is bad and because you can't receive bounces that way you never actually get to know how bad it is.
Everything here is fine. Go into DirectAdmin, find Email Routing, and uncheck the "Use this server" checkbox. Click Save on the page if necessary (can't recall if that option requires a submission to save the selection). Then, go into the catchall menu option and set a catchall address (doesn't matter what you set it to, this is only to circumvent exim sender verification). That should solve any/all problems you will have from this setup.
Happy relaying. I'll let you know if anything causes any trouble. I'm watching logs, bounce rates, and performing audits every day to find any issues.
Thanks everyone! I got it working now!
Me = happy