Miscellaneous Build 6985 Issues
Problem reported by Scarab - February 21 at 2:20 PM
Submitted
We have thus far encountered the following minor issues to the most recent build of SmarterMail 6985:

  1. Inability to override Spam Filter actions. Whether logged in as a user or impersonating a user as an Admin the toggle for SETTINGS > SPAM FILTERING > OVERRIDE SPAM FILTER OPTIONS will not work, neither can you modify actions for any probability level. This also occurs in DOMAIN SETTINGS > SPAM FILTERING, as those actions also cannot be overriden. The domain setting "Users can override domain actions" is confirmed to be "Enabled". Through trial-and-error we discovered that toggling the DOMAIIN SETTINGS > SPAM FILTERING > OVERRIDE ACTIONS FOR THIS DOMAIN will allow users to once again toggle their "Override spam filtering options" again. Looks like the action for what line to modify in the settings.json file for "Users can override domain actions" got swapped with "Override actions for this domain".

  2. System Admins and Domain Admins do not have access to the 2-Step Authentication card in a User's Settings, despite DOMAIN SETTINGS > GENERAL > 2-STEP AUTHENTICATION being set to "Enabled". In light of the first error noted we even tried toggling MANAGE > DOMAIN > SHOW PASSWORDS TO DOMAIN ADMINS but still no 2-Step Authentication options appear to System Admins or Domain Admins. It is only visible if you logout of SmarterMail as an Admin and login as the user.

  3. All SETTINGS pages intermittently give a warning prompt "Are you sure you want to exit without saving changes?" when no changes have been made. Cannot reproduce 100% of the time but it happens the majority of the time throughout the day as a SM Administrator. (We are frequently impersonating one user after the next...we'll see if we can isolate the criteria that can duplicate this prompt.)

  4. The DiskSpace Event in SETTINGS > EVENTS reports far too frequently (every minute) and reports Low DiskSpace for removable media such as DVD-ROM drives. Neither the frequency nor misreporting Low DiskSpace for removable media occurred previously.

  5. Delivery Confirmations from postmaster@*.onmicrosoft.com are undeliverable with an "Error:0". Delivery logs are showing an incorrect mail FROM: <> even though the FROM: field in the Delivery Confirmation properly shows postmaster@*.onmicrosoft.com (although the REPLY-TO: is indeed  <>). They just pile up in the Spool queue and stay there. Delivery Confirmations from providers other than Outlook.com or Office365 recipients seem to be delivered to SM users correctly.

4 Replies

Reply to Thread
1
Scarab Replied
Another one:

6. View Logs "Display Related Traffic" is drunk and should go home. As before, it will provide all the related traffic for the Search Criteria you used, but now mixed in with everything else. Not sure how it is being loosey-goosey with the Search Criteria Results, but for example if you use the Search Criteria of "MAIL FROM:<user@domain.tld>" it will include the results of any traffic from the same IP Address, Username, or Domain.tld as "related" making this feature next to useless. It's easier to RDP in and use grep or sed from the command-line and makes it to where first tier Support Technicians can't parse the SM logs for Troubleshooting.
0
echoDreamz Replied
Yes, 6 has been an ongoing issue for us for a while, but we just ignored it. Drunk and should go home though is being nice lol. It's wasted and should be banned from the bar.

The view logs though is completely useless for us though Smartermail. Trying to view SMTP logs or really any of the big logs (IMAP, SMTP etc.) on our server using Chrome or even Firefox completely stalls out the browser, chrome turns into mush, cannot click anything in SM, it just cries. This may because the "Display Related Traffic" is returning lots of unrelated traffic and just overloading the browser with data. Assumed too because our log files are massive, it is just a lot for SM and the browser to handle. So I wrote a Windows app that parses out the log for what we query for and spits it out into a smaller log that we can then sift through.

Christopher

0
echoDreamz Replied
#2, have this issue as well.

#3 as well, we have this issue too. I've had it happen numerous times on me when nothing was changed, customers have also reported it, but it seems to be a super random event, so cant really open a ticket for "super random event".

Christopher

0
Scarab Replied
#5 turned out to not be an issue with SM but an issue with a wildcard SMTP Block that we had (detailed SMTP logs were no help but found the clue in the detailed Delivery logs). I have removed it from the list.

Good to hear that we are not alone on the other issues, although it's odd that we haven't heard anything from SMTools in acknowledgment on whether these issues have been confirmed and added to their bugtraq list. Most of them are minor issues that can be lived with but #2 & #6 are pretty significant functionality issues.

Reply to Thread