Postfix + Debian ->

brgsousa · 10-15-2008, 04:18 PM

Guys,
postfix stopped delivering messages, ad i am getting these errors in postqueue -p:

Code:

2CA51594114     3030 Wed Oct 15 18:48:20  XXXXXX@burcas.co.uk
                                                (unknown mail transport error)
                                         YYYYYY@fapesb.ba.gov.br

What is happening?

TB0ne · 10-15-2008, 04:31 PM

Quote:

Originally Posted by brgsousa

Guys,
postfix stopped delivering messages, ad i am getting these errors in postqueue -p:

Code:

2CA51594114     3030 Wed Oct 15 18:48:20  XXXXXX@burcas.co.uk
                                                (unknown mail transport error)
                                         YYYYYY@fapesb.ba.gov.br

What is happening?

From the Postfix message boards:

Code:

Mail delivery fails with: "unknown mail transport error"
This is an opportunity to meet your friends egrep and less. Postfix activity, including progres and failure, is logged to a logfile, typically named /var/log/maillog. To find out where Postfix activity is logged on your machine, examine the /etc/syslog.conf file.

To find out the cause for the "unknown mail transport error", type the following command:

    egrep '(warning|fatal|panic):' /var/log/maillog | less 

Pay particular attention to messages that are labeled as fatal and panic. These describe catastrophic failures that need to be addressed before Postfix is happy. Problems labeled as fatal are fixed by you, by adjusting configuration files, file permissions and so on. Problems labeled as panic are fixed by the Postfix author, by changing Postfix source code.

billymayday · 10-15-2008, 05:19 PM

What does "postconf -n" show?

ALso, if you have any form of transport maps defined, what are the contents of the files.

Was it working OK? If so, what changed?

Also post master.cf, and show the relevant log entries.

brgsousa · 10-15-2008, 05:54 PM

Thanks for the replies guys.
It is working fine now. I am not able to explain what was the solution coz someone else fixed the problem here at work