1

I'm trying to install Cyrus with SASL for authentication. I'm struggling getting logins to work properly though. I'm trying to setup virtual hosting, as we'll have several domains worth of email on this host.

In my imapd.conf:

sasl_pwcheck_method: auxprop
virtdomains: true
defaultdomain: fqdn.example.com

From sasldblistusers2:

[email protected]: userPassword

I have a mailbox called user.matt, and I tried creating [email protected] and I got an error saying the mailbox already exists. With this setup, I am able to login using imtest localhost -m DIGEST-MD5 -a matt, however I am unable to using imtest localhost -m DIGEST-MD5 -a [email protected]. There is also not a UNIX user called matt on the system. Does anyone have any idea what I am missing?

Exact error from syslog:

imap[23310]: badlogin: localhost [127.0.0.1] DIGEST-MD5 [SASL(-13): user not found: no secret in database]

3
  • Did you already read the logs? Oct 19, 2011 at 8:39
  • @JannePikkarainen: All the logs say is auth failed because imapd thinks the user doesn't exist. Oct 19, 2011 at 9:03
  • Just got an idea, read my answer to you :) Oct 19, 2011 at 9:13

1 Answer 1

2

Do you have this in your imapd.conf?

loginrealms: fqdn.example.com

(imapd.conf man page tells you this):

   loginrealms: <empty string>
        The list of remote realms whose users may authenticate using cross-realm authentication identifiers.  Seperate each realm name by a space.  (A  cross-realm  iden‐
        tity is considered any identity returned by SASL with an "@" in it.) Note that to support multiple virtual domains on the same interface/IP, you need to list them
        all as loginreals.  If you don’t list them here, your users probably won’t be able to log in.
4
  • No I don't. Will try this tomorrow at work, but if this a real config variable, it'd definitely explain the problem. Will accept when I've tried it. Oct 19, 2011 at 9:47
  • It is a real config variable. Oct 19, 2011 at 10:19
  • Sorry, that first comment sounded horrible. Unfortunately, this doesn't seem to be helping. I've edited into the question the exact syslog that's being output. Oct 19, 2011 at 21:56
  • 1
    Gah, I'm an idiot. At some point last night I deleted the user from SASLdb. This works perfectly, thanks a lot! Oct 19, 2011 at 22:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .