Back to Community Threads
4
SM 16 Content Filtering - cannot add condition, so you cannot add any new Content Filtering rules
Problem reported by Ionel Aurelian Rau - 8/29/2017 at 7:55 AM
Resolved
Hi all,
 
Just a quick question: can anyone else verify if you can add a condition to a Content Filtering rule in SM v16.2.6439? Or is it just me?
 
The behaviour I`m seeing is that I can create a new Content Filtering rule for any of the domains and I can click the "+ New Action" button to add an action, but I cannot click the "+ New Condition" under any circumstances, so I cannot add any conditions to the CF Rules. I know I used this feature and I set up some Content Filtering Rules a while back on another SM 16 build, but this is the first time I try in this build and it does not work.
 
So, is anyone else experiencing this?
 
Thank you!

26 Replies

Reply to Thread
0
Employee Replied
8/29/2017 at 12:42 PM
Employee Post
Hello. This is working locally for me. Can you clear the browsers history, and then try this again?
0
Derek Curtis Replied
8/29/2017 at 1:29 PM
Employee Post
Hi, Ionel
 
Just as Rod stated, this is working for me as well: I can add additional Conditions and Actions to existing content filters, both for my account as well as on the domain. Clearing your cache may work...Was this an upgrade or an new install? Have you tried across browsers? 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
0
Ionel Aurelian Rau Replied
8/29/2017 at 11:57 PM
Tried cleaning browser history, cookies, locally stored data, etc and the same behaviour occurs.
0
Ionel Aurelian Rau Replied
8/30/2017 at 12:03 AM
Initially I tried on Opera and Google Chrome (cleared cache). Today I also tried from FireFox, MS Edge and Vivaldi and the same behaviour occurs.

I also tried from another system altogether where I was never logged in to the WebMail before.

Note that I`m not on the latest SM version, but on 16.2.6439 - however, I`ve not seen in the last version any mention of a fix related to this - but if you are trying to reproduce, it`s probably OK to try on the same version.

This was originally an upgrade from SM15 to one of the v16.0.x versions, after which we`ve done every other update SM has released for v16. The last version where this worked was Version 16.1.6418 (after that we skipped v16.1.6425 and updated to v16.2.6439).
0
Matt Leach Replied
8/30/2017 at 7:50 AM
I am also unable to add a condition.
 
Running Version: 16.2.6442
 
Have tried multiple browsers on multiple machines. Have tried clearing caches and history and no Joy. Clicking New Condition does nothing.
0
Derek Curtis Replied
8/30/2017 at 7:58 AM
Employee Post
Will you both check your Dev Tools -- look at the console and the network tabs, and see if there are any errors being thrown? I simply cannot replicate this at all...
 
I know you've cleared history and caches, but what about cookies? Have you tried that? I had an issue on Chrome for MacOS, but clearing out ALL cookies cleared it up. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
0
Matt Leach Replied
8/30/2017 at 9:34 AM

I cleared all cookies with no change.

Ran the Console and there is an error when i click the button:

       
0
Erick Baum Replied
8/30/2017 at 10:26 PM
I can't add conditions either on 16.2.6442.  Getting a similar error to above:
 
angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:11
    at angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:49
    at Object.d [as get] (angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:47)
    at angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:49
    at d (angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:47)
    at e (angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:47)
    at Object.invoke (angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:47)
    at R.instance (angular-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:98)
    at Object.i [as link] (vendor-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:24)
    at g (vendor-v-16.2.6442.18515.8d4e8b8bb4b8e00.js:25)
0
Ionel Aurelian Rau Replied
8/31/2017 at 12:30 AM
As I said, I also tried on a totally new machine (a VM) where no browser has ever accessed the server, so I`m sure that it was not due to cookies, but I also cleared all browser data when testing on my main machine.
 
