> However the Mailet API itself, while beautiful is missing a number of
> significant hooks that we have started to address and will update the
> main MailCatcher project soon.
> Namely there is no call-back when the MAIL FROM or RCPT TO is invoked by
> a remote SMTP server.
That isn't part of the Mailet API at all, and doesn't belong there IMO. In
JAMES, we have pluggable in-protocol handlers that are connected to such
events. I do not know that anyone wants to standardize on our in-protocol
plug-in architecture, which we're still evolving, but that seems separate
from Mailets.
> The problem with the current implementation of the API is that one must
> accept the whole email before you can do any processing as to whether or
> not you want it. For spam control, this is completely unacceptable.
I agree with the latter, but the former is addressed by the aforementioned
in-protocol handlers. Perhaps you're just behind the times with JAMES.
--- Noel
