Winsock error 10060 mdaemon

The following Winsock Error codes can be recorded by MDaemon to report socket failures. The code descriptions are detailed below followed by why these socket errors may occur in MDaemon.

WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET

WSAETIMEDOUT
10060
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

WSAECONNREFUSED
10061
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.

Mdaemon socket error 10060 тайм аут соединения

Сообщения: 132
Благодарности: 1

Thu 2013-01-03 10:04:07: Attempting SMTP connection to [212.154.154.105:25]
Thu 2013-01-03 10:04:07: Waiting for socket connection.
Thu 2013-01-03 10:04:28: * Winsock Error 10060 Тайм-аут соединения.
Thu 2013-01-03 10:04:28: * 212.154.154.105 added to connection failure cache for 5 minutes »

Thu 2013-01-03 10:04:28: Attempting to send message to smart host
Thu 2013-01-03 10:04:28: Attempting SMTP connection to [98.57.245.171:25]
Thu 2013-01-03 10:04:28: Waiting for socket connection.
Thu 2013-01-03 10:04:28: * Connection established (98.57.245.171:1786 -> 98.57.245.171:25)
Thu 2013-01-03 10:04:28: Waiting for protocol to start. »

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Сообщения: 77
Благодарности: 1

снова таки понадеюсь на помощь.
Вопрос тот же, акт второй.
Вводная: имеем почтовый сервер на MDaemon v13, отдельностоящий во внутренней локалке комп. Интернет раздается роутером TP-Link, белый интернет-адрес. Внутренний порт SMTP сменен с умолчательного 25-го на случайный, соотв. проброс портов с входа роутера (25) на почтовик сделан. С неделю назад сменены все пароли. Умолчательные пользователи (предыдущий фейл) отключены. Настройки безопасности перерыты вдоль и поперек (в инете все инструкции по настройке демона безнадежно устарели — как интерфейс, так и наличиеназвание многих опций).
А теперь, собственно, сама беда — она не изменилась: регулярно наш IP-адрес оказывается в черном списке, всегда одном и том же — cbl.abuseat.org. Сейчас в качестве описания значится следующее:

is listed in the CBL. It appears to be infected with a spam sending trojan, proxy or some other form of botnet.

It was last detected at 2013-06-17 05:00 GMT (+/- 30 minutes), approximately 3 hours ago.

It has been relisted following a previous removal at 2013-06-15 20:55 GMT (1 days, 10 hours, 52 minutes ago)

This IP is infected with, or is NATting for a machine infected with Win32/Zbot (Microsoft).

This was detected by observing this IP attempting to make contact to a Zeus Command and Control server, with contents unique to Zeus C&C command protocols.

Zbot is known by other names: Wsnpoem (Symantec) and most commonly as Zeus.

Zbot/Zeus is a banking trojan, and specializes in stealing personal information (passwords, account information, etc) from interactions with banking sites through the use of «formgrabs».

This was detected by a TCP/IP connection from on port 49168 going to IP address 87.255.51.229 (the sinkhole) on port 80.

The botnet command and control domain for this connection was «dskjhnjkdsch.info».

Behind a NAT, you should be able to find the infected machine by looking for attempted connections to IP address 87.255.51.229 or host name dskjhnjkdsch.info on any port with a network sniffer such as wireshark. Equivalently, you can examine your DNS server or proxy server logs to references to 87.255.51.229 or dskjhnjkdsch.info. See Advanced Techniques for more detail on how to use wireshark — ignore the references to port 25/SMTP traffic — the identifying activity is NOT on port 25.

This detection corresponds to a connection at 2013-06-17 04:49:20 (GMT — this timestamp is believed accurate to within one second).

These infections are rated as a «severe threat» by Microsoft. It is a trojan downloader, and can download and execute ANY software on the infected computer.

» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>

— проверку телнетом на открытый релей. »

подключиться telnet-ом (порт 23) с хоста, где запущен почтовый сервер, вот на этот адрес: relay-test.mail-abuse.org

Есть сервис для этого — http://www.test-smtp.com/, результат его проверки — ниже, под катом

Relaying test.
Attempting to connect to .

