Solved Postfix problem receiving email to relay
-
Do you have any TLS here? Any cert expire?
-
Not yet for postfix. That is on my to do list, https://mangolassi.it/topic/12545/how-do-i-setup-tls-on-a-postfix-relay
-
Maybe your firewall is blocking connection. Try to stop firewall and check if it works. Maybe you or somebody else changed some rules.
-
The odd part is that the initial connection works, then it drops afterwards.
-
@scottalanmiller said in Postfix problem receiving email to relay:
The odd part is that the initial connection works, then it drops afterwards.
right. that is what has me confused.
-
@triple9 said in Postfix problem receiving email to relay:
Maybe your firewall is blocking connection. Try to stop firewall and check if it works. Maybe you or somebody else changed some rules.
No one else even knows how to handle this.
Related note, I need to get more documentation in place.
-
firewalld has port 25 allowed.
[root@relay01 ~]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: dhcpv6-client ssh ports: 25/tcp protocols: masquerade: no forward-ports: sourceports: icmp-blocks: rich rules: -
Postfix config has not been touched since setup a year ago.
[root@relay01 ~]# ls -l /etc/postfix/main.cf -rw-r--r--. 1 root root 27281 Mar 14 2016 /etc/postfix/main.cf -
Is there any filtering in postfix, like amavis, spamassassin?
-
@triple9 said in Postfix problem receiving email to relay:
Is there any filtering in postfix, like amavis, spamassassin?
nope.
-
And problem resolved.
On the 1st, the damned DHCP lease had failed again due to the mysterious time drift issues I have been tracking down in another thread.
But I needed this system up so I launched
nmtuiand set a static IP.... Wait for it.. to 10.201.1.12/32/fucking sigh....
I also enabled the Time Synchronization in Hyper-V on March 1st. As soon as I fixed the /32, this morning, the Hyper-V integration started fixing the time every 5 seconds.. screw that. Turned it back off. I will count on
chronydit works well as long as the IP stays online.[root@relay01 ~]# tail -f /var/log/messages Mar 7 11:18:33 relay01 systemd: Time has been changed Mar 7 11:18:38 relay01 systemd: Time has been changed Mar 7 11:18:43 relay01 systemd: Time has been changed Mar 7 11:18:48 relay01 systemd: Time has been changed Mar 7 11:18:53 relay01 systemd: Time has been changed Mar 7 11:18:58 relay01 systemd: Time has been changed Mar 7 11:19:03 relay01 systemd: Time has been changed Mar 7 11:19:08 relay01 systemd: Time has been changed Mar 7 11:19:13 relay01 systemd: Time has been changed Mar 7 11:19:18 relay01 systemd: Time has been changed -
Ah ha. DHCP strikes again
-
@scottalanmiller said in Postfix problem receiving email to relay:
Ah ha. DHCP strikes again
I really want to figure out what is causing these VM's to do that. it is not normal.
This problem was caused by me not being careful enough when I changed something to avoid the DHCP problem.
-
And there goes a successful mail test.
Mar 7 11:25:24 relay01 postfix/smtpd[2206]: connect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/smtpd[2206]: CB2E6C0C82CB: client=owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/cleanup[2208]: CB2E6C0C82CB: message-id=<[email protected]> Mar 7 11:25:24 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: from=<[email protected]>, size=591, nrcpt=1 (queue active) Mar 7 11:25:24 relay01 postfix/smtpd[2206]: disconnect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:26 relay01 postfix/smtp[2209]: CB2E6C0C82CB: to=<[email protected]>, relay=domain-com.mail.protection.outlook.com[216.32.181.170]:25, delay=2.1, delays=0.05/0/0.62/1.4, dsn=2.6.0, status=sent (250 2.6.0 <[email protected]> [InternalId=42704859829911, Hostname=SN1PR0201MB1854.namprd02.prod.outlook.com] 7564 bytes in 0.244, 30.254 KB/sec Queued mail for delivery) Mar 7 11:25:26 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: removed
