| Title: | MAILBUS 400 User Forum |
| Notice: | kits 100-109 - Infocenter //www.digital.com/info/messaging |
| Moderator: | IOSG::MARSHALL |
| Created: | Thu Jun 11 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3210 |
| Total number of notes: | 9174 |
Is Mailbus 400 going to be made to route purely on a DDA?
This is an interoperability problem with Microsoft Exchange that
I didn't really understand until now.
If you send mail from Exchange to a user via a connector such as
SMTP over an X.400 backbone, then Exchange sends it to an X.400
address composed of the SENDING sites X.400 address with a
DDA attached. If this goes over an X.400 connector to Mailbus 400
then the mail will get bounced back to the Exchange server which
sent it and non-delivered as looping.
Having talked to Microsoft they are routing purely on the DDA.
Mailbus 400 currently doesn't route this way which means that
this stuff just doesn't work.
The requirement seems to be to get an X.400 address with a
DDA of SMTP (changing to RFC-822 soon supposedly) and route to
the right place based on just the DDA type, basically ignoring
the rest of the X.400 addressing information.
I don't know if there will be a problem on return mail to Exchange
since I assume that if it hits an Exchange IMC then that will have
a directory entry and be able to map the smtp address to an X.400
address and send if over the X.400 backbone correctly addressed.
Is this being worked on?
thanks,
Mike
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3155.1 | Exchange is at fault here | IOSG::MARSHALL | Wed Mar 26 1997 11:29 | 30 | |
What you want should be possible without using DDA routing.
As an example, the internal system I use has MAILbus 400 connected to SMTP via
the MAILbus 400 SMTP gateway. Mail bound for (or coming from) the gateway has
an O/R address with an RFC-822 DDA, and MAILbus 400 routes it just fine. The
way this is done is by using a unique address stem for gateway addresses; in our
case it is:
C=GB; A=GOLD 400; P=INTERNET; DDA:[email protected]
MAILbus 400 routes on the C=GB; A=GOLD 400; P=INTERNET part, and this works
perfectly because nothing else uses that address stem. Taht is the correct way
these things should be done.
>> Exchange sends it to an X.400 address composed of the SENDING sites X.400
>> address with a DDA attached
Is this configurable? If you can't tell Exchange what O/R address terms to use
to get to an SMTP gateway via X.400, then Exchange is BROKEN. For Exchange to
assume that its own address is a valid thing to use for someone else's gateway
is completely ridiculous (it would be like me saying well, I don't know your O/R
address, so I'll use mine and just change my name on it to yours and let someone
else figure it out). That is where the problem lies in this case; DDA routing
would just be a way to work around that problem, and it would be better to fix
it at source.
However, DDA routing is on the shopping list for future development. You
should submit a formal product requirement to Geoff Oades@REO if this is a
priority for you.
Scott
| |||||
| 3155.2 | exchange isn't configurable | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue Apr 01 1997 11:46 | 8 |
It isn't configurable in Exchange hence the question.
I am surprised that this hasn't been picked up since we are supposed to
have an alliance....
I'll send mail to Geoff...
cheers,
Mike
| |||||