Neues Update für NoSpamProxy 11.0
Am 23.9. wurde die Version 11.0.422 veröffentlicht. Es handelt sich um ein Maintenance-Release, mit dem unter anderem folgende Bugs behoben und Neuigkeiten eingeführt werden:
- Changed: If TLS security is required for a partner and delivery is done via a smarthost, the mail is returned to the sender with an NDR. Previously, the mail stayed in the queue until it expired.
- Improved: Routing logic
- Improved: The SwissSign provider does now support Umlaute.
- Improved: Unclear message „The SSPI negotiation failed“. Now, several different messages are displayed, depending on cause of the issue.
- Improved: Massively improved the performance of the Level of trust subsystem
- Improved: Filename handling of decrypted PGP plaintext files
- Improved: Timeout handling when sending and receiving mails
- Fixed: Incorrect encoding used on PGP encrypted mails
- Fixed: Error „Failed to get the size of the dispatch job“
- Fixed: Administrative addresses were not replicated correctly
- Fixed: Mails with a duplicate boundary were incorrectly processed.
- Fixed: Inspection report does not state when a mail is received via the Web Portal
- Fixed: Disclaimer. you cannot add the } sign in Html view
- Fixed: Disclaimer. The editor panel disappears
- Fixed: Conditions on a disclaimer rule could not be deleted.
- Fixed: An unexpected error occured. Error: Could not find a part of the path
- Fixed: Messagetrack data were not correctly processed
- Fixed: Disclaimer. Cannot not use an @ character in the template
- Fixed: Concurrency exception during Active Directory user import
- Fixed: Error message „An item with the same key has already been added.“
- Fixed: Dialog „Server performance“ could not be opened.
- Fixed: Error „Input string was not in a correct format.“ when sending a mail
- Fixed: Performance problem with SURBL filter
- Fixed: „The parameter value cannot be null. Parametername: uriString.“ in Outlook add in
- Fixed: Error message „Object reference not set to an instance of an object.“
- Fixed: Error message „Could not find a part of the path ‚C:\ProgramData\Net at Work Mail Gateway\Temporary Files\MailQueues“
- Fixed: While trying to cleanup empty queue directories, the an error occured
- Fixed: Link for Web portal download is wrong
- Fixed: Target host is not displayed in message tracking details.
- Fixed: TLS switches to „Encryption required“
- Fixed: Error message „Collection was modified; enumeration operation may not execute.“
- Fixed: Error message: „There are no records in the SqlDataRecord enumeration“
- Fixed: Word filter does not find matches containing a full stop.
- Fixed: Mails on hold view does not show all entries
- Fixed: Mail is sent unencrypted even if encryption is required.
- Fixed: Empty queues are displayed in the queue viewer
- Fixed: High cpu usage may occur on a Gateway Role
- Fixed: Empty queues are not removed
- Fixed: Error message „The operation was canceled. While not all actions and filters could be executed“
- Fixed: Using auto enrollment with a D-Trust setup causes multiple requests for a single mail address
- Fixed: Using mail enabled Exchange Public Folders in conjunction with groups do not work as expected
- Fixed: Message „Could not upload a file to the Web Portal on https://server/enQsig/api/upload/file: Unknown. {„files“:[{„error“:““}]}
- Fixed: Internal address in ‚From‘ header filter does not work correctly
- Fixed: The size of the NoSpamProxy eventlog is reset during each update
- Fixed: Not all queues are displayed
- Fixed: Performance problems with many certificates (>1000) in the store.
- Fixed: PGP decryption configuration switches were not honored.
- Fixed: Reply links with a very long subject do not work.
- Fixed: Exception when trying to copy data to the clipboard in the NoSpamProxy MMC
- Fixed: DKIM signature is not applied to NDRs or other DSNs without a sender.
- Fixed: Set-NspPartnerTlsDetail cmdlet does not expose any parameters
Die Version kann einfach über die vorhandene Version installiert werden. Beachten Sie jedoch immer die allgemeinen Updatehinweise wenn Sie einen Proxy-Server konfiguriert haben.
