On 13-11-2011 11:40, Scott Lewis wrote:

My apologies for the repost yesterday; it was not intentional. I was attempting to post a followup from my mobile, when something went awry with the editing options on my phone. Anyway..

I have managed to download and compile my own patched dovecot/dovecot-sieve/dovecot-managesieve modules from scratch, with Thanks to this page

hardc0l2e.wordpress.com/2010/02/26/managesieve-with-dovecot-on-centos-5-4/

But when I run http://mydomain.com/src/configtest.php , I am still getting the following rather non-descriptive error:

"I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=ManageSieve) is bad?"

You can test whether ManageSieve is working properly using this procedure:

http://wiki.dovecot.org/ManageSieve/Troubleshooting

Where else can I look to resolve this? should managesieve show up as its own /etc/init.d service? Or does dovecot simply control it? How can I confirm that deliver is being used as my LDA?

The Dovecot LDA produces characteristic log lines in your system log (http://wiki1.dovecot.org/Logging). For instance, with Sieve enabled, the following is reported upon delivery to INBOX:

Nov 14 10:53:41 host dovecot: deliver(stephan): sieve: msgid=<guid@example.com>: stored mail into mailbox 'INBOX'

Something similar is logged without Sieve. All such messages are prefixed with 'deliver(<user>): '. With mail_debug=yes, more verbose messages are logged as well.

Regards,

Stephan.