Noel J. Bergman wrote:
I have been thinking about a similar concept for a while now. I haven't looked at how it might fit in with existing code, though.Maybe what is needed is mailets-matcher and an Interceptor(tomcat valve like) API for handlers.Yeah, if we do want to offer support to reject during the SMTP session, I think a different class would be appropriate.I had mentioned something over the summer where I thought that we might have some notion where we could register lightweight filters with a handler, and have that filter "educated" by one or more matchers. It sounds as if we are all converging on a similar idea that will need to be fleshed out.
At first I figured that if the recipients and remote host of each inbound message could be filtered through all of the matchers configured in the root processor at SMTP dialog time, then that could be used as a method of rejecting mail without accepting it.
The trouble is that the matchers in the root processor do not define all of the messages that should be accepted. They also do not all match against message characteristics that are known before the entire message is parsed.
A separate matcher set would have to be defined. These matcher would have to match envelope characteristics, rather than body characteristics.
I think this could work.
ADK
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
