Date: Fri, 29 Mar 2024 15:44:31 +0100 (CET) Message-ID: <440767165.75.1711723471032@confluence-8.glowhost.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_74_987501936.1711723471030" ------=_Part_74_987501936.1711723471030 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Important Points:
A) Though the below are hourly limits, it does not mean that the numbers b=
elow are your maximum "list member" size. In other words, if your hourly ma=
il limit is 100 emails, you can still send your emails to lists larger than=
100 members, but your script settings may need to be adjusted to be in com=
pliance to not exceed these hourly limits.
B) Though the below are hourly limits, it does not mean that you can expec=
t to send email 24 hours per day at these limits. In other words, if your h=
ourly email limit is 100 messages per hour, sending 2400 emails per day is =
not within acceptable use. If you have a Dedicated Plan or=
Cloud Server (Enterprise Cloud or Cloud VDS), you can set=
your own mailing schedules as desired without any outbound limits.
Current Shared Plans:
Dedicated Plans:
Old Shared Hosting Package Limits:
Budget Shared Hosting Plans - =
100 emails per hour
Advanced Shared Hosting Plans - 250 emails per hour
Professional Shared Hosting Plans - 500 emails per hour
Mailing lists available from y=
our control panel:
Mailman - All Fea=
tures
PHP List - All Features
What does this mean?
If you have =
a mailman mailing list:
That has more than 5000, 500, 250 or 100 list members respectively, anythi=
ng after your hourly email limit will most likely not be delivered. The ser=
ver will automatically toss it in the garbage. This is because mailman does=
not throttle outbound email efficiently. Several factors can allow you to =
exceed 100, 250, and the 500, 5000 list member limit, like time of day, tim=
e at which the mailman list was sent, server load and other factors. Howeve=
r for easy numbers plan on list sizes no greater than your hourly email lim=
it when using mailman.
If you have a php list mailing list:<=
/strong>
You can have more than 5000, 500, 250 or 100 list members respectively. Yo=
u can bypass the problem with trying to deliver more than 500, 250 or 100 e=
mails to your list members by throttling the rate at which emails are sent.=
To see how this works, please see this thread:
Email rate throttle in php list
If you have a vBulletin forum script:
You can have more than 5000, 500, 250 or 100 forum members respectively. Y=
ou can bypass the problem with trying to deliver more than 5000, 500, 250 o=
r 100 emails to your forum members by throttling the rate at which emails a=
re sent. To see how this works, please see this vBulletin Plugin:Email rate throttle in vBulletin
=
Additional Information:
It should be noted and often is not, that when you see email "limits" (if =
your host even advertises them) that your regular sending patterns, like re=
plying to your buddy George about tonight's dinner reservation counts as on=
e email. That means that now you only have 499 list members who will actual=
ly get your list's email, assuming you are on a package that supports 500 e=
mails per hour.
You should take into account your regular email work flow and list size wh=
en selecting a hosting plan. If you anticipate that you send out something =
like one email per minute (wow, you can type fast!) that would be 60 emails=
that you replied to (sent) in one hour. Then, if you decided to send of yo=
ur mailing list within that same hour, you could successfully send to a lis=
t size of 440 members on a P=
rofessional Shared Web Hosting plan, which comes with 500 emails per ho=
ur.
Precautions:
Why does GlowHost rate-throttle outbound email?
The reason for the throttles is to provide the most reliable email hosting=
experience for ALL customers that share the mail server. It helps us to pr=
event mailserver blacklistings when a spammer makes his way onto a shared s=
erver.
We never know who is going to sign up for a hosting account and attempt to=
send spam from a server. We never will know when a long time and trusted c=
ustomer is going to decide that one day they are going to test out their "m=
arketing skills" and initiate a mailing campaign to a 50,000 email address =
list that they bought on ebay for $9.95.
Email throttles help everyone to negate the blacklistings that many long-t=
ime web site operators are familiar with, especially those coming from barg=
ain basement hosts that have no limit email hosting where server performanc=
e suffers drastically our outbound email is unreliable or bouncing back due=
to blacklistings. Though our system is not 100% effective in preventing bl=
acklistings, we do minimize them drastically for our users using these meth=
ods.
About Blacklistings:
All web hosts including major players like yahoo end up on these spam blac=
klists.
Blacklistings occur when a certain quantity of email has been reported t=
o third party RBLs (Remote Block List) like Spamcop. These RBLs will add re=
ported mailservers to it's internal block lists.
Subscribers to these RBLs include major ISP like AOL, Comcast and even sma=
ller ISP like GlowHost subscribe to RBLs. When these Internet Service Provi=
ders receive mail from a mailserver that is on one of their (subscribed) RB=
Ls, it is immediately returned to sender, rendering the email undeliverable=
.
Basically, an ISP subscribing to an RBL means penalize every web site that=
uses a particular mailserver host, because one unscrupulous spammer, and s=
ometimes even an unknowing newbie, ruins it for the whole bunch. Ever heard=
of "sour grapes?"
Blacklistings can last 24 hours and even longer for repeat offenders. Gene=
rally web hosts have little or no control over being removed from these RBL=
s with the exception of a few RBL providers that allow automatic "de-listin=
g."
However if a host removes themselves, and the spam complaints continue to =
roll in, the black listing is re-initiated, this time with a longer wait fo=
r de-listing, and that can go on indefinitely based on how bad the problem =
is with a particular mail server.