T.R | Title | User | Personal Name | Date | Lines |
---|
4072.1 | Try enclosing the routing term in quotes | IOSG::COTTINGHAM | | Tue Apr 12 1994 17:32 | 7 |
| I Think this problem should be raised in the Maibus conference as
our V1 interface to Message router uses " AT " as a routing delimiter.
Enclosing the routing term in quotes might help. i.e.
"5=computer at large"
Regards
Alan
|
4072.2 | | KERNEL::OTHENJ | | Tue Apr 12 1994 19:14 | 18 |
| Hi,
I thought this problem only occured if sending from ALL-IN-1???
If I try "computer at large" in the Organization field, I get the
message
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\AT\
and it seems to hang the screen up - very odd!!
I have tried it with 'computer at large' and I get the same problem as
.0
Thanks,
Julie
|
4072.3 | | KERNEL::OTHENJ | | Tue Apr 12 1994 19:21 | 9 |
| Hi,
I have just tried this from DECmailworks and the Organization is not
altered, so I think it is ALL-IN-1 that is translating the "AT" sign
(although I am probably wrong!)
Thanks,
Julie
|
4072.4 | Two problems, one-and-a-half solutions :-) | IOSG::MARSHALL | A glitch in reality | Tue Apr 12 1994 20:17 | 28 |
| There are two totally unrelated problems here:
1) originator not authorized to use Gateway".
This is perfectly correct. The originator has to have a DDS entry on (or
accessible from) the MRX node in order to use MRX. This is because MRX needs
the info in DDS in order to convert the originator's Message Router mail address
into an X.409 address.
2) "5=computer at large" has been translated to "5=computer@large"
I think it is ALL-IN-1 that is translating the "AT" sign
No, ALL-IN-1 isn't translating the AT, the archaic Message Router interface
used by ALL-IN-1 is translating it. However, in ALL-IN-1 V3.1, ALL-IN-1 *will*
translate it, so it then becomes our problem :-| We can't disallow the use of
AT as a delimiter, as although now discouraged and obsolete, there are a lot of
people with a lot of messages and distributionm lists that still use it :-(
The solution, as Alan said, is probably to enclose the whole term in quotation
marks. However, as you discovered, this screws up the X400 form :-(
So, for the time being create the address by hand, so you can add the quotation
marks. If it's too big to create in the TO field, use a nickname for it. A
longer term fix to the X400 form and associated command procedures will require
a formal bug report.
HTH,
Scott
|
4072.5 | | KERNEL::OTHENJ | | Wed Apr 20 1994 16:07 | 34 |
| Hello,
Thanks for everyones replies so far on this, but I have done some
testing here and am still getting nowhere.
If I try
"@5=computer at large"
then the address does not get translated to org unit (i.e. it does not
recognise the 5= part as all the string is encompassed with quotes).
If I try
@5="computer at large"
then I get the message
Unrecognised recipient name
in a non-delivery mail notification. By looking at the .nbs file, it
can be seen that the organistaion is passed as
"computer at large"
and not
computer at large
and as dds is looking for a complete match, the dds lookup fails. Any
other ideas?
Julie
|
4072.6 | try @"5=computer at large" | IOSG::COTTINGHAM | | Wed Apr 20 1994 17:24 | 6 |
| Have you tried @"5=computer at large"
i.e. enclose just the routing information in quotes
Mailbus conference may be able to help further
Regards
Alan
|
4072.7 | Try this.... | POKIE::BISHOP | | Thu Apr 21 1994 22:55 | 20 |
| X400 ADDRESSING is defined as follows:
1 COUNTRY
2 ADMD
3 PRMD
4 ORG UNIT
5 ORG
6 SURNAME
7 GIVEN NAEM
8 INITIALS
* Domain Defined attribute
The @ sign is used as a delimiter for these values.
I think you will find that the ORG value is not
needed to get a successful delivery to the X400
recipient - if you test again without ORG specified and
receive a nondelivery notification stating Ambiguous User
then you will need additional values to make the X400
recipient unique.
|