locked
Add Single SMTP Address to Multiple Accounts RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Environment: Hybrid Exchange 2013 with Office 365 (E3 plan) and, of course, ADFS for our domain

    Issue:

    Need to have copy of all incoming emails to certain accounts on O365 to be forwarded to another mailbox at on-premisses Exchange.

    When we use the normal way (through admin page of O365) the users finds out after a while, and they simply disable that configuration.

    Need either:

    1. A way to setup the forwarding without allowing the user to disable it. This was possible in Exchange 2003 and 2007 (not sure about 2010).

    2. A way to add their SMTP address as secondary address on the target mailbox. Again this was possible in Exchange 2003 (not sure about the later versions).

    Notes: please keep in mind before any suggestions this is a side requirement away from retention policy and DLP

    Thank you in advance,

    Saturday, October 5, 2013 6:19 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    This really sounds like a job for a "Distribution Group" (dg). That's basically the job of a distribution group - the mail gets sent to, for example, finance@mydomain.com - and that "finance" address is a "distribution group" so that, any message sent to that group auto-magically gets sent to every member on the distribution group.

    The "dg," in effect, becomes like a secondary smtp address to every member on the dg.

    If you setup a protected dg, it should not allow the users to change it; i.e., a dg should only be able to be modified by the "dg administrator" (whoever you designate as being able to change the dg).

    Please remember to Vote Helpful and/or Mark as Answer if appropriate. Thanks!

    tnjman

    Sunday, October 6, 2013 5:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can do that using Powershell and the Set-Mailbox cmdlet. As detailed here http://community.office365.com/en-us/wikis/solutions/4298.aspx using the EAC doesn't allow what you need, but via Set-Mailbox you can include the -DeliverToMailboxAndForward parameter. So you have something like :

    Set-Mailbox -Identity John -DeliverToMailboxAndForward $true -ForwardingSMTPAddress manuel@contoso.com

    which will forward the message to Manuel while still delivering it like normal to John, and since I assume your users don't have that kind of access to your setup they shouldn't be able to detect or change the setting.

    See http://technet.microsoft.com/en-us/library/bb123981(v=exchg.150).aspx for more info on Set-User.

    In terms of your second suggested option, it's never been possible to have the same SMTP address configured on two mailboxes (or objects in general) in the same setup, Exchange will always complain that the alias already exists. In your setup it might possibly let you add it, but I think all that would happen is that the first server to receive the message would receive it, but it would never reach the other since it's already been delivered.

    Saturday, October 5, 2013 7:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Keith,

    Thanks for the quick response. I'll try the command line option although I'm not very optimistic about it.

    Regarding the shared SMTP address, that was at a client environment and functioning very well. However, I’ve just remembered, it was never used as primary SMTP address for any of the recipients (they had several users who should monitor the webmaster@domain.com). While in this particular case, the address I used is the primary of the protected mailbox.

    Sunday, October 6, 2013 5:35 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    This really sounds like a job for a "Distribution Group" (dg). That's basically the job of a distribution group - the mail gets sent to, for example, finance@mydomain.com - and that "finance" address is a "distribution group" so that, any message sent to that group auto-magically gets sent to every member on the distribution group.

    The "dg," in effect, becomes like a secondary smtp address to every member on the dg.

    If you setup a protected dg, it should not allow the users to change it; i.e., a dg should only be able to be modified by the "dg administrator" (whoever you designate as being able to change the dg).

    Please remember to Vote Helpful and/or Mark as Answer if appropriate. Thanks!

    tnjman

    Sunday, October 6, 2013 5:47 AM