Now I also tried the same action with the Console opened and I get the same error as stated above (tried several times to click on the "New Condition" button):
site-v-16.2.6439.20618.8d4e6132f650800.js:94 SignalR Init2, Connected: undefined
site-v-16.2.6439.20618.8d4e6132f650800.js:94 SignalR Start2
site-v-16.2.6439.20618.8d4e6132f650800.js:94 SignalR Started2
site-v-16.2.6439.20618.8d4e6132f650800.js:94 SignalR connection type: webSockets
site-v-16.2.6439.20618.8d4e6132f650800.js:5 SignalR Initted, Sending connect with auth details.
site-v-16.2.6439.20618.8d4e6132f650800.js:5 SignalR Connect success.
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 TypeError: Cannot read property 'indexOf' of undefined
    at Object.getNodeFromJid (vendor-v-16.2.6439.20618.8d4e6132f650800.js:452)
    at a.Connection.connect (vendor-v-16.2.6439.20618.8d4e6132f650800.js:452)
    at t.j [as authenticateOAuth2] (site-v-16.2.6439.20618.8d4e6132f650800.js:23)
    at w (site-v-16.2.6439.20618.8d4e6132f650800.js:23)
    at site-v-16.2.6439.20618.8d4e6132f650800.js:23
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:166
    at f (angular-v-16.2.6439.20618.8d4e6132f650800.js:52)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:55
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 TypeError: Cannot read property 'indexOf' of undefined
    at Object.getNodeFromJid (https://[REDACTED-SERVER-NAME]/interface/output/vendor-v-16.2.6439.20618.8d4e6132f650800.js:452:17733)
    at a.Connection.connect (https://[REDACTED-SERVER-NAME]/interface/output/vendor-v-16.2.6439.20618.8d4e6132f650800.js:452:24111)
    at t.j [as authenticateOAuth2] (https://[REDACTED-SERVER-NAME]/interface/output/site-v-16.2.6439.20618.8d4e6132f650800.js:23:2263)
    at w (https://[REDACTED-SERVER-NAME]/interface/output/site-v-16.2.6439.20618.8d4e6132f650800.js:23:1748)
    at https://[REDACTED-SERVER-NAME]/interface/output/site-v-16.2.6439.20618.8d4e6132f650800.js:23:1570
    at https://[REDACTED-SERVER-NAME]/interface/output/angular-v-16.2.6439.20618.8d4e6132f650800.js:166:197
    at f (https://[REDACTED-SERVER-NAME]/interface/output/angular-v-16.2.6439.20618.8d4e6132f650800.js:52:148)
    at https://[REDACTED-SERVER-NAME]/interface/output/angular-v-16.2.6439.20618.8d4e6132f650800.js:55:68 Possibly unhandled rejection: {}
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
DevTools failed to parse SourceMap: https://[REDACTED-SERVER-NAME]/interface/output/angular.js.map
DevTools failed to parse SourceMap: https://[REDACTED-SERVER-NAME]/interface/output/vendor.js.map
DevTools failed to parse SourceMap: https://[REDACTED-SERVER-NAME]/interface/output/site.js.map
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
l @ angular-v-16.2.6439.20618.8d4e6132f650800.js:106
t.onload @ angular-v-16.2.6439.20618.8d4e6132f650800.js:111
XMLHttpRequest.send (async)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:112
p @ angular-v-16.2.6439.20618.8d4e6132f650800.js:107
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:105
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
angular-v-16.2.6439.20618.8d4e6132f650800.js:127 Error: [$injector:unpr] http://errors.angularjs.org/1.6.2/$injector/unpr?p0=internalTypeProvider%20%3C-%20internalType%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController%20%3C-%20userFilterRuleEditController
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:11
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at Object.d [as get] (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at angular-v-16.2.6439.20618.8d4e6132f650800.js:49
    at d (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at e (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at Object.invoke (angular-v-16.2.6439.20618.8d4e6132f650800.js:47)
    at R.instance (angular-v-16.2.6439.20618.8d4e6132f650800.js:98)
    at Object.i [as link] (vendor-v-16.2.6439.20618.8d4e6132f650800.js:24)
    at g (vendor-v-16.2.6439.20618.8d4e6132f650800.js:25)
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:127
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:99
(anonymous) @ vendor-v-16.2.6439.20618.8d4e6132f650800.js:25
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:139
$eval @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
$digest @ angular-v-16.2.6439.20618.8d4e6132f650800.js:150
$apply @ angular-v-16.2.6439.20618.8d4e6132f650800.js:153
(anonymous) @ angular-v-16.2.6439.20618.8d4e6132f650800.js:289
dispatch @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
q.handle @ angular-v-16.2.6439.20618.8d4e6132f650800.js:3
Hopefully this will help you single-out the issue and fix it soon since we need this feature asap.
Thank you!
0
Derek Curtis Replied
8/31/2017 at 7:44 AM
Employee Post
Thanks for the errors, guys. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
0
Nicolas Nicolas Replied
9/2/2017 at 3:55 AM
I have the same. issue.
It was ok in SM 16.1 , we faced this problem after updating to 16.2
 
Any solution?
 
0
Ionel Aurelian Rau Replied
9/4/2017 at 12:41 AM
Yes, is there any time-frame for fixing this issue? I was hoping we could update to a fixed build this past week-end but as I can see you no longer have weekly releases, so we do not know what to expect. I need to let our users know of an estimated date when we`ll have the feature back up and running, so please update if you have any information about the next build that includes this fixed.
 
Also, unfortunately we cannot update during week-days, so we will always need to wait for the next week-end following your release to update - further adding to the delay, thus any info on this would be useful.
 
Thank you!
0
Nicolas Nicolas Replied
9/12/2017 at 7:06 AM
Any new?
0
Nicolas Nicolas Replied
9/12/2017 at 7:06 AM
Any solution?
0
Matt Leach Replied
9/12/2017 at 7:19 AM
Support provided a new update that fixed the issue. Not sure if it was made publicy available so may want to ask.
0
Ionel Aurelian Rau Replied
9/12/2017 at 7:47 AM
Hopefully this new build will be made available before the end of the week so we can update during the week-end. If not, I guess we`ll have to ask for a custom build too.
0
User Replied
9/12/2017 at 12:41 PM
Hello everyone! If this issue is critical to get running in your environment, you can reach out to sales@smartertools.com to request a pre-release build that includes the fix for this issue. Please remember this is a pre-release build and we are still working on finalizing fixes and improvements currently.
0
Robert G. Replied
9/12/2017 at 1:37 PM
Thank you Kyle. Do you have any ETA on this release?
GearHost.com
0
User Replied
9/12/2017 at 2:07 PM
Robert, typically our minor releases are available Friday afternoon/evening but there are exceptions to this occasionally.
0
Ionel Aurelian Rau Replied
9/13/2017 at 1:52 AM
Thanks Kyle. Which is why we`d prefer waiting for a release build. Any idea if such a build will be available this Friday?
1
Tom Gorton Replied
9/14/2017 at 5:58 AM
When will the patch for this be available? This is seriously impacting my clients and business. Cannot believe this was missed in testing before a release.
0
Matt Petty Replied
9/14/2017 at 7:22 AM
Employee Post
We are aiming for Friday, but if you need one right now, I can get you one today. Just let me know here, and I can send you our most up-to-date version internally.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
0
Tom Gorton Replied
9/14/2017 at 8:42 AM
I will wait for Friday. Thanks.
0
Ionel Aurelian Rau Replied
9/18/2017 at 12:32 AM
We`ve installed the latest version (v16.3.6467) and this issue appears to be fixed.
 
Thank you!
0
Tom Gorton Replied
9/18/2017 at 2:39 PM
I can confirm it is. Thanks.
0
Nicolas Nicolas Replied
9/22/2017 at 5:27 AM
this issue has been fixed in v 16.3
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Set up Autodiscover for SmarterMailSmarterMail > Installation and Configuration
Recommended SPAM SettingsSmarterMail > Antispam and Antivirus
Attaching SmarterMail 16.x and Older Domains to New BuildsSmarterMail > Domain/User Configuration and Management
Emails Deleted UnexpectedlySmarterMail > Troubleshooting
Message Archiving in SmarterMailSmarterMail > Installation and Configuration