cyrusimap / bugzilla-migrate-test

0 stars 1 forks source link

bad sendmail directive makes lmtpd spin? #768

Closed brong closed 14 years ago

brong commented 20 years ago

From: Rob Siemborski Bugzilla-Id: 2426 Version: 2.2.x Owner: Rob Siemborski

brong commented 20 years ago

From: Rob Siemborski

I have a mailbox that needs to store it's messages and forward a copy on to an external address. my test of this procedure on 2.1.15 works fine using Squirrelmail's avelsieve plugin/editor. However, uploading the same filter to the new server (2.2.3) breaks mail delivery completely and yields the following:

stat=Deferred: 451 lmtpd: didn't exec() sendmail?!

the spawned lmtp process then runs away taking as much CPU as possible and has to be killed manually.


The problem was that the sendmail option was not set properly, but this behavior is poor in its own right -- at worst, we should fatal(), at best, we probably want to just fail the vacation action and file into the INBOX. This is worth confirming before fixing, of course.

brong commented 20 years ago

From: J.Lorec

hi, i've recently encountered quite the same problem as noticed above. I've just moved from a fully working cyrus-imap 2.2.3 to 2.2.8 w/ exactly the same conf files, file permissions, etc... and discovered that now sieve needs me to explictly fill the "sendmail:" directive inside imapd.conf. Once done i received this message in my logs: "postfix/sendmail[9861]: fatal: parameter max_idle: bad time unit: -f" the sieve mail is not sent and the smptd process dies. The problem is that i don't use sendmail but postfix; i thought it was just a program parameter annoyance and removed the reference to this switch in the source (don't remember the c file) before compiling. I now don't get this anymore but smtpd still hangs.

this is really strange that i didn't get any problem before upgrading to 2.2.8

this "smtp sieve bug" has to be confirmed but i doubt it's a configuration problem unless imapd.conf/cyrus.conf syntax changed between these 2 versions.

brong commented 20 years ago

From: J.Lorec

sorry WRONG bug report: was in fact tls-patch for postfix that caused this problem; sieve is working the way it should.