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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
[Providers] What's your SMTP limits per hour?
I recently signed up for a VPS + cPanel, was about to migrate clients when they told me that they have a limit for 100 SMTP connections per hour.
Assuming I'd migrate like 70-100 clients, they could hit these limits really, really damn easy.
They also confirmed twice they will NOT raise the limits to protect their IPs...
Even though I'd be using SpamExperts.
Assuming you have cPanel clients, people that signup for a VPS + cPanel, and have a fairly amount of clients...
What would be the hourly limit for SMTP connections?
Would you raise those if the given client was a legit company, fully verified?
Comments
@mikePT I thought you left
Simply use another SMTP server and not the one of your provider or search for a proper provider who is able to work with you.
I have, but instead of creating a new account to post this, I used my current account.
I still use servers and orders VPS's!
Cheers
It's a cPanel stack, not going to setup a remote relay.
The question is:
What would be the hourly limit for SMTP connections? Would you raise those if the given client was a legit company, fully verified?
Curious about the answers. I've faced this a few times but they've added me to the whitelist.
The limit is most likely 100 per hour per account. Probably can be adjusted. We're at higher number, but still limited, due the level of abuse on these kind of accounts.
It's not, it's Nodewatch. I did rent a VPS + cPanel license. It's a global limit for the VPS. Nodewatch does it per container, not per cPanel account. I find these limits very low. They completely refuse to raise those or to add us as exception in Nodewatch.
Since 2004, we've had 3 - 4 IPs blacklisted. We host local companies mostly.
Seriously, 100 SMTP connections per hour, for the whole VPS, is just ridiculous, isn't it?
I'm pretty sure someone has a pool going, I should've bet on this one :P
You meant, when I got back? Hehe. Been too busy, and seriously lack time to. But, I signed up for this provider and would love to know the limits for the providers here.
In fact, the said provider doesn't even provide refunds but I'll need to migrate away.
Are you sure that these are not per second?
100 per hour on VPS seems a bit low.
Maybe start reading those pesky TOS agreements. Wonder if it outlined SMTP limits? Ever thought of dumping email to an email provider like mxroute? mailgun? sendgrid? or many of the others? Might save long term headache. Cause even if this company raises limits, they seem to have had issues with smtp - so does that affect your deliverability?
Correct.
"We will be alerted by our system at 100 connections in an hour, and your server will be automatically suspended shortly after this."
Nothing there: http://serverhub.com/policies/useragreement
I'm not eligible for refund either, they do not provide any refunds.
Serverhub's network is great, and their support has been prompt replying to my tickets.
I'm setting up spamexperts, inbound and outbound filtering. Not mailgun nor sendgrid... That would only increase my costs. My reseller pricing with spamexperts is much better.
A long term headache would be setting up the relay for the given services, plus added costs...
Most of my systems have Nodewatch set to 200 for the concurrent SMTP connections, I've never had anyone hit this limit unless the VPS was sending spam (some mass mail scripts), 100 is fairly low but any modern script won't open 100+ SMTP connections in a second. WHMCS mass mail feature won't do it, I can't think of any software that would.
Either way in my situation if someone had a legitimate use I'd whitelist it, since most of my services are through OVH they block IPs that send spam pretty quickly.
Nodewatch is 100 concurrent smtp processes, not per hour.
"I'm sorry to hear that you aren't happy with the restrictions we have in place, however I would like to inform you that we have these restrictions for all our VPS customers and this is not something we're holding against you. We have such restrictions to make sure that the IP's on our network do not get blacklisted, I'm sure you are well aware that it can be a pain to get IP's delisted and is a time consuming process, not to mention some times the blacklisters won't offer normal delisting, they want to take your money."
Well, they should confirm if that is concurrent or not.
Still, if that's per hour or concurrent, it's a huge difference. The fact that they cannot increase it per customer, is also something that upsets me.
I've asked them if that's concurrent smtp connections, or per hour. They stated per hour though.
Still not good. If an account gets compromised, we'll see our server suspended.
We also say hour by default before signup but if asked for specifics (say you get caught by it) we would say concurrent. The idea is to discourage any kind of mass mail before signup.
Nodewatch doesn't allow setting limit per container. However, i am pretty sure your provider does not understand nodewatch's limits if they keep claiming it is per hour.
Yep, I see.
I fully explained my use here, though.
Hopefully that's concurrent. But if a user gets his account compromised, my server will be suspended. Heh.
Rarely happens, but may happen.
I should order a dedicated server instead.
We'll see their reply. Still worries me, though. We got an excellent VPS with them, superb. It's damn fast, and we want to launch a new service dedicated to email. We could hit those limits still....
Looks like we just lost our initial investment, not much, but 35 USD.
By the sounds of it, yes, if you want granular control at this level then you need a dedicated server.
The only issue is with the SMTP limits. Heh, looks like I won't be launching this any time soon. The dedicated server would get more expensive than what we're paying.
Well if you find a host you have a good relationship with or are prepared to put down a spam deposit I am sure you can use a VPS, but I guess I don't need to tell you that.
I have customers that use cPanel and simply pipe the outbound mail through a spam filter/external mail server, works fine.
Thank you for your reply.
Heh, spam deposit, wouldn't be much neeeded... All domains are filtered, inbound/outbound with spamexperts. :P
Cheers!
/thread @jarland
We are limiting our VPS at 250connections per account per hour. Nobody ever hit those limits yet.
Well what is the problem then? did I miss something? You just need a host that is not going to impose limits to a cpanel customer, easy to find.
it seems every purchase is drama adjacent or drama fueled
That's why I use OVH for mail. They are too big to get blacklisted and you can send all your viagra adverts.
Or a good provider. One that is not flippin' ridiculous with their limits...
I think ServerHub is just asinine here. A per-account 100 limit is fine, but essentially they're disincenting their resellers from selling. Stupid.
@MikePT
I would like to clarify a few things since it seems you host with us
. The correct answer is 100 concurrent connections. From the original post, It seems that you are taking all the appropriate steps to avoid spam abuse which I applaud you for. I understand sometimes as a reseller somethings are out of our control especially when dealing with hosting clients, therefore what I recommend is creating a support ticket requesting a whitelist. This is so that if your clients do go over the limit your account isn't automatically suspended. I'll go ahead and approve the request in your case. Just refer to this thread in the ticket.
Thanks
I just received a reply to my ticket stating that you've added me to the whitelist - thank you.
We've been running a business since 2004, it's very important for us to provide email reliability. Most clients are local companies who use email a lot, so that's why we even implemented SpamExperts.
That being said, I too applause you for hearing my request, I appreciate your prompt support and friendly replies.
Thank you! :-)
/thread
We had one case, where the customer complained because the VPS got suspended multiple times because he reached his limit of 350 emails per hour, now seriously if that isn't spamming then what else would be, we cancelled the services with the customer which was a spammer, but is strange how spammers are still the one's which complains in the end.