Due to the changed 'who can post' option, the below update was installed on our shared list servers this morning (liberty.safesecureweb.com and justice.safesecureweb.com) and it will most likely make it's way to our shared mailservers by the end of the week.

An update for SmarterMail has been released. Release notes can be found below:

ADDED: Web service functions were added to set and remove a domain forwarding block using the target server rather than a block ID
ADDED: An option in mailConfig.xml (no interface setting) allowing an admin to use the dns lookup component from version 1
CHANGED: The 'who can post' option when creating a list is now defaulted to 'Moderator Only'
CHANGED: Restarting SmarterMail is no longer necessary after changing DNS settings
CHANGED: Links in messages will open in a new window changing the url of the current one
CHANGED: SPF Pass weight value is always deducted from the weight total even if the weight given is positive
FIXED: Setting and extremely high 'Max recipients per message' value for a list would cause an out of memory exception when a message is sent to the list
FIXED: Adding a user with an apostrophe in the username would error
FIXED: The bounce message on messages sent to non existent local addresses gave the wrong reason
FIXED: Option to skip intra-domain spam filtering on the global Spam Options page wasn't being used
FIXED: JavaScript error when attaching files to a new message
FIXED: An IMAP command to fetch messages would error in cases where there are no messages in the selected folder
FIXED: Messages with more than one occurrence of a return-path field in the header prevented SPF checks from running correctly
FIXED: SmarterMail displayed "This message has been removed from the server" in messages with invalid Quoted Printable encoding
FIXED: DNS servers specified in General Settings were not being used
FIXED: A problem with activation on some servers where the default system language was not English
FIXED: The autoclean feature rarely didn't always remove the oldest messages first
FIXED: A security issue where a domain admin could potentially change the name and signature for a user in a different domain on the same server