All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
This one is about MXroute. READ IT, PLEASE!
I run a small WooCommerce store, and email is the most important thing for me.
I discovered MXroute.com while browsing this forum, and started using it in January 2025.
Now I’m in my 7th month of using it.
My verdict?
10/10 for email delivery – their IPs are clean and reliable.
10/10 for simplicity – just enter their server details and you're good to go!
Actually… maybe I should give it 1/10 because it’s too easy to use! 😄
Spam filter? Works great!
Price? Perfect – I’m on the “Large” plan (with a coupon).
Support? **I asked a question and got a quick reply.
Downsides? Just one… 😕 **No affiliate program.
I’d love to recommend MXroute to others and earn a few euros for it!
Summary:
If you need a reliable and secure SMTP server, MXroute is a 110% yes from me!
Comments
My experience is also that MXroute is simple and easy to use, but the interface is a bit ugly.
But you don’t even need to use their interface — just add the server settings to Thunderbird or any other email client, and that’s it!
Are we talking about MXroute or @jar?
I also agree. They're awesome. I haven't used other email hosting services to make a comparison. But so far it's been great.
Who is "@JAR' ?
I wrote about mxroute.com ... 
using it last 2 year - nice
MXRoute is a solid service and @jar is a solid dude.
10/10, would recommend.
@jar is a guy who'll appreciate the joke. He's also the owner of MXroute.
mxroute = supreme
Ooohhh, my bad — I didn’t know that. So, kudos to **@jar! **
Affiliate program with email hosting may spell disaster, as affiliator may spread "good news" among spammers. Spammers may sign up, wait for X amount of time (in the mean time affiliator receives payout) and than spam.
No. Email hosting business does not need affiliate program.
I like the interface.
Very good until you get into some niche scenarios where Gmail (which is known to be hard to send emails to) actually accept the emails and MXRoute just outright blocks them, until you ticket them and then maybe, and only maybe, it gets allowed. My experience has been that I've lost a shit ton of emails without me even realizing. In fact, I still can't get any emails from ColoCrossing and talking with both parties, they just blame it into each other, so ggs.
I wonder if OP still interested if affiliate payout doesn't apply if a promo is used.
This is why I recommend to selfhost email (I mean the receiving part of it)
Dont worry now we can all send you email thanks to leaked ColoCrossing user DB.
mxroute is heaven, @Jar is God! Bless him for transactional service! Bless him for speed, professionalism, bless him for being the guy!
… until one of your interns mistakenly sends a spam message, and your entire account is instantly deleted with no chance of recovery.
Years of business email, gone.
Is the interns why you keep using "we"? Reguards.
Honestly, that kind of sounds like a blessing in disguise.
Until then, enjoy your honeymoon moments..
@funku1
Hehe
/Joke
fucking love @jar and his services. cool dude and top notch services.
honestly, I’m not sure how good the profit margins are for mxroute’s plans, especially if they also have to pay affiliate bonuses on top of that. maybe jar can comment more on the possibility of having an affiliate program
Wasn't there recently a reseller that caused mxroute issues because he wasn't vetting his clients well enough? Imagine affiliates with no responsibility at all, yikes.
Verdict: Great for sending not for receiving
At least in this case at least MXRoute offers a solution to allow all sendgrid.net emails, and Jar mentioned that it was a configuration issue on CC's side - whereas CC initially required me to pay money just to switch my email.
Yeah there's like less than 10 legitimate businesses (none are household names) we've seen sending email with sendgrid.net as the envelope sender. Meanwhile everyone is breathing down my neck about phishing and spam sent via sendgrid which is almost entirely halted by blocking sendgrid.net envelope domain, and whitelisting it for users who need it (which is less than 20).
Ty friend! Only good things to come! Hoping to release a complete overhaul of inbound filtering controls for users next ♥️
Truth is there has never been a better time for receiving less spam and losing less legitimate email, but it's physically impossible to have no complaints on that front. Especially if you take it on yourself to manage it. Give users more control and they'll just think it's their fault, but they'll never strike a flawless balance anywhere if they push any kind of volume of inbound diversity. Google rejects legitimate inbound mail all day long but when they do it everyone agrees it's the sender's fault. I do it and it's always my fault (unless I hack Gmail and steal their filters so no one can say "it arrived fine at Gmail so maybe you suck"). Perceptions are more generous for larger companies, but I press on. It also seems like the users with complaints right now are more likely to be vocal than in previous iterations, likely because they're server admins and not average users.
I listen to customers, I gather their feedback, and I make strong changes that address it. It's not always quick, but I'm always paying attention. Just recently I gave users a conditional opt out for the strongest inbound filtering system, alleviating almost all complaints (not to be assumed as a statistically high number, just a noteworthy number) this year at once. It can be frustrating for users to see unique approaches to spam filtering, but the amount of user control is dramatically improving, and reinventing the wheel is absolutely what I'm trying to do. Much more user control will be coming this year.
Got a BF sale back in 2023. And planning to keep it. Do for renew in November next year.
Sounds like you're one of the users who will most appreciate changes coming to inbound filtering controls. The real test for allowing users to enable/disable massively important filters came with this: https://docs.mxroute.com/docs/changelog/mxroute-3.2.html
That has proven successful, so it will be iterated on. But of course you can see from those notes that I've got a secondary issue in rolling out those changes, so I'm having to balance a fair number of things besides just pushing the features forward.
There are always going to be outliers who have more specific needs than 99% of the customer base. I'm not ignoring them. I just can't roll back a change that dramatically reduces complaints from the 99%, and I can't always toss in a change that only helps the 1% without a longer stretch of planning or moving backwards. It is extremely challenging to not have Google's filtering system at my disposal, because everyone uses it as the benchmark while still having extremely clear demands of me. Doing nothing upsets a ton of people, doing something upsets less people. So sometimes I do something. If I happen to get that backwards, which I have before (but haven't in a good while), then I will roll it back. I am not without empathy, but when showing empathy to one user burns 600 others, I do have to make decisions. The next major release will include the introduction of a "Advanced" section for the Expert Spam Filtering in DA, where users can fine tune their preferences for the various ACLs introduced to tackle major spam/phishing events. With that will be a process change to heavily prefer opt-in rather than opt-out to new ACLs, provided the ACL isn't of emergency need.
I hope knowing that your troubles are included as part of the making of these decisions is at least more comforting than say... that time Google started massively rejecting legitimate email as legitimate senders all over the world spent the next few months trying to figure out what in the world "authentication" meant. You may be 1% of the user base, but when I've eliminated a problem for 99% then the 1% becomes 100% of my concern on that topic. Sometimes that part is just a bit more complicated. I've already got a working draft of what fixes your perfectly legitimate complaint there though. I just want to bundle it for a major release because by itself it doesn't help very many users (as in probably won't help any between now and a later release) and I'm trying to make it a bit easier to follow platform changes.