June 17, 2013 — We recently discovered a scenario that, while rare, may cause a user to not receive a digest message.  Two conditions must be met for this to occur.  First, the customer must have configured our service to suppress empty digests.  Second, during the interval covered by a given digest message, all spam messages detected for that user must be considered egregious. (Egregious spam messages are the highest scoring spam messages, and are classified in the digest messages as ‘definite’ rather than ‘probable’ spam).  In those circumstances, our service at present may simply suppress the digest message, whereas logically, the digest should be delivered even though it contains only the ‘definite’ spam messages.

To address this, we have updated the logic for the digest generation process, and will be deploying these changes on Wednesday evening Pacific time.

Thank you for your attention.