T.R | Title | User | Personal Name | Date | Lines |
---|
2594.1 | oa$primary_node not set? | FORTY2::ASH | Grahame Ash @REO | Wed Apr 21 1993 14:23 | 12 |
| Well, with our Network.dat expert currently 'out of the office' I'll have half
a guess.
There is some code in mail recognition which stops the display of network
entries if they are 'the same' as entries in the profile. I think it does this
by comparing the network entry to see if it's the same as 'this system'. And I
think the important thing to check is OA$PRIMARY_NODE - this should be equal
to the NODE in the network entry for the match.
Or something like that!
g
|
2594.2 | oa$primary_node did it! | KIPPIS::OLLIKAINEN | | Thu Apr 22 1993 08:01 | 5 |
| Hi !
That was a good guess!
thanks Grahame
|
2594.3 | Slightly different check in v3.0 | AIMTEC::WICKS_A | on the Streets of San Francisco | Mon Apr 26 1993 22:26 | 11 |
| Tapio,
it's a pity that the NETWORK.DAT expert was out at the same time as me
but Grahame really knows more than he lets on. One thing to add is that
the comparison check changed in v3.0 - there was a note somewhere from
Scott explaining this - so check your system again when you upgrade to
v3.0
regards,
Andrew.D.Wicks
|
2594.4 | The long and the short of it... | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Tue Apr 27 1993 11:06 | 15 |
| Hi,
In V2.4 and V3.0, OA$PRIMARY_NODE should be defined as the remote message router
node. You may run into problems if you redefine it to be the local node.
The 'bug' observed in .0 has been fixed in V3.0: the mail address validation and
recognition code now always uses the local node name for filtering duplicate
entries.
This whole area may improve even more in the future...
As mentioned in .3, if you need more info, searching the conf for notes written
by me will reveal lots of words about NETWORK.
Scott
|