Brian Candler schrieb:

> Check that the userdb database does actually contain the correct login name,
> complete with the % sign.

The problem wasn't that I couldn't authenticate but that I wasn't able
to enter the username into userdb in the first place, using the userdb tool:

# userdb "[EMAIL PROTECTED]" set home=/var/vmail/example.com/foo uid=500
gid=500
# userdb "bar%example.com" set home=/var/vmail/example.com/bar uid=500
gid=500
Invalid name: bar%example.com

After entering the name manually into userdb file, authentication
appears to work:

* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION
STARTTLS] Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc.
 See COPYING for distribution information.
x login bar%example.com test
x OK LOGIN Ok.

This is cool. But why does the userdb tool try to keep me from entering
that user? Am I playing against some rule? Will I lose % sign support in
some later version?

Puzzled, %-)

-martin

-- 
Schmitt Systemberatung                                       Linux/UNIX
Giessener Str. 18                                     Internet/Intranet
35415 Pohlheim/Germany                            E-Mail Infrastructure
http://www.scsy.de                                   Antispam/Antivirus

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to