You're viewing a single thread.
This is my work insisting on using people's roles for their email addresses "so the accounts can be reused when they quit." Thats, not how any of this works.
You might want to look into letting them reuse yours, that place sounds painful.
Do... do they think email accounts are a rare resource? Of all the things to be concerned about, they're worried about conserving something so intangible, cheap, and abundant?
Not sure how that's supposed to help Line Go Up, but okay.
It makes sense for some outside facing roles. For instance, you may want all vendor billing going to [email protected] rather than an individual.
I wouldn't do it for the whole company, but it could have some uses.
I think I see the logic that you might want to give say customers for product X the email [email protected] to contact, but that should map to your actual email addresses, not replace them!
Yeah this is the way. Most companies will have aliases for departments that mass send into a managed inbox or if its one person they have an actual email and then their role is an alias that redirects to their email.
position changes are as easy as just moving the alias to the new person in the position, this let's your externals be able to use the same email without having to keep the same email account for everything.
Its every fucking role.
[email protected]
[email protected]
pm
it
scheduler
am
prLike what the fuck am I looking at. I just want to fucking email Beth in accounting.
If you need to learn Beth's email, just first send an email to [email protected]/