Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Mxroute email receiving very slow - Page 3
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Mxroute email receiving very slow

13

Comments

  • GulfGulf Member

    @caracal said:
    Why do you even need MXRoute specifically for multiple accounts to receive mail? Can't you do that on any old VPS or even Directadmin reseller?

    Yes, vps + cpanel = 20$

  • SirFoxySirFoxy Member

    @Gulf said:

    @caracal said:
    Why do you even need MXRoute specifically for multiple accounts to receive mail? Can't you do that on any old VPS or even Directadmin reseller?

    Yes, vps + cpanel = 20$

    Yes, VPS + DirectAdmin + /24 IPv4 + WHMCs and you can re-create @jar entire business model.

    Thanked by 1COLBYLICIOUS
  • GulfGulf Member

    @SirFoxy said:
    Yes, VPS + DirectAdmin + /24 IPv4 + WHMCs and you can re-create @jar entire business model.

    He only needs to receive mail. So 1 IP is ok. cpanel is easier imho and can automate. some big vps providers sell it for 10$ with their vps.

  • r3kr3k Member

    @SirFoxy said:
    Yes, VPS + DirectAdmin + /24 IPv4 + WHMCs and you can re-create @jar entire business model.

    damn

  • jarjar Patron Provider, Top Host, Veteran
    edited May 2024

    @SirFoxy said:

    @Gulf said:

    @caracal said:
    Why do you even need MXRoute specifically for multiple accounts to receive mail? Can't you do that on any old VPS or even Directadmin reseller?

    Yes, vps + cpanel = 20$

    Yes, VPS + DirectAdmin + /24 IPv4 + WHMCs and you can re-create @jar entire business model.

    Oh I wish it were that easy. It was, for a period of time. Didn't last long 😂

    Thanked by 2sillycat eezcloud
  • mike1smike1s Member
    edited May 2024

    @SirFoxy said: So to clarify: with MXRoute the law doesn't determine what content is allowed, the private business (you, subjectively) does?

    MXRoute has the right to decide what's allowed and what isn't. Don't like it, use another service. Freedom of choice :smile: It's Jar's business, he can do whatever he wants outside of discrimination of protected classes.

    Thanked by 3adly emgh maverick
  • yoursunnyyoursunny Member, IPv6 Advocate

    @mike1s said:
    can do whatever he wants outside of discrimination of protected classes.

    Shall we inform each provider that we are bi, so that they cannot delete or deprioritize our service?

  • adlyadly Veteran

    @mike1s said:

    @SirFoxy said: So to clarify: with MXRoute the law doesn't determine what content is allowed, the private business (you, subjectively) does?

    MXRoute has the right to decide what's allowed and what isn't. Don't like it, use another service. Freedom of choice :smile: It's Jar's business, he can do whatever he wants outside of discrimination of protected classes.

    I think people forget that a business is not obligated to accept every customer (beyond potentially discriminating against a protected class), and exercising their right to deny custom isn’t some form of censorship.

    People get banned by Amazon, Apple, Google, etc. all the time for triggering whatever policy and often have zero recourse, so you’re about as safe with those real businesses as any other. 🤷‍♂️

  • GulfGulf Member

    On Namecheap email hosting, they suspend if you receive (!) too much spam.
    There are burstable spam attacks on my domains, and they block them every time.

    They say it impacts the server's performance. Well, you specifically pay for their Private Email and expect them to have multiple servers for this (like Gmail). But you are probably placed on something like a shared hosting. And you pay 5$ per month or so for a single domain.

    Thanked by 3jar adly emgh
  • jarjar Patron Provider, Top Host, Veteran
    edited May 2024

    @Gulf said:
    On Namecheap email hosting, they suspend if you receive (!) too much spam.
    There are burstable spam attacks on my domains, and they block them every time.

    They say it impacts the server's performance. Well, you specifically pay for their Private Email and expect them to have multiple servers for this (like Gmail). But you are probably placed on something like a shared hosting. And you pay 5$ per month or so for a single domain.

    Kinda comes down to pricing too. Like for example I set out to model email hosting after shared hosting, it wasn't a secret or some way to get rich. I wanted to challenge the pricing models. You don't get to do that and still build infrastructure out in the same way as Gmail. It's like people want to think you don't "cut corners" but that's literally exactly what you do, if everything is treated as relative to how Google does it.

    Though I don't think of it as "cutting corners" I just don't think of companies like Google as the standard, just doing my own thing the way I wanted to do it. Enough seem to like it.

    But yeah, it can be tough to handle inbound floods regardless of the source port they're hitting. Much more so if that port is supposed to be receiving the traffic that the flood is coming in as, and it's supposed to be receiving it from those sources. Normal usage though, you really don't end up with 30k recipients by Steam all in perfect sequence with no buffer between them in their customer database against a server that has 1000 customers on it. Just doesn't realistically happen without shady business going on (or hosting mail for a large ISP that gives it's users email but even then, only a fraction will be registered for the same external services while being in alphabetical order nested together in those external databases).

    I definitely think it's better to focus on the use cases that cause a problem with 1 out of every 25,000 customers than to tell everyone across the board "don't you dare get too much spam." That's how you confuse and turn off regular customers that were never going to cause problems.

  • GulfGulf Member

    Yes, true.
    Checked pricing. Namecheap charges 5$ for 5 mailboxes on a single domain (you still could use 1 as catchall).

    And the acceptable usage is about 1 mail per second. They won't handle a spam attack for you (like 10k mail queue in my case).

    NC says that it impacts other users.
    Recently, they even warned me about over-quota bounces. They do not like it, even if you send mail from your own servers.

    GMail handles that, but their throttling is insane.

    Thanked by 1jar
  • GulfGulf Member

    And yes, NC reads your mail. They forwarded me these bounces from "private" emails :)

    I was shocked a bit that a random person (from India) read the mail.

    Thanked by 1jar
  • jarjar Patron Provider, Top Host, Veteran
    edited May 2024

    @Gulf said:
    And yes, NC reads your mail. They forwarded me these bounces from "private" emails :)

    I was shocked a bit that a random person (from India) read the mail.

    We all read something, to be fair. Every email that Microsoft filters into their spam folder, they send me a full copy of the email. Stuff like that. Though I don't actually read that, it's boring. One day I plan to give users an automated summary of it every week or so to see what hit MS spam folders

  • GulfGulf Member

    Yes, this way can remove aggressive users who prefer to click spam.
    MS will forward full email and I have software that clicks Unsubscribe in the email :D

    Thanked by 2jar tentor
  • GulfGulf Member

    The best options I've used so far are yandex and mail.ru
    both have aggressive spam filters you cannot control

    Mail.ru sometimes bounces in russian :D
    But they do not check IPs in DBs like spamhaus.
    And they have handled all spam attacks without any problem.

    Mail.ru also automatically reads all emails (I think FSB may also read it).
    They will suspend you if you have many bounces, even if you send from own servers. They think you were "hacked".
    Also, a lot of blocked resources, like you cannot send mail to proton. Will get bounce "We do not send to proton mail" :D

    Thanked by 1jar
  • GulfGulf Member

    So in summary, any other mail provider like Namecheap will ban you the same way.
    Namecheap says literally that other users receive mail very slow and they suspend you.

    For such special requirements like mine or yours,
    Deal with big providers or use own servers (I prefer cPanel).

  • jarjar Patron Provider, Top Host, Veteran
    edited May 2024

    @Gulf said: Deal with big providers

    Well... I have to tell a short story there.

    When I worked at DigitalOcean I pissed off a spammer, like I always do of course. The spammer configured a bash while loop on an OVH VPS to flood [email protected] with junk at an incredible rate. Now, that email was hosted on Gsuite, quite a large and well paid for account. Google, in it's infinite wisdom, decided that I was receiving email too quickly and halted all inbound mail to my account until the attack halted. They didn't block the sender, no that would be too easy. Instead, they made me miss nearly every company email for 2 weeks.

    So, you know, the grass isn't always greener. I can blackhole an IP. Google can't figure out how to do that, no matter how much you pay them. I'm not saying I'm better than Google, but I am saying that number of employees and status on the stock exchange is not a guaranteed fix for anything.

    (The rest of that story: Our admins were able to engage some kind of additional filtering that helped me get "some" email during the second week of the event, but I still missed almost everything that was addressed to me)

  • crunchbitscrunchbits Member, Patron Provider, Top Host
    edited May 2024

    @jar said:

    @Gulf said: Deal with big providers

    Well... I have to tell a short story there.

    When I worked at DigitalOcean I pissed off a spammer, like I always do of course. The spammer configured a bash while loop on an OVH VPS to flood [email protected] with junk at an incredible rate. Now, that email was hosted on Gsuite, quite a large and well paid for account. Google, in it's infinite wisdom, decided that I was receiving email too quickly and halted all inbound mail to my account until the attack halted. They didn't block the sender, no that would be too easy. Instead, they made me miss nearly every company email for 2 weeks.

    So, you know, the grass isn't always greener. I can blackhole an IP. Google can't figure out how to do that, no matter how much you pay them. I'm not saying I'm better than Google, but I am saying that number of employees and status on the stock exchange is not a guaranteed fix for anything.

    (The rest of that story: Our admins were able to engage some kind of additional filtering that helped me get "some" email during the second week of the event, but I still missed almost everything that was addressed to me)

    I think we can take a page from Randy's T.M.I math here. There is something to be said about adjusting for a customer's distance to the c-suite. A 1-man show? Very close, but probably overworked and certainly can't possibly know everything. Google? Near impossible to reach a decision-maker, next to no way you'll ever get any real solutions that aren't on an internal wiki/checklist with a full liability shift.

    The key is to never forget to include the yaw.

    Thanked by 2jar emgh
  • emghemgh Member, Megathread Squad
    edited May 2024

    @crunchbits said:

    @jar said:

    @Gulf said: Deal with big providers

    Well... I have to tell a short story there.

    When I worked at DigitalOcean I pissed off a spammer, like I always do of course. The spammer configured a bash while loop on an OVH VPS to flood [email protected] with junk at an incredible rate. Now, that email was hosted on Gsuite, quite a large and well paid for account. Google, in it's infinite wisdom, decided that I was receiving email too quickly and halted all inbound mail to my account until the attack halted. They didn't block the sender, no that would be too easy. Instead, they made me miss nearly every company email for 2 weeks.

    So, you know, the grass isn't always greener. I can blackhole an IP. Google can't figure out how to do that, no matter how much you pay them. I'm not saying I'm better than Google, but I am saying that number of employees and status on the stock exchange is not a guaranteed fix for anything.

    (The rest of that story: Our admins were able to engage some kind of additional filtering that helped me get "some" email during the second week of the event, but I still missed almost everything that was addressed to me)

    I think we can take a page from Randy's T.M.I math here. There is something to be said about adjusting for a customer's distance to the c-suite. A 1-man show? Very close, but probably overworked and certainly can't possibly know everything. Google? Near impossible to reach a decision-maker, next to no way you'll ever get any real solutions that aren't on an internal wiki/checklist with a full liability shift.

    The key is to never forget to include the yaw.

    Yes!

    I think that’s why I like Inleed so much, they’re about 9 people. They’re basically there 24/7 in case you need help, with minutes response time, but, it’s also very possible to get actual issues to the team effectively and see it fixed next time you visit. I have experienced this first-hand.

    Edit: Also, for some reason, the % of staff that don’t have to do with the core business is a big tell to me as well. When a hosting company has more weird titles than they have ”Support” or similar roles, it’s usually not a good sign. Inleed has 1 person that’s not directly involved with the tech, and she does the finances, which of course someone has to do.

  • Google workspace has a limit of 30 aliases per account (or like thay), and the catch-all was disabled on free accounts a while ago

  • NickNick Member, Patron Provider

    @jar said:

    @Gulf said: Deal with big providers

    Well... I have to tell a short story there.

    When I worked at DigitalOcean I pissed off a spammer, like I always do of course. The spammer configured a bash while loop on an OVH VPS to flood [email protected] with junk at an incredible rate. Now, that email was hosted on Gsuite, quite a large and well paid for account. Google, in it's infinite wisdom, decided that I was receiving email too quickly and halted all inbound mail to my account until the attack halted. They didn't block the sender, no that would be too easy. Instead, they made me miss nearly every company email for 2 weeks.

    So, you know, the grass isn't always greener. I can blackhole an IP. Google can't figure out how to do that, no matter how much you pay them. I'm not saying I'm better than Google, but I am saying that number of employees and status on the stock exchange is not a guaranteed fix for anything.

    (The rest of that story: Our admins were able to engage some kind of additional filtering that helped me get "some" email during the second week of the event, but I still missed almost everything that was addressed to me)

    I recall helping you with that bastard back in 2016 :hushed:

    Thanked by 1jar
  • JosephFJosephF Member

    @rafaelscs said:
    Google workspace has a limit of 30 aliases per account (or like thay), and the catch-all was disabled on free accounts a while ago

    Are you sure? I have a free account for 15 years with a catch-all as well as users with more than 30 aliases.

  • zedzed Member

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

  • jarjar Patron Provider, Top Host, Veteran
    edited May 2024

    @zed said:

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

    SMS is heavily regulated and differently per region. The carriers are super protective of the email to SMS gateways as a result. However, the infrastructure of some major carriers is shared with several major emails services like Yahoo, att.net, etc. Because they're so protective of it, it's incredibly easy to get entire IP ranges blocked and have to navigate significant hoops to get them unblocked.

    When AT&T ignored me because of it, I had to use contacts to run it up the chain and it took weeks.

    When Verizon blocked us for the same and then refused to unblock, I had to communicate with the CEO's team for a few weeks to get it unblocked.

    The risk vs reward is too high in favor of risk. Meanwhile, software like Pushover does it better. Services like Twilio are better equipped to navigate the SMS regulatory environments.

    Fortunately this policy can be ignored, and no action will be taken for violating it. The emails will be rejected.

    Thanked by 3zed tentor MateiSR
  • zedzed Member

    @jar said: The risk vs reward is too high in favor of risk.

    What a mess, appreciate your taking the time to explain.

    Thanked by 1jar
  • JosephFJosephF Member

    @jar said:

    @zed said:

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

    SMS is heavily regulated and differently per region. The carriers are super protective of the email to SMS gateways as a result. However, the infrastructure of some major carriers is shared with several major emails services like Yahoo, att.net, etc. Because they're so protective of it, it's incredibly easy to get entire IP ranges blocked and have to navigate significant hoops to get them unblocked.

    When AT&T ignored me because of it, I had to use contacts to run it up the chain and it took weeks.

    When Verizon blocked us for the same and then refused to unblock, I had to communicate with the CEO's team for a few weeks to get it unblocked.

    The risk vs reward is too high in favor of risk. Meanwhile, software like Pushover does it better. Services like Twilio are better equipped to navigate the SMS regulatory environments.

    Fortunately this policy can be ignored, and no action will be taken for violating it. The emails will be rejected.

    If the risk is the carrier blocking your service from sending, and your fix is to block it yourself, then why do you worry about the risk? The worst they'll do is what you're doing yourself.

  • jarjar Patron Provider, Top Host, Veteran

    @JosephF said:

    @jar said:

    @zed said:

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

    SMS is heavily regulated and differently per region. The carriers are super protective of the email to SMS gateways as a result. However, the infrastructure of some major carriers is shared with several major emails services like Yahoo, att.net, etc. Because they're so protective of it, it's incredibly easy to get entire IP ranges blocked and have to navigate significant hoops to get them unblocked.

    When AT&T ignored me because of it, I had to use contacts to run it up the chain and it took weeks.

    When Verizon blocked us for the same and then refused to unblock, I had to communicate with the CEO's team for a few weeks to get it unblocked.

    The risk vs reward is too high in favor of risk. Meanwhile, software like Pushover does it better. Services like Twilio are better equipped to navigate the SMS regulatory environments.

    Fortunately this policy can be ignored, and no action will be taken for violating it. The emails will be rejected.

    If the risk is the carrier blocking your service from sending, and your fix is to block it yourself, then why do you worry about the risk? The worst they'll do is what you're doing yourself.

    Because when they block IP ranges it impacts delivery to Yahoo, ATT DSL customers, etc. The impact is further reaching than just the email to SMS. It ends up being one customer causing a large problem for every customer.

    Thanked by 1JosephF
  • JosephFJosephF Member

    @jar said:

    @JosephF said:

    @jar said:

    @zed said:

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

    SMS is heavily regulated and differently per region. The carriers are super protective of the email to SMS gateways as a result. However, the infrastructure of some major carriers is shared with several major emails services like Yahoo, att.net, etc. Because they're so protective of it, it's incredibly easy to get entire IP ranges blocked and have to navigate significant hoops to get them unblocked.

    When AT&T ignored me because of it, I had to use contacts to run it up the chain and it took weeks.

    When Verizon blocked us for the same and then refused to unblock, I had to communicate with the CEO's team for a few weeks to get it unblocked.

    The risk vs reward is too high in favor of risk. Meanwhile, software like Pushover does it better. Services like Twilio are better equipped to navigate the SMS regulatory environments.

    Fortunately this policy can be ignored, and no action will be taken for violating it. The emails will be rejected.

    If the risk is the carrier blocking your service from sending, and your fix is to block it yourself, then why do you worry about the risk? The worst they'll do is what you're doing yourself.

    Because when they block IP ranges it impacts delivery to Yahoo, ATT DSL customers, etc. The impact is further reaching than just the email to SMS. It ends up being one customer causing a large problem for every customer.

    Got it. When you ran into this problem, all customers were unable to send email to Yahoo/AT&T for the several weeks until it was resolved?

  • jarjar Patron Provider, Top Host, Veteran

    @JosephF said:

    @jar said:

    @JosephF said:

    @jar said:

    @zed said:

    @jar said:

    It's in the policy: https://mxroute.com/policy.html

    I re-read this just now and I'm curious why sending SMS via e-mail is on the forbidden list, can you expand on that?

    SMS is heavily regulated and differently per region. The carriers are super protective of the email to SMS gateways as a result. However, the infrastructure of some major carriers is shared with several major emails services like Yahoo, att.net, etc. Because they're so protective of it, it's incredibly easy to get entire IP ranges blocked and have to navigate significant hoops to get them unblocked.

    When AT&T ignored me because of it, I had to use contacts to run it up the chain and it took weeks.

    When Verizon blocked us for the same and then refused to unblock, I had to communicate with the CEO's team for a few weeks to get it unblocked.

    The risk vs reward is too high in favor of risk. Meanwhile, software like Pushover does it better. Services like Twilio are better equipped to navigate the SMS regulatory environments.

    Fortunately this policy can be ignored, and no action will be taken for violating it. The emails will be rejected.

    If the risk is the carrier blocking your service from sending, and your fix is to block it yourself, then why do you worry about the risk? The worst they'll do is what you're doing yourself.

    Because when they block IP ranges it impacts delivery to Yahoo, ATT DSL customers, etc. The impact is further reaching than just the email to SMS. It ends up being one customer causing a large problem for every customer.

    Got it. When you ran into this problem, all customers were unable to send email to Yahoo/AT&T for the several weeks until it was resolved?

    I was able to mitigate it with external relays at least.

    Thanked by 1JosephF
  • winerwiner Member

    I have zero tolerance for any abnormal use of email because it affects everyone.

Sign In or Register to comment.