Pravila in omejitve pošiljanja e-mails
Informacije o pravilih in omejitvah za pošiljanje e-poštnih sporočil s Spletnega gostovanja, WebSite, Mailhostinga ter z virtualnih ali namenskih strežnikov.
Za preprečevanje in omejevanje pošiljanja neželenih e-poštnih sporočil (neželene pošte) so za vse naše storitve gostovanja določena posebna pravila. Te omejitve varujejo ugled naših deljenih poštnih strežnikov, zlasti v primeru kompromitiranih e-poštnih predalov ali spletnih obrazcev.
Web Hosting, WMS, WebSite, Mailhosting
Pošiljanje kakršnih koli množičnih e-poštnih sporočil iz storitev Web Hosting, WMS, WebSite in Mailhosting je strogo prepovedano, ne glede na to, ali gre za zaželena ali nezaželena sporočila. Sem spadajo tako množične komercialne ponudbe kot tudi e-novice, poslane prijavljenim prejemnikom.
Če morate pošiljati tovrstno pošto, si vzpostavite storitev, specializirano za množično pošiljanje pošte (VEDOS nobene take storitve ne ponuja, ne posreduje in ne priporoča), ali pa si lahko vzpostavite svoj poštni strežnik naVPS or dedicated server.
Spletni hosting, WMS in WebSite pošiljajo e-pošto na dva načina:
Funkcija mail() v PHP
From the web hosting server using the mail() function in PHP. This includes many contact forms, WordPress password recovery, and various other, at least partially automated, messages.
Sending via SMTP
Iz e-poštnega programa prek našega strežnika SMTP. Za pošiljanje e-pošte na ta način se morate v predal prijaviti z uporabniškim imenom in geslom.
Mailhosting omogoča pošiljanje e-pošte samo prek SMTP. Pri spletnem hostingu in WMS ni mogoče pošiljati neavtorizirane e-pošte prek protokola SMTP (odhodne povezave prek vrat TCP 25 ni mogoče vzpostaviti). Za pošiljanje pošte prek protokola SMTP iz spletne aplikacije jo je treba poslati avtorizirano (torej po prijavi) prek našega poštnega strežnika ali strežnika tretje osebe na vratih 587.
Limits on sending e-mails for hosting services
The following table summarizes the limits on sending e-mails for hosting services:
| Limit | Web Hosting NoLimit/Extra, WebSite (except Free), WMS |
Web Hosting LowCost | Mailhosting Individual | Mailhosting Business (can be activated for any Web Hosting) |
|---|---|---|---|---|
| Maximum number of e-mails sent via PHP per day | 500 | 50 | – | – |
| Maximum number of e-mails sent via SMTP per day | 500 | 50 | 500 | 2500 |
| Maximum size of an e-mail sent, including attachments (MB) | 100 | 100 | 100 | 100 |
If you try to send an e-mail above the set limit
- Za
mail()function in PHP returnsfalseand the server discards the message. - The SMTP server rejects the message with an error message informing you that the limit has been exceeded.
The limit applies to a calendar day; the counter resets every day at midnight (CET/CEST).
The stated limits on sent e-mails can only be increased by purchasing the add-on service Upgrade to the Business variant. There is no entitlement to a limit increase, and the provider reserves the right to refuse a request for an increase (or for provision of the add-on service) even without giving a reason. Increasing the limit does not permit bulk sending of e-mail messages, nor does it justify it in any way.
Virtualni in namenski strežniki
You can use VPS and dedicated servers for the bulk sending of solicited messages, provided you meet the following conditions:
- The messages must be solicited, meaning the recipients must be aware that they have signed up to receive these messages.
- Messages must be sent in a non-intrusive volume.
- Messages must be sent in reasonably small batches, never all at once in large quantities.
- The message must include a procedure for unsubscribing, and the sender must accept and respect unsubscribe requests.
Information the customer is required to provide at our request
- Kako se pridobivajo e-poštni naslovi prejemnikov in kako se pridobiva soglasje za pošiljanje sporočil.
- What messages are being sent.
- How often the messages are sent.
- In what volume they are sent (total number, sending rate).
- How recipients can unsubscribe.
- Any other information at our request.
If the customer violates these conditions or fails to provide us with the required information, we are entitled to completely block e-mail sending or suspend the entire server.
Why these limits?
First of all, it should be emphasized that these limits are not primarily aimed at our customers. Common causes and sources of spam include:
- A security hole in a PHP script that allows it to be exploited, for example the bulk insertion of posts into a discussion forum (the forum then sends these new posts to its members), a bug directly in a contact form, and similar.
- Kraja gesla FTP za spletno mesto (običajno z okuženega domačega računalnika); napadalec nato na spletno mesto stranke namesti zlonamerno skripto PHP, prek katere nato pošilja množično neželeno pošto. Stranka o tem morda nima pojma.
- Napaka v odjemalčevi skripti PHP, ki se na primer zatakne v zanki in začne nepričakovano ter intenzivno pošiljati e-pošto.
Deliberate sending of spam by our customer is the last thing that happens and the last thing we deal with.
So why these limits? E-poštne storitve Web Hostinga, WMS, WebSite in Mailhostinga so deljene. En sam strežnik gosti spletna mesta ali poštne predale več sto strank. Če tak strežnik začne (iz kakršnega koli razloga) pošiljati množična sporočila in ga nato blokira e-poštni strežnik prejemnika, bodo začasno ali celo trajno blokirane tudi vse druge stranke na istem strežniku (ker vse delijo isti naslov IP).
Če tako blokado nastavi velik ponudnik e-poštnih storitev, kot so Seznam, Gmail ali Outlook, veliko število uporabnikov in strank s tega strežnika ne bo prejelo niti legitimnih sporočil, dokler se stanje ne odpravi in naslov ne odblokira. To lahko traja ure ali celo dlje.
Why aren’t the limits addressed only once something happens? The solution must be preventive. If an attacker finds a security gap in a website or e-mail account and starts exploiting it for bulk spamming, it is already too late. Sending tens of millions of messages is a matter of a single script and a relatively short amount of time. By the time we received and processed a report, such a server would already be blocked in various places across the Internet.
This solution is not a bad thing. Tega ne jemljite kot omejitev, uperjeno proti vam. Vzemite to kot svojo zaščito pred zlorabo vaše spletne strani za nezakonite dejavnosti. Zahvaljujoč temu preventivnemu ukrepu lahko zagotovimo, da pravilna in zaželena e-pošta z vaše spletne strani vedno prispe do vaših strank, znancev, obiskovalcev in tako naprej. Brez te omejitve to morda ne bi bilo mogoče.