Miscellaneous V17 Issues
Problem reported by Scarab - December 28, 2018 at 4:31 PM
Resolved
Haven't taken v17 Live yet, but encountered the following issues while testing the latest build 6928 thus far:

  1. MANAGE > DOMAINS lists domains out of alphabetical order. It is apparently sorted by number, CAPITAL LETTERS, lowercase letters, i.e, 4example.com, SAMPLE.COM, TestDomain.com, anotherdomain.com, etc. The sort shouldn't be case-sensitive.

  2. Although there is a DEFAULT DOMAIN SETTING & DOMAIN PROPAGATION for 2-Step Authentication under "Features", there is not a DEFAULT DOMAIN SETTING & DOMAIN PROPAGATION for the "General" 2-Step Authentication Status of "Disabled", "Enabled", or "Forced", requiring it to be manually set for each individual domain.

  3. 2-Step Authentication is not visible when Impersonating User. This not only prevents System Administrators from troubleshooting whether the user even has it turned on, but prevents them from disabling it for a user who loses their Authenticator or Backup Email Address, or from assisting the user with their Device & WebDAV passwords. If it is enabled the System Administrator can't even login manually as the user as they do not have the secondary code. So, basically this has reduced 2-Step Authentication to "Use at your own risk! We cannot disable it for you once it is enabled and your warranty will effectively become null and void."

I'm sure I'lll encounter others in the next couple of days, but overall impressed with how quickly the install and conversion from v16 went. Other than attempting to convert domains that had been deleted from SmarterMail years ago (in the v4 & v8 eras) and throwing errors because they were 99% deleted but still existed as ghosts somewhere, it otherwise went smooth.

11 Replies

Reply to Thread
0
Robert Emmett Replied
Employee Post
Thank you for reporting these issues.  I have added them to our bugs lists for further review by the development team.  I have fixed issue #1 already.  It will be included in the next release.  I will update this thread concerning issues #2 and #3.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
echoDreamz Replied
The domain propagation setting for the max maillist message size too, doesnt propagate. I have a ticket open for it as well as well as other aspects of the domain propagation page.

I'd really like to see the 2FA notification to be improved with wording to let the user fully know and understand that their protocol passwords WILL CHANGE and the current password WILL NOT work for these.

Christopher

0
Scarab Replied
Robert,

Thanks for the update and adding those items to the list. Two more issues with Build  6928 that I found:

1.    The SETTINGS > ANTISPAM > SPAM CHECKS only displays the contents of the first item. So, no matter which user-added Spam Check you chose, unless it is a system Spam Check, it displays incorrectly. For example, our first (of 57) Spam Checks is:

Rule Name: .ASIA
Rule Source: Header
Header: Return-Path
Rule Source: Regular Expression
Rule Text: .+\.asia>?

So, for example, when we attempt to open the Custom Rule CELEBS, CHINESE, FOREIGN, RUSSIAN VOWELS, etc. it shows the same fields and criteria as .ASIA. As these rules are showing correct in the \service\spamConfig.xml I'm assuming that this is a display error in the web interface. (Note: RBLs and URIBLs display item details properly.)

2.    Under SETTINGS > ANTISPAM > SPAM CHECKS we had several Custom Rules disappear during the update/conversion from v16 (about 7 of them), along with 30 RBLs and 12 URIBLs that are now missing and have to be manually re-entered. Many system Spam Checks, such as DKIM, and SPF are duplicated (but oddly not all of them).
0
Robert Emmett Replied
Employee Post
Scarab, can you PM me your settings.json found under C:\Program Files (x86)\SmarterTools\SmarterMail\Settings?
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
David Thomas Replied
Same problem here after deleting a custom rule : all other custom rules desapearing ! (SM 100.0.6928)
0
David Thomas Replied
...RBL too….
0
Robert Emmett Replied
Employee Post
Scarab, thank you for sending the file.  It truly help pinpoint the issue.  The underlying issue has been fixed (all of the custom spam rules had an empty Guid).  This fix will be in the next SmarterMail release.  Regarding the duplicate entries from DKIM and SPF, etc., it appears that you actually have custom rules named the same as the default spam rules.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Robert Emmett Replied
Employee Post
David, can you check your settings.json (by default it's in C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Settings) and look for "spam_ip4r_lookups".  That will contain all of your RBLs.  Do any (or all) of them have a "guid": "00000000-0000-0000-0000-000000000000"?
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
David Thomas Replied
Yep, all have guid like "0000....00000"
0
Scarab Replied
Robert,

Glad the file helped pinpoint the issue.

My apologies about the false call on the duplicate Spam Checks. You are right, those are duplicates we created on our Primary SM server before we offloaded those checks to an Incoming Gateway SM server. I've been jumping in between 3 different Live servers on SmarterMail v16 and 3 different Dev servers on SmarterMail Build 6928, and when facing inevitable interruptions when comparing I start accidentally comparing Apples & Oranges...Gateways vs Primary SM servers. I caught it on the "missing" Custom Rules but apparently totally fumbled it on the "duplicate" Spam Checks.

Hopefully the next Beta I'll still have the available resources to join in and get this done early instead of coming so late to the party.
1
Robert Emmett Replied
Employee Post
The items with an empty (all zero) guid has been fixed in last night's public release of SmarterMail.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread