locked
Exchange 2007-Dist Group Caching Old List?? RRS feed

  • Question

  • I apologize if this has been covered in earlier posts...I spent the last 2 days searching everywhere for an answer...

    I've inherited an Exchange 2007 server.  I was asked to make some changes to an existing distribution group.  Group type is Universal.  Scope is Distribution.  I made the changes in the EMC and verified that it sync'd with AD.  When I send internal emails to the group name, the emails go to the new members.  If I send an external email (from my gmail account) into the group, it goes to the OLD list of people.  This list has been changed for the last 3 days and it still hasn't sync'd up.  I've deleted and re-created the list.  I've restarted the File Distribution service and eventually the server and emails are still going to list members that no longer are on the list.

    Based on what I'm seeing, it looks as if the old distribution list is cached somewhere, but I have no idea where to look to clear it out.

    Thanks for your help,

    bob

    Wednesday, February 15, 2012 1:20 PM

All replies

  • Are you using an Exchange Edge server as your internet facing mail server or a third party appliance?

    TBrennan

    Wednesday, February 15, 2012 5:44 PM
  • As indicated check the edge and transport server in question .

    Also check the logs and try starting the transport and AD service on hub if possible .

    There is a cache present on e2007 , but it is less compared to e2010
    Wednesday, February 15, 2012 6:00 PM
  • We're using Symantec Mail Security instead of an Exchange Edge server.
    Wednesday, February 15, 2012 6:08 PM
  •  Check this

    Hub Transport server maintains a recipient cache that is used to look up recipient and distribution list information. The recipient cache updates every four hours and you can't modify the recipient cache update interval. Therefore, changes to transport rule recipients, such as the addition or removal of distribution list members, may not be applied to transport rules until the recipient cache is updated. To force an immediate update of the recipient cache, you must stop and start the Microsoft Exchange Transport service.

    http://social.technet.microsoft.com/Forums/en/exchangesvrtransport/thread/65205fb5-9ca7-4eeb-8bbc-8528c9966aa5



    Check for any related events on hub server and increase logging if possible
    also run the folliwng command to check the recipient cache .. get-transportconfig | fl
    http://technet.microsoft.com/en-us/library/bb124703.aspx
    Wednesday, February 15, 2012 7:36 PM
  • The fact that the DL is correctly expanded when the email originates within your Exchange organization but does not when it comes from an external source would seem to indicate the problem is with the appliance handling Internet mail.  Unless your organization is configured so a different HUB server handles all mail coming from the Symantec Mail Security system.  In that case take a hard look at that specific HUB server and try to use a different HUB (the same as an email originating internally would use).

    TBrennan

    Wednesday, February 15, 2012 8:19 PM
  • hello,

    First you should send emails to new email address manully not to DL from your gmail account. That make sure those email address are capable to rescive emails from the internet and if this problem related to DL or not.

    Regards


    Chinthaka Shameera | MCITP: EA | MCSE: M | http://howtoexchange.wordpress.com/

    Wednesday, February 15, 2012 11:37 PM