I agree with some of your comments, I disagree with some others. In
general, I would rather not artificially restrict the approach to implement
a usage policy. And we have other services, e.g., NNTP, where this could be
useful.
I would permit something like:
<filter event="<event>">
</filter>
so that one might be allowed to say:
<filter event="<CONNECT>">
... DNS RBL checks ...
</filter>
<filter event="MAIL FROM">
... sender checks, e.g., sender in fake domain or SPF ...
</filter>
<filter event="RCPT TO">
... recipient checks, e.g., quota, relaying, etc., ...
</filter>
Leaving the choice of what and when to the mail admin, or possibly some
future RFC.
And, just as a talking point, I think that we may want a Mailet that
explicitly provides a return code and message so that we can better collect
statistics.
But rather than hash any of this out now, I think we should do it
post-release.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
