This issue occurs due to a PureMessage Spam Rules update failure and relates to the credentials in use by the update
↧