ESMTP MDaemon 13.0.5; Mon, 17 Jun 2013 12:02:51 +0300
>>> EHLO www.test-smtp.com
Hello ns3000624.ovh.net, pleased to meet you
>> HELP
>> AUTH LOGIN
>> AaAaAa
>> AaAaAa
>> VRFY postmaster
>> STARTTLS
>> NOOP
>> RSET
>> MAIL FROM:
, Sender ok
>>> RCPT TO:
, Recipient unknown
Test 2/28
>>> RSET
>> MAIL FROM:
>, Sender unknown
Error: bad SMTP reply
Test 3/28
>>> RSET
>> MAIL FROM: >
> is invalid or DNS says does not exist
Error: bad SMTP reply
Test 4/28
>>> RSET
Error: host didn’t reply on time
>>> NOOP
Connection lost
Attempting to connect to .
ESMTP MDaemon 13.0.5; Mon, 17 Jun 2013 12:02:55 +0300
>>> EHLO www.test-smtp.com
Hello ns3000624.ovh.net, pleased to meet you
>> RSET
>> MAIL FROM: ]>
]> is invalid or DNS says does not exist
Error: bad SMTP reply
Test 5/28
>>> RSET
Error: host didn’t reply on time
>>> NOOP
Connection lost
Attempting to connect to .
ESMTP MDaemon 13.0.5; Mon, 17 Jun 2013 12:02:55 +0300
>>> EHLO www.test-smtp.com
Hello ns3000624.ovh.net, pleased to meet you
>> RSET
>> MAIL FROM:
is invalid or DNS says does not exist
Error: bad SMTP reply
Test 6/28
>>> RSET
Error: host didn’t reply on time
>>> NOOP
Connection lost
Attempting to connect to .
ESMTP MDaemon 13.0.5; Mon, 17 Jun 2013 12:02:55 +0300
>>> EHLO www.test-smtp.com
Hello ns3000624.ovh.net, pleased to meet you
— Reverse: gate2.
is blacklisted by Spamhaus
ESMTP: yes — TLS: no — AUTH: yes — VRFY: no — MTA: Unknown
Average time : 0.16sec — Slowest : 1.62sec — Fastest : 0.06sec

Последний раз редактировалось 3абанен, 13-12-2014 в 02:23 .

Источник

Mdaemon Winsock Errors while sending emails. WinServer2008 R2

From last few days i am having an error while my Mdaemon server (v13.0.4) sending emails to another server. I tried troubleshooting by upgrading server, disabling Anti-virus and etc, but still few on few domains it is having SMTP error

Winsock error 10053
Winsock error 10054
Winsock error 10060

These are the errors . kindly help to resolve this issue

Ensure AV Gear Plays Nice on the Corporate Network

finally the issue was with my FIber connection. i Have had two connections, one wireless and the other one is Fiber.

The issue was with the Up stream in fiber. (ISP)

Thank you all for support and time.

Do these errors occur when sending to one specific domain, or are you getting these errors for all outgoing emails?

Brand Representative for MDaemon Technologies

Further on what AceOfSpades mentioned.

Without a snippet of the SMTP out log, I’m unable to verify the exact reason but the Winsock errors are network related errors. Depending on where the errors are in the SMTP out transaction between the servers, it could clue you to what could be causing the issue.

Verify if there is anything on the network that could be filtering these outbound SMTP sessions, such as a third party Firewall, Windows Firewall, third party AntiVirus software, ISP, etc.

Feel free to PM me a snippet of the SMTP out logs where the issue is happening. The SMTP out log can be found in the MDaemonLogs directory.

Let me know if I can help further.

#ACE: These error comes out only with few random domains. otherwise SMTP is working fine.

For more information kindly see the logs.

Tue 2015-09-01 11:11:28: [6314:2] Session 6314; child 2

Tue 2015-09-01 11:11:28: [6314:2] Parsing message

Tue 2015-09-01 11:11:28: [6314:2] * From: ***@abc.com.pk

Tue 2015-09-01 11:11:28: [6314:2] * To: *****@xyz.com.pk

Tue 2015-09-01 11:11:28: [6314:2] * Subject: FW: LIGHTING FIXTURES

Tue 2015-09-01 11:11:28: [6314:2] * Size (bytes): 1292502

Tue 2015-09-01 11:11:28: [6314:2] * Message-ID:

Tue 2015-09-01 11:11:28: [6314:2] Attempting SMTP connection to [xyz.com.pk]

