Postfix check ok
[root@edge ~]# postfix check
but start fails
[root@edge ~]# postfix start
postfix/postfix-script: starting the Postfix mail system
postfix/postfix-script: fatal: mail system startup failed
[root@edge ~]#
log
[root@edge ~]# tail /var/log/maillog
May 16 03:48:41 edge spamc[23884]: connect to spamd on ::1 failed, retrying (#2 of 3): Connection refused
May 16 03:48:41 edge spamc[23884]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused
May 16 03:48:42 edge spamc[23884]: connect to spamd on ::1 failed, retrying (#3 of 3): Connection refused
May 16 03:48:42 edge spamc[23884]: connect to spamd on 127.0.0.1 failed, retrying (#3 of 3): Connection refused
May 16 03:48:42 edge spamc[23884]: connection attempt to spamd aborted after 3 retries
May 16 03:48:42 edge postfix/local[23790]: 3C12B3248C2B: to=<a1z@edge.a1z.us>, orig_to=<pause@a1z.us>, relay=local, delay=25, delays=0.23/0.01/0/24, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME)
May 16 03:48:42 edge postfix/qmgr[7789]: 3C12B3248C2B: removed
May 16 03:48:42 edge postfix/smtpd[9028]: warning: unknown[45.142.195.14]: SASL LOGIN authentication failed: authentication failure
May 16 03:48:45 edge postfix/smtpd[32687]: connect from unknown[45.142.195.14]
May 16 03:48:45 edge postfix/smtpd[9028]: disconnect from unknown[45.142.195.14] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
[root@edge ~]#
I tried
[root@edge ~]# spamd -d
[root@edge ~]#
Still did not work.
Status:
Closed (fixed)
Comments
update
more from maillog
Submitted by andreychek on Fri, 05/15/2020 - 23:30 Comment #2
Howdy -- thanks for contacting us!
Hmm, I'm not actually seeing any Postfix related errors in the logs there.
What output do you see if you run this command:
service postfix restart
That should show any errors that are occurring.
OK
Killed the pid in .lock.
Thereafter, postfix started without error.
[root@edge ~]# postfix start
I had to comment out this part in master.cf
it gave me error
It results in a warning usually. I also noticed it being added and reported by many people.
We need to figure out, if it's a Postfix bug or Virtualmin's one.
I will look into it.
This is no longer an issue in the latest Virtualmin 6.11.
Submitted by IssueBot on Sat, 08/22/2020 - 07:11 Comment #8
Automatically closed - issue fixed for 2 weeks with no activity.