This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PureMessage Quarantine Digest

One of our customers has a problem with the quarantine digest of PureMessage. When I open the PureMessage console and go to the Quarantine I can see that there are a few quarantined messages for a certain user. But the user does not receive a quarantine digest e-mail (and this is configured at 08:00 and 16:00) and when the user goes to http://servername:8081/ it says that the Quarantine is empty. I tried to manualy trigger by using the command "firejob.exe 2" but with no results. The PureMessage version used is PureMessage for Exchange v3.1.2.0 and it is installed on a Microsoft SBS 2011 (Exchange 2010) server.

:28323


This thread was automatically locked due to age.
Parents
  • Hi,

    Within PureMessage for Exchange, the quarantine that's visible through the end user website (along with the digest email) will only show messages that were detected as Suspected Spam. Emails quarantined for other reasons -- including viruses, restricted attachments, blocked phrases, etc. -- will only be visible through the PureMessage console, so no digest will be sent out and these messages won't be seen over port 8081. When viewing the quarantine through the console, the reason for the quarantine is listed there, so you can confirm why a message was quarantined.

    The reason behind only showing suspected spam is based around the greater possibility of false positives, so if an email was expected but matched enough criteria to raise its spam score, then the enduser can take a look in part of the quarantine to see what's there. The logic behind keeping the other policy rule hits away deals with matters of preventing the release of infected email, maintaining the organization's policy on acceptable attachments and filtered phrases.

    Now, if there are suspected spam messages for that user that should be visible through either the digest or the website, then it's possible that there may be something else at play here. Let us know if this is the case; at this point, it may be worthwhile to open a call with one of our support engineers since this may require some deeper investigation into your environment.

    :28353
Reply
  • Hi,

    Within PureMessage for Exchange, the quarantine that's visible through the end user website (along with the digest email) will only show messages that were detected as Suspected Spam. Emails quarantined for other reasons -- including viruses, restricted attachments, blocked phrases, etc. -- will only be visible through the PureMessage console, so no digest will be sent out and these messages won't be seen over port 8081. When viewing the quarantine through the console, the reason for the quarantine is listed there, so you can confirm why a message was quarantined.

    The reason behind only showing suspected spam is based around the greater possibility of false positives, so if an email was expected but matched enough criteria to raise its spam score, then the enduser can take a look in part of the quarantine to see what's there. The logic behind keeping the other policy rule hits away deals with matters of preventing the release of infected email, maintaining the organization's policy on acceptable attachments and filtered phrases.

    Now, if there are suspected spam messages for that user that should be visible through either the digest or the website, then it's possible that there may be something else at play here. Let us know if this is the case; at this point, it may be worthwhile to open a call with one of our support engineers since this may require some deeper investigation into your environment.

    :28353
Children
No Data