Hi Eric,
The ip's that are listed in general turn out to be
NXDomain but I get the idea thanks.
I have had only one person ask why they did not
get an email. Turns out it was the sender not the
QMT box.
best wishes
Tony White
Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717
Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)
Be aware: All calls to and from YCS landlines and mobiles are recorded
IMPORTANT NOTICE
This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.
On 1/11/2014 02:29, Eric Broch wrote:
I tracked a similar scenario--connection problems--when there were
Riverbed devices between the sending email server and my QMT host and my
QMT host was closing the connection because of a problematic
configuration on their Riverbed device. The real problem was that we
were not receiving email and these connection drops in the log confirmed it.
So, I would try to figure out if anyone not receiving email that they're
supposed to receive? And, do the IP addresses from the disconnects
represent legitimate senders to your clients? I'd worry only if email
wasn't being received, IMHO.
On 10/31/2014 8:59 AM, Tony White wrote:
Hi Eric,
The server is on CentOS 5.11
Here is a sample...
2014-11-01 01:37:44.188786500 tcpserver: end 23117 status 0
2014-11-01 01:37:44.188787500 tcpserver: status: 1/100
2014-11-01 01:37:45.266227500 tcpserver: status: 2/100
2014-11-01 01:37:45.266228500 tcpserver: pid 23119 from 213.76.139.194
2014-11-01 01:37:45.266228500 tcpserver: ok 23119
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::43839
2014-11-01 01:37:52.821276500 tcpserver: end 23100 status 0
2014-11-01 01:37:52.821278500 tcpserver: status: 1/100
2014-11-01 01:37:56.085725500 tcpserver: status: 2/100
2014-11-01 01:37:56.085828500 tcpserver: pid 23121 from 213.76.139.194
2014-11-01 01:37:56.085884500 tcpserver: ok 23121
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::52796
2014-11-01 01:38:06.905923500 tcpserver: status: 3/100
2014-11-01 01:38:06.906038500 tcpserver: pid 23122 from 213.76.139.194
2014-11-01 01:38:06.906092500 tcpserver: ok 23122
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::54477
2014-11-01 01:38:14.466842500 tcpserver: end 23121 status 0
2014-11-01 01:38:14.466844500 tcpserver: status: 2/100
2014-11-01 01:38:14.467514500 tcpserver: end 23119 status 0
2014-11-01 01:38:14.467515500 tcpserver: status: 1/100
2014-11-01 01:38:17.769041500 tcpserver: status: 2/100
2014-11-01 01:38:17.769149500 tcpserver: pid 23125 from 213.76.139.194
2014-11-01 01:38:17.769203500 tcpserver: ok 23125
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::56079
2014-11-01 01:38:25.281435500 tcpserver: end 23122 status 0
2014-11-01 01:38:25.281436500 tcpserver: status: 1/100
2014-11-01 01:38:28.620829500 tcpserver: status: 2/100
2014-11-01 01:38:28.620932500 tcpserver: pid 23127 from 213.76.139.194
2014-11-01 01:38:28.620986500 tcpserver: ok 23127
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::53072
2014-11-01 01:38:39.466667500 tcpserver: status: 3/100
2014-11-01 01:38:39.466772500 tcpserver: pid 23133 from 213.76.139.194
2014-11-01 01:38:39.466834500 tcpserver: ok 23133
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::55702
2014-11-01 01:38:46.923490500 tcpserver: end 23125 status 0
2014-11-01 01:38:46.923492500 tcpserver: status: 2/100
2014-11-01 01:38:46.923553500 tcpserver: end 23127 status 0
2014-11-01 01:38:46.923554500 tcpserver: status: 1/100
2014-11-01 01:38:50.285064500 tcpserver: status: 2/100
2014-11-01 01:38:50.285066500 tcpserver: pid 23138 from 213.76.139.194
2014-11-01 01:38:50.285066500 tcpserver: ok 23138
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::61661
2014-11-01 01:38:56.243615500 tcpserver: status: 3/100
2014-11-01 01:38:56.243616500 tcpserver: pid 23140 from 62.146.74.3
2014-11-01 01:38:56.243617500 tcpserver: ok 23140
indialau.bigpuddle.net:111.223.234.146:25 :62.146.74.3::57187
2014-11-01 01:38:57.783421500 tcpserver: end 23133 status 0
2014-11-01 01:38:57.783422500 tcpserver: status: 2/100
2014-11-01 01:39:01.111513500 tcpserver: status: 3/100
2014-11-01 01:39:01.301013500 tcpserver: pid 23142 from 213.76.139.194
2014-11-01 01:39:01.303583500 tcpserver: ok 23142
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::63458
2014-11-01 01:39:11.976260500 tcpserver: status: 4/100
2014-11-01 01:39:11.976361500 tcpserver: pid 23240 from 213.76.139.194
2014-11-01 01:39:11.976417500 tcpserver: ok 23240
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::65137
2014-11-01 01:39:16.689435500 tcpserver: status: 5/100
2014-11-01 01:39:16.689535500 tcpserver: pid 23241 from 114.79.164.123
2014-11-01 01:39:16.689604500 tcpserver: ok 23241
indialau.bigpuddle.net:111.223.234.146:25 :114.79.164.123::10737
2014-11-01 01:39:16.697501500 tcpserver: end 23241 status 0
2014-11-01 01:39:16.697502500 tcpserver: status: 4/100
2014-11-01 01:39:19.477752500 tcpserver: end 23138 status 0
2014-11-01 01:39:19.477754500 tcpserver: status: 3/100
2014-11-01 01:39:19.478749500 tcpserver: end 23142 status 0
2014-11-01 01:39:19.478750500 tcpserver: status: 2/100
2014-11-01 01:39:22.832608500 tcpserver: status: 3/100
2014-11-01 01:39:22.832609500 tcpserver: pid 23245 from 213.76.139.194
2014-11-01 01:39:22.832610500 tcpserver: ok 23245
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::56415
2014-11-01 01:39:30.298896500 tcpserver: end 23240 status 0
2014-11-01 01:39:30.298897500 tcpserver: status: 2/100
2014-11-01 01:39:33.663006500 tcpserver: status: 3/100
2014-11-01 01:39:33.663008500 tcpserver: pid 23247 from 213.76.139.194
2014-11-01 01:39:33.663008500 tcpserver: ok 23247
indialau.bigpuddle.net:111.223.234.146:25 :213.76.139.194::3614
2014-11-01 01:39:37.407752500 tcpserver: status: 4/100
best wishes
Tony White
On 1/11/2014 01:41, Eric Shubert wrote:
On 10/31/2014 07:31 AM, Tony White wrote:
Hi all,
Is anyone else seeing an increase in the connect then disconnect
on port 25 on their QMT servers?
Just watching the log there are many entries that connect do
nothing then disconnect all day long.
Is this something to worry about or should I try to ignore it?
thanks in advance.
best wishes
Tony White
---------------------------------------------------------------------
Which version(s) are you running? Logging is quite a bit different in
the latest QMT6 versions.
Can you post a sample of what you're talking about?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
