[ http://issues.apache.org/jira/browse/JAMES-486?page=comments#action_12411958 ]
Stefano Bagnara commented on JAMES-486: --------------------------------------- 1. to do so you should store the old error_message somewhere.. maybe as mail attributes. 2. no: after the first attempt, if it results in a temporary failure the lastUpdated is updated, otherwise it is removed from the spool because it is a permanent success or failure. 3. I tend to think that this command is used to anticipate the next attempt to now: if I call the flush 5 times in 5 minutes I did 5 attempts and should be counted in the attempts calculation (I know this has pros and cons, but it is importat we understand them). If we reset the counter to 0 then the command should be called "requeue" because it resets the current queue and restart a new queue. ---- Evaluating the above my *current* idea is that the best would be to fix JAMES-499, and change the flush command to update the last_updated to 0 (or null if it works). I'm still undecided about the "error_message = error_message -1". > Spool managing commands for remote manager > ------------------------------------------ > > Key: JAMES-486 > URL: http://issues.apache.org/jira/browse/JAMES-486 > Project: James > Type: New Feature > Components: Remote Manager > Reporter: Norman Maurer > Assignee: Norman Maurer > Fix For: 2.4.0 > Attachments: RemoteDelivery-retry-fix.patch, RemoteManHandler.diff, > RemoteManager-SpoolManagement.patch > > Spool managing commands for remote manager - first proposal for review -- 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]
