Mdaemon socket error 10054 соединение было перезапущено на другом конце

Socket error 10054 соединение было перезапущено на другом конце This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions. Answered by: Question I am using SMTPClient to send email. However, I get feedback from customer that, some user doesn’t receive email from our application. it only happens randomly. From our […]

Содержание

  1. Socket error 10054 соединение было перезапущено на другом конце
  2. Answered by:
  3. Question
  4. Answers
  5. All replies
  6. An application may receive the «10054» error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed
  7. Symptoms
  8. Resolution
  9. Hotfix information
  10. Prerequisites
  11. Registry information
  12. Restart requirement
  13. Hotfix replacement information
  14. File information
  15. Mdaemon 14.5 Winsock Error 10054
  16. Popular Topics in Email
  17. 6 Replies
  18. Read these next.
  19. poor wifi, school’s third floor
  20. Need help crafting a job posting for an IT Pro
  21. Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal
  22. Spark! Pro series – 13th January 2023
  23. Ошибка Windows Sockets 10054

Socket error 10054 соединение было перезапущено на другом конце

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I am using SMTPClient to send email. However, I get feedback from customer that, some user doesn’t receive email from our application. it only happens randomly.

From our application, no exception was thrown. However, when check on their email server log, we found the below

I have tried suggestions found from google

1. Wrapped SMTPClient and implement IDisposable — tested no working

Any other ideas?

Answers

Try the following link I found on mdaemon forum and let me know the result.

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

  • Marked as answer by Herro wong Microsoft contingent staff Tuesday, March 18, 2014 7:32 AM

Winsock error 10054 shows that server encounter some mistake and then the connection is closed by the server. For more information about Winsock error, please refer to the following link. http://msdn.microsoft.com/en-us/library/aa924071.aspx.

If you control the server, I think you should do some troubleshooting on server. If not, I recommend you wait some time and then reconnect to server after you catch this error.

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

From the .NET code, no exception is actually captured.

What to troublesbhoot at server side ?

From the description of the log, I know that the server turn off the connection when the remote host is suddenly stopped or the remote host uses a hard close. If you are using IIS SMTP Server, I recommend you post thread on IIS forum for effective response. http://forums.iis.net/1047.aspx/1?Setup.

If you just want to work around this issue, you can write some code to reconnect to server after a while.

> From the .NET code, no exception is actually captured.

Really? How did you know there is an exception when server closes the connection?

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Источник

An application may receive the «10054» error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed

Symptoms

Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.

A Transport Driver Interface (TDI) filter driver is installed on the computer. For example, a TDI filter driver is installed when you install McAfee VirusScan.

An application opens a TCP listening port to receive connections.

In this scenario, the application may receive the following error message:

WSAECONNRESET (10054) Connection reset by peer.
A existing connection was forcibly closed by the remote host.

This issue occurs because the TCP/IP driver does not close an incomplete TCP connection. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection.

Resolution

To resolve this issue, install this hotfix.

Note This hotfix temporarily resolves this issue for application vendors before they migrate their implementation to Windows Filtering Platform (WFP). These application vendors use the TDI filter driver or the TDI extension driver (TDX) on a computer that is running Windows 7 or Windows Server 2008 R2.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in WindowsTo enable the hotfix in this package, follow these steps:

In Registry Editor, locate the following registry subkey:

If you are running a 32-bit operating system, perform the following step:

Right-click the Parameters registry subkey, point to New, and then click DWORD Value.If you are running a 64-bit operating system, perform the following step:

Right-click the Parameters registry subkey, point to New, and then click DWORD (32-bit) Value.

Rename the new registry entry to TdxPrematureConnectIndDisabled and set the value to 1.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Источник

Mdaemon 14.5 Winsock Error 10054

i am facing issue with my mdaemon server, its working accordingly and most of my email send through mdaemon and clients are getting my mail too but some email not sending i dont know whats the actual problem i have been talk with many professionals but still getting same error, i am sharing email server log kindly help me.

  • local_offer Tagged Items
  • email

Popular Topics in Email

Brand Representative for MDaemon Technologies

Winsock 10054 errors usually indicate that the other server is resetting the connection.

Is this happening with messages from specific senders/domains?

Do you have a firewall, proxy, or other device that mail is routed through before it reaches MDaemon?

You can find more troubleshooting tips in this discussion on our forums:

  • local_offer Tagged Items
  • MDaemon Email Server star 4.4

Brand Representative for MDaemon Technologies

yes we are using firewall which is ASA 5508-X but we are not blocking inside traffic

Brand Representative for MDaemon Technologies

Your router’s MTU settings might be a possible cause. Here’s more:

thanks for your support issue has been solved my firewall logs showed esmtp session block i just run a command on firewall no esmtp inspect.

Brand Representative for MDaemon Technologies

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

Ошибка Windows Sockets 10054

Причины возникновения
Причины этой ошибки разняться по своей «природе», но их объединяето то, что уже существующее (т.е. ранее установленое) соединение с клиентом разрывает сервер.

1. С версии 8.1.11 включен циклический перезапуск процессов, по наступлению интервала происходит автоматический перезапуск рабочих процессов rphost.

2. В некоторых случаях причиной ошибки могут стать утечки памяти.

3. Действия администратора в консоли (команда удалить пользователя)

4. Процесс rphost на серверном компьютере завершился аварийно

5. Ошибочное принятие высокой интенсивности пользователей за атаку на протокол в некоторых случаях Windows

6. Устаревание данных в кэшах

7. Плохо отслеживаемые события в фоновых процессах

8. Нестандартные запросы могут приводить к падениям rphost

