> > I've just tested that it runs and it accept a message in smtp. > > I won't have time this week to do more than this. > > I am doing thorough testing. I am planning to refactor some > more and start work on MatcherMessageHandler.
IMHO any effort to be able to use Mathers/Mailets or even full processors from the MessageHandlers would be useful. > Do you want me to work on something specific for my next release? We could change the default "command unknown" to: 500 5.5.1 Command "COMMANDUSED" unrecognized. 5.5.1 is DSNStatus.PERMANENT+"."+DSNStatus.DELIVERY_INVALID_CMD And here is a few ideas on features related to the new inprotocol command handlers: - add a few commented out sample in the james-config.xml: e.g. Bayesian filter in the MessageHandler. - I would love to see a configurable RCPTHandler that will let us to configure regexps against recipients we allow for relay (not based on local domains but on configuration). - I would also like a confirugable MAILHandler that allow to specify banned from addresses. - Another idea could be an RCPTHandler that check the user inbox quota and reply an error when overquota. - Maybe we could add VRFY and EXPN commands for users that want to enable them (maybe working only when authenticated or from given Ips). - A ConnectHandler that would check how many messages are in the main spool and reply a "too busy, retry later" code instead of accepting the connection. If you like any of this ideas I can help you identifying james services you need and how to use Avalon lifecycle interfaces to gain access to the user db or to the repositories. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
