We currently have Exchange setup to manage our email addresses as domain.com. How can I setup a subdomain (sorry if this isn't the correct terminology) so that I can also create emails like @portal.domain.com? Thanks!

Depending on the Exch version create a Recipient Policy (2003) or a Email Address Polic (2007/2010). If @portal.domain.com is going to be used externally, then configure MX records for this domain and point to your Exch server or relay server/device if used.Sukh

Thanks for the reply Sukh828. I hope you don't mind a few follow-ups... FYI, I am using Exchange 2010... First, when I looked up information about Email Address Policies in 2010, they seemed to reference the portion BEFORE the "@" and not after which I am looking for in my case. Second, my goal is to use the @portal.domain.com addresses as the email address format for incoming email to SharePoint 2010 server that sits on a seperate box. Does this make sense? Thanks!

Hi Edward, ok you will add a domain only for the SharePoint Server, so that your Server knows the internal domain. new-AcceptedDomain -Name 'Portal' -DomainName 'portal.domain.com' -DomainType 'InternalRelay' After that your emails to xyz@portal.domain.com will be accepted and now you have to create a route to the destination Server (SharePoint Server). new-SendConnector -Name 'Portal' -Usage 'Internet' -AddressSpaces 'SMTP:*.portal.domain.com;1' -IsScopedConnector $false -DNSRoutingEnabled $false -SmartHosts 'sharepoint.domain.local' -SmartHostAuthMechanism 'None' -UseExternalDNSServersEnabled $false -SourceTransportServers 'Exchange Server' The Smarthost should be the Sharepoint Server with enabled incomming email function and the SourceTransport Server should be the Exchange Server. If you will send emails from outside your network you must add an DNS MX record for this domain. Hope this helps... Arne Arne Tiedemann | Active Directory and Exchange specialist

Thanks for the reply Sukh828. I hope you don't mind a few follow-ups... FYI, I am using Exchange 2010... First, when I looked up information about Email Address Policies in 2010, they seemed to reference the portion BEFORE the "@" and not after which I am looking for in my case. Second, my goal is to use the @portal.domain.com addresses as the email address format for incoming email to SharePoint 2010 server that sits on a seperate box. Does this make sense? Thanks! In that case you need to do what Arne has says. As you're only going to use it for SharePoint internally. You will find you will see the second portion of an SMTP address @portal.domain.com when configuring the accepted domain.Sukh

Thank you both for the replies. One point of clarification... these portal.domain.com addresses ill be assigned to SharePoint groups. All members of those groups will have Acive Directry accounts. However, some of these users will have email addresses that are NOT internal to our system. Does this matter?

No, but if you have groups which use @portal.domain.com and are not in your AD then you will have to configure a shared namespace. In your situation email is sent to a SP group>contains AD account>email sent to users in that group.Sukh

So, basically, when I email enable a SharePoint Group, it automatically creates an AD Contact and an Exchange Mail Contact for this group. Anything more needed? Thanks and sorry for all the amateur questions!!

That's about it, I'd go over this simple guide here which explains what you have asked in this post - http://www.petri.co.il/configure-email-sharepoint-2010-part-1.htmSukh

Hi Edward, ok you will add a domain only for the SharePoint Server, so that your Server knows the internal domain. new-AcceptedDomain -Name 'Portal' -DomainName 'portal.domain.com' -DomainType 'InternalRelay' After that your emails to xyz@portal.domain.com will be accepted and now you have to create a route to the destination Server (SharePoint Server). new-SendConnector -Name 'Portal' -Usage 'Internet' -AddressSpaces 'SMTP:*.portal.domain.com;1' -IsScopedConnector $false -DNSRoutingEnabled $false -SmartHosts 'sharepoint.domain.local' -SmartHostAuthMechanism 'None' -UseExternalDNSServersEnabled $false -SourceTransportServers 'Exchange Server' The Smarthost should be the Sharepoint Server with enabled incomming email function and the SourceTransport Server should be the Exchange Server. If you will send emails from outside your network you must add an DNS MX record for this domain. Hope this helps... Arne Arne Tiedemann | Active Directory and Exchange specialist Arne, you are awesome. I think we are about 90% of the way there now. Finally got this taken care of. Worked like a charm! Just two more issues to resolve, and I'm sure I'm missing something obvious... Issue #1: Whan I email-enable a list, it creates an Exchange Mail Contact and assigns it an email address. Problem is, the Exchange Mail Contact is still getting the address @servername.local (which is what was used when email was originally configured) rather than the new @portal.domain.com. Issue #2: I created a new SharePoint Group and chose the option to create an e-mail distribution group. Again, an Exchange Contact was successfully created and I manually changed the Mail Contact address to reflect the @portal.domain.com address. Problem is, when I send an email to this address, the users who are part of this group do not receieve the message. Email enabled lists and libraries are working fine using the new email format. So, I'm not sure what could be going on there. Thoughts? Thanks!