https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7191
Bug ID: 7191
Summary: TxRep uses username from another user
Product: Spamassassin
Version: 3.4.1
Hardware: PC
OS: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: Plugins
Assignee: [email protected]
Reporter: [email protected]
spamd is called with the username set. The username recorded in the txrep data
is sometimes the username of the previous email checked.
The username in the bayes data is correct showing that spamd has been given the
correct username.
I inspect the with:
SELECT DISTINCT username, atime FROM bayes_token JOIN bayes_vars ON
bayes_token.id = bayes_vars.id WHERE atime > (SELECT MAX(atime) - 3600 FROM
bayes_token) ORDER BY atime;
SELECT DISTINCT username, CAST (extract (epoch from last_hit) AS INTEGER) -
3600 AS last_hit FROM txrep WHERE last_hit > (now() - INTERVAL '1 hour') ORDER
BY last_hit;
These should give the same usernames for bayes and txrep but sometimes the user
is that of the email before. The dates are slightly offset as the bayes and
txrep actions are not coincident (the extra 3600 is I guess a timezone offset).
Not all checks result in bayes learn so some lines are in txrep only.
Alternatively I can check the receipt mail log and compare with the txrep data.
This assumes the username given to spamd is correct, (the bayes user name
recorded says it is).
SELECT DISTINCT username, last_hit FROM txrep WHERE last_hit > (now() -
INTERVAL '1 hour') ORDER BY last_hit;
The emails in question have single recipients and are from different senders so
no ambiguity nor overlap of usernames.
--
You are receiving this mail because:
You are the assignee for the bug.
