I'm getting ready to request a new batch of administrative e-mail addresses to replace an outdated hierarchy within my organization. I have the opportunity of choosing new aliases for 24/7 alert recipients, monitoring recipients, all team members, etc.
What does your org use for these purposes?
Groups in my org use things like: org-dept@, org-dept-all@, org-dept-alert@, org-dept-monitoring@, org-dept-status@.
TIA!!!!!111
-
It depends on the conditions; I worked at a large multinational company and we had to go a stage further than that, because we had org-dept-project@location.company.net, and that had to go to a subset of org-dept-project@company.net, and all mail had to go the other direction.
(Somehow it all worked great; we actually dropped the org names, and when we were talking about a specific project, it went to projectname@company.net, and if it had to go to a whole department, it was dept@company.net)
To actually answer your question, for alerts we went for the syslog standard; our mail system supported *-emerg|alert|crit|err|warn|notice|info|debug@company.net
(actually, dunno who added it in but it was great; full names were expanded, so that *-emergency would redirect to emerg, etc)
Ali Nabavi : Thanks a lot, Andrew! That is very helpful. I never thought about using syslog's convention. Your "org versus project" issue is something I'm grappling with -- sounds very dramatic! -- now. I think I favor your solution for this also.Andrew Bolster : When i started at $COMPANY they had an almost reversed system of what your talking about; project-dept-org-location@company.net, but then switched to a more 'free' convention of project names and departments @company.net. To my knowledge once it was set up and the allocation of names standardised, it actually reduced the mailadmin's workload (only spoke to him at xmas party so his speech and my hearing may have been impaired) Glad to help!From Andrew Bolster
0 comments:
Post a Comment