Return-Path: Sender: To: CGatePro Date: Wed, 10 Mar 2010 06:43:16 -0800 Message-ID: X-Original-Return-Path: Received: from email.macdock.com ([216.168.129.144] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.3.4) with ESMTPS id 59072577 for CGatePro@mail.stalker.com; Tue, 09 Mar 2010 07:32:54 -0800 Received-SPF: pass receiver=mail.stalker.com; client-ip=216.168.129.144; envelope-from=mike@323inc.com Received: from [70.90.74.77] (account mike@323inc.com HELO [192.168.1.3]) by email.macdock.com (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 9468098 for CGatePro@mail.stalker.com; Tue, 09 Mar 2010 10:38:10 -0500 From: Mike Yrabedra Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: write failed. Error Code=broken connection - Chain Authority issue? X-Original-Date: Tue, 9 Mar 2010 10:32:31 -0500 X-Original-Message-Id: X-Original-To: CommuniGate Pro Discussions Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Hello, I have 4.2.10 running on Mac OS X. Within the past few weeks we started getting alot of errors like the = following, when a user tried to email someone with an attachment... write failed. Error Code=3Dbroken connection The only thing that happened around this time that was different, is = that we replaced the SSL cert. The new one is a wildcard cert ( from = COMODO ). It works fine ( web, connecting,sending text emails, etc...), = but I am wondering if something with the CA is different, causing the = TLS connection to break when sending attachments. Am I barking up the wrong tree here? Does the cert have nothing to do = with normal attachment sending? The issue is intermittent and only occurs on certain remote receiving = servers. Any assistance would be awesome. Cheers. -- Mike