james-server-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: understanding matcher/mailet pairs
Date Sat, 17 Jan 2004 15:25:16 GMT
> finding out how to understand the matcher/mailet concept


> after each mailet processes a mail, the state of the message
> is examined. If the state has been changed, the message does
> not continue in the current processor."...

In context, "the state" refers a specific thing.  It does not refer to the
overall state of the mail, but literally to a property of that name.  The
"state" property is actually the processor name that should be handling the
mail object.  The GHOST state is special, and is the terminating state.

For matchers, see the above mentioned thread.  Matchers are not binary,
although some can give that impression.  They bifurcate recipient sets into
matching and non-matching sets.  Each non-empty recipient set then proceeds
independently through the pipeline.

> <mailet match="All" class="Null"/>

All recipients would be put into the matching set, and a mail object
containing that set given to the Null mailet, which would then discard it.

> <mailet match="RecipientIsLocal" class="LocalDelivery"/>

Recipients considered local would be put into the matching set for
processing by LocalDelivery, which will set the state to GHOST afterwards
after processing.  Others would be put into the non-matching set, which
would continue in the pipeline.

> how do the mailets determine either "RecipientIsLocal" or "HostIsLocal"?

They don't.  Matchers do.  See:

	--- Noel

To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

View raw message