comment on

In general, my answer to questions like this is that freshmeat is your friend. A search for IMAP gives quite a number of results. Freshmeat has a nice filter-by-category function, though. Hitting the filter link next to "Environment :: No Input/Output (Daemon)" gives you 16 projects, #5 of which is called DBMAIL, and seems to be exactly what you're looking for.

As far as the path sepperator thing goes...

It shouldn't be a difficult change to make at all. I suspect you wouldn't even have to know C if your source-diving skills are in good shape.
What client are your users using? Would it figure it out itself?

Also, many mail folder formats have one file per message... it may not be neccessary to go with a non-standard IMAP server.

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

In reply to Re: (OT) Giving users what they want / My mail administration dilemma by theorbtwo
in thread (OT) Giving users what they want / My mail administration dilemma by submersible_toaster

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks