I followed the instructions to proxy to a loopback port according to the installation instructions, and generally, things work out as they should.

However, I have found that sending email (Outlook 2007) to external destinations by authenticated users can quite often result in an exception reading from the port after a send on the close of the message transmission by Mailwasher, which results in a failure to the client. Although the message was sent, the error is sent back to the client, and the client will continue to retry until it is successful. On average, it will take 3-10 attempts before this occurs, resulting in the receiver of the messages getting duplicates.

There are no errors in the event log or the Mailwasher log at all other than described. Mail can be received, users authenticated, and same-domain email sent without issues. I've included a snippet of the log that indicates the "trailing error" that causes this failure (with some changes to remove IP and personal names/email addresses/computer names). Due to the non-deterministic failure rate of the error (1 in 10 works first time), it's difficult to say where the error lies. I have disabled all Firewall and Anti-virus applications on both the server and the client in an attempt to isolate the issue, and have stripped down security permissions on anything I can get my hands on in the Exchange management tools, with no change in behavior.

It's important to restate that even in the error cases, the message is sent correctly.

Any ideas why this might be happening? I could find nothing like it in the forums or abroad.

The error you have presented indicates a dropped connection (without closing the socket) by Exchange.

I would recomend upgrading to the release version of Exchange 2010, as a beta is often prone to issues (it's the idea of a beta).I have tested MWES with the release version of Exchange 2010 without issue.

Apologies, I may have used the "Beta" reference a little too quickly. I was under the impression when I was installing it from the MSDN download, that it was very close to RTM and would be upgraded in place with merely a product key. However, I can find no trace of anything like that now, and I haven't updated it.

The version Exchange 2010 indicates from the management console is 14.00.0639.021, and the KB article at MS indicates this is the RTM version.

Let me continue to test and check and see if I can find anything more about it. Any suggestions or guidance would be welcome.

An easy way may be to confirm he download file name.The current MSDN download is labelled: mu_exchange_server_2010_x64_dvd_x15-82068.iso with the date: 11/9/2009 (American format).I tested a beta myself a while back, and it did not require a key to install (keys weren't even available at the time). Once the RTM was released the keys were immediately available. This may help with the time frame of installation?

The debug log you've posted below is incomplete and altered. There is missing data that you have edited or changed so we can not effectively see what's happening at all staged of the SMTP conversation.Can you please post a complete unedited log, or if you're not comfortable posting it, please email it to: cliff@firetrust.com for analysis.

Last edited by cliff on Mon Oct 12, 2015 10:50 pm, edited 1 time in total.

Who is online

Firetrust Support Forum

Your go-to-support-center for all Firetrust software.
Firetrust is a market leader in internet security software. We have experienced incredible success with our products worldwide.
Firetrust’s products are noted for their simplicity, requiring minimal technical expertise.
The Firetrust website also provides comprehensive user support for products, including frequently asked questions and tutorials.