> your configuration example: > > > <smtp-processor> > <matcher class="SenderCheck"> > [...] > <code> 220 </code> > </matcher> > </smtp-processor> > [..] > <rule class="SenderCheck"> > <code>5xx</code> > </rule> > <accept-rule class="accept"> > <code>220</code> > </accept-rule> > [..]
I just added ENHANCEDSTATUSCODES support to james smtp server. So you should take care to add a DSN status to every smtp reply and not only the SMTP code. E.g: 220 2.1.5 Recipient ok 550 5.7.1 User unknown I think (as I said in past) that allowing full smtp reply code control at this level will be an error. I haven't seen in your example how a command handler change the current smtp context: e.g: accepting a recipient means we add the recipient to the collection to whom we will send the message, rejecting it means we don't add it. When a DATA is received the server must check wether we accepted at least a recipient or not. I wouldn't like the SMTP server to read the "code" that an handler returns and decide how to behave dependently on the first char of that code. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
