I have captured a bad message. It seems innocuous; it's from me at a host in my domain, to me, basically
From: g...@foo.lexort.com
To: g...@lexort.com
and has a body "foo", no DKIM headers, just Received, Subject,
Message-Id.
Processing this with my normal config results in the timeout.
I noticed lockfiles for txrep, even though I couldn't figure out that
txrep was involved from' -D all', and turned off txrep in my config
("use_txrep 0" instead of 1). Then, the message processes in 2s.
When I had txrep enabled, I saw a tx-reputation.lock with a single line
that was a pid of the spamd child process that was accumulating CPU
time. I also had files like:
tx-reputation.lock.bar.lexort.com.5023
where that was another pid, and this second file seemed to be
accumulating lines.
I did find a stray sa-learn from October and killed it.
Running my spam learning script, which just calls sa-learn with --spam
or --ham (and -L always) is turning out slow, probably from the same thing.
So it sort of smells like one of
- something is wrong with my txrep database
- some code is hitting O(n^k) or something
- there is some strange locking/spinning behavior
- something else I don't understand, as always
Does anyone have pointers to a database export/import script for txrep?
signature.asc
Description: PGP signature
