Conference abbott::teamlinks_windows

The PAB validate validates using the same algorithm as the addressing 
control. Or at least it is supposed to. What is happening that leads you to 
believe that it is not doing this?

Cheers, 
jal

    We have a site that reported when validating the PAB it does not
    validate against network.dat.
    
    I think I found this to be true also.
    
    In Mail Profile Addressing the selection for use Standard Settings was
    selected.  This is an IOS system.  The logical oa$dds_prime was set to
    1.
    
    There is an entry in network.dat.  If you create a mail message
    and enter part of the username in the To: field the Select Recipients
    dialog box is displayed with this entry in the box.
    
    If I then select the PAB and complete a new entry and enter the
    address that is in the network.dat in the Mail Address field the
    information is taken.  I then select that entry in the PAB  and
    select File Validate and a message is returned
    
    No matches were found for entry beth andres,
    Address: Andres_B@water@hydro.
    
    Would you like to mark this entry external so that it will not be
    validated in the future.
    
    The Address above is in network.dat.
    
    Beth
    

OK I am going to toss this out and see if it is good enough. The pab 
validate validates against the last name field not the mail address field. 
Does this come as a surprise to you? I know it does to me! I started to 
look into how this could be true and when did it change and it seems that 
it has been like this forever. For instance I have an address in 
network.dat BLISSTL1 and the address is "Test Account  (BLISSTL1)" not in 
quotes of course. Now if I were to pass the address back to the addressing 
control it of course would validate because it is a complete address but I 
really want to look the address up again and get the expanded address. In 
order to do this the last name is used and it is looked up again. If the 
result is not the same as the current address then it is not validated. If 
you don't like it TOUGH! Learn to live with it. no.no.no Just kidding!! If 
this is not what you expected please enter a bug with what you would have 
expected. My first thought was that isn't right but the more I think about 
it the less I am convinced. Anyway, give it another try with this in mind 
and see if it doesn't work better. 

Cheers, 
jal

    jal,
    
    OK, so I am still a little confused.  I just played with this a little
    more and I agree it does validate against last name but what if an
    entry is just in network but not in profile.  Will it still validate?
    
    The site I am working this issue for has changed their addressing
    scheme and they need their PABS updated and this was going to be
    done by validating against network.dat.  I can't get this to work
    if I have added an entry to network.
    
    Thanks,
    
    Beth
    

The only thing I can think of is that the node field in network.dat is the 
same as the node called out by the logical OA$PRIMARY_NODE. The AIDA 
server, as would be expected, will not return these addresses to the client 
as they are, by definition, local users and should be serviced by 
profil.dat. If this is not the case then it sounds like something is broken 
for sure and we will need to have a closer look at it.  
 

    JAL,
    
    Well, I cannot get back to the node I was testing on but I know
    the entries in network.dat had a different node in the node field
    that the logical oa$primary_node because until that was changed I
    could not validate against the PAB.
    
    Now I can validate against the PAB but if I create a Distribution
    List with entries from network and try the validate the distribution
    list they do not validate?
    
    I could possibly be doing something wrong and I will reverify the
    node field when the node I need is available again but other than
    that could it be anything else.  If you have a DL with an entry 
    from network.dat and then try to validate the DL was it validate?
    
    Thanks,
    
    Beth 
    

    The node I was testing on just came back.  The node field is
    different that oa$primary_node logical.
    
    Beth
    

Dist List validation? I don't  think you can validate dist list entries 
from the PAB. Am I missing something here?

Cheers, 
jal

    jal,
    
    Sorry if I did not make this clear but they are not validating
    the distribution lists against the PAB.  The dls are being validated
    against whatever is set in mail profile.  The first issue with
    this note was validating the PAB against network.dat.  I have 
    figured out why that is not working for the user and we have
    corrected some of those entries.  
    
    Now this same user is trying to validate the dls using File | Validate
    Selected List from the Distribution List Editor Window.  This is
    where then entries in the dl are not validating.
    
    Beth Andres
    

    jal,
    
    Have you been able to successfully validate a DL against network.dat?
    
    Thanks,
    
    Beth