Tue 2015-09-01 11:11:28: [6314:2] Resolving MX records for [xyz.com.pk] (DNS Server: 10.10.1.10).

Tue 2015-09-01 11:11:28: [6314:2] * P=010 S=000 D=xyz.com.pk TTL=(10) MX=[igw5002.site4now.net]

Tue 2015-09-01 11:11:28: [6314:2] Attempting SMTP connection to [igw5002.site4now.net:25]

Tue 2015-09-01 11:11:28: [6314:2] Resolving A record for [igw5002.site4now.net] (DNS Server: 10.10.1.10).

Tue 2015-09-01 11:11:28: [6314:2] * D=igw5002.site4now.net TTL=(10) A=[208.118.63.21]

Tue 2015-09-01 11:11:28: [6314:2] * D=igw5002.site4now.net TTL=(10) A=[208.118.63.23]

Tue 2015-09-01 11:11:28: [6314:2] * D=igw5002.site4now.net TTL=(10) A=[208.118.63.5]

Tue 2015-09-01 11:11:28: [6314:2] * D=igw5002.site4now.net TTL=(10) A=[208.118.63.12]

Tue 2015-09-01 11:11:28: [6314:2] Randomly picked 208.118.**.** from list of A records

Tue 2015-09-01 11:11:28: [6314:2] Attempting SMTP connection to [208.118.**.**:25]

Tue 2015-09-01 11:11:28: [6314:2] Waiting for socket connection.

Tue 2015-09-01 11:11:28: [6314:2] * Connection established (203.170.**.**:24861 -> 208.118.**.**:25)

Tue 2015-09-01 11:11:28: [6314:2] Waiting for protocol to start.

Tue 2015-09-01 11:11:29: [6314:2] EHLO webmail.clipsal.com.pk

Tue 2015-09-01 11:11:29: [6314:2] MAIL From: SIZE=1292502

Tue 2015-09-01 11:11:30: [6314:2] RCPT To:

Tue 2015-09-01 11:11:31: [6314:2] DATA

I dont know about should i share this or not, but 5 emails were stuck in the queue from yesterday and they just delivered after a power restart of Network Switch :/

Is there could be any relation of the network switch in all this ?

Brand Representative for MDaemon Technologies

Most likely, the messages were stuck in the retry or remote queue and attempting to retry at intervals that are defined in MDaemon.

From the snippet, MDaemon is attempting to transfer the message to the recipient server, but there is a long delay:

Tue 2015-09-01 11:11:31: [6314:2] Sending to [208.118.**.**]
Tue 2015-09-01 11:12:28: [6314:2] * Winsock Error 10054

I can’t confirm that it was the switch, but it is possible it was the switch causing these network issues. You should be able to look at the Network Switch log to verify what it was doing while you were sending these messages.

Let me know if you require any more assistance and we’ll be happy to help.

Hi, thanks for the response IAN, but it was not a switch because after three hours again two emails are stuck in remote and then retry queue, one of them is at private/business domain and the other one is for gmail.com

I tried troubleshooting all the things and tired to troubleshoot the things.

I looked into every possible reason which can cause this issue i.e. SPF, Greylisting, Reverse DNS and etc.

Brand Representative for MDaemon Technologies

Thanks for the update.

Try sending another test message to one of these domains you can’t send to. When it fails, could you provide a SMTP out log snippet for the test message? I’d like to compare it to the snippet you provided above to see if the network error happens at the same point in the SMTP session.

Brand Representative for MDaemon Technologies

Sounds good. Let us know if we can help more and we’ll be happy to.

Can you confirm that any unused network cards have been disabled?

AceofSpades: Yes all unusable network cards are disable.

So far there is no error after resetting network card. Still i am monitoring, will update you shortly.

Thank you guys for your help and support 🙂

Again another email stuck. after so many hours.

Wed 2015-09-02 17:24:40: [358:2] Parsing message

Wed 2015-09-02 17:24:40: [358:2] * From: feroz@abc.com.pk

Wed 2015-09-02 17:24:40: [358:2] * Subject: =Price_&_availability_//__p?= =?UTF-8?Q?ak=C4=B1stan?=

Wed 2015-09-02 17:24:40: [358:2] * Size (bytes): 6431385

Wed 2015-09-02 17:24:40: [358:2] * Message-ID:

