Our organization has lots of people with pagers, so we have internal email
addresses (i.e., page Fred) that alias to the actual pager company email
address (i.e.866...@pagerco.com). When we're out in the field, we often
need to send pages to each other - but unless you've loaded your pager
address book with a couple hundred addresses yourself, you have to address
the messages to 86612...@pagerco.com. Personally, I don't know everybody
else's actual pager address, but I can remember "page Fred" pretty well.
So... what I'd like to set up is a way to have page...@ourorganization.com
alias to the existing "page Fred" internal address so that we can run
messages through our own server and have them automatically end up in Fred's
pager. Our admin is reluctant to set up an entire set of duplicate
mailboxes because it's just one more place to change when somebody's pager
number changes or a new employee comes in. It's clearly best to just have
one place with the actual pager data and let other addresses point to it -
but is there an easy way to set this up?
Thanks for any assistance...
Ben
"Scott Dunham" <sjdu...@telocity.com> wrote in message
news:3da6e5d7$1...@nopics.sjc...
-Peter
"Ben Winzenz" <benwi...@gardnerwhite.com> wrote in message
news:#Nh0RdTcCHA.2524@tkmsftngp11...
Thanks for the advice. I'll see if I can sell the idea - it certainly
doesn't seem all that tough to accomplish. Just to make sure I get it, when
a custom recipient is set up, it can have both an external destination
internet address (86612...@pagerco.com) and an incoming alias
(page...@ourorganization.com) that will automatically get the incoming
message routed to the right custom recipient address in the Exchange
database, thence off to the external address? There essentially wouldn't
be any internal action at all with these custom recipient addresses: they'd
just
be relay points passing the incoming message to the external recipient
address.
I suspect that Peter is right - the existing "page Fred" set of addresses is
probably already configured as custom recipients, so if it's just a matter
of hanging the incoming alias addresses on them, I should be able to talk
the IT poobahs into this - even if I have to do all the initial entries
myself. :-)
"Peter Durkee" <pdu...@mac.invalid> wrote in message
news:#pJYKUVcCHA.1544@tkmsftngp09...
"Scott Dunham" <sjdu...@telocity.com> wrote in message
news:3daa3290$1...@nopics.sjc...