Prioritizing messages that gets picked by the spoolmanager

[MKONWEB <mk...@yahoo.com>]

I am a new James User and I need to use version James 2.2.0. I am exploring
options to implement a priority based email processing. Currently the order
in which the messages get picked by the spoolmanager is indeterministic. So
I have issues where emails that need to be dispatched right away get queued
behind scheduled mass emails.

I browsed through the code and see that the email processing order is based
on key set (java.util.HashSet) in 
http://svn.apache.org/repos/asf/james/server/tags/build_2_2_0_fcs/src/java/org/apache/james/mailrepository/AvalonMailRepository.java 
AvalonMailRepository.java . I can patch James to provide a custom iterator.
But it'll make my upgrade path harder. I would like to avoid this if
possible.

Another option I am considering is to have a parallel instance of james app
that has its own smtp and post all higher priority emails to that instance. 

I wanted to check the following: 
1. Do you see any issues with above approaches 
2. Is there a better approach to achieving this? Possibly a custom component
that I can plug-in to James instead of patching.

Thank you.

= MKONWEB
 


-- 
View this message in context: http://www.nabble.com/Prioritizing-messages-that-gets-picked-by-the-spoolmanager-tp22834761p22834761.html
Sent from the James - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org