mailman list server?
So, those services which provide listservers at $4/mo/list aren't a good fit due to having a couple hundred tiny lists - those would be extremely expensive to maintain, considering what they are. Google apps is also not an option, because even if we registered for a business account we'd still be limited to 2k emails per day per account - which means we wouldn't be able to send our club-wide emails.
So the question then is - is Linode friendly to clubs who have membership lists that are very active? In a world that is filled with spam and anti-spam, is Linode still a good fit for making a server that is sending and receiving lots of mail, none of it spam?
The lists are all legit - it's a gaming club. Some of them are "IC" (in character) lists. most are "OOC" (out of character) lists. People discuss rules, games, etc on the OOC lists. People make IC posts on the IC lists. It's a lot of traffic, but all of it is real, legit traffic. Part of the reason there are hundreds of tiny lists is because most of those are very topic-focused, going to specific small OOC or IC audiences. It's oddly a very hard thing to find hosting for…which, at the moment, we're suddenly needing to do.
Google apps, also sends emails, so again they can control how many you send.
Linode gives you a server, you install the mail server and control it so you set the limits (or no limits).
The only time Linode would care about the e-mails you're sending would be if they got abuse reports from folks complaining about spam.
I would have to assume that linode does some sort of rate limiting, otherwise they'd be too attractive to spammers as a haven, which would then get their IP block blacklisted - and then it would be worthless to legit groups who want to send out emails. Thus I'm just curious what that rate limiting would be, or if there's a way to apply for limit increases, etc.
You cause trouble and they take it away from you - that's really the only limitation you will face.
By default, there is an outbound rate limit of ~50 Mb/sec, mostly to prevent runaway/rogue systems from causing too much damage. At, say, 5 kilobytes per email, that is effectively a rate limit of 1250 emails per second. Also, with a transfer quota of 200 GB/month, you'll start to run into overage fees after ~40,000,000 of these 5 kilobyte hypothetical emails.
Similar mathematics would apply to 5 kilobyte objects via HTTP, 5 kilobyte Usenet articles, 5 kilobytes of pure, uncut Colombian coffee, etc.
Why not rate limit SMTP traffic? If a spam run were to generate abuse complaints at a rate of 0.001%, and were sending out at full speed, a spammer on a Linode should expect to last 40 seconds before an abuse ticket is opened. A spammer using Google Apps at 2,000 e-mails per day should expect to last 25 days. Rate limiting hides the problem; not rate limiting makes it show up very quickly.
(Note: The math in this speculation, or at least the assumptions, may be dubious. But the point probably isn't.)
This requires that
pure, uncut Colombian coffee
I recommended she not leave it out on the seat in case she gets pulled over.
But yeah - the raw volume isn't really that much, since the overwhelming majority of it is just…text.