I recreated the table, using varchars rather than chars. In addition, I have home, maildir, clear, and crypt set as case-sensitive.
Unfortunately, still no dice. Thanks for the suggestion, thought. It did seem plausible. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Peter C. Norton Sent: Tuesday, June 25, 2002 7:08 AM To: [EMAIL PROTECTED] Subject: Re: [courier-users] MySQL authorization On Tue, Jun 25, 2002 at 09:44:18AM +0300, Antony Dovgal wrote: > > Have you tried using varchars instead of chars? > I don't think this can be the reason. In the postgres module, using char instead of varchar returns a whitespace padded string which prevents matching of hashed passwords. I don't know if the mysql module does the same or not. Why not test it? -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users ------------------------------------------------------- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
