Considering that spam accounts for the bulk of all client connections to
an MX these days, it might be beneficial if we had log data showing
total time per session, not just for queued mail, so an OP can see how
long it's taking to reject at the smtpd stage, as well as time elapsed
when rejecting messages at cleanup with header/body checks, or with a
pre-queue content filter, etc.

If a server accepts 10k smtpd connections a day and rejects 9k via
smtpd_*_restrictions, 400 via a pre-queue content filter, and 100 via
header checks, etc, it would seem that the amount of processing time
required for the remaining 500 legitimate emails is less relevant in the
absence of time metrics for the 95% of the mail rejected as spam.  If
we're using delays=a/b/c/d for troubleshooting that's fine.  But if
we're expecting to be tuning a server for performance based on log
metric data we need time data for our rejected messages as well.

The main reason I ask is that my filters are constantly becoming more
complex and the hardware remains the same.  I'd like to be able to see
how much additional load I'm adding to my system with the constant
addition of new filters.

Any chance this is on the agenda?  Or does this type of log data already
exist, and I'm simply too blind to find it?


Thanks.

-- 
Stan

Reply via email to