<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
A google for "apache 2.0 bandwidth" turned up <A HREF="http://www.topology.org/src/bwshare/README.html">http://www.topology.org/src/bwshare/README.html</A> as the first hit.<BR>
<BR>
You also want to spend sometime understanding apache's server settings and performance tuning (there is lots of stuff on this at the apache site), and possibly the IMAP server's as well. If you need tighter controls still, I'd look into traffic shaping tools at the firewall level.<BR>
<BR>
I think it would be overkill for webmail, but another long term option is splitting the site into separate servers, so images and static content are served from one server while the app resides on another server which more horsepower behind it. This will also allow separate traffic controls to dynamic and static content, so image requests don't get queue behind application processing.<BR>
<BR>
Mike<BR>
<BR>
On Thu, 2004-05-13 at 15:51, SAiello@Jentoo.com wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#0000ff"><I>Seems mod_throttle and mod_bandwidth are based on apache 1.3.x</I></FONT></PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>