On Mon, Jan 26, 2009 at 7:22 AM, Daniel Watts <
d@...> wrote:
> Dear Devs,
>
> I am pretty sure a while ago I saw someone who was talking about the
> squirrelmail imap handling layer in his own application. Presumably
> because they can then rely on a imap library that is maintained by some
> mail experts (you!).
>
> We're trying to do this ourselves but have found there is a whole bunch
> of stuff (eg in imap_general.php) that is non-imap - eg calls to
> creating error boxes and use of global language variables.
>
> These require certain other webmail related files to be required which,
> of course, is added overhead.
>
> Do you have available anything/anymethod that doesn't require these
> extra includes? Or do we just need to go through and strip out anything
> that isn't directly related to interfacing with imap?
There is not anyone I know of using the IMAP code separately for
exactly the reason you found. Doing what you are trying to do is part
of the work needed to abstract that code so it is better suited for
use in the RPC interface, from whence any application can then make
use of it.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword-----
squirrelmail-devel mailing list
Posting guidelines:
http://squirrelmail.org/postingguidelinesList address:
squirrelmail-devel@...
List archives:
http://news.gmane.org/gmane.mail.squirrelmail.develList info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
