Mailing list client processing example:
Admin of list.working-dogs.com sets up a machine for running bots and sets
up one of the bots to retrieve and send mail on behalf of
[EMAIL PROTECTED] ,[EMAIL PROTECTED] and so
on. As [EMAIL PROTECTED] ,this bot forwards messages it receives
to all the recipients on the list.
As [EMAIL PROTECTED] this bot replies to the mailing
list registration requests and so on.
I guess it can be done not on the server. Where am I wrong?
Daniel
Federico Barbieri wrote:
> Daniel Sadolevsky wrote:
> >
> > My 1 cent here:
> > Why if so the mail servlet api should reside on server, and not be
something
> > like "mail client bot framework", i.e. reside on the client? It can be
then
> > integrated seamlessly with all the existing mail servers (sendmail,
> > exchange, ...)
> >
> > Daniel
> >
>
> Miss your point...
>
> Some processing MUST be performed server-side. Take the mailing list as
> example.
> Other things like message filters reside on the client but that's not
> our buisness!
>
> Federico
>
> *-----------------------------------*
> "Troubles occurr when two people try
> to be intelligent in the same time."
> - Murphy
> *-----------------------------------*
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
