----- Original Message -----
From: "Neeme Praks" <[EMAIL PROTECTED]>
> I started looking into James for example on implementing a more generic
> messaging server (right now our company needs SMS messaging with similar
> concept to mailet's). Most of the code and configuration stuff is quite
> self-explanatory; however, I couldn't figure out how the <processor> tags
> (in conf files) fit into the general picture. I makes sense to have
> different processors as "root" and "error"... however, how are the emails
> mapped to these different processors? And are there any system-defined
> processors (root, error)?
>
> There is a way to specify a processor when sending emails inside mailet,
but
> is this the only way?

You can think of processors as a block of code.  A message enters the top of
the processor and checks whether it should get processed depending on the
results of each Matcher object.  A mailet then processes the message (if the
Matcher says to) and assuming nothing changes, it moves to the next
matcher/mailet in the processor.  The message then either continues until it
reaches the bottom of the processor (at which point it's destroyed), can get
destroyed mid-processor by setting the message state to GHOST, or it can get
sent to a new processor.

root and error are system-defined processors in the sense that all incoming
messages are sent initially to the root processor, and if there are
exceptions created while processing a message, the message is sent to the
error processor.  The fact that the conf file defines the error processor,
for example, means you can chose whether to notify the sender or the
postmaster or error, or log someplace special, or whatever you want.  There
are no restrictions on the number of processors you can create.

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



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to