COOL SITE

The postlogin hook is only designed to be called when IMP is 
responsible for logging the user in.  if you are authenticating via 
horde, the IMP login code isn't called.

AFAIK the postlogin hook is only supposed to be used if Horde 
authentication is done by IMP. Why don't you use Horde's 
postauthenticate hook instead?

here is the code snippet for _imp_hook_postlogin auto creating 
default/fixed folders

when using horde with kolab auth (problem probably applies to other 
auth methods), the used login screen is the horde login.php screen.



what i want:



   o use _imp_hook_postlogin

   o test for fixed folders, default folders (SPAM, Trash, etc.) and 
if not exist, create them



while settings this up i made the experience, that _imp_hook_postlogin 
is only very rarely called on login. my horde's login.php redirects 
directly to the imp INBOX view. sometimes IMP says that the user is 
not yet authenticated and offers IMP's login.php screen in main frame. 
on a frame reload (main frame) IMP's login screen disappears and the 
INBOX is shown. i suppose this issue is related to some sort of IMAP 
timeout (that i can live with).



but: only when this detour on login takes place (every 10-20 logins) 
the _imp_hook_postlogin function is called. this is not really reliable.



do work around this, i applied the attached patch ,, 
20090507_IMP_postlogin_workaround.patch''. i am aware that 
_imp_hook_postlogin now gets called on every IMP page load (i guess).



FYI find also attached my hook to check for existence of certain 
default/fixed folders.