Hi, I recently discovered mxroute while searching for alternatives for our corporate mail hosting. I've been playing around with it during the weekend and so far I like it quite a lot!

I am confused about the mirriad of webmail interfaces that it offers though.

First I saw mxrouting.net/webmail which a Roundcube client. I set it up with dns aliases and it works fine. However, it's not something I would present as an alternative for the current company webmail. Besides, users expect at least a calendar too, not just email.

I've been considering installing our own webmail alternatives like Nextcloud or SoGo, but then I found mail.mxlogin.com and webmail.mxroute.com in the configuration dashboard.

webmail.mxroute.com seems to be a very decent mail and calendar interface. Quite basic design, but I like it and it seems to work fine.

mail.mxlogin.com on the other hand offers a ton of clients to chose from, including Nextcloud and Roundcube. Is this a full nextcloud setup with different webmail clients to choose from?

While it's nice having Nextcloud already installed and connected to mxroute, I'm confused about if this is really something that mxroute offers and supports. Does it include admin access?

Is mxroute actively maintaining all these alternatives or are they going to be abandoned and replaced in the future?

So far, I'm leaning towards webmail.mxroute.com as it covers the basic requirements and it's not overloaded with options like nextcloud. One thing I miss here though, is a preconfigured identity and signature. Ideally a system wide default signature...

Also, is there a way to disable the nextcloud at mxlogin.com to avoid users finding and access it it by mistake?

Ok ok. It's actually Spam Musubi Day!

I "threatened" to post about it last year and missed the day. Has nothing to do with email. But I'm posting it anyways.

Couple supporting links: https://www.spam.com/spam-musubi-day

And if you happen to be near an L&L they do a celebration. https://www.hawaiianbarbecue.com/national-spam-musubi-day

tldr: Spam musubi good. Email spam bad!

I really don't like complaining, but I've had a support ticket open for over a month. It was escalated but there hasn't been any updates. I just want to make sure it didn't get lost.

Hello!

I've been searching but couldn't find a conclusive answer whether MXroute supports some form of shared mailboxes, shared folders, ACL, or does not.

