Συντάκτης: John McMurray Ημερομηνία: Προς: exim-users Αντικείμενο: [exim] ratelimit database not available
Hi everyone,
Firstly, thank you for always helping out!
I'm setting up a new hosting server on Centos 7. I've installed exim
4.90 from source and am now testing it. Mail is not reaching the server
and the logs complain about the ratelimit database not being available.
If I install exim 4.89 from the yum repos it does work, but without SPF
which is why I want to install via source....
I ran a fake transaction with exim -bh x.x.x.x and got the following:
>>> check ratelimit = ${lookup mysql { SELECT option_value FROM
email_options WHERE option_name = 'max_per_hour' AND deleted = 0 AND
extra1 = '$sender_address_domain' AND deleted = 0 UNION SELECT
IFNULL(MIN(option_value), 300) FROM email_options WHERE option_name =
'max_per_hour' AND deleted = 0 AND extra1 IS NULL AND NOT EXISTS
(SELECT option_value FROM email_options WHERE option_name =
'max_per_hour' AND extra1 = '$sender_address_domain' AND
deleted = 0) LIMIT 1; }} / 1h / per_rcpt / $sender_address_domain
>>> = 300 / 1h / per_rcpt / softsmart.co.za
>>> ratelimit condition count=1 300.0/1h/per_rcpt/softsmart.co.za
BDB1566 DB_ENV->rep_flush interface requires an environment
configured for the replication subsystem
BDB1566 DB_ENV->log_cursor interface requires an environment
configured for the logging subsystem
BDB1566 DB_ENV->rep_flush interface requires an environment
configured for the replication subsystem
BDB1566 DB_ENV->log_cursor interface requires an environment
configured for the logging subsystem
>>> ratelimit database not available
>>> deny: condition test deferred in ACL "acl_check_rcpt"
451 Temporary local problem - please try later
LOG: 798 [8074] H=(softsmart.co.za) [192.168.11.22]
F=<john@???> temporarily rejected RCPT
john@???: ratelimit database not available
I use the same config file for both 4.89 and 4.90...
I'm not sure if I'm missing something in my build process / make file?
I've googled this and there are dozens of sites all saying to clear the
/var/spool/db directory which I've done but that didn't work.
It does oddly create a ratelimit.lock file but not the ratelimit file
itself...