I think this is misguided and would seem to reinforce bad practices, poor etiquette and bad culture.<p>bad practices, i.e. if you want work life balance, don't check your email when you aren't in the office. Manage your co-workers expectations that you won't be replying when you aren't on the clock, don't work for a boss that has the expectation that you are functionally on-call at times when you should be with your family and friends.<p>bad etiquette, i.e. stop sending so much email yourself and stop responding to email that doesn't merit a response. OOO messages and other auto-responders are vile and just add to the mess - calendar requests, project updates, FYIs, CC"s, etc. Most of this messaging traffic is just unnecessary and only adds to the weight of one's inbox without making much of a contribution. Deal with your messaging in your app - turn off the notifications and update options and actually log into your calendar once or twice a day to view requests. Same goes for the rest of your web apps (I'm thinking of project and task tools like Asana, et al).<p>bad culture, i.e. be part of the solution, tell people when their email practices are dysfunctional. We have this thing at our office where staff will send out an email to 10 people asking "when is a good time to get together?" which triggers an avalanche of 25 messages all with conflicting instructions and requests about what might be the best time. I actively ask people to use my calendar and ignore the rest of the email on the subject. People are slowly starting to use my calendar for this sort of thing. Same goes for after-hours email. If you don't want people to think you'll respond after-hours, don't send email after hours! In the most extreme cases, if you can't change culture, then find a better place to work. Life is too short.<p>Corporate policy along the lines of "delete email while you are on vacation" just serve to reinforce all of these other bad practices. Email can be a force for good, you just have to use it that way.