While testing Fluffy on my desktop, I'm regularly seeing
the above error in the detailed (7/6) debug log. It
doesn't seem to be causing any problems, but I thought
I'd let you know. I've attached an extract of the log
window (in technicolor).
I realise I should be adding 127.0.0.1 but I removed it for
testing purposes. I was testing Fluffy by sending emails from
the same system Fluffy runs on.
I have now added 127.0.0.1 again and I'm sending test
messages from another system, which happens to be in the
same LAN, but it's not in Fluffy's "Local Network". I have
added a special DNSBL (bogons.cymru.com) to block
192.168.0.2 (the IP of my test client). Now, if I start Fluffy, it
does one correct lookup (and block), but every next lookup
seems to fail and therefore the connection is not blocked,
although it's supposed to.
I just found out that this behaviour is apparently related to
the Expiry setting. When I set "DNSBL/Sapmtrap Expiry to 0
hours" (which I did for testing), that's when this error comes
up. I have now changed it to 1 hour and that seems to fix the
problem (after restarting Fluffy).
I have attached an extract of the log. In here, you can see
another strange side effect of the Expiry=0 setting: after
Fluffy finishes validating for the first time, it seems to "hang"
for 30 seconds before closing the connection.
I hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
error
Logged In: YES
user_id=660239
You really really really ought to make 127.0.0.1 as part of
your local network. Don't you think?
The local network tab has a button for automatically
assigning the correct settings.
Logged In: YES
user_id=898950
I realise I should be adding 127.0.0.1 but I removed it for
testing purposes. I was testing Fluffy by sending emails from
the same system Fluffy runs on.
I have now added 127.0.0.1 again and I'm sending test
messages from another system, which happens to be in the
same LAN, but it's not in Fluffy's "Local Network". I have
added a special DNSBL (bogons.cymru.com) to block
192.168.0.2 (the IP of my test client). Now, if I start Fluffy, it
does one correct lookup (and block), but every next lookup
seems to fail and therefore the connection is not blocked,
although it's supposed to.
I just found out that this behaviour is apparently related to
the Expiry setting. When I set "DNSBL/Sapmtrap Expiry to 0
hours" (which I did for testing), that's when this error comes
up. I have now changed it to 1 hour and that seems to fix the
problem (after restarting Fluffy).
I have attached an extract of the log. In here, you can see
another strange side effect of the Expiry=0 setting: after
Fluffy finishes validating for the first time, it seems to "hang"
for 30 seconds before closing the connection.
I hope this helps.
Stuck Log