Hi,

Thanks for replying. My bad, I realised I posted the log message from
 /var/log/message. It's quite similar to what I get in postfix log
too. Here's the postfix /var/log/mailog version of a test mail that I just
sent, hope this is better (also there are no other warning/panic errors
before this). :)

-------------------------
Aug 22 21:50:17 node1 postfix/smtpd[71236]: 4F4056EB019:
client=unknown[172.31.0.181]
Aug 22 21:50:17 node1 postfix/cleanup[71239]: 4F4056EB019: message-id=<
4c712a92.8020...@aaa.com>
Aug 22 21:50:17 node1 postfix/smtpd[71236]: disconnect from
unknown[172.31.0.181]
Aug 22 21:50:17 node1 postfix/qmgr[59650]: 4F4056EB019: from=<sen...@aaa.com>,
size=1498409, nrcpt=1 (queue active)
Aug 22 21:50:17 node1 postfix/virtual[71240]: panic: file size limit 1000000
< message size 1498997. This causes large messages to be delivered
repeatedly after they were submitted with "sendmail -t" or after recipients
were added with the Milter SMFIR_ADDRCPT request
Aug 22 21:50:18 node1 postfix/qmgr[59650]: warning: private/virtual socket:
malformed response
Aug 22 21:50:18 node1 postfix/qmgr[59650]: warning: transport virtual
failure -- see a previous warning/fatal/panic logfile record for the problem
description
Aug 22 21:50:18 node1 postfix/master[59648]: warning: process
/usr/local/libexec/postfix/virtual pid 71240 killed by signal 6
Aug 22 21:50:18 node1 postfix/error[71260]: 4F4056EB019: to=<r...@aaa.com>,
relay=none, delay=1.2, delays=0.15/1/0/0.01, dsn=4.3.0, status=deferred
(unknown mail transport error)

mailq command:
4F4056EB019  1498409 Sun Aug 22 21:50:17  sen...@aaa.com
                                                (unknown mail transport
error)
                                         r...@aaa.com
----------------------------


On Sun, Aug 22, 2010 at 9:24 PM, Wietse Venema <wie...@porcupine.org> wrote:

> Squeeshh Me:
> > Aug 21 11:12:55 node1 kernel: pid 40382 (virtual), uid 5000: exited on
> > signal 6
>
> For details, look in your MAILLOG file.
>
>        Wietse
>
> 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