Another bug in postfix (wrong time or timestamp in the logs)

[JarekG]

Another one with postfix.

Jul 26 06:00:25 MY_SERVER spamd[22332]: spamd: processing message <PPPPPPP> for [email protected]s:110
Jul 26 06:00:25 MY_SERVER postfix/qmgr[3161]: 6C7907901A: from=<[email protected]>, size=6286, nrcpt=1 (queue active)
Jul 26 05:00:25 MY_SERVER postfix/smtpd[13992]: disconnect from unknown[127.0.0.1]
Jul 26 06:00:25 MY_SERVER postfix-local[14136]: postfix-local: [email protected], [email protected], dirname=/var/qmail/mailnames
Jul 26 06:00:25 MY_SERVER postfix-local[14136]: hook_dir = '/usr/local/psa/handlers/before-local'
Jul 26 06:00:25 MY_SERVER postfix-local[14136]: recipient[3] = '[email protected]'
Jul 26 06:00:25 MY_SERVER postfix-local[14136]: handlers dir = '/usr/local/psa/handlers/before-local/recipient/[email protected]'
Jul 26 06:00:25 MY_SERVER postfix-local[14136]: call_handlers: call executable = '/usr/local/psa/handlers/info/10-spam-EfGkCG/executable'
Jul 26 05:00:25 MY_SERVER postfix/smtpd[9583]: disconnect from unknown[XX.XX.XX.XX]
Jul 26 05:00:26 MY_SERVER postfix/smtpd[5230]: connect from unknown[YY.YY.YY.YY]
Jul 26 05:00:26 MY_SERVER postfix/smtpd[5230]: NOQUEUE: reject: RCPT from unknown[YY.YY.YY.YY]: 554 5.7.1 Service unavailable; Client host [YY.YY.YY.YY] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=YY.YY.YY.YY; from=<****@email.address> to=<[email protected]> proto=ESMTP helo=<HELO>
Jul 26 05:00:26 MY_SERVER postfix/smtpd[5230]: disconnect from unknown[YY.YY.YY.YY]
Jul 26 06:00:28 MY_SERVER postfix/pickup[8189]: 3F0706F5B8: uid=10018 from=<>

If you will see all processes of smtpd have a wrong time.

Solution.

create directory /var/spool/postfix/etc/

# mkdir /var/spool/postfix/etc

copy file /etc/localtime to /var/spool/postfix/etc/
# cp /etc/localtime /var/spool/postfix/etc/

I don't know if it's more postfix or Plesk bug. However it would be nice if Parallels selling the software could fix some 3rd party software small bugs too.

 

[IgorG]

Yes, it is known issue and we have corresponding request. As far as I know it will be fixed in the one of nearest Plesk update.