Ben Wylie wrote:
Can a trustpath be discontinuous?
Here are the relays of a recent email:
debug: received-header: relay 127.0.0.1 trusted? yes internal? yes
debug: received-header: relay 127.0.0.1 trusted? yes internal? yes
debug: received-header: relay 212.250.162.15 trusted? no internal? no
debug: received-header: relay 212.250.162.8 trusted? no internal? no
debug: received-header: relay 81.104.195.141 trusted? no internal? no
debug: received-header: relay 127.0.0.1 trusted? no internal? no
debug: received-header: relay 80.41.122.64 trusted? no internal? No
In fact all of the ips in that list are trusted and are specified in
trusted_networks, apart from 212.250.162.15 and 80.41.122.64.
Is there a reason why they are not marked as trusted?
Who's to say I didn't send you an email with the first (bottom most) 5
headers forged as your trusted hosts.
SpamAssassin only trusts the headers it can trust. :)
I am also having an issue with syncing happening when I haven't told it to.
I have
bayes_auto_expire 0
in my local.cf, but I still get this issue:
debug: bayes: found bayes db version 3
debug: bayes: opportunistic call found journal sync due
debug: Syncing Bayes and expiring old tokens...
If I remember correctly that last debug: is generic... it's used for
both expires and syncs. In this case a sync.
debug: lock: 3328 trying to get lock on F:/DOCUME~1/ADMINI~1/SPAMAS~1/bayes
with 0 retries
debug: lock: 3328 link to F:/DOCUME~1/ADMINI~1/SPAMAS~1/bayes.lock: sysopen
ok
debug: bayes: 3328 tie-ing to DB file R/W
F:/DOCUME~1/ADMINI~1/SPAMAS~1/bayes_toks
debug: bayes: 3328 tie-ing to DB file R/W
F:/DOCUME~1/ADMINI~1/SPAMAS~1/bayes_seen
debug: bayes: found bayes db version 3
debug: refresh: 3328 refresh F:/DOCUME~1/ADMINI~1/SPAMAS~1/bayes.lock
debug: synced Bayes databases from journal in 113 seconds: 14988 unique
entries (14988 total entries)
debug: Syncing complete.
Yeah, database sync... not an expire.
DB File requires journal syncs since the database is updated by
autolearning or bayes token atime updates.
If your load is great enough that this is causing you issues, you may
want to consider moving to an SQL backend.
I can't find anything about a configuration option or a command line option
that will let me stop SA from automatically syncing the bayes tokens.
You can't. Even if you don't autolearn tokens, token atimes still need
to be update for bayes to function. Syncing the journal with the
database is necessary for database backends such as DB File.
Is there anything?
Use SQL.
Daryl
