On 7/31/2013 8:33 PM, LuKreme wrote:
>
> On 31 Jul 2013, at 17:35 , Wietse Venema <[email protected]> wrote:
>
>>
>> http://www.postfix.org/DEBUG_README.html#logging
>
> Since I last stopped and started postfix (2.10.1):
>
> # egrep '(warning|error|fatal|panic):' /var/log/maillog
> Jul 31 18:47:59 mail postfix/qmgr[81937]: warning: connect to transport
> private/smtp: Connection refused
OK, that's the message we need.
> here's postconf -Mf
Looks as if you clobbered your smtp transport "smtp unix ... smtp"
>
> pickup fifo n - n 60 1 pickup
> cleanup unix n - n - 0 cleanup
> qmgr fifo n - n 300 1 qmgr
> rewrite unix - - n - - trivial-rewrite
> bounce unix - - n - 0 bounce
> defer unix - - n - 0 bounce
> flush unix n - n 1000? 0 flush
> proxymap unix - - n - - proxymap
> relay unix - - n - - smtp
> showq unix n - n - - showq
> error unix - - n - - error
> local unix - n n - - local
> virtual unix - n n - - virtual
> lmtp unix - - n - - lmtp
> procmail unix - n n - - pipe
> flags=uhFORD user=vpopmail argv=/usr/local/bin/procmail -t -m
> USER=${recipient} EXTENSION=${extension} /usr/local/etc/procmailrc.common
> trace unix - - n - 0 bounce
> verify unix - - n - 1 verify
> anvil unix - - n - 1 anvil
> scache unix - - n - 1 scache
> discard unix - - n - - discard
> tlsmgr unix - - n 1000? 1 tlsmgr
> retry unix - - n - - error
> proxywrite unix - - n - 1 proxymap
> smtp inet n - n - 1 postscreen
> smtpd pass - - n - - smtpd
> dnsblog unix - - n - 0 dnsblog
> tlsproxy unix - - n - 0 tlsproxy
>
> cranking up the logging on qmgr I see this:
debug logging is rarely useful with postfix. 99%+ of the time
normal logging is sufficient to solve whatever problem you're
having. As in this case.
-- Noel Jones
