Mehul Ved put forth on 12/21/2009 5:01 AM: > logs after the problem occurred - http://pastebin.ca/1722318 > logs before the problem occurred - http://pastebin.ca/1722322
You inbound for relay (I assume so due to the TLS): Dec 19 00:03:18 www postfix/smtpd[23607]: connect from c-24-34-20-2.hsd1.ma.comcast.net[24.34.20.2] Dec 19 00:03:18 www postfix/smtpd[23607]: setting up TLS connection from c-24-34-20-2.hsd1.ma.comcast.net[24.34.20.2] Dec 19 00:03:19 www postfix/smtpd[23607]: TLS connection established from c-24-34-20-2.hsd1.ma.comcast.net[24.34.20.2]: TLSv1 with cipher RC4-MD5 (128/128 bits) Dec 19 00:03:20 www postfix/smtpd[23607]: 41A432CB8B2E: client=c-24-34-20-2.hsd1.ma.comcast.net[24.34.20.2] Dec 19 00:03:20 www postfix/cleanup[24661]: 41A432CB8B2E: message-id=<20091218183320.41a432cb8...@www.progresspartners.co.in> Dec 19 00:03:20 www postfix/smtpd[23607]: disconnect from c-24-34-20-2.hsd1.ma.comcast.net[24.34.20.2] Me inbound for relay: Dec 20 15:17:42 greer postfix/smtpd[18910]: connect from gffx.hardwarefreak.com[192.168.100.53] Dec 20 15:17:42 greer postfix/smtpd[18910]: 4B64C6C439: client=gffx.hardwarefreak.com[192.168.100.53] Dec 20 15:17:42 greer postfix/cleanup[18912]: 4B64C6C439: message-id=<4b2e9476.4090...@hardwarefreak.com> Dec 20 15:17:42 greer postfix/qmgr[18646]: 4B64C6C439: from=<s...@hardwarefreak.com>, size=2039, nrcpt=1 (queue active) Dec 20 15:17:42 greer postfix/smtpd[18910]: disconnect from gffx.hardwarefreak.com[192.168.100.53] Dec 20 15:17:43 greer postfix/smtp[18913]: 4B64C6C439: to=<postfix-users@postfix.org>, relay=mail.cloud9.net[168.100.1.3]:25, delay=1, delays=0.04/0.02/0.52/0.43, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 1FB851035EB) Dec 20 15:17:43 greer postfix/qmgr[18646]: 4B64C6C439: removed At the worst, it looks like your qmgr daemon isn't running, or isn't being called, or, at the least, isn't being logged. Assuming it's the first, why isn't your qmgr daemon running? If it's the 2nd, why isn't your cleanup process handing the mail off to qmgr? If it's the 3rd, either you've got your logging level set funky, _or_ the first is true: the qmgr daemon isn't running. Or maybe you've got some special configuration I'm not familiar with that just doesn't log qmngr messages. -- Stan
