Aaron Wiebe writes:
Getting to the point, I need a little direction here. No offence, but 40 .c files makes for difficult reading. I specifically need to know the points at which courier-imap directly interacts with the maildir itself - getting a list of messages, determaning flags on messages, moving and deleting messages, and inserting messages.
There are many places where something happens to messages in a folder. There is no centralized abstraction layer that can be replaced in order to read messages from some alternative source. This IMAP server was designed for one purpose only: to provide IMAP access to mail in maildirs. As such, everything gets accessed directly, without any elaborate tap-dancing show-and-tell. There are some common functions that are used frequently for some common tasks (the expected message filename does not exist -- perhaps someone changed the message's status, so rescan the maildir and look for the renamed file).
In the future, once this project is done, I may be interested in rewriting your maildir implementation into something a little more flexible and readable. Do you folks accept patches, or is there a contribution doc somewhere I can browse through?
There are no formal contribution procedures. If I don't know you, you will need to make your case and convince me beforehand that what you want to do: 1) makes sense, and 2) is useful. I generally look at unsolicited, out-of-the-blue code patches only from people I already know and trust, and who've proven themselves in the past.
pgplh8S3eLY32.pgp
Description: PGP signature
