Alan Williamson wrote:
Good morning one and all, and it's good to see the Mailet API getting
some attention specifically outside of JAMES. I joined this list after
spotting a blog entry from Danny requesting a discussion.
Unfortunately we never gave this list too much publicity. We should fix
this problem and the blong entry from Danny is a start :-)
[...]
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.
I agree this is a big missing piece.
I think we should provide a more fine API for this. Sometimes mailets
only care of connection data, sometimes of SMTP envelope data (sender,
recipients...), sometimes only of mime message header, sometimes of the
full body, sometimes of the mime structure of the body, sometimes
combinations of the previous.
I think we should provide a mean to make the container aware of this.
Now that even james started supporting fastfail operations (in protocol
handlers) it would be cool if we all could agree on something like
"mailets" for the in-protocol operations.
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
You want to nuke the connection ASAP and only spend the resources to
accept an email you really want. To that end we've added a new
interface that deals with this.
So I am looking forward to being part of this discussion and promoting
the use of the Mailet API to hopefully the point where other vendors and
developers want to start supporting it also.
Do you know anything about what we are doing with the smtp handlerapi in
Apache James Server?
I ask this to understand what is the common knowledge and if I need to
provide some detail about previous discussions on this topic.
Stefano
