> I suspect that mail which fails the condition will be automatically
> terminated if it reaches the end of the processor, rather than
> falling back through (which *I* think it should do..)
Yes, it is automatically deleted. This has been the case since before James
1.2. A section:
//Add a Null mailet with All matcher to the processor
Mailet mailet = mailetLoader.getMailet("Null", mailetcontext, null);
Matcher matcher = matchLoader.getMatcher("All", mailetcontext);
in JamesSpoolManager.initialize() can be found as long ago as in:
http://cvs.apache.org/viewcvs.cgi/james-server/src/org/apache/james/transpor
t/Attic/JamesSpoolManager.java?rev=1.14&hideattic=0&view=markup. Current
versions of the code handle that differently by delegating the
responsibility to the processor class.
> remember that the contents of the standard processors aren't sacrosanct,
> and you can add as many new processors as you wish in order to get the
> job done.
Absolutely. The stock config.xml is just one way of configuring a server,
and it has evolved as people have contributed generally useful changes.
I'm thinking that it might make sense, at least to clarify things, to move
the anti-SPAM measures into a separate processor, rather than leaving them
all in root.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
