When I was asked a few years ago to spec this out, I was given a criteria of, users should not have low or normal priority mail delivered to them, high priority mail should be delivered, users should be able to access their mailboxes.  From memory (I am getting old so may be slightly out) The solution I came up with was to have 2 POAs per post office, one only doing high priority message delivery and everything else, the other doing all message delivery.  Then just have a cron job to take down/start the second POA at the times required.  Users can still connect access mail, high priority mail is delivered but normal/low priority is queued until the second POA is restarted.

I think message delivery based on urgent being in the subject would be difficult as messages are encrypted in the GW system so we could not check on that easily.  The only way I could see would be at the GWIA use the third party directory and check for urgent in the subject of inbound mail and set the priority before it comes in, the other would be to use a C3PO or Token API to trap a message as it is sent and change the priority, but that would only work for the windows client.

Hi Robin!

Thanks for the reply, interesting idea.

I am wondering, if I have two POAs per post office, to which should I point groupwise client? To the one processing only high priority messages, right? Because it is running all the time?

I also see that there are POA parameters like -nomfhigh, -nomf and -nomflow. Do I understand correctly that for POA doing high priority message delivery and everything else I should use "nomf" and "nomflow"? Or will "nomf" completely disable message file processing, also for high priority messages?

And probably POA responsible for normal and low priority messages but nothing else, I should enable all other "--no*" parameters, like noada, noerrormail, nogwchk, nomtp, nonuu, noqf, ...?

Kind regards,

Sebastijan.

Yes have users point to the POA port that is doing the High priority delivery. This you just set to high priority delivery in the administration console (see below)

The second POA you just have set to do all delivery.  If you wish you can, in admin console,  disable admin task processing, client server, scheduled events, maintenance & quickfinder etc.  Since these are being done on the primary POA.

I have tried this but I must have done something wrong.

What I did:

- On same server I have created new POA (POA-NL) with "Message File Processing" set to "All" (of course with different TCP ports than original POA). I have also disabled admin tasks, client access, scheduled events, maintenance, Quick finder indexing...

- On existing POA I have changed "Message File Processing" to "High Priority Only":

With both POAs running I have tested low, normal and high priority emails from outside and inside. All were delivered, so working as expected.

Then I have stopped POA-NL (POA to deliver all messages) and tried same test. Interestingly, no message was delivered, not even a high priority message.

I waited for 30 minutes then started POA-NL. At that time all messages were delivered.

Any idea why high priority messages were not delivered when POA-NL was stopped, even though running POA has setting to deliver "high priority only"?

Kind regards,

Sebastijan

And you  have created a separate POA startup file for the new poa. This startup file needs a setting for the name of the new poa (POA-NL).

Yes. I needed to do this manually. New poa startup file is copy of original one, only change is name parameter.

I have also checked what is in poa startup file and there are only 3 parameters uncommented: home, name and language

I have also added entry to /etc/opt/novell/groupwise/gwha.conf (copied original poa and changed startup parameter to point to new poa file)

Ok, I see that you enabled --nomflow which is High Priority Only. 

Here is the explanation:
Turns off processing lower priority messages files (message queues 2 through 7).

Mail flow will happen in queues 2 to 7 (2 is high, 4 is normal and 6 is low priority). So this approach does not work because we want to stop to queues 4 - 7!

Ok, I see that you enabled --nomflow which is High Priority Only. 

Here is the explanation:
Turns off processing lower priority messages files (message queues 2 through 7).

Mail flow will happen in queues 2 to 7 (2 is high, 4 is normal and 6 is low priority). So this approach does not work because we want to stop to queues 4 - 7!

Well, I took the good old Tay Kratzer GroupWise 6.5 Administration Book to check the settings.

There it says that --nomflow will check queues 0 -3 but prohibits to chec queues 4 - 7. My statement above is out of the official documentation.

I trust Tay a little bit more .

So repeat your steps again but do it in your startup files. Do not trust the web page! And do not disable any other features like admin messages and so on.

Ah, I remember I had the same problem before, what I did there was to have a cron job running every min to move files from 2 to 0, They then get delivered, but if it works in the startup file so much the better.