Q: Will imapproxy run on my alpha/mac/microwave/... ?
A: I don't know. Since I have only a tiny bit of experience with writing 
   portable code, I suppose it's possible it won't work. If you believe 
   your platform should be supported, feel free to port it ! 
   Please let me know if it works too.

Q: The program compiles nicely, but when it starts, it says there is 
   no configfile ?
A: You need a configfile with the options (or at least an empty configfile 
   to use defaults). Unless you changed defines.h, the default configfile 
   is named ".imapproxy" without the quotes, and is located in the 
   working directory of imapproxy. You can also supply the name of a 
   configfile at the commandline. Please read the section about configuring 
   and running the program, in the INSTALL file.
   
Q: The program compiles and I made a configfile, but when I connect to the
   listening port, it says "* BYE Access to proxy denied." ?
A: The default action of the built-in accesslist, is to deny all connections.
   Please read the configuration section in the INSTALL file.

Q: When I start the proxy, I get the following error: 
   "Error: Couldn't setup listener !"
A: The most likely problem is that you specified a portnumber < 1024, and 
   are not running the program as root. Since I do not recommend running the 
   program as root, I advise you to change the portnumber to something > 1023.
   It is also possible that another program is using that port.

Q: I enabled debug in the config file and sent a SIGHUP to imapproxy, but I see
   no debug messages in the logs ?
A: Debug messages are sent to the same log facility as the other log messages,
   but on loglevel LOG_DEBUG. Perhaps you need to edit syslogd.conf ?

Q: I enabled debug in the config file, but I receive no debug at all ! 
A: Make sure that you put "debug on" at the very start of the config file, in 
   case an error occurs before debugging is turned on.
   Also make sure that debugging is not turned off later in the config file, 
   as the configfile parser only uses the last set value for a variable.

Q: I changed the password of my mail-account, and I can now login with both 
   my old and new password. How is this possible ?
A: Imapproxy keeps connections to the imap-server open, once the client logs 
   out. The password and username associated with this connection are 
   remembered, in order to bind an authenticated client to it. 
   Since imapproxy only caches the usernames and passwords, it can not know 
   when you changed your password, and will keep the old username and password 
   associated with a connection, untill that session expires.
   If you stop using the old password for a while, you won't be able to log 
   in with it, because the connection(s) associated with it, will have expired.

Q: But if imapproxy keeps connections alive, it is possible that a session 
   never gets terminated ! This is a breach of security, isn't it ?
A: It is true that this scenario would lead to a security breach. However,
   an aging option is built in, which stops records from being reused too long.
   By default, this option is set to 0, indicating that no aging is performed.
   Setting this value to (for example) 5, will stop an old password from being
   used more than 5 times. More information about this can be found in the 
   configfile documentation (the INSTALL file).
   
Q: I don't understand how this imapproxy can work. Where can I get more 
   information ?
A: Information about the inner working of imapproxy, is available on 
   the website at http://www.kuleuven.net/projects/imapproxy/

Q: I use the CRAM-MD5 authentication method on my IMAP server, but imapproxy
   cries that it doesn't support it.
A: CRAM (Challenge-Response Authentication Mechanism) is a mechanism in which 
   the server sends a challenge, and the client replies to that challenge. 
   With CRAM-MD5, the server challenges the client to "encrypt" a given string 
   with a shared secret (a password or key). Since imapproxy caches the 
   password/username pairs, it would also need the shared secret. This entire 
   method is too complex for me, and I chose not to implement it. Sorry ! 
   However, the client should understand the LOGIN command, which is supported 
   by imapproxy...

Q: I have an idea/bugreport/bugfix/donation proposal/... Where can I send it ?
A: You may send it to imapproxy@kuleuven.net.