Wed 2015-09-02 17:24:40: [358:2] Attempting SMTP connection to [xyz.com.tr]

Wed 2015-09-02 17:24:40: [358:2] Resolving MX records for [xyz.com.tr] (DNS Server: 10.10.1.10).

Wed 2015-09-02 17:24:40: [358:2] * P=000 S=000 D=xyz.com.tr TTL=(200) MX=[aspmx.l.google.com]

Wed 2015-09-02 17:24:40: [358:2] Attempting SMTP connection to [aspmx.l.google.com:25]

Wed 2015-09-02 17:24:40: [358:2] Resolving A record for [aspmx.l.google.com] (DNS Server: 10.10.1.10).

Wed 2015-09-02 17:24:40: [358:2] * D=aspmx.l.google.com TTL=(3) A=[64.233.**.**]

Wed 2015-09-02 17:24:40: [358:2] Attempting SMTP connection to [64.233.1**.**:25]

Wed 2015-09-02 17:24:40: [358:2] Waiting for socket connection.

Wed 2015-09-02 17:24:40: [358:2] * Connection established (203.170.**.**:20042 -> 64.233.**.**:25)

Wed 2015-09-02 17:24:40: [358:2] Waiting for protocol to start.

Wed 2015-09-02 17:24:41: [358:2] EHLO webmail.abc.com.pk

Wed 2015-09-02 17:24:41: [358:2] MAIL From: SIZE=6431385

Wed 2015-09-02 17:24:41: [358:2] RCPT To:

Wed 2015-09-02 17:24:42: [358:2] DATA

Brand Representative for MDaemon Technologies

From the log snippets you’ve provided, the network error is happening in the same place during the SMTP session.

From an MDaemon standpoint, MDaemon is simply trying to transfer the message to the recipient mail server. However, something on the network is closing the connection during that transfer. Notice 20 seconds go by before the network error:

Wed 2015-09-02 17:24:42: [358:2] Sending to [64.233.1**.**]
Wed 2015-09-02 17:25:02: [358:2] * Winsock Error 10054

In this case, I would verify there isn’t anything installed on the MDaemon server that could be filtering these SMTP sessions, such as AntiVirus software.

If there isn’t anything installed on the MDaemon server that could be filtering this SMTP session, try doing a trace route from the MDaemon server to the recipient’s IP address (64.233.1**.**) to verify how the connection is routed. Are there any servers between your MDaemon server and the recipient server that you can see might be filtering these connections, such as a firewall, switch, ISP, etc.

If there isn’t anything installed on your MDaemon server or on the network on your side that could be filtering these connections, I’d suggest contacting the Administrator of the recipient mail server and compare the logs to verify if they are closing connections from your mail server for any reasons.

Источник

   kupec

31.07.13 — 10:19

Установил данную программу, зарегистрировал домэн, добавил пользователя с адресом юзер@домен.ру, если посылаю из внешки письмо данному пользователю то оно доходит, но если начинаю отвечать на это письмо то оно остается на сервере, хотя в нстройках демона стоит отправлять сразу на сервер получателя, подскажите что нужно сделать чтобы письмо уходило, строго не судите так как в этом деле не силен

   ДенисЧ

1 — 31.07.13 — 10:20

Может, ты всё-таки логи посмотришь?

   kupec

2 — 31.07.13 — 10:22

   ДенисЧ

3 — 31.07.13 — 10:24

Winsock Error 10060

Это значит, что получатель не отвечает.

Кстати, большинство публичных почтовиков давно на 25м порту не отвечают. Пошукай в его справке

   kupec

4 — 31.07.13 — 10:26

telnet smtp.yandex.ru 25 открывается

   kupec

5 — 31.07.13 — 10:32

(3) что за справка в которой шукать ?? )))

   ДенисЧ

6 — 31.07.13 — 10:34

(5) Яндексовая…

   kupec

7 — 31.07.13 — 10:34

в яндексе порт 25 есть однозначно

   ДенисЧ

8 — 31.07.13 — 10:34

И вообще — я тебе ещё вчера говорил, что не будут работать открытые почтовики релеями…

   kupec

9 — 31.07.13 — 10:39

