Andy Smith writes:
+---------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | NO | PRI | | | | local_part | varchar(255) | NO | PRI | | | | password_hash | varchar(255) | YES | | NULL | | | mbox_name | varchar(255) | YES | | NULL | | +---------------+--------------+------+-----+---------+-------+The password fields have MD5 passwords stored and look like: {md5}177b8fafcf4d5454f605c563e212f156 But Im not sure this will work with courier from what I read, the docs state that MD5 passwords have to be stored in clear text in MySQL. Any advice from
That's for challenge-response authentication. For normal password authentication, this is fine.
anyone as to whether I can use my existing MySQL table for auth or will I have to recreate passwords for every user? Also the default MySQL config in courier has many more fields, can I get away with just these four fields as used by tpop3d?
No, at the minimum, userid and groupid are also required. You will need to specify a custom query for two reasons, namely because you store the login ID in two separate fields, instead of storing a [EMAIL PROTECTED] in a single field; and you'll also need to return a uid and gid. See MYSQL_SELECT_CLAUSE.
pgpLjoHtvEicL.pgp
Description: PGP signature
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
