s multiple accesses is really necessary.
> -Original Message-
> From: Ask Bjoern Hansen [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 08, 2002 5:32 PM
> To: Richard Clarke
> Cc: [EMAIL PROTECTED]
> Subject: Re: persistent Mail::ImapClient and webmail
>
>
> On
, 2002 9:28 AM > To:
[EMAIL PROTECTED] > Subject: persistent Mail::ImapClient and
webmail > > > List, > I
have the task in my hands of creating a web mail > application.
Initial > thoughts lead me to think I would use an external popper to
> pop mail a
On Fri, 7 Jun 2002, Richard Clarke wrote:
> p.s. Yes quite obviously if I have 100 children then I'll be connected to
> the IMAP server 100 times per user, hence possibly the need to have a either
> a dedicated daemon connected to the IMAP server once or some successfuly way
> of sharing IMAP obj
that as a service so
I think they might get mad if I gave away our product.
I hope this helps.
Joe
> -Original Message-
> From: Richard Clarke [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 07, 2002 9:28 AM
> To: [EMAIL PROTECTED]
> Subject: persistent Mail::ImapClient and we
M
> To: [EMAIL PROTECTED]
> Subject: persistent Mail::ImapClient and webmail
>
>
> List,
> I have the task in my hands of creating a web mail
> application. Initial
> thoughts lead me to think I would use an external popper to
> pop mail and
> parse it
List,
I have the task in my hands of creating a web mail application. Initial
thoughts lead me to think I would use an external popper to pop mail and
parse it into a database for retrieval by the modperl application. The only
problem here is that I must provide the implementation of the mail
