sieve and SASL

Dan White dwhite at olp.net
Wed May 11 17:42:31 EDT 2011


On 11/05/11 17:35 -0400, Chris Conn wrote:
>Hello,
>
>I am trying to get sieve working with a RPM distro of Cyrus I built
>using Invoca.  I believe my problem is caused by timsieved not
>advertising LOGIN or PLAIN capability and causing the client
>(horde/ingo....) to fail`;
>
>"IMPLEMENTATION" "Cyrus timsieved v2.4.8-Invoca-RPM-2.4.8-1.el6"
>"SASL" ""
>"SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags
>notify envelope relational regex subaddress copy"
>"STARTTLS"
>OK
>
>
>after SASL is "", which usually has;
>
>"SASL" "PLAIN"
>
>in other implementations I have seen.  The error I see in horde/ingo is;
>
>There was an error activating the script. The driver said: No supported
>authentication method found. The server supports these methods: , but we
>only support: DIGEST-MD5,CRAM-MD5,EXTERNAL,PLAIN,LOGIN
>
>I note that horde/ingo seems to not see any useable authentication
>methods and therefore fails.
>
>Is there something I forgot to set somewhere to allow sieve to use PLAIN
>or LOGIN?

What does your imapd.conf look like? In particular, your sasl entries and
allowplaintext.

Use pluginviewer/saslpluginview to list the mechanisms that are installed
on the server, and make sure you have PLAIN/LOGIN installed if those are
the mechanisms you intend to use.

-- 
Dan White


More information about the Info-cyrus mailing list