Received-SPF: pass (Last token {include:_spf.customer.net} (res=PASS)) client-ip=64.235.154.226; envelope-from=<bob@serve.net>; x-ip-name=15pmail.ess.barracuda.com;
X-Received: from 15pmail.ess.barracuda.com (15pmail.ess.barracuda.com [64.235.154.226])
by netwin.co.nz (SurgeMail 7.3p) with ESMTP (TLS) id 7417168-1391920
for <surgemail-list@netwin.co.nz>; Thu, 17 Jan 2019 21:13:00 +0000
X-Return-Path: bob
X-Received: from ganymede.customer.net (ganymede.customer.net [136.179.32.230]) by mx1404.ess.rzc.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 17 Jan 2019 21:11:53 +0000
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=192.168.10.11;
X-Received: from [192.168.10.11] (unverified [192.168.10.11])
by ganymede.customer.net (SurgeMail 7.2i) with ESMTP (TLS) id 6719951-1879441
for <surgemail-list@netwin.co.nz>; Thu, 17 Jan 2019 13:11:51 -0800
X-Return-Path: bob
Subject: Re: [SurgeMail List] TCP read failed
To: surgemail-list@netwin.co.nz
References: <5c40e212.68a6.e36b2700.4ad02595@netwin.co.nz>
From: Bob Fera
Message-ID: <7bd2f0de-affa-7b32-a32b-6852b6cc6cb5@serve.net>
Date: Thu, 17 Jan 2019 13:11:50 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <5c40e212.68a6.e36b2700.4ad02595@netwin.co.nz>
Content-Language: en-US
X-X-Authenticated-User: rmf@zis.com
X-BESS-ID: 1547759511-382908-30474-418-1
X-BESS-VER: 2019.1-r1901172007
X-BESS-Apparent-Source-IP: 136.179.32.230
X-BESS-Outbound-Spam-Score: 0.32
X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.207860
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
0.00 HTML_MESSAGE BODY: HTML included in
message
0.32 URI_HEX URI: URI hostname has long hexadecimal sequence
0.00 BSF_BESS_OUTBOUND META: BESS Outbound
X-BESS-Outbound-Spam-Status: SCORE=0.32 using account:ESS63616 scores of KILL_LEVEL=7.0 tests=HTML_MESSAGE, URI_HEX, BSF_BESS_OUTBOUND
X-BESS-BRTS-Status:1
X-Originating-IP: 64.235.154.226
X-Country: code=US country="United States" ip=64.235.154.226
X-ORBS-Accept: hostkarma_white, hostkarma_quitok
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: ***: 3.4 sd=3.4 lv=0.00 nok=8/0 m=7 nf=8 Exact 0.04(X-myrbl:Color=white) 0.90(X-Phrase:isspam) 0.76(X-Verify-Helo:-ERR) 0.27(StandardTLD) 0.37(X-Verify-Helo:wrongip) 0.38(X-NotAscii:utf) 0.44(spfpass) 0.44(X-LangGuess:English) Saned 5.0 Sval 3.4 bsan 5.0 Moved 5.0->3.4 Sval 3.4
X-NotAscii: charset=utf-8
X-LangGuess: English
X-Probe: +OK nothing bad found
X-Phrase: IsSpam score=1.00
X-Verify-Helo: -ERR wrongip: 15pmail.ess.barracuda.com -> 209.222.*.* not in 64.235.154.226
X-Encryption: SSL encrypted
X-MyRbl: Color=White Age=512 Spam=1 Notspam=7 Stars=1 Good=3510 Friend=5316 Surbl=1 Catch=0 r=0.002 ip=64.235.154.226
X-IP-stats: Incoming Last 0, First 0, in=93, out=0, spam=0 ip=64.235.154.226
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 8bit
Thanks, Chris. Makes sense. I guess I'll open a case with Barracuda
to see if they can shed any light on why it seems to be happening so
often lately...
Bob Fera
I.T. Manager
Zenith Information Group
18757 Burbank Blvd., Suite 116
Tarzana, CA 91356
Phone: 818-206-8634 Ext. 160
Fax: 818-345-2605
www.zis.com
Members of NACHA
The Electronic Payments Association
On 1/17/2019 12:14 PM, Support ChrisP
wrote:
It means the connection was closed while surgemail is waiting
for the confirmation that the message has been sent.
I recommend sending direct and scanning incoming email only,
but that's just my opionion :-) .
ChrisP.
On Friday 18/01/2019 at 8:22 am, Bob Fera wrote:
Hi all,
I'm sure this has been discussed before, but could someone
please refresh my memory what this message means? We're
sending outbound mail through Barracuda's cloud-based scanning
service and have been seeing a lot of these lately. The amount
of time reported varies -- sometimes a few seconds like this
one, other times much more (I seem to recall seeing 180
seconds frequently).
Site xxxxx.com (d140454.o.ess.barracudanetworks.com) said
after data sent: 399 TCP Read failed (Err Code Zero after 2
seconds) 2 sec
Any ideas?
Thanks,
Bob
--
Bob Fera
I.T. Manager
Zenith Information Group
18757 Burbank Blvd., Suite 116
Tarzana, CA 91356
Phone: 818-206-8634 Ext. 160
Fax: 818-345-2605
www.zis.com
Members of NACHA
The Electronic Payments Association