> Have you tried virtdomains: userid ? This will disable the reverse lookup.
Yes, it doesn't reverse but it also tacks on the domain.tld of the server. Or, more accurately, it tacks on the domain.tld of the interface on which the connection was made. So if 192.168.12.2 is 'mail.domain2.tld' then connections into it would be from '[EMAIL PROTECTED]'. Equally true if there are other IP addresses configured to respond to mail then their domain.tld will be used. > It does work in cyrus and I think it also does work with SASL auxprop > LDAP. It does not work with auxprop SQL where this auxprop plugin will > always append the servername as a realm to unqualified userids. Ah, that explains it. I'll have to compare the source between the sql.c plugin and the others. > you set virtdomains: userid and login with an unqualified userid the > auxprop plugin will always append the servername. The 'auxprop' concept itself? Or the SQL plugin that's called via auxprop? > I may be wrong here, but the defaultdomain setting is there to > "unqualify" qualified userids. So if you login with [EMAIL PROTECTED] as > in your example above the defaultdomain is stripped and the userid > becomes joe. SASL auxprop plugin SQL will then append the servername as > a realm leading to a lookup of [EMAIL PROTECTED] > > So the answer is that auxprop plugin SQL does not support unqualified > userids, I think. Unfortunately you may be correct. Which may lead me back to using pam_mysql via saslauthd. Six steps forward, eight steps back, it seems. Here I was thinking it'd be more efficient to call SQL directly, but noooooooo! Yeesh. Of course by using PAM I get stuck not being able to use challenge-response, correct? -Bill Kearney ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
