What to consider for choice of database account email - prevent 'out of office' reply problems

Here's the problem we are having: I have Job Notifications turned on for several SQL Server nightly Jobs. Sometimes those email notifications come to me when I'm out of office, and my Outlook is set up to automatically send "out of office" emails. **The problem is that the "out of office" emails are going to my coworker.** Similarly, when my stored procedures sends users a warning email, if the users have "out of office" emails turned on, my co-worker gets all those "out of office" emails. My coworker is annoyed. My co-worker set up our SQL Server database mail. He set up an account called 'Internal DBAs' and then put his own email as the email for the 'Internal DBAs' account. The "Internal DBAs" account is the only database mail account currently set up on the SQL Server. I'm not very familiar with SQL Server database mail, but I'm guessing that this is why my coworker is getting all the "out of office" emails. I would think that the solution would be to substitute my coworker's email address with an un-monitored email address to use as the database mail account. That way no one gets the "out of office" emails. We didn't have this problem with our old SQL Server. I don't know why he set things up this way, but I think my coworker thinks that he needs to have his email address as the email to use for the database mail account. Is there a good reason to use a DBA's personal email address as the address for the database mail account? Does anyone have a sense of what is standard practice? Or am I mistaking the cause of the problem? Any illuminating thoughts would be most appreciated!