XWall release 3.44
Monday, 09 March 2009 13:04 Last Updated on Friday, 20 March 2009 12:27
The latest XWall release allows you to add comments in the ini file. Seasoned XWall users will love this option. As example you can add notes to an IP address so it makes still sense to you tomorrow morning. There are a lot of other new features that makes administration easier. Download it Today.
- New: Support for GBK ( Chinese ) codepage
- New: Block outbound messages that are not from an internal domain ( OutboundBlockAddressOnlyInternal=True )
- New: Optional startup delay in the case the virus scanner or DNS server is not starting fast enough ( StartupDelayFresh=5 )
- New: XWall.ini allows comments using a semicolon
- New: Comment for every list field
- New: Send information message after startup ( SendStartup=True )
- New: Send information message when there was a warning after startup ( SendStartupWarn=True )
- New: Hide SLS service info in error message; needed for Trend Micro Reputation Service ( InboundESMTPHideSLSInfo=True )
- New: Warning when ini is read-only or no read-write ACL
- New: Heuristic checks for text obfuscation with HTML tags in plain text
- New: Verbose logging for disclaimer ( VerboseDisclaimer=True )
- New: The logfile shows which e-mail template was used to block an e-mail address
- New: Recommended SLS/RBL b.barracudacentral.org
- Chg: yahoogroups.com removed from default exclusion
- Chg: Update of X-Mailer in Options->Blocking->Header
- Chg: Files for disclaimer can be in any directory, default is XWall directory
- Chg: UAC is requireAdministrator for MBSever.exe and highestAvailable for MBAdmin.exe
- Fix: Ignoring MIME Content-Disposition header fields with longer value like "filenamexxx"
- Fix: White List was not properly updated when the message was sent to more than one recipient
- Fix: Exchange 2007 is not able to decode a MIME subject with more than 225 bytes word len
- Fix: Disclaimer and S/MIME address with a star was not working as expected
- Fix: Reassemble message uses codepage UTF-7 when the original codepage is US-ASCII, but the text contains non-ASCII characters
- Fix: DNS validation is repeated several times in the case of a DNS error
- Fix: Manifest and UAC elevation also for MBServer.exe
- Fix: ESMTP AUTH LOGIN with Microsoft .NET Framework (Namespace System.Net.Mail)
- Fix: non-delivery report for a message with a 4xx and 5xx error showed the reason for the 4xx rather then 5xx error
Over the past year or two we have seen new types of spam to evolve. In some cases spamers come up with some pretty interesting ways of getting their message delivered. However there is something they have in common. It's quantity - the more spam they send the more profits they can expect. That's exactly where XWall CCS enters the picture. The CCS is based on a message body checksum. All XWalls with CCS send their checksums to the central server and it keeps track of the bad guys. Actually the more spam the better it gets. A year ago you may considered CCS to catch an other percent or two of your spam. Today it's getting to be a premier tool to catch spam. Take a look at the screenshots. Not only has CCS moved up in the ranks, it catches a lot of spam other filters will not. Best of all it stops new variant of spam without your intervention.
It thanks you for signing up and includes a link to a website .... bad news of course. But there is good news. Your current Xwall (3.29+) can block the ip address. Add a string http://#.#.#.# in admin-> option-> blocking-> html