Re: [SLE] Sieve: unable to connect at line 169
From: Sandy Drobic (suse-linux-e_at_japantest.homelinux.com)
Date: 09/13/05
- Previous message: Peter Nikolic: "Re: [SLE] friendly English lesson"
- In reply to: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Next in thread: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Reply: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Reply: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 13 Sep 2005 20:49:01 +0200 To: "suse-linux-e "@suse.com
Gianni Socionovo wrote:
> Hi Sandy,
>
> thanks a lot for the "working in progress" help you are giving me.
> Below you can see the steps i tryed following your suggestions.
You're welcome. (^-^)
> Telnet localhost sieve shows:
>
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v2.2.8" "SIEVE" "fileinto reject
> envelope vacation imapflags notify subaddress relational regex"
> OK
> > logout
> OK "Logout Complete"
> Connection closed by foreign host.
>
> I cannot see the row "SASL" "LOGIN PLAIN" though i should (I think i
> should see MD5 also as results from my entries in imapd.conf and
> imapd-local.conf below) . This is the main problem i think.
>
> In my imapd.conf and imapd-local.conf i have this entry for sasl
>
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: md5
>
Okay, we're getting closer. Normally saslauthd does not support md5, it
only supports plain and login. The example you mentioned also set
sasl_mech_list=plain. Though you did mention that Imap was working for
you, right?
I assume that you copied the pam file according to the example for sieve
as well as for imap?
>> The SASL mechanisms should be the same as those you use to login to
>> Imap.
>
> telnet localhost imap shows:
>
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> * OK myfully.qualified.hostname Cyrus IMAP4 v.2.2.8 server ready
> a01 user myuser.mydom.com secretpwd
> a01 OK User logged in
> ? logout
> * BYE LOGOUT received
> ? OK completed
> Connection closed by foreign host.
Okay, authentication with Imap obviously works
>> sieveshell localhost
>> (with no additional parameters)
>>
> If you have a system user (with login shell) with a mailbox in Cyrus,
> please login as that user and try to connect to sieveshell with
> I create a system user (with login shell) with a mailbox in Cyrus.
> sieveshell localhost returns:
>
> connecting to localhost
> unable to connect to server at /usr/bin/sieveshell line 169
I would like you to check something...I dimly remember that I had a bit
of trouble, too, when I tried to set up sieve. Somewhere in the
Smartsieve docs they mentioned that a libmcrypt was needed for sieve to
work correctly.
what does rpm -qa | grep -i "crypt" gives as result?
Sandy
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Peter Nikolic: "Re: [SLE] friendly English lesson"
- In reply to: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Next in thread: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Reply: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Reply: Gianni Socionovo: "Re: [SLE] Sieve: unable to connect at line 169"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|