Am 16.10.2012 23:46, schrieb John Reddy:
Before tracing anything (processes or network traffic) the OP should check the maillog. It for sure will the the truth about what is going on.
Here's some of the printout from that log:
Oct 16 10:36:19 mydomain postfix/master[14058]: warning: process /usr/libexec/postfix/proxymap pid 1438 exit status 1 Oct 16 10:36:19 mydomain postfix/master[14058]: warning: /usr/libexec/postfix/proxymap: bad command startup -- throttling Oct 16 10:36:19 mydomain postfix/smtpd[26426]: warning: premature end-of-input on private/proxymap socket while reading input attribute name Oct 16 10:36:19 mydomain postfix/smtpd[26426]: warning: private/proxymap socket: service dict_proxy_open: Success Oct 16 10:36:19 mydomain postfix/master[14058]: warning: process /usr/libexec/postfix/proxymap pid 1439 exit status 1 Oct 16 10:36:19 mydomain postfix/cleanup[14062]: warning: premature end-of-input on private/proxymap socket while reading input attribute name Oct 16 10:36:19 mydomain postfix/cleanup[14062]: warning: private/proxymap socket: service dict_proxy_open: Connection reset by peer
TIA, John
Your other reply with the "postconf -n" output shows that you are running Postfix 2.3.3 which is coming with CentOS 5. Are you running precisely that version or the one from the centosplus repository?
The Postfix from CentOS 5 base does not support mysql as a valid map type! Thus it must fail when you specify maps of type mysql, as you do.
Regards
Alexander