Noel J. Bergman wrote:
Doing a store would bypass the James pipeline.  Doing the send
puts the message through local message processing.  This is considered
desirable.  An argument could be made for it being a configuration option.


IMHO, absolutely not... if you want to put it at the top of the
pipeline, put it in the root repository, which is always the top
of the spool for local message processing.

Serge, please clarify your point.  The term "repository" is overloaded a bit
too much for clarity in this context.  I am not at all sure that we are
disagreeing.

FetchPOP inserts mail the same way that the SMTPHandler does, using
sendMail().  Eventually, sendMail() calls setState(), which specifies which
processor.  It does not store the user's mail directly in the user's
mailbox.
Yeah, probably are, so just to clarify...

All sendMail(Mail) does is store the mail object in the _inbound_ repository, which out of the box is something like file://var/mail/spool. So if fetchpop just stored the mail object to file://var/mail/spool repository, you'd have the same result (mail gets processed).

You could have this target repository as an optional configuration setting (as you suggested) so maybe we are agreeing. But since it seemed you were saying that fetchpop had to do sendMail() to get the mail processing to happen, I didn't think we were.

--
Serge Knystautas
Loki Technologies
http://www.lokitech.com


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

Reply via email to