Способы устранения
1. с 8.1.11 включен циклический перезапуск процессов, для анализа этого события на компьютере сервера 1С:Предприятия необходимо включить запись в технологический журнал событий PROC (пример файла logcfg.xml).
Когда процесс выключается, будет выведено событие PROC со свойством Txt=Process become disable.
Когда процесс останавливается, будет выведено событие PROC со свойством Txt=Process terminated. Any clients finished with error. Если аварийные завершения работы пользователей совпадают по времени с выводом этого события, то причиной является принудительная остановка рабочего процесса либо администратором (через консоль кластера), либо вследствие автоматического перезапуска.

2. перезагрузить сервер
3. убедиться, что причиной являются/не являются действия администратора в консоли
4. создать на сервере приложения два или более рабочих процесса, чтобы иметь возможность переподключиться в случаи сбоя рабочего процесса
5. Запусти программу regedit.exe, добавь новое значение типа DWORD с именем SynAttackProtect в раздел реестра HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters и присвой ему значение 00000000
Имеет смысл делать для ОС Windows 2003 SP1 (http://msdn.microsoft.com/ru-ru/library/ms189083.aspx).

6. arp -d *
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
nbtstat -RR

7. отключить фоновые процессы во всех базах

8. найти технологическим журналом запрос, приводящий к падению

p.s. Кроме того, 54 ошибку можно получить на релизах 81(SQL) в типовой ТиС (демо, взятой с ИТС) релиз. 954 в клиент-серверном варианте.

обойти можно так:

— выполните конвертацию в файловый фариант информационной базы 1С:Предприятия 8.1,
— выгрузите полученную информационную базу в файл,
— загрузите в клиент-серверный вариант информационной базы 1С:Предприятия 8.1.

Источник

Источник

Здравствуйте!
Почтовый сервер — 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 открывается.

Источник

Socket errors are one of the most common problems that can occur when using a computer. The socket error 10054 is caused by an existing connection that is forcibly closed by the remote. The error could be solved by restarting your router, checking if the address of the computer or host is correct, scanning for malware and lastly trying to connect through a different port.

This is an error that occurred when attempting to connect with the server. The primary reason for this issue is due to a software or network problem. Error 10054 might also be caused by accidentally shutting down or disconnecting a program while the computer is attempting to establish contact with a server.

There might be a problem with your Internet connection or a proxy server shutting down server connections. The firewall might be malfunctioning and causing the connection to break, as it does with all concerns.

How to Fix Socket Error 10054

Restart Your Router or DNS

When you are connecting to a new network, it is best to restart your router. If the computer is able to make a direct connection with the internet, then the problem lies somewhere else and not with your network.

You can follow these steps to clear DNS cache:

  1. Click Windows Start and type Command Prompt.
  2. Right-click the Command prompt and select Run as Administrator.
  3. In the Command Prompt, type netsh winsock reset and press Enter key.
  4. Type netsh int ip reset and press Enter key.
  5. Type ipconfig /release and press Enter key.
  6. Type ipconfig /renew and press Enter key.
  7. Type ipconfig /flushdns and press Enter key.

Check if The Address of Your Computer or Host Is Correct

The default gateway address should be different from the IP address assigned by DHCP (Dynamic Host Configuration Protocol). When there’s no difference in these values, it shows that something might be wrong with the settings in all programs that are related to the internet like firewalls.

You can check this by typing in “ipconfig /all” on Command Prompt (which will show your IP address and default gateway).

Scan for Malware

When you suspect that malware might be causing the issue, then it’s time to scan again with an antivirus if necessary. Sometimes, even after restarting your computer and router, malware can still cause problems as they are installed on a deeper level into the system.

It is best to scan for Malware at least twice to make sure that any remaining traces of malicious programs have been detected. If the problem persists even after removing them from your computer, then you may need a deeper analysis or a complete reformatting of your machine.

Reboot Your Computer

It doesn’t matter whether you want to call it a “warm reboot” or a “cold boot”, but rebooting your computer is a basic step in troubleshooting any problems that could affect your PC performance.

Check Your Settings In All Programs That Are Related to the Internet (Like Firewalls)

If you don’t have enough knowledge about networking, then it’s best to consult with a network specialist when dealing with internet-related problems. Or if you still think that you can handle it on your own, then make sure to check and change all of your settings in every program related to the internet.

For instance, anything related to Skype or Firefox should be disabled especially if you suspect that these programs might cause this issue.

Try Connecting Through a Different Port

If nothing seems out of order regarding your router and hardware settings but socket error 10054 keeps on occurring, then it is best to try connecting through a different port.

These errors usually mean that there’s a problem with the connection settings where it creates a faulty connection between two programs for a specific port number. This means that you have to configure your network so that outgoing connections use other ports instead of the default one.

Источник

Просмотр полной версии : Help Срочно MDaemon Пожалуйста юзеры без почты

Arkasheg

15.08.2012, 11:10

Добрый день. Всем заранее спасибо за момощь. вот лог проблемы из MDaemon Server: v9.6.6. Это почта не доходит из вне. Еще проблема сообщения могут задваиваться приходить по 10 штук одному и тому человеку. Было всё в норме ничего никто не трогал, а тут раз и такое всю голову уже себе поломал. Отправляються письма без проблем.

Wed 2012-08-15 10:43:10: Session 3580; child 5
Wed 2012-08-15 10:36:33: MultiPOP получает почту от (pop3.timeweb.ru) для (Дмитрий Адаменко)
Wed 2012-08-15 10:36:33: MultiPOP полученная почта будет удалена с удаленного хоста!
Wed 2012-08-15 10:36:33: Устанавливаю MultiPOP подключение к [pop3.timeweb.ru:110]
Wed 2012-08-15 10:36:33: Разрешение A-записи для [pop3.timeweb.ru] (DNS-сервер: 212.96.96.38)…
Wed 2012-08-15 10:36:33: * D=pop3.timeweb.ru TTL=(0) A=[92.53.98.109]
Wed 2012-08-15 10:36:33: Устанавливаю MultiPOP подключение к [92.53.98.109:110]
Wed 2012-08-15 10:36:33: Ожидание подключения сокета…
Wed 2012-08-15 10:36:33: * Соединение установлено (127.0.0.1:4806 -> 92.53.98.109:110)
Wed 2012-08-15 10:36:33: Ожидание запуска протокола…
Wed 2012-08-15 10:36:33: <— +OK POP3 ready
Wed 2012-08-15 10:36:33: —> USER [email protected]
Wed 2012-08-15 10:36:33: <— +OK
Wed 2012-08-15 10:36:33: —> PASS ******
Wed 2012-08-15 10:36:34: <— +OK logged in.
Wed 2012-08-15 10:36:34: —> STAT
Wed 2012-08-15 10:36:34: <— +OK 9 49781954
Wed 2012-08-15 10:36:34: —> UIDL
Wed 2012-08-15 10:36:34: 1 UID4676-1294998612 — new message
Wed 2012-08-15 10:36:34: 2 UID4677-1294998612 — new message
Wed 2012-08-15 10:36:34: 3 UID4678-1294998612 — new message
Wed 2012-08-15 10:36:34: 4 UID4679-1294998612 — new message
Wed 2012-08-15 10:36:34: 5 UID4680-1294998612 — new message
Wed 2012-08-15 10:36:34: 6 UID4681-1294998612 — new message
Wed 2012-08-15 10:36:34: 7 UID4682-1294998612 — new message
Wed 2012-08-15 10:36:34: 8 UID4683-1294998612 — new message
Wed 2012-08-15 10:36:34: 9 UID4684-1294998612 — new message
Wed 2012-08-15 10:36:34: —> .
Wed 2012-08-15 10:36:34: —> NOOP
Wed 2012-08-15 10:36:34: <— +OK Yup.
Wed 2012-08-15 10:36:34: —> LIST 1
Wed 2012-08-15 10:36:34: <— +OK 1 2604312
Wed 2012-08-15 10:36:34: —> RETR 1
Wed 2012-08-15 10:36:34: <— +OK 2604312 octets follow.
Wed 2012-08-15 10:36:34: Creating temp file (MPOP): c:mdaemonqueuestemp42md50000000010.tmp
Wed 2012-08-15 10:38:00: Передача данных завершена <c:mdaemonqueuestemp42md50000000010.tmp>
Wed 2012-08-15 10:38:00: Создание сообщения successful: c:mdaemonqueuestemp42md50000000010.tmp
Wed 2012-08-15 10:38:00: —> DELE 1
Wed 2012-08-15 10:38:01: <— +OK Deleted.
Wed 2012-08-15 10:38:01: —> LIST 2
Wed 2012-08-15 10:38:02: <— +OK 2 10552749
Wed 2012-08-15 10:38:02: —> RETR 2
Wed 2012-08-15 10:38:02: <— +OK 10552749 octets follow.
Wed 2012-08-15 10:38:02: Creating temp file (MPOP): c:mdaemonqueuestemp45md50000000010.tmp
Wed 2012-08-15 10:43:10: * Winsock Error 10054 Соединение было перезапущено на друго конце!
Wed 2012-08-15 10:43:10: POP session complete (Bytes in/out: 11833980/102)
Wed 2012-08-15 10:43:10: ———-

Добавлено через 3 минуты

Wed 2012-08-15 00:00:41: Session 2872; child 1
Wed 2012-08-15 00:00:39: Parsing message <c:mdaemonqueuesremotepd75000019477.msg>
Wed 2012-08-15 00:00:39: * From: [email protected][84.54.224.39]
Wed 2012-08-15 00:00:39: * To: [email protected]
Wed 2012-08-15 00:00:39: * Subject: Mail Statistics Summary — [84.54.224.39] — Tue, 14 Aug 2012
Wed 2012-08-15 00:00:39: * Message-ID: <[email protected][84.54.224.39]>
Wed 2012-08-15 00:00:39: Устанавливаю SMTP подключение к [smtp.timeweb.ru]
Wed 2012-08-15 00:00:39: Устанавливаю SMTP подключение к [smtp.timeweb.ru:25]
Wed 2012-08-15 00:00:39: Разрешение A-записи для [smtp.timeweb.ru] (DNS-сервер: 212.96.96.38)…
Wed 2012-08-15 00:00:39: * D=smtp.timeweb.ru TTL=(0) A=[92.53.116.15]
Wed 2012-08-15 00:00:39: Устанавливаю SMTP подключение к [92.53.116.15:25]
Wed 2012-08-15 00:00:39: Ожидание подключения сокета…
Wed 2012-08-15 00:00:39: * Соединение установлено (192.168.1.33:2357 -> 92.53.116.15:25)
Wed 2012-08-15 00:00:39: Ожидание запуска протокола…
Wed 2012-08-15 00:00:39: <— 220 smtp.timeweb.ru ESMTP
Wed 2012-08-15 00:00:39: —> EHLO [84.54.224.39]
Wed 2012-08-15 00:00:40: <— 250-smtp.timeweb.ru Hello [84.54.224.39] [77.39.21.27]
Wed 2012-08-15 00:00:40: <— 250-SIZE 104857600
Wed 2012-08-15 00:00:40: <— 250-PIPELINING
Wed 2012-08-15 00:00:40: <— 250-AUTH PLAIN LOGIN
Wed 2012-08-15 00:00:40: <— 250-STARTTLS
Wed 2012-08-15 00:00:40: <— 250 HELP
Wed 2012-08-15 00:00:40: —> STARTTLS
Wed 2012-08-15 00:00:40: <— 220 TLS go ahead
Wed 2012-08-15 00:00:40: SSL negotiation successful (TLS 1.0, 2048 bit key exchange, 128 bit RC4 encryption)
Wed 2012-08-15 00:00:40: —> EHLO [84.54.224.39]
Wed 2012-08-15 00:00:40: <— 250-smtp.timeweb.ru Hello [84.54.224.39] [77.39.21.27]
Wed 2012-08-15 00:00:40: <— 250-SIZE 104857600
Wed 2012-08-15 00:00:40: <— 250-PIPELINING
Wed 2012-08-15 00:00:40: <— 250-AUTH PLAIN LOGIN
Wed 2012-08-15 00:00:40: <— 250 HELP
Wed 2012-08-15 00:00:40: —> AUTH LOGIN
Wed 2012-08-15 00:00:40: <— 334 VXNlcm5hbWU6
Wed 2012-08-15 00:00:40: —> YWRtaW4tc3R2QHl1Z3Byb20ucnU=
Wed 2012-08-15 00:00:40: <— 334 UGFzc3dvcmQ6
Wed 2012-08-15 00:00:40: —> TG1paDhBbkw0MEI=
Wed 2012-08-15 00:00:41: <— 235 Authentication succeeded
Wed 2012-08-15 00:00:41: —> MAIL From:<[email protected][84.54.224.39]> SIZE=15840
Wed 2012-08-15 00:00:41: <— 501 <[email protected][84.54.224.39]>: domain literals not allowed
Wed 2012-08-15 00:00:41: —> QUIT
Wed 2012-08-15 00:00:41: Message has no return path, it was deleted
Wed 2012-08-15 00:00:41: <— 221 smtp.timeweb.ru closing connection
Wed 2012-08-15 00:00:41: SMTP сессия отменена (Байт принято/передано: 472/291)

Добавлено через 6 минут

Wed 2012-08-15 01:02:18: Session 2593; child 1; thread 1396
Wed 2012-08-15 01:02:18: Принимаю SMTP подключение от [192.168.0.16:60764]
Wed 2012-08-15 01:02:18: —> 220 [84.54.216.158] ESMTP MDaemon 9.6.6; Wed, 15 Aug 2012 01:02:18 +0400
Wed 2012-08-15 01:02:18: <— EHLO SERVER-1C
Wed 2012-08-15 01:02:18: —> 250-[84.54.216.158] Hello SERVER-1C, pleased to meet you
Wed 2012-08-15 01:02:18: —> 250-ETRN
Wed 2012-08-15 01:02:18: —> 250-AUTH=LOGIN
Wed 2012-08-15 01:02:18: —> 250-AUTH LOGIN CRAM-MD5
Wed 2012-08-15 01:02:18: —> 250-8BITMIME
Wed 2012-08-15 01:02:18: —> 250-STARTTLS
Wed 2012-08-15 01:02:18: —> 250 SIZE 35000000
Wed 2012-08-15 01:02:18: <— AUTH LOGIN
Wed 2012-08-15 01:02:18: —> 334 VXNlcm5hbWU6
Wed 2012-08-15 01:02:18: <— YWRtaW5Ac2tsYWQuc3R2Lnl1Z3Byb20ucnU=
Wed 2012-08-15 01:02:18: —> 334 UGFzc3dvcmQ6
Wed 2012-08-15 01:02:18: <— ******
Wed 2012-08-15 01:02:18: —> 535 Authentication failed
Wed 2012-08-15 01:02:18: Соединение прервано
Wed 2012-08-15 01:02:18: SMTP сессия отменена (Байт принято/передано: 84/293)

ну оно вам черным по белоу пишет что
Wed 2012-08-15 00:00:41: —> MAIL From:<[email protected][84.54.224.39]> SIZE=15840
Wed 2012-08-15 00:00:41: <— 501 <[email protected][84.54.224.39]>: domain literals not allowed
501 оштбка это ошибка синтаксиса , я так понимаю получателю не нравиться ИП адрес вместо имено домена, в MAIL From:

в третем случае
535 Authentication failed
судя по логу не проходит авторизация вашего сервера 1С у мейлдемона.

Arkasheg

16.08.2012, 09:54

осталось разобраться с вот этим логом

Wed 2012-08-15 10:38:02: Creating temp file (MPOP): c:mdaemonqueuestemp45md50000000010.tmp
Wed 2012-08-15 10:43:10: * Winsock Error 10054 Соединение было перезапущено на друго конце!
Wed 2012-08-15 10:43:10: POP session complete (Bytes in/out: 11833980/102)
Wed 2012-08-15 10:43:10: ———-

Помогите пожалуйста меня юзеры уже сожрут скоро

Добавлено через 2 часа 6 минут
Это официальный ответ с Таймвеба откуда скачиваеться почта, как я понимаю это из за того что мой сервер не может скачать сообщение нет обращения к серверу с моего и он его закрывает

Добрый день.
Обратите внимание на время в записях:
Wed 2012-08-15 10:38:02: Creating temp file (MPOP):
c:\\mdaemon\\queues\\temp\\45\\md5000000 0010.tmp
Wed 2012-08-15 10:43:10: * Winsock Error 10054 Соединение было
перезапущено на друго конце!
Дело в том, что после получения письма, сессии активна, но не используется.
Сервер закрывает ожидающие сессии.
В случае непрерывной работы по отправке-получению писем — вы не увидите данной ошибки.

Это официальный ответ с Таймвеба откуда скачиваеться почта, как я понимаю это из за того что мой сервер не может скачать сообщение нет обращения к серверу с моего и он его закрывает
ну судя по всему Мдемон таки получает сообщения, только после этого не закрывает роо сессию с таймвебом, и сервер таймвеба обрывает ее по таймауту. А уж что потом с почтой происходит ХЗ. может антиспам не пропускает, или она падает в нежелательную почту или еще что..

Arkasheg

17.08.2012, 11:21

ну судя по всему Мдемон таки получает сообщения, только после этого не закрывает роо сессию с таймвебом, и сервер таймвеба обрывает ее по таймауту. А уж что потом с почтой происходит ХЗ. может антиспам не пропускает, или она падает в нежелательную почту или еще что..

Либо я чего то не понимаю либо поддержка мне просто дурит. как так если они говорят что мой сервер получает почту. Он её не получает потому что здоровый лог

Fri 2012-08-17 08:33:10: Session 1403; child 4
Fri 2012-08-17 08:32:54: MultiPOP получает почту от (pop3.timeweb.ru) для (admin)
Fri 2012-08-17 08:32:54: MultiPOP полученная почта будет удалена с удаленного хоста!
Fri 2012-08-17 08:32:54: Устанавливаю MultiPOP подключение к [pop3.timeweb.ru:110]
Fri 2012-08-17 08:32:54: Разрешение A-записи для [pop3.timeweb.ru] (DNS-сервер: 212.96.96.38)…
Fri 2012-08-17 08:32:54: * D=pop3.timeweb.ru TTL=(0) A=[92.53.98.109]
Fri 2012-08-17 08:32:54: Устанавливаю MultiPOP подключение к [92.53.98.109:110]
Fri 2012-08-17 08:32:54: Ожидание подключения сокета…
Fri 2012-08-17 08:32:54: * Соединение установлено (127.0.0.1:3550 -> 92.53.98.109:110)
Fri 2012-08-17 08:32:54: Ожидание запуска протокола…
Fri 2012-08-17 08:32:54: <— +OK POP3 ready
Fri 2012-08-17 08:32:54: —> USER [email protected]
Fri 2012-08-17 08:32:54: <— +OK
Fri 2012-08-17 08:32:54: —> PASS ******
Fri 2012-08-17 08:32:59: <— +OK logged in.
Fri 2012-08-17 08:32:59: —> STAT
Fri 2012-08-17 08:32:59: <— +OK 16 29223
Fri 2012-08-17 08:32:59: —> UIDL
Fri 2012-08-17 08:32:59: 1 UID10815-1295001712 — new message
Fri 2012-08-17 08:32:59: 2 UID10816-1295001712 — new message
Fri 2012-08-17 08:32:59: 3 UID10817-1295001712 — new message
Fri 2012-08-17 08:32:59: 4 UID10818-1295001712 — new message
Fri 2012-08-17 08:32:59: 5 UID10819-1295001712 — new message
Fri 2012-08-17 08:32:59: 6 UID10820-1295001712 — new message
Fri 2012-08-17 08:32:59: 7 UID10821-1295001712 — new message
Fri 2012-08-17 08:32:59: 8 UID10822-1295001712 — new message
Fri 2012-08-17 08:32:59: 9 UID10823-1295001712 — new message
Fri 2012-08-17 08:32:59: 10 UID10824-1295001712 — new message
Fri 2012-08-17 08:32:59: 11 UID10825-1295001712 — new message
Fri 2012-08-17 08:32:59: 12 UID10826-1295001712 — new message
Fri 2012-08-17 08:32:59: 13 UID10827-1295001712 — new message
Fri 2012-08-17 08:32:59: 14 UID10828-1295001712 — new message
Fri 2012-08-17 08:32:59: 15 UID10829-1295001712 — new message
Fri 2012-08-17 08:32:59: 16 UID10830-1295001712 — new message
Fri 2012-08-17 08:32:59: —> .
Fri 2012-08-17 08:32:59: —> NOOP
Fri 2012-08-17 08:32:59: <— +OK Yup.
Fri 2012-08-17 08:32:59: —> LIST 1
Fri 2012-08-17 08:32:59: <— +OK 1 1827
Fri 2012-08-17 08:32:59: —> RETR 1
Fri 2012-08-17 08:33:00: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:00: Creating temp file (MPOP): c:mdaemonqueuestemp12md50000000002.tmp
Fri 2012-08-17 08:33:00: Передача данных завершена <c:mdaemonqueuestemp12md50000000002.tmp>
Fri 2012-08-17 08:33:00: Создание сообщения successful: c:mdaemonqueuestemp12md50000000002.tmp
Fri 2012-08-17 08:33:00: —> DELE 1
Fri 2012-08-17 08:33:00: <— +OK Deleted.
Fri 2012-08-17 08:33:00: —> LIST 2
Fri 2012-08-17 08:33:00: <— +OK 2 1827
Fri 2012-08-17 08:33:00: —> RETR 2
Fri 2012-08-17 08:33:00: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:00: Creating temp file (MPOP): c:mdaemonqueuestemp13md50000000002.tmp
Fri 2012-08-17 08:33:01: Передача данных завершена <c:mdaemonqueuestemp13md50000000002.tmp>
Fri 2012-08-17 08:33:01: Создание сообщения successful: c:mdaemonqueuestemp13md50000000002.tmp
Fri 2012-08-17 08:33:01: —> DELE 2
Fri 2012-08-17 08:33:01: <— +OK Deleted.
Fri 2012-08-17 08:33:01: —> LIST 3
Fri 2012-08-17 08:33:01: <— +OK 3 1827
Fri 2012-08-17 08:33:01: —> RETR 3
Fri 2012-08-17 08:33:01: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:01: Creating temp file (MPOP): c:mdaemonqueuestemp14md50000000002.tmp
Fri 2012-08-17 08:33:02: Передача данных завершена <c:mdaemonqueuestemp14md50000000002.tmp>
Fri 2012-08-17 08:33:02: Создание сообщения successful: c:mdaemonqueuestemp14md50000000002.tmp
Fri 2012-08-17 08:33:02: —> DELE 3
Fri 2012-08-17 08:33:02: <— +OK Deleted.
Fri 2012-08-17 08:33:02: —> LIST 4
Fri 2012-08-17 08:33:02: <— +OK 4 1827
Fri 2012-08-17 08:33:02: —> RETR 4
Fri 2012-08-17 08:33:02: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:02: Creating temp file (MPOP): c:mdaemonqueuestemp15md50000000002.tmp
Fri 2012-08-17 08:33:02: Передача данных завершена <c:mdaemonqueuestemp15md50000000002.tmp>
Fri 2012-08-17 08:33:02: Создание сообщения successful: c:mdaemonqueuestemp15md50000000002.tmp
Fri 2012-08-17 08:33:02: —> DELE 4
Fri 2012-08-17 08:33:02: <— +OK Deleted.
Fri 2012-08-17 08:33:02: —> LIST 5
Fri 2012-08-17 08:33:02: <— +OK 5 1827
Fri 2012-08-17 08:33:02: —> RETR 5
Fri 2012-08-17 08:33:02: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:02: Creating temp file (MPOP): c:mdaemonqueuestemp16md50000000002.tmp
Fri 2012-08-17 08:33:03: Передача данных завершена <c:mdaemonqueuestemp16md50000000002.tmp>
Fri 2012-08-17 08:33:03: Создание сообщения successful: c:mdaemonqueuestemp16md50000000002.tmp
Fri 2012-08-17 08:33:03: —> DELE 5
Fri 2012-08-17 08:33:03: <— +OK Deleted.
Fri 2012-08-17 08:33:03: —> LIST 6
Fri 2012-08-17 08:33:03: <— +OK 6 1827
Fri 2012-08-17 08:33:03: —> RETR 6
Fri 2012-08-17 08:33:03: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:03: Creating temp file (MPOP): c:mdaemonqueuestemp17md50000000002.tmp
Fri 2012-08-17 08:33:03: Передача данных завершена <c:mdaemonqueuestemp17md50000000002.tmp>
Fri 2012-08-17 08:33:03: Создание сообщения successful: c:mdaemonqueuestemp17md50000000002.tmp
Fri 2012-08-17 08:33:03: —> DELE 6
Fri 2012-08-17 08:33:03: <— +OK Deleted.
Fri 2012-08-17 08:33:03: —> LIST 7
Fri 2012-08-17 08:33:03: <— +OK 7 1827
Fri 2012-08-17 08:33:03: —> RETR 7
Fri 2012-08-17 08:33:03: <— +OK 1827 octets follow.
Fri 2012-08-17 08:33:03: Creating temp file (MPOP): c:mdaemonqueuestemp18md50000000002.tmp
Fri 2012-08-17 08:33:03: Передача данных завершена <c:mdaemonqueuestemp18md50000000002.tmp>
Fri 2012-08-17 08:33:03: Создание сообщения successful: c:mdaemonqueuestemp18md50000000002.tmp
Fri 2012-08-17 08:33:03: —> DELE 7
Fri 2012-08-17 08:33:04: <— +OK Deleted.
Fri 2012-08-17 08:33:04: —> LIST 8
Fri 2012-08-17 08:33:04: <— +OK 8 1826
Fri 2012-08-17 08:33:04: —> RETR 8
Fri 2012-08-17 08:33:04: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:04: Creating temp file (MPOP): c:mdaemonqueuestemp19md50000000002.tmp
Fri 2012-08-17 08:33:05: Передача данных завершена <c:mdaemonqueuestemp19md50000000002.tmp>
Fri 2012-08-17 08:33:05: Создание сообщения successful: c:mdaemonqueuestemp19md50000000002.tmp
Fri 2012-08-17 08:33:05: —> DELE 8
Fri 2012-08-17 08:33:05: <— +OK Deleted.
Fri 2012-08-17 08:33:05: —> LIST 9
Fri 2012-08-17 08:33:05: <— +OK 9 1826
Fri 2012-08-17 08:33:05: —> RETR 9
Fri 2012-08-17 08:33:05: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:05: Creating temp file (MPOP): c:mdaemonqueuestemp20md50000000002.tmp
Fri 2012-08-17 08:33:05: Передача данных завершена <c:mdaemonqueuestemp20md50000000002.tmp>
Fri 2012-08-17 08:33:05: Создание сообщения successful: c:mdaemonqueuestemp20md50000000002.tmp
Fri 2012-08-17 08:33:05: —> DELE 9
Fri 2012-08-17 08:33:05: <— +OK Deleted.
Fri 2012-08-17 08:33:05: —> LIST 10
Fri 2012-08-17 08:33:05: <— +OK 10 1826
Fri 2012-08-17 08:33:05: —> RETR 10
Fri 2012-08-17 08:33:05: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:05: Creating temp file (MPOP): c:mdaemonqueuestemp21md50000000002.tmp
Fri 2012-08-17 08:33:05: Передача данных завершена <c:mdaemonqueuestemp21md50000000002.tmp>
Fri 2012-08-17 08:33:05: Создание сообщения successful: c:mdaemonqueuestemp21md50000000002.tmp
Fri 2012-08-17 08:33:05: —> DELE 10
Fri 2012-08-17 08:33:06: <— +OK Deleted.
Fri 2012-08-17 08:33:06: —> LIST 11
Fri 2012-08-17 08:33:06: <— +OK 11 1826
Fri 2012-08-17 08:33:06: —> RETR 11
Fri 2012-08-17 08:33:06: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:06: Creating temp file (MPOP): c:mdaemonqueuestemp22md50000000002.tmp
Fri 2012-08-17 08:33:07: Передача данных завершена <c:mdaemonqueuestemp22md50000000002.tmp>
Fri 2012-08-17 08:33:07: Создание сообщения successful: c:mdaemonqueuestemp22md50000000002.tmp
Fri 2012-08-17 08:33:07: —> DELE 11
Fri 2012-08-17 08:33:07: <— +OK Deleted.
Fri 2012-08-17 08:33:07: —> LIST 12
Fri 2012-08-17 08:33:07: <— +OK 12 1826
Fri 2012-08-17 08:33:07: —> RETR 12
Fri 2012-08-17 08:33:07: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:07: Creating temp file (MPOP): c:mdaemonqueuestemp23md50000000002.tmp
Fri 2012-08-17 08:33:07: Передача данных завершена <c:mdaemonqueuestemp23md50000000002.tmp>
Fri 2012-08-17 08:33:07: Создание сообщения successful: c:mdaemonqueuestemp23md50000000002.tmp
Fri 2012-08-17 08:33:07: —> DELE 12
Fri 2012-08-17 08:33:07: <— +OK Deleted.
Fri 2012-08-17 08:33:07: —> LIST 13
Fri 2012-08-17 08:33:07: <— +OK 13 1826
Fri 2012-08-17 08:33:07: —> RETR 13
Fri 2012-08-17 08:33:07: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:07: Creating temp file (MPOP): c:mdaemonqueuestemp24md50000000002.tmp
Fri 2012-08-17 08:33:08: Передача данных завершена <c:mdaemonqueuestemp24md50000000002.tmp>
Fri 2012-08-17 08:33:08: Создание сообщения successful: c:mdaemonqueuestemp24md50000000002.tmp
Fri 2012-08-17 08:33:08: —> DELE 13
Fri 2012-08-17 08:33:08: <— +OK Deleted.
Fri 2012-08-17 08:33:08: —> LIST 14
Fri 2012-08-17 08:33:08: <— +OK 14 1826
Fri 2012-08-17 08:33:08: —> RETR 14
Fri 2012-08-17 08:33:08: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:08: Creating temp file (MPOP): c:mdaemonqueuestemp25md50000000002.tmp
Fri 2012-08-17 08:33:08: Передача данных завершена <c:mdaemonqueuestemp25md50000000002.tmp>
Fri 2012-08-17 08:33:08: Создание сообщения successful: c:mdaemonqueuestemp25md50000000002.tmp
Fri 2012-08-17 08:33:08: —> DELE 14
Fri 2012-08-17 08:33:08: <— +OK Deleted.
Fri 2012-08-17 08:33:08: —> LIST 15
Fri 2012-08-17 08:33:09: <— +OK 15 1826
Fri 2012-08-17 08:33:09: —> RETR 15
Fri 2012-08-17 08:33:09: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:09: Creating temp file (MPOP): c:mdaemonqueuestemp26md50000000002.tmp
Fri 2012-08-17 08:33:10: Передача данных завершена <c:mdaemonqueuestemp26md50000000002.tmp>
Fri 2012-08-17 08:33:10: Создание сообщения successful: c:mdaemonqueuestemp26md50000000002.tmp
Fri 2012-08-17 08:33:10: —> DELE 15
Fri 2012-08-17 08:33:10: <— +OK Deleted.
Fri 2012-08-17 08:33:10: —> LIST 16
Fri 2012-08-17 08:33:10: <— +OK 16 1826
Fri 2012-08-17 08:33:10: —> RETR 16
Fri 2012-08-17 08:33:10: <— +OK 1826 octets follow.
Fri 2012-08-17 08:33:10: Creating temp file (MPOP): c:mdaemonqueuestemp27md50000000002.tmp
Fri 2012-08-17 08:33:10: Передача данных завершена <c:mdaemonqueuestemp27md50000000002.tmp>
Fri 2012-08-17 08:33:10: Создание сообщения successful: c:mdaemonqueuestemp27md50000000002.tmp
Fri 2012-08-17 08:33:10: —> DELE 16
Fri 2012-08-17 08:33:10: <— +OK Deleted.
Fri 2012-08-17 08:33:10: —> QUIT
Fri 2012-08-17 08:33:10: <— +OK Bye-bye.
Fri 2012-08-17 08:33:10: POP session complete (Bytes in/out: 31096/474)

Добавлено через 5 минут
Да и вообще как такое может быть? вот два лога за один день с разницой в 10 минут при этом никто ничего не трогал и не менял в настройках

Fri 2012-08-17 08:34:28: Session 1404; child 5
Fri 2012-08-17 08:32:54: MultiPOP получает почту от (pop3.timeweb.ru) для (Дмитрий Адаменко)
Fri 2012-08-17 08:32:54: MultiPOP полученная почта будет удалена с удаленного хоста!
Fri 2012-08-17 08:32:54: Устанавливаю MultiPOP подключение к [pop3.timeweb.ru:110]
Fri 2012-08-17 08:32:54: Разрешение A-записи для [pop3.timeweb.ru] (DNS-сервер: 212.96.96.38)…
Fri 2012-08-17 08:32:54: * D=pop3.timeweb.ru TTL=(0) A=[92.53.98.109]
Fri 2012-08-17 08:32:54: Устанавливаю MultiPOP подключение к [92.53.98.109:110]
Fri 2012-08-17 08:32:54: Ожидание подключения сокета…
Fri 2012-08-17 08:32:54: * Соединение установлено (127.0.0.1:3553 -> 92.53.98.109:110)
Fri 2012-08-17 08:32:54: Ожидание запуска протокола…
Fri 2012-08-17 08:32:54: <— +OK POP3 ready
Fri 2012-08-17 08:32:54: —> USER [email protected]
Fri 2012-08-17 08:32:54: <— +OK
Fri 2012-08-17 08:32:54: —> PASS ******
Fri 2012-08-17 08:32:59: <— +OK logged in.
Fri 2012-08-17 08:32:59: —> STAT
Fri 2012-08-17 08:32:59: <— +OK 1 3299013
Fri 2012-08-17 08:32:59: —> UIDL
Fri 2012-08-17 08:32:59: 1 UID4702-1294998612 — new message
Fri 2012-08-17 08:32:59: —> .
Fri 2012-08-17 08:32:59: —> NOOP
Fri 2012-08-17 08:32:59: <— +OK Yup.
Fri 2012-08-17 08:32:59: —> LIST 1
Fri 2012-08-17 08:32:59: <— +OK 1 3299013
Fri 2012-08-17 08:32:59: —> RETR 1
Fri 2012-08-17 08:32:59: <— +OK 3299013 octets follow.
Fri 2012-08-17 08:32:59: Creating temp file (MPOP): c:mdaemonqueuestemp11md50000000002.tmp
Fri 2012-08-17 08:34:28: * Winsock Error 10054 Соединение было перезапущено на друго конце!
Fri 2012-08-17 08:34:28: POP session complete (Bytes in/out: 2641801/78)

Fri 2012-08-17 08:44:47: Session 1421; child 5
Fri 2012-08-17 08:42:55: MultiPOP получает почту от (pop3.timeweb.ru) для (Дмитрий Адаменко)
Fri 2012-08-17 08:42:55: MultiPOP полученная почта будет удалена с удаленного хоста!
Fri 2012-08-17 08:42:55: Устанавливаю MultiPOP подключение к [pop3.timeweb.ru:110]
Fri 2012-08-17 08:42:55: Разрешение A-записи для [pop3.timeweb.ru] (DNS-сервер: 212.96.96.38)…
Fri 2012-08-17 08:42:55: * D=pop3.timeweb.ru TTL=(0) A=[92.53.98.104]
Fri 2012-08-17 08:42:55: Устанавливаю MultiPOP подключение к [92.53.98.104:110]
Fri 2012-08-17 08:42:55: Ожидание подключения сокета…
Fri 2012-08-17 08:42:55: * Соединение установлено (127.0.0.1:4032 -> 92.53.98.104:110)
Fri 2012-08-17 08:42:55: Ожидание запуска протокола…
Fri 2012-08-17 08:42:56: <— +OK POP3 ready
Fri 2012-08-17 08:42:56: —> USER [email protected]
Fri 2012-08-17 08:42:56: <— +OK
Fri 2012-08-17 08:42:56: —> PASS ******
Fri 2012-08-17 08:42:56: <— +OK logged in.
Fri 2012-08-17 08:42:56: —> STAT
Fri 2012-08-17 08:42:56: <— +OK 1 3299013
Fri 2012-08-17 08:42:56: —> UIDL
Fri 2012-08-17 08:42:56: 1 UID4702-1294998612 — new message
Fri 2012-08-17 08:42:56: —> .
Fri 2012-08-17 08:42:56: —> NOOP
Fri 2012-08-17 08:42:56: <— +OK Yup.
Fri 2012-08-17 08:42:56: —> LIST 1
Fri 2012-08-17 08:42:56: <— +OK 1 3299013
Fri 2012-08-17 08:42:56: —> RETR 1
Fri 2012-08-17 08:42:56: <— +OK 3299013 octets follow.
Fri 2012-08-17 08:42:56: Creating temp file (MPOP): c:mdaemonqueuestemp29md50000000002.tmp
Fri 2012-08-17 08:44:47: Передача данных завершена <c:mdaemonqueuestemp29md50000000002.tmp>
Fri 2012-08-17 08:44:47: Создание сообщения successful: c:mdaemonqueuestemp29md50000000002.tmp
Fri 2012-08-17 08:44:47: —> DELE 1
Fri 2012-08-17 08:44:47: <— +OK Deleted.
Fri 2012-08-17 08:44:47: —> QUIT
Fri 2012-08-17 08:44:47: <— +OK Bye-bye.
Fri 2012-08-17 08:44:47: POP session complete (Bytes in/out: 3299323/92)

sakhalin64

17.08.2012, 13:59

Наезжайте на поддерку,это их косяки

vBulletin® v3.8.9, Copyright ©2000-2023, vBulletin Solutions, Inc.

Источник

Понравилась статья? Поделить с друзьями:
  • Mdaemon letsencrypt error the challenge did not complete
  • Md5 error binary is invalid что это
  • Md5 error binary is invalid odin как исправить
  • Md unwind support h 65 47 error dereferencing pointer to incomplete type struct ucontext
  • Md 0011 30024 ошибка