> I propose that we some changes to the configuration for FetchPOP.  The
> primary change is to add the SMTP address to the configuration, so that
> FetchPOP knows to what address to send the mail.

Not quite sure what you're on about Noel.. what we need to do is to parse
the Received header to get the FOR address from the envelope.
Thereafter the mail will simply be processed by the normal spool.
d.



> There is a bit more to this, actually.  We want to set the Mail object
> recipient to the default address initially, but also want to be
> able to run
> the message through a processor so that we can apply matchers and
> re-set the
> recipient address according to message headers.  The message
> itself remains
> unchanged.

Unless we do this for incoming SMTP messages (which we don't) why would we
do it for fetched messages?

>
> Anyone feel like working on FetchPOP?  For James v2 we can prototype in
> config.xml, but for James v3 we ought to have all of this in a repository.
>
>       --- Noel
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to