[valarauca1]

As a contractor at Daimler, and somebody who is technical works for a German company this trend is catching on in a lot of Germany, and frankly I'm tempted to try it myself.

It solves a lot of problems in a single blow, and most problems people have with it can be answered by:

You shouldn't use your work email for that

or the opposite

You shouldn't use your personal email for that

[cpwright]

It depends, I think there are probably a reasonable number of automated processes that could be messed up by something like this. For example, reminders that you need to do some sort of training or HR process could get black holed; creating a larger problem in the long run (e.g., instead of doing it at your leisure you have to do it in a big rush).

That isn't something that falls under your "you shouldn't use your work email for that", and it may be an acceptable trade-off; but it is certainly something that could cause pain. Probably not as much pain as the number of emails you'd wade through anyway, but something to consider.

[valarauca1]

Most automated processes thats report to one and only maintainer who's currently on vacation sound like a problem. Responsibilities and event emails should shift accordingly with vacation.

Also HR department invitations that do not have a secondary reminder, or take place while an employee is on vacation sound like the issue of the HR department not that employee in particular.