Oh, well, of course you are right. I was locked in thinking of what i
particulary need from the mail servlets, and it was a kind of email customer
service interface. Like people would ask questions and the servlet would
reply according to the keywords in the message with excerpts from the
comany's FAQ.
Serge Knystautas wrote:
> I started thinking of several far fetched examples as to why this won't
> work (notes scribbled below), but I have 2 really good reasons (IMHO)
> why this won't work. (I agree it'd be a nice hack if it allowed us to
> work against other mail servers, but consider these issues.)
>
> 1. There is delivery information that is not contained in the email
> message itself. You designate through SMTP's RCPT TO command who this
> message should be delivered to... these addresses are in no way required
> to be in the email address.
>
> 2. It restricts mail servlets as receivers only... a real life example
> is such as attaching a disclaimer on all email leaving the company (or
> logging it, whatever)... you need to process email messages as they are
> handled by the SMTP server and not wait for them to arrive at a POP3
> address.
>
> It also means you need a separate mail box for every address you're
> going to consider processing. This introduces much more overhead and
> administration it seems to the mail server... it also means you can't
> use dynamic email addresses (not sure whether it's a good practice or
> not).
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> ------------------------------------------------------------
> 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]
