On 11 Aug 2008 at 8:24, Eduardo M KALINOWSKI wrote:
How are you calling deliver in postfix? Do you see in postfix's logs the
messages being handled to deliver?
Hmm, oddly enough, adding a .forward in the users home dir with
| /usr/libexec/dovecot/deliver
Then everything works. Any
On 8/11/2008, Harondel J. Sibble ([EMAIL PROTECTED]) wrote:
dovecot-1.0.7-2.el5
dovecot-sieve-1.0.2-6.el5
If I'm not mistaken, sieve support has improved dramatically in the
latest versions (1.1.2 being the current).
Use the atrpms repo...
--
Best regards,
Charles
Harondel J. Sibble wrote:
Following the wiki here for system users
http://wiki.dovecot.org/LDA/Postfix
I never get any info in the logs about cmusieve, the only way I see anything
show up is if I add the transport settings to postfix/master.cf or see below
From reading the list archives,
On 11 Aug 2008 at 8:24, Eduardo M KALINOWSKI wrote:
To use -d ACCOUNT, you need a master socket where deliver looks up
user information: see the Virtual Users section in
http://wiki.dovecot.org/LDA . But if you are not using virtual users
(and only used -d to test), you should not need it.
On 11 Aug 2008 at 6:35, Charles Marcus wrote:
If I'm not mistaken, sieve support has improved dramatically in the
latest versions (1.1.2 being the current).
Use the atrpms repo...
Sure, I see that in the version history, but that won't necessarily solve the
current problem I am having
On 11 Aug 2008 at 8:24, Eduardo M KALINOWSKI wrote:
How are you calling deliver in postfix? Do you see in postfix's logs the
messages being handled to deliver?
Well, I seem to have made the problem worse as I was adjusting settings
throughout the day.
Here's where I am at, if I now enable
Okay, after reading the wiki and list archives, I am confused.
I am attemping to get the deliver LDA working on a centos 5.1 system
# rpm -qa | grep dovecot
dovecot-1.0.7-2.el5
dovecot-sieve-1.0.2-6.el5
# rpm -qa | grep postfix
postfix-2.3.3-2
so that I can use Sieve for mail filtering to imap
