Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Sasa Stupar (sasa.stupargmail.com)
Date: Fri Jul 06 2007 - 04:14:52 CDT
2007/7/6, Reko Turja <reko.turjaliukuma.net>:
> ----- Original Message -----
> From: "Sasa Stupar" <sasa.stupargmail.com>
> To: <postfix-userspostfix.org>
> Sent: Friday, July 06, 2007 9:03 AM
> Subject: Re: Sieve stops working after Postfix install
> > I have decided to change Sendmail (8.14.1)+Cyrus-Imapd on FreeBSD
> > (5.5) to
> > Postfix 2.4.
> > Installation and configuration went well and the mail system is
> > working BUT
> > my Sieve scripts are no longer working.
> > I haven't changed anything in Cyrus (2.2.13_1) just changed Sendmail
> > for
> > Postfix.
> > What have I missed in configuration of Postfix?
> Do the received mail headers look like:
> Return-Path: <owner-postfix-userspostfix.org>
> Received: from www.liukuma.net ([unix socket])
> by www.liukuma.net (Cyrus v2.3.8) with LMTPA;
> Fri, 06 Jul 2007 09:03:39 +0300
> X-Sieve: CMU Sieve 2.3 <-- Do you have this?
Received: from xmail.homelinux.net ([unix socket])
by xmail.homelinux.net (Cyrus v2.2.13) with LMTPA;
Fri, 06 Jul 2007 08:13:01 +0200
X-Sieve: CMU Sieve 2.2
> That's the best telltale sign that sieve is active and processing
> inbound mail.
> Your Postfix configuration has both:
> mailbox_transport = cyrus
> mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
Ooups. I knew I've missed something.
> You can drop the: mailbox_transport = cyrus
> If the mail gets delivered to Cyrus afterall, I wouldn't say that the
> problem lies with Postfix, unless the "cyrus" method trumps the lmtp
> transport defined later. (Been running several versions of
> Cyrus/Postfix on FreeBSD now without a hitch...) The only, very
> remote, possibility I can see from recent Postfix changes is the
> workaround for some Linux "features" that makes Postfix to use
> dotlocks with traditional mailstores. I use the Cyrus' native method
> of storing mail, but if you use regular *nix storage with Postfix, you
> might try setting the following to:
> mailbox_delivery_lock = flock
> virtual_mailbox_lock = fcntl
I'll try that.
> removing the new default setting of dotlock added to the above.
> Except the possible locking issue I'd strongly think that something's
> amiss at the Cyrus' end as Postfix cannot really interfere with the
> mail after it is delivered forward to Cyrus. I wonder if the Cyrus
> mailing lists might be a better place for this question?
Well, if it doesn't work then I will try then on cyrus list.
> PS. And as you're at it, do check that postfix configuration file has
> only spaces in it, not tabs. Haven't found anything from the
> documentation mentioning this, but tabs in the assignments seem to
> cause anything following them to be not understandable by Postfix.
I have no tabs in Postfix config files.
Thank you for quick reply.