Hi there, I'm getting a lot of the following on our proxmox:
Jul 28 14:06:14 smtpd 3007 lost connection after DATA (0 bytes) from unknown[60.221.144.138]
Jul 28 14:06:17 smtpd 2790 lost connection after DATA (0 bytes) from unknown[62.241.152.81]
Jul 28 14:06:19 smtpd 3021 lost connection after DATA (0 bytes) from unknown[41.129.13.2]
Jul 28 14:06:19 smtpd 3019 lost connection after DATA (0 bytes) from unknown[119.152.61.26]
Jul 28 14:06:21 smtpd 2791 lost connection after CONNECT from unknown[122.168.13.158]
Tue Jul 28 13:38:28 3111 pete******@eo******s.co.uk administrator@brad********ics.co.uk
SMTP RESULT: conversation with 217.37.***.150[217.37.***.150] timed out while sending message body
Tue Jul 28 13:21:22 20 MAILER-DAEMON Pam******@brad********ics.co.uk
SMTP RESULT: connect to 217.37.***.150[217.37.***.150]:25: Connection timed out
I've replaced the router that was serving the proxmox's internet connection & still getting the problem. I've updated to the latest proxmox servicepack.
I'm wondering if these are likely symptoms of a saturated WAN interface? Is there anything else I should look at?
Jul 28 14:06:14 smtpd 3007 lost connection after DATA (0 bytes) from unknown[60.221.144.138]
Jul 28 14:06:17 smtpd 2790 lost connection after DATA (0 bytes) from unknown[62.241.152.81]
Jul 28 14:06:19 smtpd 3021 lost connection after DATA (0 bytes) from unknown[41.129.13.2]
Jul 28 14:06:19 smtpd 3019 lost connection after DATA (0 bytes) from unknown[119.152.61.26]
Jul 28 14:06:21 smtpd 2791 lost connection after CONNECT from unknown[122.168.13.158]
Tue Jul 28 13:38:28 3111 pete******@eo******s.co.uk administrator@brad********ics.co.uk
SMTP RESULT: conversation with 217.37.***.150[217.37.***.150] timed out while sending message body
Tue Jul 28 13:21:22 20 MAILER-DAEMON Pam******@brad********ics.co.uk
SMTP RESULT: connect to 217.37.***.150[217.37.***.150]:25: Connection timed out
I've replaced the router that was serving the proxmox's internet connection & still getting the problem. I've updated to the latest proxmox servicepack.
I'm wondering if these are likely symptoms of a saturated WAN interface? Is there anything else I should look at?