search

aio-libs / aiosmtpd

A reimplementation of the Python stdlib smtpd.py based on asyncio.
https://aiosmtpd.aio-libs.org
Apache License 2.0
319 stars 96 forks source link

TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy #362

Open 1756816846 opened 1 year ago

1756816846 commented 1 year ago

Traceback (most recent call last): File "C:/Users/Darkness/Desktop/crazy-email-recv-srv-master/dd.py", line 11, in controller.start() File "D:\python37\lib\site-packages\aiosmtpd\controller.py", line 315, in start "SMTP server started, but not responding within allotted time. " TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy. Try increasing the ready_timeout parameter. image

wevsty commented 1 year ago

On Windows: You can try the ipconfig command to confirm the local IP address.

Plaese make sure that the IP 192.168.1.3 is the local IP and that there is no firewall blocking incoming connections.

1756816846 commented 1 year ago

I run it on my computer, the firewall is turned off, and there is no anti-virus software

------------------ 原始邮件 ------------------ 发件人: "aio-libs/aiosmtpd" @.>; 发送时间: 2023年1月8日(星期天) 晚上8:35 @.>; @.**@.>; 主题: Re: [aio-libs/aiosmtpd] TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy (Issue #362)

You can try the ipconfig command to confirm the local IP address. Plaese make sure that the IP 192.168.1.3 is the local IP and that there is no firewall blocking incoming connections.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

wevsty commented 1 year ago

I run it on my computer, the firewall is turned off, and there is no anti-virus software

I run the same code with aiosmtpd 1.4.3 and it does not reproduce the problem. My suggestion is still to check if the local IP address is correct, or you can bind 127.0.0.1 to test if you have the same fault.

If bind 127.0.0.1 is successful, you can run ipconfig and post the output to help diagnose the problem.

pepoluan commented 1 year ago

I run it on my computer, the firewall is turned off, and there is no anti-virus software

Yes, as @wevsty mentioned, can you verify that your computer's IP address is 192.168.1.3 and that IP address is active?

With no further information from you, I will close this issue because your error is not reproducible.