Hi,

I'm wondering if anyone sees any flaws with my idea, i'd like to run a
policy server to trac traffic usage in postfix, with 2.2 it seems it
sends the size of the message, thus i can track size, as well as any
other information to the policy server. What i'd like to know is if
this'd be feasable, tracking via policy server that is.

Comments?
Patrick

Patrick wrote:
> Hi,
>
> I'm wondering if anyone sees any flaws with my idea, i'd like to run a
> policy server to trac traffic usage in postfix, with 2.2 it seems it
> sends the size of the message, thus i can track size, as well as any
> other information to the policy server. What i'd like to know is if
> this'd be feasable, tracking via policy server that is.
>
> Comments?
> Patrick

My initial thought is: Why? Much of the same data (size) is recorded in the
Postfix syslog file, and can be fished out with pflogsumm and other programs.

Also, using the policy daemon hook adds a level of complexity and a new
point of failure to the actual mail delivery process.

But I can see where if you are an analytical type of person how this could
be fun to stuff entries into a database, and run reports on it.

Your question was if it would be feasible; feasible meaning able to be carried
out successfully; yes sure it could be done. I dunno how useful it would be, but
it should keep you out of the bars for a while. :-)

--
Greg

the only thing is, every time a message comes into the system, and
every time it goes to queue, as well as in and out of the content
filter, it gets a size attribute, and there's no easy way to see what's
mail in, if you read the pflogsumm readme, they actually mention that
there's no way to exclude mail that's in from the content filter... (
that's why mail's counted twice on the content filter path )

Thus the policyd would fix that.

P