> If you want a law with teeth, prohibit employers from emailing workers outside of work hours
1. Do automated mails count? For example, we've got several automated reports that run outside of work hours and email results to the people who care about them. We run them outside of work hours because they use a lot of CPU, RAM, and/or data from the databases, which could hit resource limits if we ran them during the day.
2. I'm not in the IT department but it helps with my work to know what issues IT has been dealing with, so I've subscribed to the mailing list that IT's monitoring system send alerts to when something goes wrong. The alerts can happen outside of my work hours. Would these count as my employer emailing me?
3. Suppose I'm a senior engineer, and I supervise a couple of junior engineers. I know that one of them has been having trouble coming up with a good solution to a particular problem, and I was not able to come up with anything either. Late one night at home, I see a link in an HN discussion to a paper that gives a great solution to that problem.
Would I not be allowed to use the "Email link..." feature in my browser to send a link to the paper to that junior engineer right then? Would I have to bookmark it, or mail it to myself, or something like that, and then during work hours mail it?
If the above emails would not be allowed, it would be a pain to have to enforce that by just making people and programs try to not send mail outside of work hours. Reports would have to know the work schedules of everyone they send to, and have a way to defer sending if the report is generated outside a given person's hours. Same for people who are personally sending mail.
So the way you'd probably have to do it is either in the SMTP server or the POP/IMAP server. The former would have to hold mail until the recipient's work hours, or the later would have to not allow it to be read outside of the person's work hours.
OK...that could be done. It will also need to know about exceptions to one's regular hours, such as vacations, which could be a pain if HR's systems are properly isolated from other company systems.
There should also probably be a white listing system, because some employees want to get out of hours email. For example, I want to know when things go wrong outside of work hours, because when that happens it (1) is usually something that I can ssh in and fix in a couple minutes, and (2) it is often something that if allowed to fester all night will disrupt numerous overnight activity like reports and re-billing subscription customers, which generates a whole lot of high priority work that I will have to deal with during my next work hours, and can turn what is normally a fairly relaxed job into multiple days (possibly requiring overtime--which does not generate extra pay because I am salaried) that are quite stressful.
I would gladly give up 5 minutes of watching TV or reading (which is what I am doing 99% of the time when something I can quickly fix goes wrong outside of work hours) to save several days of work hell.