This is a slightly odd problem, it could be a network fault/issue with 
large tcp packets, or the remote end deciding to reject the message 
uncleanly for some reason.

The first step is to check the logs on the receiving server to see what 
it reports .

And confirm the connectivity is as expected. e.g.  from your server, 
send a an email into the other server directly to see if it works...
	telnet remote.server 25
	helo me
	mail from:<>
	rcpt to:HIDDEN@omain.name>
	data
	From: bob
	Subject: test

	test
	.
Also make sure the ip address is correct and it really is going to the 
destination you expect...

	ChrisP.

On 4/10/2011 6:17 a.m., Charles Bender wrote:
> I am having an issue with a certain error from our Surgewall proxy. When
> keep getting this error when trying to send an email through the
> Surgemail host to an exchange server on the other end. I have looked at
> each of the reasons in the manual and am not seeing our settings causing
> this problem.
>
> Can I get some direction?
>
> Gave up after 12 hours, last error:
>
> to=74.92.226.77 TCPWrite failed 0/53544, tot=65800 upto=0 64 sec An
> existing connection was forcibly closed by the remote host.
> write_timed3.1 64sec ()
>
> 10054 An existing connection was forcibly closed by the remote host.
> after 0 seconds r=-1
>
> Thanks
>
> Chuck
>