I think the last time this happened had something to do with the received
headers in the message, if I recall correctly.  There was a fix for an
instance of this fairly recently, but I don't recall the details. The fix
may have been in the 3.1 stream.

Thank you.

I have 3.0.4 here and no particularly convenient way to look at 3.1. If 3.1 does contain the fix would someone be able to post or send the relevant lines of the rules? I'd love to incorporate them in the local config here.

cheers

rolf.


Reply via email to