RaSca:
> Hi all,
> I've got Postfix running on two machines balanced with lvs, the 
> configuration is obviously identical on every machine, but in only on 
> one of them and with some messages i see this kind of error message in 
> the log:
> 
> Jan 21 11:52:55 mail-2 postfix/error[4716]: E2B4A208256: 
> to=<xxxx...@xxxxxxx.com>, relay=none, delay=181215, 
> delays=181215/0.05/0/0.25, dsn=4.3.0, status=deferred (mail transport 
> unavailable)
> 
> I've got many line like this one, the ID is identical for some lines so 
> it seems to be a retry.
> All the daemons are started (I've got postfix+spampd+clamav) and 
> responsive (as i can see from telnet checks).
> What else should I check? Have you got any idea? Note that the mail 
> server works perfectly, only for those group 150 messages I receive this 
> error.

http://www.postfix.org/DEBUG_README.html#logging

Look for obvious signs of trouble
=================================

Postfix logs all failed and successful deliveries to a logfile.
The file is usually called /var/log/maillog or /var/log/mail; the
exact pathname is defined in the /etc/syslog.conf file.

When Postfix does not receive or deliver mail, the first order of
business is to look for errors that prevent Postfix from working
properly:

    % egrep '(warning|error|fatal|panic):' /some/log/file | more

Note: the most important message is near the BEGINNING of the
output. Error messages that come later are less useful.

The nature of each problem is indicated as follows:

    * "panic" indicates a problem in the software itself that only
      a programmer can fix. Postfix cannot proceed until this is
      fixed.

    * "fatal" is the result of missing files, incorrect permissions,
      incorrect configuration file settings that you can fix.
      Postfix cannot proceed until this is fixed.

    * "error" reports an error condition. For safety reasons, a
      Postfix process will terminate when more than 13 of these
      happen.

    * "warning" indicates a non-fatal error. These are problems
      that you may not be able to fix (such as a broken DNS server
      elsewhere on the network) but may also indicate local
      configuration errors that could become a problem later.

Reply via email to