hehe..... straight and to the point. From looking over the code, it looks like I could add the functionality by editing authldaplib.c. Probably in auth_ldap_do3. I could use copy_value to retrieve the expiration date from ldap. I figure the code could go either just before or after:

if (rc == 0 && callback) rc= (*callback)(&auth, arg);

What function does the *callback run? and does it have any bearing on if I put my code before or after. If after I basically planned on something like:

// pseudo-pseudo code obviously :) if (rc == 0) { copy_value(my_ldap_fp, expire_date, "expire", &p, user) ;

// would need to find c functions /librarys for modifying unix timestamps. if (//compare dates) rc = -1 ; else rc = 0 ; }

This would return a bad password (permanent error) correct? Is there anyway that I could return a custom negative return code, and have the calling function report back a custom error message to the user? i.e. "Password has expired" (I know, very original, thoughtful and catchy error message :-) (I would need to add the "custom error message" functionality to both imapd and pop3d.

Thanks for the help, Bryan