Peter Lauda wrote:
>
> Well I'm a bit stupid for missing that in the previous posting, but even
> after I have made that change I have even more errors in the log than
> before. anyway, new error messages that I hope are going to be the last.
>
> Here goes:
>
> ---8<---SNIP-----
>
> Mar 3 19:32:23 linux postfix/postfix-script: starting the Postfix mail
> system
> Mar 3 19:32:23 linux postfix/master[27323]: daemon started
>
> ****** I don't understand the wrong date/time here either...
>
> Mar 4 00:32:23 linux postfix/nqmgr[27325]: 4881815AE0:
> from=<rootmagna.net>, s
> ize=280, nrcpt=1 (queue active)
> Mar 4 00:32:23 linux postfix/smtp[27327]: fatal: unknown service:
> smtp/tcp
> Mar 4 00:32:24 linux postfix/nqmgr[27325]: warning: premature
> end-of-input from
> private/smtp socket while reading input attribute name
> Mar 4 00:32:24 linux postfix/nqmgr[27325]: warning: private/smtp socket:
> malfor
> med response
> Mar 4 00:32:24 linux postfix/nqmgr[27325]: warning: transport smtp
> failure -- s
> ee a previous warning/fatal/panic logfile record for the problem
> description
> Mar 3 19:32:24 linux postfix/master[27323]: warning: process
> /usr/libexec/postf
> ix/smtp pid 27327 exit status 1
> Mar 3 19:32:24 linux postfix/master[27323]: warning:
> /usr/libexec/postfix/smtp:
> bad command startup -- throttling

Some postfix processes runs chrooted on your box. But chroot jail isn't
set up properly. Wither do not run smtp (and other services) chrooted
(see chroot column in master.cf) or set up /var/spool/postfix for chroot
operations. Invalid date is after the same problem: there is no
/etc/timezone or equivalent in /var/spool/postfix.

If you reinstalled postfix from scratch, it may be better to start with
zero configuration as well. I.e. remove /etc/postfix, /var/spool/postfix
and /usr/lib[exec]/postfix and make install.

Regards,
 Michael.
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]