[Mailman-Users] Can one use EC2 for bandwidth spikes?
brian at emwd.com
Thu Nov 8 04:53:13 CET 2007
Actually we charge $4 a month hosting for a list of your size. You can check
out our hosting plan that is designed specifically for mailman users at
http://www.emwd.com/mailman.html. We also do not impose any sort of sending
limits on our mailman clients. We have been doing this for years now.
EMWD - Executive Officer
From: mailman-users-bounces+brian=emwd.com at python.org
[mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of John
Sent: Wednesday, November 07, 2007 8:51 PM
To: Mailman Users
Subject: Re: [Mailman-Users] Can one use EC2 for bandwidth spikes?
On 11/4/07 12:29 PM, "Chuck Peters" <cp at ccil.org> wrote:
> We have a newsletter with 1500+ subscribers which is currently hosted on
> friends house. He has DSL and the connection goes to crap for 5-15
> every time we send one out, other than that it works fine. When I looked
> some of the low cost hosting options none of them seem to be good because
> various limitations like 500 messages per hour. We send out 1 or 2
> newsletters a week at most so it has been hard to justify spending the
> $40-$100 or more a month for better hosting.
> I have been wanting to try out Amazon's Elastic Compute Cloud,
> http://aws.amazon.com/ec2, and I think it would be really cool to fire up
> the EC2 instance (basically a linux server) for an hour and fire off the
> Has anyone done this sort of thing?
> I doubt it could it be as simple as making a temporary exim smarthost with
> some configuration tweaks.
> What is required to make this work properly?
Brad points out disk performance issues and others.
In addition, each time you fire up your EC2 server, it gets a dynamically
assigned IP which is virtually certain to differ from the last time. And
that includes restarts after crashes (but of course they don't crash).
So you have to deal with the usual problems of running mail servers on
dynamic IPs. Both incoming and outgoing servers in this case...the incoming
problem can be solved by routing through the home server--that leaves the
list members who won't get their copies because the mail comes from a
dynamic pool space--but the list may already have that problem.
So nice as the idea sounds, it likely isn't practical.
Unfortunately, I can't help with specific configurations.
Mailman-Users mailing list
Mailman-Users at python.org
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
More information about the Mailman-Users