Hi,
When testing greylisting with synchronizing we noticed the following

strange behavior:

Machine A (10.100.64.234) is the machine we receive mail through.

Machine B (10.100.64.233) is synced through spamd
Check out the expire value on machine A after the state have gone from

Grey to White!

It has taken the default 36 days ahead instead of our 2 hour (testvalue)

from spamd_flags!!

But Machine B (the passive "brother" which gets synced through

spamd-sync) behaves as it should!?
spamdb (A):

WHITE|10.100.64.199|||1193231843|1193232057|1196342528|3|1
spamdb (B):

WHITE|10.100.64.199|||1193231843|1193232057|1193239279|3|1
pf.conf:
no rdr inet proto tcp from  to any port smtp

rdr pass inet proto tcp from ! to $ext_if:0 port smtp ->

127.0.0.1 port spamd

pass in quick log on $ext_if proto tcp from any to ($ext_if) port

$public_tcp

pass in log on $int_if proto tcp from  to ($int_if) port $sec_tcp
/etc/rc.conf.local (B)
pf=YES

syslogd_flags="-a /var/spool/postfix/dev/log"

spamd_flags="-y fxp0 -Y 10.100.64.234 -G 3:1:2"

spamlogd_flags="-i fxp0 -Y 10.100.64.234"
/etc/rc.conf.local (A)
pf=YES

syslogd_flags="-a /var/spool/postfix/dev/log"

spamd_flags="-y fxp0 -Y 10.100.64.233 -G 3:1:2"

spamlogd_flags="-i fxp0 -Y 10.100.64.233"
---

Probably some small "feature" to fix....
Regards

Claes Strvm