Re: [toaster] log files for each domain

Tue, 21 Feb 2006 04:16:56 -0800

I'll be releasing it at some point via the GPL. There are some fundamental things I need to do, but the overall task of calculating per-domain data is pretty much accomplished. The rest relates to being able to look at the data and interface. 


Thanks;

Michael Bagnall
ElusiveMind

On Feb 21, 2006, at 6:12 AM, Seferovic Edvin wrote:

Hi Michael,

 

yes ! you are right, I would like to analyse the usage of my mail server for a few domains hosted on them. ( traffic reporting is less interesting for me ).

 

So you have written your own script – are you planning to publish it under GPL or are you trying to keep it to your self?

 

I personally do not belive that such logging is possible, but I hoped someone has a trick for doing such pseudo-logging ! I accept all ideas or scripts for testing purposes J

 

Regards,

 

Edvin

 

From: ElusiveMind [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 21. Februar 2006 12:53
To: toaster@shupp.org
Subject: Re: [toaster] log files for each domain

 

Hey Edvin;

 

I assume you are wanting this for some kind of usage analysis or traffic reporting functionality (correct me if I am wrong).

 

While I do not believe that qmail or vpopmail support this, I have written some software which will analyze existing log files and report on bandwidth used as well as total # of messages. I do not have it perfected yet and I'm still working on it, but I'm about 85% of the way toward something I think will be useful. Furthermore I also have a related script which will report on mailing list traffic (# of messages sent and bandwidth, etc). 

 

Thanks;

 

Michael Bagnall

ElusiveMind

 

On Feb 21, 2006, at 3:59 AM, Seferovic Edvin wrote:



Hello Bill, Hello list members :D

 

I’ve been using this toaster for quite a long time now. But now I have an extra wish :) Is it possible to have separate log files for each domain ? If so – where can I find any documentation about setting it up?

 

Thank you in advance !

 

Regards,

 

Edvin

 

 

 



 



Reply via email to