> > > In-Protocol processor for SMTP handler: > > > I don't like this, sorry mate, because (pls read all of this, it is > > *constructive*): > > I am feeling a bit snarky at the moment, but did you and the > others who replied, happen to read the REST of my e-mail, or > just the first part?
Hi Noel, I read both parts, but I've doubt on the first one: the In-protocol processor. I think that we should first improve (add) delivery status tracking in every james part, then we can simply add the "in-protocol" handler or make the root processor synchronized with the smtphandler (so that it returns SMTP errorcodes instead of bounces). We need informations from mailet about what they did with our messages: we need this for your in-protocol processor but I think we more need this for a good DSN behaviour. I already tried to discuss some solutions for this but haven't received much feedback. Look at the comment here: http://issues.apache.org/jira/browse/JAMES-322 In fact we need a delivery status tracking object that mailets and the linearprocessor (perhaps the mailetcontext too) will update with their informations: SMTP in-protocol processor or DSNBounce mailet will then use this object to decide what to do. Is there an extensible way to provide this feature? Any idea? I think that once resolved the DSN tracking issue for ESMTP-DSN support then we will have a simpler solution than the in-protocol processor. I agree about your second proposal: I would like further details and better I would like to know if Mike's work on the MINA based SMTP handler already provide this behaviour (when there is ready code is better to start from there instead of running utopic discussions ;-) ). Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
