Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 42244 - Usernames of the form "user@domain.org" do not work with saslauthd from cyrus-sasl-2.1.17.ebuild
Summary: Usernames of the form "user@domain.org" do not work with saslauthd from cyrus...
Status: RESOLVED DUPLICATE of bug 39497
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-20 06:00 UTC by Ben Cressey
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Cressey 2004-02-20 06:00:35 UTC
I emerged cyrus-sasl-2.1.17.ebuild last night, in an attempt to get a functional cyrus-sasl install.

(aside: I had previously installed cyrus-sasl-2.1.14, and rimap in this ebuild no longer works correctly with the new /etc/services that's been released.  Any chance of the fix in the 2.1.17 ebuild being backported?)

I am using saslauthd with rimap as the authentication mechanism.  My imap user names are all of the form "user@domain.org", the user's email address.

This works fine under 2.1.14, but under 2.1.17, the "domain name" part of the user id is split off into the "realm" value:

Feb 20 06:46:38 ghostwheel saslauthd[6831]: do_auth         : auth failure: [user=benjamin.cressey] [service=smtp] [realm=koden.net] [mech=rimap] [reason=remote server rejected your credentials]

In this case the "user" field should be benjamin.cressey@koden.net.  Using just the first part causes authentication to fail.  The realm should probably remain my mail server, but I am not sure that's particularly important.



Reproducible: Always
Steps to Reproduce:
1. Configure saslauthd to use rimap.
2. Create an imap user with a username of the form "user@domain.com"
3. Attempt to authenticate to SASL.  (my MUA is Outlook Express, but I could also reproduce the problem by connecting directly to my MTA and supplying the credentials from there.)

Actual Results:  
SASL authentication fails even when using the correct password.

Expected Results:  
SASL authentication should have succeeded.

MTA: postfix
Comment 1 Tuan Van (RETIRED) gentoo-dev 2004-03-26 20:57:09 UTC
see bug #39497
Comment 2 Max Kalika (RETIRED) gentoo-dev 2004-03-27 08:35:05 UTC

*** This bug has been marked as a duplicate of 39497 ***