ну а как же тогда сделать ?? (((

   ДенисЧ

10 — 31.07.13 — 10:40

(9)

|—|—|

|  |  |

|  |  |

|  0  |

|     |

   kupec

11 — 31.07.13 — 10:41

(10) эт что значит ???

   Builder

12 — 31.07.13 — 10:50

Обычно почта отправляется через SMTP вашего провайдера.

   Trotter

13 — 31.07.13 — 10:59

(11) Похоже на виселицу )

   kupec

14 — 31.07.13 — 11:09

MDaemon определяет что письмо должно отправиться на яндекс.ру и пытается соединиться с яндекс ру на 25 порт, вместо смтп.яндес.ру 25…вот в чем проблема

   Builder

15 — 31.07.13 — 11:11

Убери отправку прямо на сервер.

Позвони своему провайдеру, узнай его SMTP и пропиши его.

Все будет работать.

   kupec

16 — 31.07.13 — 11:11

так там должна быть аутентификация, пусть я её пропишу, но имя отправителя не будет совпадать с именем в аутентификации

   Builder

17 — 31.07.13 — 11:26

не нужна там идентификация как правило.

Ну или спроси у провайдера.

   kupec

18 — 31.07.13 — 11:50

Поменял в настроках DNS сервера, вместа адресов виндоус указал сервера провайдера. теперь напрямую на майл и рамблер отправляет а при отправке на яндекс сам яндекс возвращает следующее

Wed 2013-07-31 11:35:18: Parsing message <c:mdaemonqueuesremotepd50000000010.msg>

Wed 2013-07-31 11:35:18: *  From: admin@kupec.asuscomm.com

Wed 2013-07-31 11:35:18: *  To: alexei-kupec@yandex.ru

Wed 2013-07-31 11:35:18: *  Subject: =?koi8-r?B?8NLJ18XU?=

Wed 2013-07-31 11:35:18: *  Size (bytes): 2356

Wed 2013-07-31 11:35:18: *  Message-ID:

Wed 2013-07-31 11:35:18: Attempting SMTP connection to [yandex.ru]

Wed 2013-07-31 11:35:18: Resolving MX records for [yandex.ru] (DNS Server: 81.20.97.254)…

Wed 2013-07-31 11:35:18: *  P=010 S=000 D=yandex.ru TTL=(60) MX=[mx.yandex.ru]

Wed 2013-07-31 11:35:18: Attempting SMTP connection to [mx.yandex.ru:25]

Wed 2013-07-31 11:35:18: Resolving A record for [mx.yandex.ru] (DNS Server: 81.20.97.254)…

Wed 2013-07-31 11:35:18: *  D=mx.yandex.ru TTL=(12) A=[93.158.134.89]

Wed 2013-07-31 11:35:18: *  D=mx.yandex.ru TTL=(12) A=[213.180.193.89]

Wed 2013-07-31 11:35:18: *  D=mx.yandex.ru TTL=(12) A=[213.180.204.89]

Wed 2013-07-31 11:35:18: *  D=mx.yandex.ru TTL=(12) A=[77.88.21.89]

Wed 2013-07-31 11:35:18: *  D=mx.yandex.ru TTL=(12) A=[87.250.250.89]

Wed 2013-07-31 11:35:18: Randomly picked 93.158.134.89 from list of A records

Wed 2013-07-31 11:35:18: Attempting SMTP connection to [93.158.134.89:25]

Wed 2013-07-31 11:35:18: Waiting for socket connection…

Wed 2013-07-31 11:35:18: *  Connection established (192.168.0.100:3213 -> 93.158.134.89:25)

Wed 2013-07-31 11:35:18: Waiting for protocol to start…

Wed 2013-07-31 11:35:18: <— 220 mxfront4m.mail.yandex.net (Want to use Yandex.Mail for your domain? Visit http://pdd.yandex.ru)

Wed 2013-07-31 11:35:18: —> EHLO kupec.asuscomm.com

Wed 2013-07-31 11:35:18: <— 250-mxfront4m.mail.yandex.net

Wed 2013-07-31 11:35:18: <— 250-8BITMIME

Wed 2013-07-31 11:35:18: <— 250-PIPELINING

Wed 2013-07-31 11:35:18: <— 250-SIZE 42991616

Wed 2013-07-31 11:35:18: <— 250-DSN

Wed 2013-07-31 11:35:18: <— 250 ENHANCEDSTATUSCODES

Wed 2013-07-31 11:35:18: —> MAIL From:<admin@kupec.asuscomm.com> SIZE=2356

Wed 2013-07-31 11:35:18: <— 250 2.1.0 <admin@kupec.asuscomm.com> ok

Wed 2013-07-31 11:35:18: —> RCPT To:<alexei-kupec@yandex.ru>

Wed 2013-07-31 11:35:18: <— 250 2.1.5 <alexei-kupec@yandex.ru> recipient ok

Wed 2013-07-31 11:35:18: —> DATA

Wed 2013-07-31 11:35:18: <— 354 Enter mail, end with «.» on a line by itself

Wed 2013-07-31 11:35:18: Sending <c:mdaemonqueuesremotepd50000000010.msg> to [93.158.134.89]

Wed 2013-07-31 11:35:18: Transfer Complete

Wed 2013-07-31 11:35:19: <— 451 4.7.1 Sorry, the service is currently unavailable. Please come back later. AkBcmB7pzF-bD2iWYXc

Wed 2013-07-31 11:35:19: —> QUIT

Wed 2013-07-31 11:35:19: <— 221 2.0.0 Closing connection.

Wed 2013-07-31 11:35:19: Возраст этого сообщения равен 0 минутам; осталось 5 минут его нахождения в этой очереди

Wed 2013-07-31 11:35:19: SMTP session terminated (Bytes in/out: 486/2480)

Wed 2013-07-31 11:35:19: ———-

   Builder

19 — 31.07.13 — 12:32

Продолжайте дальше биться головой об стену.

Когда надоест — прочитайте (15).

   VlLight

20 — 31.07.13 — 12:36

   kupec

21 — 31.07.13 — 12:57

(20) что такое PTR ?

   kupec

22 — 31.07.13 — 13:02

(20) почитал…теперь начинаю немного понимать что к чему

   kupec

23 — 31.07.13 — 13:05

Кто нибудь знает ростелеком имеет SMTP-релей ?

   VlLight

24 — 31.07.13 — 13:09

А это проще через техподдержку их узнать, наверное.

Можете воспользоваться такой услугой от Яндекса: https://pdd.yandex.ru/domains_add/#tab=1. Я не пробовал, но пишут, что бесплатно

   kupec

25 — 31.07.13 — 13:20

(24) про это я тоже в курсе, спасибо

   oleg_km

26 — 31.07.13 — 14:21

(26) Усложняют зачем-то. Попробовал сам telnetoм сейчас отправить через mx.yandex.ru: из дома (белый IP, нет PTR-записи) получаю

«451 4.7.1 Sorry, the service is currently unavailable. Please come back later», с работы (белый IP, есть PTR) — всё OK — с интервалом в одну минуту. Получается, что вводит в заблуждение

Do these errors occur when sending to one specific domain, or are you getting these errors for all outgoing emails?

Further on what AceOfSpades mentioned.  

Without a snippet of the SMTP out log, I’m unable to verify the exact reason but the Winsock errors are network related errors.  Depending on where the errors are in the SMTP out transaction between the servers, it could clue you to what could be causing the issue.

Verify if there is anything on the network that could be filtering these outbound SMTP sessions, such as a third party Firewall, Windows Firewall, third party AntiVirus software, ISP, etc…

Feel free to PM me a snippet of the SMTP out logs where the issue is happening.  The SMTP out log can be found in the MDaemonLogs directory.

Let me know if I can help further.

Ian

Most likely, the messages were stuck in the retry or remote queue and attempting to retry at intervals that are defined in MDaemon.

From the snippet, MDaemon is attempting to transfer the message to the recipient server, but there is a long delay:

Tue 2015-09-01 11:11:31: [6314:2] Sending to [208.118.**.**]
Tue 2015-09-01 11:12:28: [6314:2] * Winsock Error 10054

I can’t confirm that it was the switch, but it is possible it was the switch causing these network issues.  You should be able to look at the Network Switch log to verify what it was doing while you were sending these messages.

Let me know if you require any more assistance and we’ll be happy to help.

Thanks for the update.  

Try sending another test message to one of these domains you can’t send to.  When it fails, could you provide a SMTP out log snippet for the test message?  I’d like to compare it to the snippet you provided above to see if the network error happens at the same point in the SMTP session.

Ian

Sounds good.  Let us know if we can help more and we’ll be happy to.

Can you confirm that any unused network cards have been disabled?

From the log snippets you’ve provided, the network error is happening in the same place during the SMTP session.

From an MDaemon standpoint, MDaemon is simply trying to transfer the message to the recipient mail server.  However, something on the network is closing the connection during that transfer.  Notice 20 seconds go by before the network error:

Wed 2015-09-02 17:24:42: [358:2] Sending to [64.233.1**.**]
Wed 2015-09-02 17:25:02: [358:2] * Winsock Error 10054

In this case, I would verify there isn’t anything installed on the MDaemon server that could be filtering these SMTP sessions, such as AntiVirus software.  

If there isn’t anything installed on the MDaemon server that could be filtering this SMTP session, try doing a trace route from the MDaemon server to the recipient’s IP address (64.233.1**.**) to verify how the connection is routed.  Are there any servers between your MDaemon server and the recipient server that you can see might be filtering these connections, such as a firewall, switch, ISP, etc…?

If there isn’t anything installed on your MDaemon server or on the network on your side that could be filtering these connections, I’d suggest contacting the Administrator of the recipient mail server and compare the logs to verify if they are closing connections from your mail server for any reasons.  

Are you referring to being stuck remote/retry queue?

I can’t think of any reason why SecurityPlus would be the cause of this issue.  SecurityPlus will scan the message as it comes into MDaemon, not as the message is routed to the remote queue and transferred to the recipient server.

The message ID for the last session you provided is:

010201d0e577$d179e540$746dafc0$@com.pk

Verify if SecurityPlus scanned this message as it came into the server, and if it did, were there any issues with the scan?  You can verify with the message ID above and finding it in the AntiVirus.log file.  

Thanks, let me know.

Thanks for the update on this.  

If you have any other questions let us know.

Ian

Здравствуйте!
Почтовый сервер — Mdaemon 15.0.1. Операционная система — Windows Server 2003 R2 Enterprise Edition.
Некоторые сообщения не отправляются и остаются в Удаленной очереди. В логе SMTP out такие сообщения:
1.
Tue 2018-12-11 11:07:45.831: Session 517348; child 0001
Tue 2018-12-11 11:07:45.831: Parsing message
Tue 2018-12-11 11:07:45.831: * From: chfvfdvuev.zm@dgstk.ru
Tue 2018-12-11 11:07:45.831: * To: matveedsv@mrser.ru
Tue 2018-12-11 11:07:45.831: * Subject:
Tue 2018-12-11 11:07:45.831: * Size (bytes): 847427
Tue 2018-12-11 11:07:45.831: * Message-ID: <004d01d49128$52e31480$f8a93d80$@dgstk.ru>
Tue 2018-12-11 11:07:45.847: Resolving MX record for mrser.ru (DNS Server: 192.168.5.129)…
Tue 2018-12-11 11:07:46.003: * P=020 S=000 D=mrser.ru TTL=(10) MX=[mail.mrser.ru]
Tue 2018-12-11 11:07:46.003: * P=030 S=001 D=mrser.ru TTL=(10) MX=[mail1.mrser.ru]
Tue 2018-12-11 11:07:46.003: Attempting SMTP connection to mail.mrser.ru
Tue 2018-12-11 11:07:46.003: Resolving A record for mail.mrser.ru (DNS Server: 192.168.5.129)…
Tue 2018-12-11 11:07:46.003: * D=mail.mrser.ru TTL=(10) A=[92.42.8.82]
Tue 2018-12-11 11:07:46.003: Attempting SMTP connection to 92.42.8.82:25
Tue 2018-12-11 11:07:46.003: * 92.42.8.82 in connection failure cache for up to 5 minutes due to previous connection failure(s)
Tue 2018-12-11 11:07:46.003: Attempting SMTP connection to mail1.mrser.ru
Tue 2018-12-11 11:07:46.003: Resolving A record for mail1.mrser.ru (DNS Server: 192.168.5.129)…
Tue 2018-12-11 11:07:46.003: * D=mail1.mrser.ru TTL=(8) A=[91.143.157.2]
Tue 2018-12-11 11:07:46.003: Attempting SMTP connection to 91.143.157.2:25
Tue 2018-12-11 11:07:46.003: Waiting for socket connection…
Tue 2018-12-11 11:07:46.034: * Connection established 192.168.5.133:2913 —> 91.143.157.2:25
Tue 2018-12-11 11:07:46.034: Waiting for protocol to start…
Tue 2018-12-11 11:07:46.050: <— 220 mail.mrser.ru ESMTP MDaemon 15.0.3; Tue, 11 Dec 2018 11:07:45 +0300
Tue 2018-12-11 11:07:46.066: —> EHLO mail2.dgstk.ru
Tue 2018-12-11 11:07:46.081: <— 250-mail.mrser.ru Hello mail2.dgstk.ru, pleased to meet you
Tue 2018-12-11 11:07:46.081: <— 250-ETRN
Tue 2018-12-11 11:07:46.081: <— 250-AUTH LOGIN CRAM-MD5 PLAIN
Tue 2018-12-11 11:07:46.081: <— 250-8BITMIME
Tue 2018-12-11 11:07:46.081: <— 250-ENHANCEDSTATUSCODES
Tue 2018-12-11 11:07:46.081: <— 250 SIZE 16000000
Tue 2018-12-11 11:07:46.081: —> MAIL From: SIZE=847427
Tue 2018-12-11 11:07:46.112: <— 250 2.1.0 Sender OK
Tue 2018-12-11 11:07:46.112: —> RCPT To:
Tue 2018-12-11 11:07:46.144: <— 250 2.1.5 Recipient OK
Tue 2018-12-11 11:07:46.144: —> DATA
Tue 2018-12-11 11:07:46.159: <— 354 Enter mail, end with .
Tue 2018-12-11 11:07:46.159: Sending to [91.143.157.2]
Tue 2018-12-11 11:08:05.175: * Socket error 10054 — Соединение было перезапущено на друго конце!
Tue 2018-12-11 11:08:05.175: Ошибка при записи в сокет
Tue 2018-12-11 11:08:05.175: Socket connection closed by the other side (how rude!)
Tue 2018-12-11 11:08:05.175: * Socket error 10053 — Соединение отменено.
Tue 2018-12-11 11:08:05.175: Соединение прервано
Tue 2018-12-11 11:08:05.175: * Возраст этого сообщения равен 2 минутам; осталось 58 минут его нахождения в этой очереди

2.
Tue 2018-12-11 11:07:55.941: Session 517355; child 0003
Tue 2018-12-11 11:07:55.941: Parsing message
Tue 2018-12-11 11:07:55.941: * From: djabrailova.im@dgstk.ru
Tue 2018-12-11 11:07:55.941: * To: kaspb@mail.ru
Tue 2018-12-11 11:07:55.941: * Subject:
Tue 2018-12-11 11:07:55.941: * Size (bytes): 1609218
Tue 2018-12-11 11:07:55.941: * Message-ID:
Tue 2018-12-11 11:07:55.956: Resolving MX record for mail.ru (DNS Server: 192.168.5.129)…
Tue 2018-12-11 11:07:55.956: * P=010 S=000 D=mail.ru TTL=(9) MX=[mxs.mail.ru]
Tue 2018-12-11 11:07:55.956: Attempting SMTP connection to mxs.mail.ru
Tue 2018-12-11 11:07:55.956: Resolving A record for mxs.mail.ru (DNS Server: 192.168.5.129)…
Tue 2018-12-11 11:07:55.956: * D=mxs.mail.ru TTL=(0) A=[94.100.180.104]
Tue 2018-12-11 11:07:55.956: * D=mxs.mail.ru TTL=(0) A=[94.100.180.31]
Tue 2018-12-11 11:07:55.956: Randomly picked 94.100.180.31 from list of possible hosts
Tue 2018-12-11 11:07:55.956: Attempting SMTP connection to 94.100.180.31:25
Tue 2018-12-11 11:07:55.956: Waiting for socket connection…
Tue 2018-12-11 11:08:16.941: * Socket error 10060 — Тайм-аут соединения.
Tue 2018-12-11 11:08:16.941: * 94.100.180.31 added to connection failure cache for 5 minutes
Tue 2018-12-11 11:08:16.941: * Возраст этого сообщения равен 0 минутам; осталось 60 минут его нахождения в этой очереди
Tue 2018-12-11 11:08:16.941: SMTP session terminated (Bytes in/out: 0/0)

При этом телнетом 94.100.180.31:25 открывается.