Here is the fix for a known issue with SM 15.5.6222 and external Message Sniffer command line scanning

Question asked by - 2/22/2017 at 1:43 PM

Unanswered

Hi everyone. I wanted to share something that one of our customers discovered while using the external Message Sniffer as a command line scanner in SM 15.5.6222. Prior to upgrading to 15.5.6222, my customer was running SM 15.3.6109 and the external Message Sniffer command line scanning option without issue. Once he upgraded to SM 15.5.6222, he noticed that there were no Sniffer headers in any of the email that he was receiving. After general troubleshooting, I submitted a ticket to SM support and they helped to resolve it by providing me with a new SM build. If you are experiencing this issue, please contact me and I will provide the link to the new build. I tried to post it here, but I received an error which said my forum account does not have permission to use hyperlinks in posts. Perhaps someone from SM support will see this and post the link for me.

Please note that this only affects people using the external Message Sniffer from Arm Research and only if they are using it with SmarterMail as a command line scanner. If you guys have any questions, please feel free to ask. Thanks!

6 Replies

Reply to Thread

David Fisher Replied

2/23/2017 at 8:59 AM

Hi Linda,

Thanks for this post, do you have the exact version and build? If so we can just download it knowing that, as the custom build urls are the same.

Example: SmarterMail 15.5.6222.23822 is the latest released version.

Thanks!
-dave

Matt Petty Replied

2/24/2017 at 8:36 AM

Employee Post

David,

15.5.6249.24396 should be the one.

Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com

David Fisher Replied

2/28/2017 at 10:00 AM

Hi Matt & Linda,

Ever since installing this custom build, I noticed the Content Filtering that we setup under Filtering -> Content Filtering, doesn't work right anymore.

I have had them setup for years, and since installing this custom build, the rules are not working, or at least some of them. The one that is not working is one I have matching the To field, move to a folder, it now shows up in my Inbox. I have two users that are complaining about this not working now.

Is there a newer custom build that possible fixes this?

Thank You,

-dave

User Replied

3/1/2017 at 2:19 PM

Thanks Matt. For some reason I was not notified via email that someone responded to this post. I was just looking in the forums and happened to see this. I apologize for not responding, Dave.

David Fisher Replied

3/1/2017 at 3:07 PM

Hi,

Just as an update, it seems this breaks a particular Content Filter, on the To Field, if it is not to you, possible it doesn't work, sometimes the To Field might be an alias or another server that forwards email to you. I have one match that isn't working when the To and From fields are the same.

Probably just going to downgrade for now, and hopefully more testing will be done before this is released publicly.

-dave

User Replied

3/2/2017 at 8:32 AM

Thanks for the update Dave. I haven't heard that report from any of my customers, but I'm guessing most of them don't use the Content Filtering in SM. I'm hoping Matt will chime in with a fix for you.

Back to Community Threads

Please leave this box unchecked

6 Replies

Reply to Thread

Tags

Related Knowledge Base Articles