Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: ludo@gnu.org (Ludovic Courtès)
Cc: ding@gnus.org
Subject: Re: [PATCH] sieve-manage: use auth-source
Date: Wed, 13 Oct 2010 16:44:43 +0200	[thread overview]
Message-ID: <sa362x6tan8.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <87hbgqma0z.fsf@inria.fr> ("Ludovic =?utf-8?Q?Court=C3=A8s=22?= =?utf-8?Q?'s?= message of "Wed, 13 Oct 2010 16:39:56 +0200")

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

On Wed, Oct 13 2010, Ludovic Courtès wrote:

> ‘sieve-manage’ fails for me:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   string-match("DIGEST-MD5" nil)
>   sieve-manage-capability("SASL" "DIGEST-MD5" " *sieve* imap.example.com:2000")
>   sieve-manage-digest-md5-p(" *sieve* imap.example.com:2000")
>   sieve-manage-open("imap.example.com")
>   sieve-open-server("imap.example.com" nil)
>   sieve-manage("imap.example.com")
>   call-interactively(sieve-manage t nil)
>   execute-extended-command(nil)
>   call-interactively(execute-extended-command nil nil)

I've fixed that bug recently. But maybe you use an older version.

> Connecting to that server on port 2000 shows this:
>
> Connected to imap.example.com.
> Escape character is '^]'.
> "IMPLEMENTATION" "dovecot"
> "SASL" ""

This is not valid. The server is saying there's no way to SASL method to
authenticate with.

> Any idea what could go wrong or how I should proceed to debug further?
> It seems to be trying to use SASL, which isn’t supported by this server.

Just put:
disable_plaintext_auth = no
in dovecot.conf. It will then tells you:
"SASL" "PLAIN"

And things will work.

You can also put other authentification mechanisms such as CRAM-MD5,
etc, in auth default { mechanisms = … } in dovecot.conf. I did not had
the time to play with that yet however, but it should also work with
sieve-manage.

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-10-13 14:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 16:16 Julien Danjou
2010-10-05 17:18 ` Lars Magne Ingebrigtsen
2010-10-05 17:28   ` Ted Zlatanov
2010-10-08 15:40 ` Ted Zlatanov
2010-10-08 16:01   ` Julien Danjou
2010-10-13 14:39     ` Ludovic Courtès
2010-10-13 14:44       ` Julien Danjou [this message]
2010-10-13 15:34         ` Ludovic Courtès
2010-10-13 15:51           ` Julien Danjou
2010-10-13 18:26             ` Lars Magne Ingebrigtsen
2010-10-13 18:35               ` Julien Danjou
2010-10-13 18:52                 ` Lars Magne Ingebrigtsen
2010-10-14  9:54                   ` Julien Danjou
2010-10-14 18:58                     ` Lars Magne Ingebrigtsen
2010-10-14 19:09                       ` Julien Danjou
2010-10-14 19:11                         ` Lars Magne Ingebrigtsen
2010-10-14 19:24                           ` Julien Danjou
2010-10-14 19:29                             ` Lars Magne Ingebrigtsen
2010-11-21 14:22           ` sieve-manage & starttls Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sa362x6tan8.fsf@cigue.easter-eggs.fr \
    --to=julien@danjou.info \
    --cc=ding@gnus.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).