the real question, imho, is what you want to measure. and what you want
to bill for.
when someone sends a message to one of your customers, that message is x
bytes. when your customer sends a message to an external server, that's
if your customer uses pop to download messages to a client, he (she)
downloads n bytes in that download.
if they use surgeweb, they transfer z bytes during a session, which of
course, includes the web pages.
if they use imap at all, then disk utilization may be a billable
resource - i had one customer who accumulated over 5G of messages and
never realized they needed to prune things once in a while. i wonder how
long it took to load their inbox....
bytes of thruput can be converted to bandwidth - i BELIEVE 221Gb of
transfer in one month is equivalent to 1Mb/sec.
i frankly don't know where or whether this info is available in the
myriad of logs. but, if it is, it is certainly possible to extract it
with some neat grepping and perl scripting.
we do this on our shared web servers for customers with heavy ftp
traffic. on the first of the month, we look at the ftp transfer logs for
the previous month and accumulate transferred bytes (in and out) by
user. we can then bill based on total transfer. we even keep history in
a little mysql database.
advanced web systems
On 3/8/2011 5:00 PM, VinnyHIDDEN@@Dell.com wrote:
> I don't, but if you had each domain on a different IP address, you could easily turn on ip accounting on a Cisco device and measure it via SNMP... or just via the Cisco CLI.
> -----Original Message-----
> From: Tony Zakula [mailtoHIDDEN@firstname.lastname@example.org]
> Sent: Tuesday, March 08, 2011 3:57 PM
> To: surgemailHIDDEN@etwinsite.com
> Subject: [SurgeMail List] Bandwidth Accounting
> Does anyone do bandwidth accounting for their email services?
> Especially if you are running lots of domains on one mail server and web services on other servers? If so, what do you use to measure per customer?
> Tony Z