re selinux:
Yes, once I discovered the fix, I considered that could have been the casue. 
FWIW I'm not using it and it's disabled, so it *shouldn't* hose anything. 
But I would not be surprised if it were the culprit.

View this message in context:
Sent from the SpamAssassin - Users mailing list archive at

Reply via email to