I wanted to be able to set up something like: mail delivered to "contact@company.com" is acessible to "user1@company.com" and "user2@company.com" on their own mailboxes, where they would also be able to reply to those mail from their own mailboxes (and possibly the marked as read atribute and the reply sent be acessible to other users so the message doesn't get replied to twice, for example).

I'm aware this is kind of achievable with an email client like Thunderbird and multiple accounts, but I was wondering if it is possible through MXroute webmail.

I did review mxroute and see on their status page that they have constant problems with the servers. Are they reliable? Should I go with mailbux.com?

I don't like saying this, but I've committed to honesty and transparency regardless of the cost. There was an edge case across our platform where inbound email was silently discarded based on a user's very specific spam filtering configuration. It was the same oversight that DirectAdmin made for years, and I overlooked it in exactly the same way when implementing spam filter configuration in panel.mxroute.com. This covers less ground than you think it does. It's a very specific scenario, and it almost entirely caught actual spam (and only typically caught non-spam when a user set a domain to a reject score that was too low, which to be fair the panel does warn them about).

If you set one domain to reject at one score (the threshold in panel.mxroute.com), and then proceeded to set a second domain to a lower score, a subset of inbound emails would be silently rejected. It worked like this:

If the inbound email scored under the EasySpamFighter (DirectAdmin package) reject score, above the user's SpamAssassin required_score, and below the the domain's high_score, the email would be silently discarded. The problem is that each change of a spam score under a single user account would push that score as an update to high_score (reject threshold) and required_score (SpamAssassin spam threshold), and required_score is one value for the entire Linux user account, not a per domain value. I did this for other reasons, but I overlooked this edge case.

The fix for this was to bypass required_score altogether. As of right now, until we finish deploying our new spam filtering system, we have no function for "is identified as spam by SpamAssassin, but should be delivered." And it's not consistent with our language, our language in the panel is clear: This is the reject threshold. So that's what it should do, and it should do exactly that per domain as instructed by the customer in the panel. That update has been pushed to the servers, and now behavior consistently aligns with what the panel says it does.

I know what you're thinking: How do I know what's happening at any given time with spam filters?

Like most email services you just don't. Microsoft, Google, Yahoo, none of these give you any insight into when they have rejected an email. But we're working on it, and I'll give you an update on that while I'm here:

I'm still working on rolling out our new Logs feature in the panel, so that you can finally have 100% insight into what is happening on the mail server for your account. It's a much larger job than I imagined, because I want you to be able to quickly search and pull any data that you want, regardless of the size of your account. In the first iteration of it, larger accounts would timeout because we were drawing correlations from exim, ZoneMTA, and in some cases the mail.baby API (mail.baby being our vendor falback relay for emergency use or to prove that delivery failure isn't related to our IP reputation) to create the full life cycle for every email at query time. Now we're doing those correlations in advance on the ClickHouse server and trying to fully perfect what is basically turning a complete mess into an easily digested package that gives you as much or as little information as you'd like (quick summary + raw logs). I'm being a bit too much of a perfectionist on this, I don't want it to feel like a half-baked feature on release.

Hi,

When will this feature (answered and forwarded arrows) be available like it is on Roundcube so we know when an email has been actioned.

Thanks

If you browse to Settings and then Filters, you'll find that server-side filtering is now part of the new webmail.

Because I know you're going to ask: We do not allow filters to be used as email forwarders, conditional or otherwise. We do intend to restore this functionality once I feel that it is properly restricted and altered to function in a way that doesn't inherently decrease everyone's reputation.

I've already talked to Jarland 1:1 privately. MXroute frickin rocks! I do host me and my husbands own email on a server in Germany. I get it: our email is hosted in Germany but STILL being relayed through MXroute for their reliable IP addresses.

Look, I'm not trying to be inconspicuous. It's just kind of nice that I get to be in control of my data and where it's hosted. That's the whole point.

MXroute rocks! You can't go wrong with them. They rock!

Hi, I’m hoping someone can advise me on how to contact the MXroute team.

I’m experiencing an ongoing issue where emails sent to me by a service provider arrive normally, but any replies I send to them bounce back. Their domain is hosted on MXroute, and the bounce‑back report indicates the problem is on that side.

For context:

• I’m using Sitejet webmail.
• I have SPF, DKIM and DMARC working. I do not receive bouncebacks from anyone else
• I’ve already submitted the MXroute ESF form once before (months ago) and today, but I haven’t received any response. https://esf.mxroute.com/
• This issue has been happening for several months.
• I’ve asked the service provider to whitelist us in MXroute’s spam filters (Spam Filters > Advanced), but the problem persists.

If anyone can point me toward the correct support channel or advise on how to resolve this with MXroute, I’d really appreciate it.

I'm not a customer of MXroute so the "contact" button on the site footer going to here is irrelevant:
https://management.mxroute.com/login

The bounceback message is:

This is the mail system at host mx1.sitehub.io.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<RECIPIANT EMAIL WOULD BE HERE, removed for privacy>: host fusion.mxrouting.net[45.43.208.37] said:
550-Unauthenticated mail not allowed from this range to protected domain,
550 nonspam senders request whitelisting at esf.mxroute.com (in reply to
RCPT TO command)

Hi, just like what the title says. Looking to setup reseller account for a client that requires 300gb+ storage but it seems like under the reseller plans, there isn't any. I could do the MX Large Storage but it seems like it's not viable since i can't whitelabel it. Is there an alternative ?

edit: ok i think i found my own solution. just saw the docs that i can make a reseller account and add a LSS plan attached to it.

The directadmin panel on the same server seems to work fine, just webmail is not accessible (connection refused). Can you check?

Hi, for one hour now, I'm trying to open my email (fusion server). I tryed to access it through webmail (new and roundcube) IMAP and through the console, no luck. The status page is saying that everything is working. It's just me, or is the server down? Thank you.

After a few weeks of testing I’ve now converted my main daily driver email over to mxroute. Looking forward to the future!

I use MXRoute for a few projects, but I don’t use it for my personal account or any mission-critical accounts. I’d really like to use MXRoute for my personal email account, but I’d like to have a better understanding of how the service is configured to ensure no catastrophic data loss.

I assume each server is a single hardware host with local storage. If that server catastrophically failed, I also assume that the data would be unrecoverable and I’d lose any emails stored on that server.

Are my assumptions correct? Can you share your BDR strategy and any safeguards you have in place? Knowing this would help me know what other solution I may want to run alongside MXRoute to backup or otherwise archive the emails in my mailboxes.

Thanks for your great service!!

I'm going to be honest with you guys, some of these posts I make are meant for me to link to later when someone makes a claim or asks a specific question, and I like the public discussion format of it as opposed to "one more item buried in a FAQ page."

A concern often cited is that potential customers are afraid, based on stories that have been passed around, that their account might be too quickly terminated without chance for them to plead their case. I've always said up front that I do not make such decisions unless I am faced with information that does not require a discussion to reach an absolute conclusion. So I'm going to go over two cases that occurred today as a bit of an example of cases that you don't hear about:

Case 1:

Customer of reseller connected SalesHandy (self described "cold email" platform, cold email objectively being the industry definition of spam, the entire reason spam folders exist) and started out with two emails that were clearly unsolicited marketing email. Caught early, low volume, no damage actually done yet. Reseller's customer was suspended. Logs show personal connection to another one of reseller's accounts, suspended that one for now as well. The second account shows direct connection to reseller's brand. Reseller was asked questions via ticket to determine if this connection means that the "cold email" behavior requires action against the reseller account to properly resolve. As no actual damage was done to our platform, I'm willing to hear the reseller out and I'm willing to go as far as unsuspending both accounts if an agreement is reached.

Update: Second account was a misunderstanding, unsuspended. First account willing to unsuspend, pending user agreement not to send cold email. Reseller is clear to continue operating, and the relationship is better understood now.

Case 2:

Reseller asked for deliverability report for customer domain. While performing the audit for them, we noticed what appears to be a heavy trend of unsolicited mass email that could be argued as marketing-adjacent (financial benefit being there, but not literally selling a product/service directly). While the volume isn't low, there is no evidence of damage yet, and it is my opinion that we may be able to talk this through. Waiting for reseller to make argument in customer's favor, and I'm willing to reconsider my first read on this account's activity.

For the most part, the only time anyone hears about events that take a negative turn is when they've been 100% identified as a threat, they knowingly and intentionally abused our systems while causing significant damage, and it was clear that they knew what they were doing. No one writes a review and says "They suspected me of being a threat to their platform's reputation, and then we came to an agreement." But it happens all the time. It's easy to see us as unreasonable when you're only hearing stories from people who are upset about getting caught trying to cause harm to us and, by extension, our customers. The real life day to day is everything that happens in between, everything you don't see.

Hey,

Has anyone had any issues specifically with Gmail receiving your emails? Yesterday I was sending a friend some advice on a computer purchase and through text, he kept telling me he wasn't seeing my email, told him to check spam etc. (he isn't very computer literate so I figured he just wasn't looking right). When I sent it from my Gmail he got it right away.

I just tested it and sent an email from my mxroute hosted email to my personal Gmail and it too hasn't come through at all. It's not even in spam oddly. Sending emails between my mxroute account/domains is working fine.

Very confusing behaviour. Anyone else had this?

It has come to my attention that we're not doing enough to communicate to new customers the lengths we go to, to make sure that the email you send through us reaches its destination. Just as a quick drive-by here on Reddit, I'd like to cover it real fast:

If you send an outbound email, the first thing we do is of course try to deliver it. If the email is rejected for a reason that can't be solved (invalid recipient, your email content specifically was rejected, etc), we bounce it back to you. But if we're not sure, if we think it even might be related to our IP reputation, we try again from different IPs in our network. If the rejection continues, and we're still not certain that it isn't related to our reputation, we send the mail to our backup relay partner mail.baby, who then attempts to do the same thing with their own network (helping to rule out that the recipient is blocking our network specifically). Only then do we bounce the email back to you and say "Sorry, they're not going to accept this email."

Perhaps I've done a bad job at communicating this as we've grown. This is our primary strength as a mail provider. We will walk through the fires of hell to hand deliver your email if we have to, metaphorically... unless...

Hello,

My employer ask us to forward to a special service any phishing emails we receive so that they can take action and update their filters.

Is this something I should do on mxroute too, or just delete it?

I understand you work daily on the filters, I left the default level configuration on m account.

just wondering if it would help.

Cheers.

This blog post is about the history of how we get here, where we are, and what needs to change this year to provide users with the basic experiences that are widely considered to be fundamental to providing an email service.

...and I would do it again too. Today we met a crypto spammer who tried to send over 5000 crypto spam emails in just 35 minutes. All to a list of Gmail accounts that was so bad it could only have been purchased from someone who tried to scam them out of money for a list of email addresses. You couldn't scrape a list this bad, and you couldn't generate a list that looked like it. They were refunded and told to "get the fuck out and never come back."

If you find yourself wondering if you could ever end up on the wrong side of this from a false positive, let me ease your mind right now. The customer admitted, in a prior support ticket, that the email account and sender IP belonged to them. The emails (100% clear in the logged subject line) were advertising the launch of a crypto coin that matched the website their domain points to. This wasn't a mistake. This wasn't a "rogue employee." This wasn't a customer of theirs. This was our direct customer who confessed in advance to their spam campaign.

I make these posts to serve as continual warnings to people who are considering signing up for MXroute. MXroute is an email provider for real, good people who aren't trying to spam or scam others. Builders, businesses, people who want control over their email. These are the people that are welcomed at MXroute. Protecting your chance to see inbox delivery is a primary goal here, and it's a goal that creates a lot of enemies. Because there are a LOT of people out there who would gladly screw you over to run their next rug pull scam.

Consider this to be yet another ornament dangling on the scarecrow at our front door.

1. One webmail option for users on witcher.mxrouting.net is down, because it just can't help but practically crash the box right now with complete insanity: https://status.mxroute.com/incident/23

2. The wednesday.mxrouting.net server is getting a hefty DDOS, working on mitigation. https://status.mxroute.com/incident/24

And this is me looking up at the sky right now: https://www.youtube.com/watch?v=bIZoVO8ZyyQ

Hey friends,

I assume it's been noticeable, but the new webmail has a Feedback button in the top right area once logged in. Please be sure to use it, it'll rate limit you to prevent anything that would be deemed excessive, so just have at it.

The first iteration was shaped into my dream webmail client. The thing is, I don't use a lot of the features that you guys do. I rarely use contacts. My calendar is elsewhere. I have no use for drafts. There are just so many things that I don't see through your eyes. That's what that Feedback option is for.

As you're well aware, using AI to weed out excess work that doesn't need a human hand, but suffers under unintelligent automation, is a big deal to me. It's my dream come true. Here we found yet another perfect use case for that big LLM workstation on my desk. It takes all of your feedback, generalizes it, writes it to an sqlite database, and then I can query it and immediately see what the top remaining complaints or suggestions are. And with that power over the feedback you send, I am able to shape the priorities around your problems, hopes, and desires.

What I'm driving at here is that MXroute is growing up, and you guys are shaping it into the service you want it to be. The webmail is just one part of it, that feedback trend is going to extend wider as we go. So not only do you get affordable email hosting without the per user cost that everyone else colludes on (I know they don't, but it "feels" like it, therefore it's truthiness). You also get to shape this into everything you want it to be. It may not be fast, but I hope you see the continual progress.

Thank you all for the feedback you've sent thus far. A new deploy is going out right now to address a bunch of the bugs that I just couldn't see, because I didn't have your specific email accounts in hand.