[ http://issues.apache.org/jira/browse/JAMES-468?page=comments#action_12373674 ]
Stefano Bagnara commented on JAMES-468: --------------------------------------- Is this alternative described in an RFC ? If not we should follow the standard behaviour (452 and accept remaining recipients) >From my "status codes knowledge" I believe that a 571 code sent in reply to an >RCPT TO will make the client think the recipient address is permanently >invalid and that you will not be able to send any other message to the same >recipient and this is not the intended behaviour. > Limit MaxRcpt per Email > ----------------------- > > Key: JAMES-468 > URL: http://issues.apache.org/jira/browse/JAMES-468 > Project: James > Type: New Feature > Reporter: Norman Maurer > Assignee: Stefano Bagnara > Fix For: 2.3.0a2 > Attachments: DataCmdHandler-maxrcpt.patch, RcptCmdHandler-maxrcpt.patch, > SMTPServerTest-maxrcpt.patch, SMTPTestConfiguration-maxrcpt.patch, > james-config.xml-maxrcpt.patch > > I add a new configuration option to RCPTCmdHandler to limit the RCPT that are > set per Mail. This can be usefull for Admins that want to set a limit for > RCPTs. > The RCPT count get reseted if the DATACmdHandler get called. > Here it is.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
