I'm not sure when the import/export of spam settings got added but it allows a great opportunity to crowd source these settings and keep them up to date and help ST with anti-spam.

1) ST does not need to push a new build to revise anti-spam settings. They can have a status page or some area of the SM area or customer portal to allow a user to update or compare settings at any time. If something was sent out in error it can be immediately updated. Allow customers to get change notifications.

2) Put the spam config on GitHub. Allow users to branch/pull request changes which ST owns. This allows the user base to keep this absolutely up to date or even have anti-spam vendors make changes to help the ST community. We can see what changed with GitHub's change tracking (history) feature and be able to pull a new copy at any time. ST may need to revise what's imported so as not to change my grey list settings but only revise anti-spam settings.

3) As mentioned in a prior thread, ST should detect when a spam config is different from the default and indicate so. A link can show the diff between ST's version and the modified version and also a reset to default option. This also comes in handy if ST pushes a new release that has changes but doesn't change our spam configs, we need to know what to revise.

This area is crucial to reliable email delivery and when comparing SM to Gmail it is night and day different, I trust Gmail, I do NOT trust SM and that is what ST has to earn back.