[SOLVED]socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx

Raise/discuss any potential issues with MailEnable for consideration in project issue register.
Post Reply
poweredge
Posts: 157
Joined: Sat May 29, 2021 11:16 am

[SOLVED]socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx

Post by poweredge »

Recently, I've encountered a strange problem that ONLY one domain cannot send email to our ME email server.

May I know what could be the problem? Thanks in advance

================
Result: [AE3F2D260C8D4C43B299613D43DE8BE2.MAI] was not routed from the SMTP inbound message queue by the local MTA Service.
This may indicate the message was never fully received, or rerouted/deleted by a third party application or filter.
If the server is in a mail cluster, check logs on other servers.

SMTP Debug log matches:
12/08/22 12:51:33 ME-I0070: [AE3F2D260C8D4C43B299613D43DE8BE2.MAI] (recv) socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx.
Important: Message ID [AE3F2D260C8D4C43B299613D43DE8BE2.MAI] has not been routed through MailEnable queues. Check the log details for the reason. If in a cluster you will need to check each cluster server log files.
Last edited by poweredge on Tue Feb 21, 2023 4:37 am, edited 2 times in total.

poweredge
Posts: 157
Joined: Sat May 29, 2021 11:16 am

Re: socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx

Post by poweredge »

Turn out to be sender's network is very slow, and it gave up after 60 seconds which shows "socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx" in the log file.

Admin
Site Admin
Posts: 1127
Joined: Mon Jun 10, 2002 6:31 pm
Location: Melbourne, Victoria, Australia

Re: [solved]socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx

Post by Admin »

Hi,

If it is on the QUIT command only then this will be after the message was accepted, so I would not have expected that you see the "has not been routed" error. This indicates the email data was not fully received. Maybe if you check the SMTP Debug log for the message filename before this error it may show another error, as you should have seen that the message was accepted and delivery was going to happen.

poweredge
Posts: 157
Joined: Sat May 29, 2021 11:16 am

Re: [solved]socket [2588] was gracefully closed during [QUIT] command by the remote client xxx.xxx.xxx.xxx

Post by poweredge »

I wonder if the problem I was having actually related to this bug?

https://www.mailenable.com/forum/viewtopic.php?f=2&t=44550

Post Reply