Implementation of "Right to disconnect"

Hi everybody!

I'm wondering if anybody of you has an experience in implementation of "Right to disconnect".

Probably the easiest way is to just power down POA or at least GMS server outside working hours, but what about a bit more sophisticated rules, like:

All messages sent to employees outside of working hours should be delivered only next working day in the morning (that goes also for messages sent inside same POA), except if message is tagged as High priority or message has word "URGENT" in subject.

How is this handled for example in France, Italy, Germany and other countries with such legislation? Any GW users from those countries?

Kind regards,

Sebastijan

Kind regards,

Sebastijan

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Parents
  • 0  

    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.

Reply
  • 0  

    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.

Children
  • 0   in reply to   

    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.

    Kind regards,

    Sebastijan

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button