After a kernel update the pmg doesn't forward email to its default relay

J

JuanCAguilar

New Member
Feb 14, 2023
17
2
3
México
www.conafor.gob.mx
Hello to everyone

I have a seriuos issue derived since the an applied kernel update (at least I think so) the pmg doesn't detects incoming traffic although the incomming sockets are reflected, as you can see in the next output command...

root@sagw:~# netstat -untap | grep ESTABLISHED
tcp 0 0 sagw.pmg:25 40.107.220.59:2622 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.44.83:6180 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.92.70:23233 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.173.243:9216 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.236.40:32961 ESTABLISHED -
tcp 0 0 sagw.pmg:25 199.187.174.149:45509 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.45.88:19808 ESTABLISHED -
tcp 0 0 sagw.pmg:25 209.85.217.48:57804 ESTABLISHED -
tcp 0 0 sagw.pmg:25 83.126.36.240:57483 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.18.104:12539 ESTABLISHED -
tcp 0 0 sagw.pmg:25 137.59.55.27:56477 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.237.139:33728 ESTABLISHED -
tcp 0 0 sagw.pmg:25 200.57.3.187:40174 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.154.225:36097 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.212.221:14720 ESTABLISHED -
tcp 0 0 sagw.pmg:25 95.173.184.222:51103 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.160.207:29253 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.15.21:16965 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.171.200:54656 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.174.234:30912 ESTABLISHED -
tcp 0 0 sagw.pmg:25 148.105.10.81:59198 ESTABLISHED -
tcp 0 0 sagw.pmg:25 148.105.10.81:52411 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.42.79:27552 ESTABLISHED -
tcp 0 0 sagw.pmg:25 103.25.195.119:19589 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.103.7.23:51297 ESTABLISHED -
tcp 0 0 sagw.pmg:25 200.57.3.187:40158 ESTABLISHED -
tcp 0 0 sagw.pmg:25 103.30.75.60:51743 ESTABLISHED -
tcp 0 0 sagw.pmg:25 208.113.156.243:58284 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.236.100:63329 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.74.13:16129 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.22.25:33825 ESTABLISHED -
tcp 0 0 sagw.pmg:25 187.217.4.90:59166 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.40.30:33121 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.161.217:24640 ESTABLISHED -
tcp 0 0 sagw.pmg:25 107.143.137.97:40790 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.158.214:33370 ESTABLISHED -
tcp 0 0 sagw.pmg:25 200.104.200.3:49358 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.165.234:35936 ESTABLISHED -
tcp 0 0 sagw.pmg:25 216.106.42.246:60800 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.101.54.27:49989 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.103.10.1:59076 ESTABLISHED -
tcp 0 0 sagw.pmg:25 54.183.29.174:9814 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.167.206:40512 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.97.94:3648 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.89.32:62111 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.171.200:47457 ESTABLISHED -
tcp 0 0 sagw.pmg:25 109.199.186.125:6631 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.94.137:21857 ESTABLISHED -
tcp 0 0 sagw.pmg:25 209.85.219.174:55345 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.49.74:16797 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.96.99:13312 ESTABLISHED -
tcp 0 0 sagw.pmg:25 131.0.206.156:18047 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.20.10:23392 ESTABLISHED -
tcp 0 0 sagw.pmg:25 109.199.186.125:6660 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.219.234:17377 ESTABLISHED -
tcp 0 0 sagw.pmg:25 208.113.156.243:57924 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.172.248:19904 ESTABLISHED -
tcp 0 0 10.0.0.180:22 10.0.1.225:60187 ESTABLISHED 8868/sshd: root@not
tcp 0 0 sagw.pmg:25 84.237.85.79:50721 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.13.237:26945 ESTABLISHED -
tcp 0 0 sagw.pmg:50952 103.224.212.34:25 ESTABLISHED 18325/smtp
tcp 0 0 sagw.pmg:25 40.92.42.60:21658 ESTABLISHED -
tcp 0 0 sagw.pmg:25 173.254.64.10:46185 ESTABLISHED -
tcp 0 0 sagw.pmg:25 58.76.180.172:3432 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.74.97:28544 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.20.10:62689 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.220.45:44768 ESTABLISHED -
tcp 0 0 sagw.pmg:25 200.57.3.187:40162 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.43.51:19365 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.19.72:45146 ESTABLISHED -
tcp 0 0 sagw.pmg:25 149.20.206.79:18960 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.167.221:13985 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.40.16:61600 ESTABLISHED -
tcp 0 0 sagw.pmg:25 67.217.63.26:40572 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.223.43:42560 ESTABLISHED -
tcp 0 0 sagw.pmg:25 209.85.128.44:53624 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.41.96:23520 ESTABLISHED -
tcp 0 0 10.0.0.180:22 10.0.1.225:59482 ESTABLISHED 1512/sshd: root@not
tcp 0 0 sagw.pmg:25 52.100.173.203:5056 ESTABLISHED -
tcp 0 0 sagw.pmg:25 192.254.118.54:26680 ESTABLISHED -
tcp 0 0 sagw.pmg:25 60.43.211.253:44328 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.165.236:63680 ESTABLISHED -
tcp 0 64 10.0.0.180:22 10.0.1.225:59481 ESTABLISHED 1510/sshd: root@pts
tcp 0 0 sagw.pmg:25 40.92.91.11:42848 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.222.212:31101 ESTABLISHED -
tcp 0 0 sagw.pmg:25 200.57.3.187:37582 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.163.207:5281 ESTABLISHED -
tcp 0 0 sagw.pmg:25 107.143.137.97:40778 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.103.7.23:8844 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.167.241:22145 ESTABLISHED -
tcp 0 0 sagw.pmg:25 107.143.137.97:40971 ESTABLISHED -
tcp 0 0 sagw.pmg:25 68.107.201.134:9969 ESTABLISHED -
tcp 0 0 sagw.pmg:25 135.84.81.179:48497 ESTABLISHED -
tcp 0 0 sagw.pmg:25 12.231.236.151:58450 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.155.216:47232 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.161.234:37407 ESTABLISHED -
tcp 0 0 sagw.pmg:25 104.161.47.153:52308 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.18.38:27939 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.46.32:15936 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.107.237.64:29664 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.41.62:6624 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.107.17:16613 ESTABLISHED -
tcp 0 0 sagw.pmg:25 40.92.97.73:14785 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.101.47.27:22651 ESTABLISHED -
tcp 0 0 sagw.pmg:25 52.100.155.227:16090 ESTABLISHED -
udp 0 0 127.0.0.1:44062 127.0.0.1:44062 ESTABLISHED 780/postgres
udp 0 0 10.0.0.180:2938 10.0.0.247:53 ESTABLISHED 12385/pmg-smtp-filt
udp 0 0 10.0.0.180:15325 10.0.0.247:53 ESTABLISHED 12384/pmg-smtp-filt


So in consecuence the pmg since this time isn't forward email to its default relay host.

Greets.

Juan C. Aguilar
 

Attachments

  • WithoutSMTPIncommongTraffic.png
    WithoutSMTPIncommongTraffic.png
    75.1 KB · Views: 5
This sounds odd - please share the journal of the system after the upgrade - this might help us seeing where the issue is.
 
I'm sorry friend... I was urged to reinstall the pmg linux core at night, this due by the user's complains about their not receiving emails from external domains. The new issue today is the subscription activation. May you help me with this new issue?

Statusinvalid: Invalid Server ID
Server ID########################
Last checked2023-05-16 10:50:45

Is there any way to solve it? Could be release the subscription activation key from the prior Server ID (damaged pmg core) associated with it?

Greetings
Juan Carlos
 

Attachments

Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom