Exchange routing of FAX: address format??

microsoft.public.exchange.misc

14 Apr 2009 3:17 PM

Chris

I'm seeing an issue with how Exchange routes the FAX: format. We are using a
fax server software that runs a connector on the Exchange server. When users
want to send a fax, they type in the recipient address as
[FAX:Jane@999-555-1234]. When this fax is sent, it takes on the format of
'IMCEAFAX-Jane+40999-555-1***@domain.com' as it is routed by the Exchange
system. Exchange somehow recognizes this format (categorizer?) and knows
that it is supposed to route it to the fax specific connector.

The problem that I am having is that we are trying to integrate a 3rd party
email system that will share the smtp name space domain.com. I followed the
documentation at http://support.microsoft.com/kb/321721/ and it worked great
for routing messages between systems. However the emails with the
'IMCEAFAX-Jane+40999-555-1***@domain.com' address format seem to get routed
to the 3rd-party email sytem and create a routing loop and NDR with a 4.4.6.
Due to the way the shared namespace setup works, Exchange appears to be
saying "there isn't an Exchange mailbox for the address
'IMCEAFAX-Jane+40999-555-1***@domain.com' so I'm forwarding to the 3rd party
email system. It's as if Exchange now prioritizes the emails to be routed
via the shared name space over the fax connector. It never bothers to
evaluate if its a fax or not and doesn't route it to the fax connector.

Another thing is that now the authorative smtp name space for Exchange is
domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
submitted, should it not append @domain.local now instead? If it did, this
would fix my problem as @domain.com is the shared name space specified in the
smtp connector.

Keep in mind that none of the above is a problem with the fax software,
connector, etc. It never even makes it that far. The problem lies somewhere
in the categorizer or routing engine of Exchange.

15 Apr 2009 12:03 AM

Ed Crowley [MVP]

You should ask the developer of the fax server software.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:D57692C8-58D6-4D9E-86D8-8C9F666DB579@microsoft.com...
> I'm seeing an issue with how Exchange routes the FAX: format. We are
> using a
> fax server software that runs a connector on the Exchange server. When
> users
> want to send a fax, they type in the recipient address as
> [FAX:Jane@999-555-1234]. When this fax is sent, it takes on the format of
> 'IMCEAFAX-Jane+40999-555-1***@domain.com' as it is routed by the Exchange
> system. Exchange somehow recognizes this format (categorizer?) and knows
> that it is supposed to route it to the fax specific connector.
>
> The problem that I am having is that we are trying to integrate a 3rd
> party
> email system that will share the smtp name space domain.com. I followed
> the
> documentation at http://support.microsoft.com/kb/321721/ and it worked
> great
> for routing messages between systems. However the emails with the
> 'IMCEAFAX-Jane+40999-555-1***@domain.com' address format seem to get
> routed
> to the 3rd-party email sytem and create a routing loop and NDR with a
> 4.4.6.
> Due to the way the shared namespace setup works, Exchange appears to be
> saying "there isn't an Exchange mailbox for the address
> 'IMCEAFAX-Jane+40999-555-1***@domain.com' so I'm forwarding to the 3rd
> party
> email system. It's as if Exchange now prioritizes the emails to be routed
> via the shared name space over the fax connector. It never bothers to
> evaluate if its a fax or not and doesn't route it to the fax connector.
>
> Another thing is that now the authorative smtp name space for Exchange is
> domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
> submitted, should it not append @domain.local now instead? If it did,
> this
> would fix my problem as @domain.com is the shared name space specified in
> the
> smtp connector.
>
> Keep in mind that none of the above is a problem with the fax software,
> connector, etc. It never even makes it that far. The problem lies
> somewhere
> in the categorizer or routing engine of Exchange.

15 Apr 2009 1:12 PM

Chris

Heh, can't say I didn't expect answers like that. The problem is not the fax
software and that's what they say. According to message tracking, it never
even makes it to the fax connector. Exchange acts like the shared name space
forward takes precedence over the routing of the FAX: format.

Show quoteHide quote

"Ed Crowley [MVP]" wrote:

> You should ask the developer of the fax server software.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "Chris" <Ch***@discussions.microsoft.com> wrote in message
> news:D57692C8-58D6-4D9E-86D8-8C9F666DB579@microsoft.com...
> > I'm seeing an issue with how Exchange routes the FAX: format. We are
> > using a
> > fax server software that runs a connector on the Exchange server. When
> > users
> > want to send a fax, they type in the recipient address as
> > [FAX:Jane@999-555-1234]. When this fax is sent, it takes on the format of
> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' as it is routed by the Exchange
> > system. Exchange somehow recognizes this format (categorizer?) and knows
> > that it is supposed to route it to the fax specific connector.
> >
> > The problem that I am having is that we are trying to integrate a 3rd
> > party
> > email system that will share the smtp name space domain.com. I followed
> > the
> > documentation at http://support.microsoft.com/kb/321721/ and it worked
> > great
> > for routing messages between systems. However the emails with the
> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' address format seem to get
> > routed
> > to the 3rd-party email sytem and create a routing loop and NDR with a
> > 4.4.6.
> > Due to the way the shared namespace setup works, Exchange appears to be
> > saying "there isn't an Exchange mailbox for the address
> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' so I'm forwarding to the 3rd
> > party
> > email system. It's as if Exchange now prioritizes the emails to be routed
> > via the shared name space over the fax connector. It never bothers to
> > evaluate if its a fax or not and doesn't route it to the fax connector.
> >
> > Another thing is that now the authorative smtp name space for Exchange is
> > domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
> > submitted, should it not append @domain.local now instead? If it did,
> > this
> > would fix my problem as @domain.com is the shared name space specified in
> > the
> > smtp connector.
> >
> > Keep in mind that none of the above is a problem with the fax software,
> > connector, etc. It never even makes it that far. The problem lies
> > somewhere
> > in the categorizer or routing engine of Exchange.
>
>

15 Apr 2009 2:38 PM

Ed Crowley [MVP]

The way I understand it is that Exchange knows nothing about "FAX:"
addresses unless you install a DLL that resolves those addresses to
something. That DLL would be provided by the facsimile software provider.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:6876B427-7C70-4DD1-8EEF-9CCBB07CF794@microsoft.com...
> Heh, can't say I didn't expect answers like that. The problem is not the
> fax
> software and that's what they say. According to message tracking, it
> never
> even makes it to the fax connector. Exchange acts like the shared name
> space
> forward takes precedence over the routing of the FAX: format.
>
> "Ed Crowley [MVP]" wrote:
>
>> You should ask the developer of the fax server software.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:D57692C8-58D6-4D9E-86D8-8C9F666DB579@microsoft.com...
>> > I'm seeing an issue with how Exchange routes the FAX: format. We are
>> > using a
>> > fax server software that runs a connector on the Exchange server. When
>> > users
>> > want to send a fax, they type in the recipient address as
>> > [FAX:Jane@999-555-1234]. When this fax is sent, it takes on the format
>> > of
>> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' as it is routed by the
>> > Exchange
>> > system. Exchange somehow recognizes this format (categorizer?) and
>> > knows
>> > that it is supposed to route it to the fax specific connector.
>> >
>> > The problem that I am having is that we are trying to integrate a 3rd
>> > party
>> > email system that will share the smtp name space domain.com. I
>> > followed
>> > the
>> > documentation at http://support.microsoft.com/kb/321721/ and it worked
>> > great
>> > for routing messages between systems. However the emails with the
>> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' address format seem to get
>> > routed
>> > to the 3rd-party email sytem and create a routing loop and NDR with a
>> > 4.4.6.
>> > Due to the way the shared namespace setup works, Exchange appears to be
>> > saying "there isn't an Exchange mailbox for the address
>> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' so I'm forwarding to the 3rd
>> > party
>> > email system. It's as if Exchange now prioritizes the emails to be
>> > routed
>> > via the shared name space over the fax connector. It never bothers to
>> > evaluate if its a fax or not and doesn't route it to the fax connector.
>> >
>> > Another thing is that now the authorative smtp name space for Exchange
>> > is
>> > domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
>> > submitted, should it not append @domain.local now instead? If it did,
>> > this
>> > would fix my problem as @domain.com is the shared name space specified
>> > in
>> > the
>> > smtp connector.
>> >
>> > Keep in mind that none of the above is a problem with the fax software,
>> > connector, etc. It never even makes it that far. The problem lies
>> > somewhere
>> > in the categorizer or routing engine of Exchange.
>>
>>

17 Apr 2009 8:42 PM

Chris

I previously said:

>Another thing is that now the authorative smtp name space for Exchange is
>domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
>submitted, should it not append @domain.local now instead? If it did, this
>would fix my problem as @domain.com is the shared name space specified in
>the smtp connector.

And this was exactly my problem. After the primary address in the default
recipient policy was changed to domain.local and Exchange was no longer
marked auhtoritative for domain.com, every Exchange server's routing engine
needed to be restarted. I restarted it on just the ones that were the
bridgehead servers for the new connector created when setting up the shared
name space. So the user would be connecting to a front-end server, send the
FAX: address and the Exchange server they were connected to would append
domain.com instead of domain.local. Once the routing engine was restarted on
the other servers, every email addressed without a specific smtp domain
appended would get domain.local.

Show quoteHide quote

"Ed Crowley [MVP]" wrote:

> The way I understand it is that Exchange knows nothing about "FAX:"
> addresses unless you install a DLL that resolves those addresses to
> something. That DLL would be provided by the facsimile software provider.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "Chris" <Ch***@discussions.microsoft.com> wrote in message
> news:6876B427-7C70-4DD1-8EEF-9CCBB07CF794@microsoft.com...
> > Heh, can't say I didn't expect answers like that. The problem is not the
> > fax
> > software and that's what they say. According to message tracking, it
> > never
> > even makes it to the fax connector. Exchange acts like the shared name
> > space
> > forward takes precedence over the routing of the FAX: format.
> >
> > "Ed Crowley [MVP]" wrote:
> >
> >> You should ask the developer of the fax server software.
> >> --
> >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> ..
> >>
> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
> >> news:D57692C8-58D6-4D9E-86D8-8C9F666DB579@microsoft.com...
> >> > I'm seeing an issue with how Exchange routes the FAX: format. We are
> >> > using a
> >> > fax server software that runs a connector on the Exchange server. When
> >> > users
> >> > want to send a fax, they type in the recipient address as
> >> > [FAX:Jane@999-555-1234]. When this fax is sent, it takes on the format
> >> > of
> >> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' as it is routed by the
> >> > Exchange
> >> > system. Exchange somehow recognizes this format (categorizer?) and
> >> > knows
> >> > that it is supposed to route it to the fax specific connector.
> >> >
> >> > The problem that I am having is that we are trying to integrate a 3rd
> >> > party
> >> > email system that will share the smtp name space domain.com. I
> >> > followed
> >> > the
> >> > documentation at http://support.microsoft.com/kb/321721/ and it worked
> >> > great
> >> > for routing messages between systems. However the emails with the
> >> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' address format seem to get
> >> > routed
> >> > to the 3rd-party email sytem and create a routing loop and NDR with a
> >> > 4.4.6.
> >> > Due to the way the shared namespace setup works, Exchange appears to be
> >> > saying "there isn't an Exchange mailbox for the address
> >> > 'IMCEAFAX-Jane+40999-555-1***@domain.com' so I'm forwarding to the 3rd
> >> > party
> >> > email system. It's as if Exchange now prioritizes the emails to be
> >> > routed
> >> > via the shared name space over the fax connector. It never bothers to
> >> > evaluate if its a fax or not and doesn't route it to the fax connector.
> >> >
> >> > Another thing is that now the authorative smtp name space for Exchange
> >> > is
> >> > domain.local. When the email with recipient [FAX:Jane@999-555-1234] is
> >> > submitted, should it not append @domain.local now instead? If it did,
> >> > this
> >> > would fix my problem as @domain.com is the shared name space specified
> >> > in
> >> > the
> >> > smtp connector.
> >> >
> >> > Keep in mind that none of the above is a problem with the fax software,
> >> > connector, etc. It never even makes it that far. The problem lies
> >> > somewhere
> >> > in the categorizer or routing engine of Exchange.
> >>
> >>
>
>