Paul J. Smith wrote:
> Our spamassassin is taking around 30 seconds per message, way too
> long. I'm trying to find out how to enable some timing logging so I
> can see exactley what tests are taking the time. I read about
> 'timelog_path'm, which seems to be exactley what I was looking for,
> however, it's been removed apparently in one of the v2 versions :(
>
> Can anyone tell me how to enable some timing logging so I can see
> exactley what tests are taking what times?
>
> Currently running 3.2.4 / linux / spamd
Curious:
...
Mar 10 13:52:34 filtermail spamd[6101]: spamd: identified spam
(13.8/5.0) for <username>:1066 in 6.0 seconds, 2752 bytes.
...
Mar 10 13:52:34 filtermail spamd[9695]: spamd: clean message (2.7/5.0)
for <username>:1158 in 3.7 seconds, 21418 bytes.
...
CentOS4, SA 3.2.4 installed from RPMForge - no special tweaks I'm aware
of in their packaging that would affect this.
By default, spamd logs to the MAIL facility - have you changed this and
then accidentally discarded the destination?
Are you sure your SA calls are going through spamd? Other integration
methods won't give you times like this - another system I maintain calls
the SA Perl library via MIMEDefang and doesn't show scan times in its
log because I haven't added any code/configuration to do so.
-kgd
