On Sat, 06 Sep 2003, John Fawcett wrote: > In the past few days I have had several incoming messages bounced due to > Command time limit exceeded in /usr/lib/cyrus/bin/deliver.
> I have a Postfix -> Amavis-new -> Postfix -> Cyrus configuration. Use the dual postfix cleanup setup described in the amavisd-new docs, and configure postfix properly. Mail will queue inside postfix (after being processed by amavisd-new) waiting for cyrus to become available again. > postfix main.cf), postfix bounces message. In fact the postfix/pipe log line If you are using postfix/pipe, you are doing things wrong. You should be using: postfix ->[smtp/lmtp]->amavisd-new->[smtp]->postfix->[lmtp]->cyrus. (unless you're using extremely old cyrus 1.5, that is) > Sep 5 10:11:42 romolo postfix/smtpd[20899]: AF5732BEC4: > client=localhost.localdomain[127.0.0.1] > Sep 5 10:11:42 romolo postfix/cleanup[20886]: AF5732BEC4: > message-id=<[EMAIL PROTECTED]> > Sep 5 10:11:42 romolo postfix/qmgr[1708]: AF5732BEC4: > from=<[EMAIL PROTECTED]>, size=4651, nrcpt=1 > (queue active) > Sep 5 10:11:42 romolo postfix/smtpd[20899]: disconnect from > localhost.localdomain[127.0.0.1] > Sep 5 10:14:43 romolo postfix/pipe[20902]: AF5732BEC4: > to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>, relay=cyrus, > delay=181, status=bounced (Command time limit exceeded: > "/usr/lib/cyrus/bin/deliver") Well, WHY is postfix bouncing that message if deliver times-out? Configure it properly to retry such errors. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
