locked
OLD DOMAIN RRS feed

  • Question

  • Hello,

    I use Exchange 2007 and have some users who have SMTP address with an old domain that we barely use.

    I would like to know how I could indicate to internal and external to replace the *@priordomain.com with the *@currentdomain.com ??

    Also would it be possible to track timestamp, sender,recipients and messagesubject of senders who tried to reach my users through the old domain?

    Many tanks in advance,

    Graig

    Tuesday, August 14, 2012 12:50 PM

Answers

  • For your first question, replacing the @priordomain with the @currentdomain as the users' primary SMTP address (reply address) should be a good start, if you haven't done so already.

    For your second question, you should be able to pull that information from message tracking.   An example would be:

    Get-MessageTrackingLog -server "Hub_Server_Name" -start "start_time" -End "end_time" -EventId receive | ? {$_.Recipients -like "*@priordomain.com"} | ft timestamp, sender, recipients, messagesubject


    -Matt

    Tuesday, August 14, 2012 2:48 PM
  • Hi Graig,

    A potential option would be to use a transport rule to append a disclaimer to each message that states something to the effect of the domain name change.   You could then scope the disclaimer transport rule to just those that have the old domain, so that it only appends the disclaimer to those targeted users.


    -Matt

    Thursday, August 16, 2012 1:50 PM

All replies

  • For your first question, replacing the @priordomain with the @currentdomain as the users' primary SMTP address (reply address) should be a good start, if you haven't done so already.

    For your second question, you should be able to pull that information from message tracking.   An example would be:

    Get-MessageTrackingLog -server "Hub_Server_Name" -start "start_time" -End "end_time" -EventId receive | ? {$_.Recipients -like "*@priordomain.com"} | ft timestamp, sender, recipients, messagesubject


    -Matt

    Tuesday, August 14, 2012 2:48 PM
  • Thanks Matt,

    But is there any transport rule I can maybe use to inform senders that @priordomain should now be @currentdomain ?

    The @priordomain with the @currentdomain is already in place. My goal is to inform internaly an dexternaly senders not to use @priordomain  and later on delete the domain: priordomain.

    Graig

    Thursday, August 16, 2012 12:42 PM
  • Hi Graig,

    A potential option would be to use a transport rule to append a disclaimer to each message that states something to the effect of the domain name change.   You could then scope the disclaimer transport rule to just those that have the old domain, so that it only appends the disclaimer to those targeted users.


    -Matt

    Thursday, August 16, 2012 1:50 PM