Tickets can be detected as spam for various reasons, leading to their suspension. This can happen if the requester was previously marked as spam, or if the content of the ticket is flagged by Zendesk's spam filter, Cloudmark, due to suspicious characteristics. To resolve this, you may need to unsuspend the user or adjust your email practices to avoid triggering the spam filter. For more details, check out the originalZendesk article.
There are two main types of tickets that can be marked as 'Detected as Spam': those where the requester has been suspended, and those flagged by the spam filter due to suspicious content. If an agent marks a ticket as spam, it can suspend the…
Zendesk uses a spam filter service called Cloudmark to detect spam in tickets. While Zendesk doesn't have direct insight into Cloudmark's algorithms, they receive encoded 'fingerprints' to help analyze suspensions. Agents can recover emails from…
Common reasons for email suspensions include users marking emails as spam, domain blocks, shared hosting IP issues, and suspicious email content. Other factors include poorly formatted HTML, unapproved words, and bulk emails using BCC. Ensuring…
To recover a ticket marked as spam, agents and admins can retrieve it from the suspended queue. This action sends a coded message to Cloudmark, indicating the email is legitimate. Over time, this feedback can help reduce false positives and improve…
Legitimate emails might be flagged as spam due to Cloudmark's stricter spam detection compared to services like Gmail. Factors such as email content, sender reputation, and previous spam markings can contribute to false positives. Regularly…
To prevent emails from being marked as spam, use a dedicated support address, ensure proper email formatting, and avoid using spammy words or practices. Regularly review suspended tickets and recover legitimate ones to help train the spam filter….