Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 7095 views
  • Users 0 members are here
Options
Suggested
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

Outbound spam reports from users within organization

PeterPokorny

Not sure if I am missing something, but currently, we are having an issue with some messages getting spammed when heading outbound. This can be due to attachments, RFC2183 violations, etc... 

The issue we have is there is no reporting to the user that the message was spammed - it takes an administrator looking at the recent messages to know, which depending on the day, might not happen. This simply can't happen with some time sensitive stuff, where the user assumes it made it to the destination. 

Is there a setting I am missing, or maybe make it a feature request, where the user can have outbound messages either quarantined like inbound messages are, or at least send a report back to the user that the message couldn't be sent due to X/Y/Z reason?



This thread was automatically locked due to age.
Parents
  • 0

    Second this.

     

    We have run into this. Especially with important / time sensitive emails being silently discarded as Spam due to not meeting the RFC2183 standard setting in Reflexion. This is really bad for companies, as you stated most can't or don't monitor outgoing reports 24/7 for these emails which are fairly frequent especially in an Exchange / Outlook environment.

    • As suggested either add them to a Quarantine Report for Outbound emails.

     

    • Or add a setting in Attachment Filtering > Advanced Features  for a separate Inbound / Outbound option for the setting ("Block all messages with attachments that do not meet RFC2183 standards) so it can be disabled on its own (Outbound).

     

    • Or allow more granular control of Attachment Filtering which would allow companies allow/deny filetypes by extension/MIME on their now like MXLogic / McAfee has. In turn a company could allow winmail.dat files or all .dat files to get by this check on Reflexions end for incoming and/or outgoing emails that contain the RFC2183 standard.

    Also of not maybe the Topic author Peter could change this thread title to add FEATURE REQUEST to the beginning like similar topics in the forum.

     

     

     

Reply
  • 0

    Second this.

     

    We have run into this. Especially with important / time sensitive emails being silently discarded as Spam due to not meeting the RFC2183 standard setting in Reflexion. This is really bad for companies, as you stated most can't or don't monitor outgoing reports 24/7 for these emails which are fairly frequent especially in an Exchange / Outlook environment.

    • As suggested either add them to a Quarantine Report for Outbound emails.

     

    • Or add a setting in Attachment Filtering > Advanced Features  for a separate Inbound / Outbound option for the setting ("Block all messages with attachments that do not meet RFC2183 standards) so it can be disabled on its own (Outbound).

     

    • Or allow more granular control of Attachment Filtering which would allow companies allow/deny filetypes by extension/MIME on their now like MXLogic / McAfee has. In turn a company could allow winmail.dat files or all .dat files to get by this check on Reflexions end for incoming and/or outgoing emails that contain the RFC2183 standard.

    Also of not maybe the Topic author Peter could change this thread title to add FEATURE REQUEST to the beginning like similar topics in the forum.

     

     

     

Children
No Data
Unfiltered HTML