- gnarwl.c: readHeader() is quite picky about the syntax of To: and Cc:
  (but this shouldn't be a problem).

- Probably lots of memory leaks

- dbstuff.c may not be y2038 complient, it uses EPOC as base for 
  expiration.

- dbstuff.c stores the timestamp by casting time_t to int, which will then
  be put into char*. Seems to work so far ...

- dbstuff.c copies time_t into int, and stores that into char*. Will that
  work reliably ?!

- No checks, wheter an email goes to several recepients. For example: If
  webmaster is forwarded to jane and joe, and jane goes on vacation, 
  writing to webmaster will get you an reply from jane. The funny part
  about this is: if joe goes on vacation, nothing will happen. This is because
  gnarwl only uses ldap_first_entry(), ignoring subsequent hits. Don't know,
  how to fix this (blacklist ? taking ldap_filter apart and count how 
  many ldapentries are associated with mail=%s ?)

- Only the first match of the ldap query is used
- Gnarwl uses ldap_search_s(), this means, gnarwl will block until it gets
  the datafrom the LDAP server.
  
