You can simulate the problem if you authenticate horde3 users using another horde module, like IMP, which I'm sure many people do.
If you do have horde3 configured to authenticate users with IMP, having the ingo1 conf.php script empty disallows any horde3 authentication - so you can't generate a new conf.php script. Disabling ingo1 is the only way to allow yourself to log in, even to change authentication methods, if the ingo1 conf.php script is blanked and you're using IMP to authenticate. At least it certainly seems so in our case! Thanks for the idea on disabling ingo1 in the registry.php file Pelayo... Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
