Sending e-mails and restrictions
Information about rules and restrictions for sending e-mail messages from a webhosting via SMTP server, virtual and dedicated servers.
For the purpose of prevent and suppress the sending of unsolicited e-mail messages (spam) we have implemented certain rules and restrictions for our hosting services.
It should be underlined that these restrictions are not directed against the majority of our customers who are decent and do not send spam messages. The vast majority of them will never affect this restrictions.
Webhosting and SMTP server
Webhosting offers two ways of sending e-mails:
- from webhosting server with function mail() in PHP
- from e-mail software through our SMTP server
At the webhosting is absolutely forbidden to carry out any mass e-mail messages regardless of whether it is a solicited or not. There is not allowed to send various newsletters to registered customers. If the customer needs something like that, he must find another service, eg. choose our VPS or Dedicated server.
- maximum number of sent e-mails from webhosting: 500 / day
- maximum number of sent e-mails via SMTP server: 500 / day
- maximum size of outgoing e-mails including attachments: 100 MB
When you try to send an e-mail over the limit:
- function mail() in PHP returns false and the message is discarded
- SMTP server rejects the message with an error message informing about limit is exceeded
Limit applies to the calendar day to reset the counters will therefore midnight.
These limits can be increased after agreement with us. The validity of such the requests are assessed by us. Conditions are at end of article.
At webhosting is not possible to send messages via the SMTP protocol in PHP (not allowed to establish connection over TCP port 25). To send SMTP mail from a web application, you need to send it through our mail server or third-party server on port 587 (SMTP authentication is required).
Virtual and dedicated servers
VPS and dedicated servers can be used to mass mailing.
Conditions for mass mailing from VPS and dedicated servers:
- must be requested messages so recipients should be aware that subscribing to these messages
- reports shall be sent in non inconvenience amount
- message must be sent by small doses, can not be sent once in a large amount
- email must contain instructions to unsubscribe and the sender must accept request to unsubscribe and respect it
For virtual and dedicated servers, the customer is obliged to share information about the performed mass emailing at our request:
- how are collected e-mail addresses, and how is obtained consent to receive
- what messages are sent
- how often messages are sent
- in what quantities are sent (total, sending rate)
- how can recipients unsubscribe
- any other information according to our requirements
If the customer violates these terms or fails to deliver the required information to us, we are authorized to block e-mails sending or suspend whole server.
Why this restriction?
Mainly, it should be underlined, that such restrictions are not primarily directed against our customers.
We do not do it all because we assume that our customers are naughty and they want to use our hosting for mass sending of unsolicited mail. The most common causes and sources of spam are totally different and the customer that's mostly innocent.
Usually the causes and sources of spam:
- Security "hole" in PHP script that allows abuse - such as collective posting to a forum (forum then sends these new posts forum members), the error directly in a contact form, etc.
- Stealing your password to FTP site account (usually from an infected home PC), the attacker then placed on a customer web some malicious PHP script, which produces mass spamming. The customer may not have the slightest idea about that.
- Error in customers PHP script which contains "infinite loop" and starts unexpectedly intense sending e-mails.
Intentional spam distributing by our customer is the last thing happens and what we are dealing with.
So why these restrictions? Again, this is due to the fact that web hosting is shared service. So on one web page server has hundreds of customers. If one of the sites begins (for any reason) to send mass messages and then blocked by some e-mail server, then will be blocked everyone else from the same server (because all sites have the same IP address).
Other e-mail servers on the Internet protecting their users and customers by blocking of source of a suspicious e-mail messages. Such blocking may be temporary, but also permanent. And if the mail server decides to permanently block all e-mails from our webhosting, than any customer from us is not able to send emails to this server(neither requested regular emails). And surely nobody do not want it.
Why limit does not comes up when something happens? The solution must be preventive. If an attacker finds a loophole in the security of your site and begins to exploit the mass spamming, it's too late. Before we find something, analyze and introduce measures attacker could already distribute tens of millions of messages and then web server would be blocked in various places on the Internet.
This solution is not nothing wrong. Do not take this as a restriction against you. Take it as your protection against abuse of your site for illegal activities. With this preventive measure we are able to ensure that the correct requested e-mail always arrives from your website to your customers, friends, visitors, etc. Without this restriction it would not work.
On our datacenter website you can find answer to the question ofhow could we offer such low prices. There are details about our facilities, the construction, equipments and the operation of the datacenter. Our datacenter is among the largest and most modern datacenters in the Czech Republic.