locked
Exch2k7 spk3 - E.A.P using "%g@domain.com.br" fail for users without LastName field filled RRS feed

  • Question

  • Hi,

    I found that a new Email Address Policy using the format '%g@domain.com.br' - designed to users with the ExtendedAttribute1 with value 'xyz' - doesn´t work if the user name dont have any character on the 'LastName' field. After fill up that field the EAP worked fine.

    Is this a bug????

    * I followed the following article to create a new EAP: http://technet.microsoft.com/en-us/library/bb124401(EXCHG.80).aspx


    tks, Renato P

    • Edited by jr3151006 Thursday, September 29, 2011 5:35 PM english correction
    Thursday, September 29, 2011 5:34 PM

All replies

  • On Thu, 29 Sep 2011 17:34:19 +0000, jr3151006 wrote:
     
    >I found that a new Email Address Policy using the format '%g@domain.com.br' - designed to users with the ExtendedAttribute1 with value 'xyz' - doesn´t work if the user name dont have any character on the 'LastName' field. After fill up that field the EAP worked fine.
    >
    >Is this a bug????
     
    More like a bad choice of properties. What would you have the address
    policy use for the <local-part> of the address if the givenName
    property is empty?
     
    It would make sense to design your policy with two addresses. One
    using %g and the other using %m or %d. You'd always get at least one
    address.
     
     
    >
    >* I followed the following article to create a new EAP: http://technet.microsoft.com/en-us/library/bb124401(EXCHG.80).aspx
    >tks, Renato P
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, September 30, 2011 1:14 AM
  • Hi jr3151006,

     

    I tested in my lab (Exchange 2010 SP1 and Exchange 2007 SP3):

     

    Exchange  2007 SP3:

     

    I get the same result as your described.

     

    Exchange 2010 SP1,

     

    The issue your described will not occur.

     

    I will do more research on this issue, and update the post.

     

    Thanks,

     

    Evan

    Wednesday, October 5, 2011 9:07 AM
  • Hi Evan,

     

    tks for reply and test. Do you think that is possible ask a patch to fix it or we will need  upgrade our Exchange server from 2007 to 2010?? :)


    tks, Renato P
    Thursday, October 6, 2011 8:17 PM