From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: SSL problems on dovecot 2.1.7
Date: Thu, 09 May 2013 16:20:59 +0200 [thread overview]
Message-ID: <874necdyk4.fsf@dod.no> (raw)
In-Reply-To: <87txmceaxj.fsf@dod.no>
Turns out this wasn't an SSL issue at all. Or at least I think it
wasn't... it may come back to that.
One problem I had with debugging this, was that I've had no logging
since the upgrade. Which eventually (as in: half an hour ago) led me to
suspect the syslogd... and it turned out that I didn't have one:
rainey:~# dpkg -S /etc/syslog.conf
sysklogd: /etc/syslog.conf
rainey:~# dpkg -l sysklogd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================-==================-==================-============================================================
rc sysklogd 1.5-6 i386 System Logging Daemon
sysklogd exists for squeeze and sid, but not for wheezy and testing:
http://packages.debian.org/squeeze/sysklogd
It turns out debian has changed its preferred syslogd from sysklogd to
rsyslog: http://wiki.debian.org/Rsyslog
An "apt-get install rsyslog" installed the new syslogd and then dovecot
started logging to /var/log/mail.log.
It turns out the reason I can't log in, is that I'm trying a cram-md5
login, which none of the configured password providers can provide:
May 9 15:08:47 rainey dovecot: auth: Fatal: CRAM-MD5 mechanism can't be supported with given passdbs
May 9 15:08:47 rainey dovecot: master: Error: service(auth): command startup failed, throttling for 60 secs
Oh well!
next prev parent reply other threads:[~2013-05-09 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:53 Steinar Bang
2013-05-09 10:14 ` Steinar Bang
2013-05-09 10:44 ` Adam Sjøgren
2013-05-09 11:40 ` Steinar Bang
2013-05-09 14:09 ` Bjørn Mork
2013-05-09 14:20 ` Steinar Bang [this message]
2013-05-09 18:24 ` James Cloos
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=874necdyk4.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).