Exchange 2013 - Location for SMTP Receive Connector verbose logs

So I'm trying to troubleshoot a relay failure:
+ 1415809433 51000008 Wed Nov 12 11:23:53 2014
F:[email protected]
T:[email protected]
A:c:\v1\temp\200046.pdf
S:Sales Order Number  200046
! Error in SMTP conversation:
  550 5.7.1 Unable to relay
  dbmailsend error 8 (Error in SMTP conversation).
! Command-line dump follows (delimited by colons):
  [0]:c:\v1\dbmail\bin\dbmailsend:
  [1]:-vv:
  [2]:-a:
  [3]:c:\v1\temp\200046.pdf:
  [4]:-s:
  [5]:Sales Order Number  200046:
  [6]:-t:
  [7]:[email protected]
  [8]:-r:
  [9]:[email protected]
  [10]:-h:
  [11]:C:\Users\sagert\AppData\Local\Temp\dbf72A3.tmp:
! Error in SMTP conversation:
  451 4.7.0 Temporary server error. Please try again later. PRX5
  dbmailsend error 8 (Error in SMTP conversation).
! Unable to send report to administrator.
Note the SMTP Converstion error, I've done the steps in this forum article:
https://social.technet.microsoft.com/Forums/fr-FR/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5?forum=exchangesvrgeneral
but the issue still exists... so I need to review my Exchange logs for this relay (I've enabled verbose logging on the specific receive connector this should be using)

Fromhttp://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
Set-ReceiveConnector
The location of the Receive connector protocol logs for all Receive connectors configured in the Transport service on a Mailbox server or an Edge server is specified by using the Set-TransportService cmdlet with the ReceiveProtocolLogPath parameter.
Run a get-transportservice|fl *logpath* and that should get you what you need.

Similar Messages

  • Installing Exchange 2013 CU7 fails - multiple Receive connectors

    Coming from CU4 (aka SP1) and running this upgrade (to comply with hybrid requirements!), setup errors out on the transport role, that I have 2 receive connectors bound to the same IP address, and stops there.
    The problem is that Exchange won't come back up for me to fix or delete the additional Recv connector.
    Now what?
    [12/17/2014 00:28:07.0489] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
    [12/17/2014 00:28:07.0489] [2] User specified parameters: -Identity:'MAIL\Default Frontend MAIL' -MaxLocalHopCount:'5'
    [12/17/2014 00:28:07.0490] [2] Beginning processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0494] [2] Searching objects "MAIL\Default Frontend MAIL" of type "ReceiveConnector" under the root "$null".
    [12/17/2014 00:28:07.0503] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0504] [2] Searching objects "MAIL" of type "Server" under the root "$null".
    [12/17/2014 00:28:07.0544] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0572] [2] Processing object "MAIL\Default Frontend MAIL".
    [12/17/2014 00:28:07.0588] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0607] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0611] [2] Ending processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0614] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
    [12/17/2014 00:28:07.0615] [2] User specified parameters: -Identity:'MAIL\Outbound Proxy Frontend MAIL' -MaxLocalHopCount:'5'
    [12/17/2014 00:28:07.0615] [2] Beginning processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0619] [2] Searching objects "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" under the root "$null".
    [12/17/2014 00:28:07.0630] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0631] [2] Searching objects "MAIL" of type "Server" under the root "$null".
    [12/17/2014 00:28:07.0669] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0696] [2] Processing object "MAIL\Outbound Proxy Frontend MAIL".
    [12/17/2014 00:28:07.0711] [2] No properties changed for the object "MAIL\Outbound Proxy Frontend MAIL".
    [12/17/2014 00:28:07.0711] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Outbound Proxy Frontend MAIL' have been modified.
    [12/17/2014 00:28:07.0712] [2] Saving object "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
    [12/17/2014 00:28:07.0712] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0714] [2] Ending processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0717] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
    [12/17/2014 00:28:07.0718] [2] User specified parameters: -Identity:'MAIL\Client Frontend MAIL' -MaxLocalHopCount:'5'
    [12/17/2014 00:28:07.0718] [2] Beginning processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0723] [2] Searching objects "MAIL\Client Frontend MAIL" of type "ReceiveConnector" under the root "$null".
    [12/17/2014 00:28:07.0732] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0733] [2] Searching objects "MAIL" of type "Server" under the root "$null".
    [12/17/2014 00:28:07.0778] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0806] [2] Processing object "MAIL\Client Frontend MAIL".
    [12/17/2014 00:28:07.0820] [2] No properties changed for the object "MAIL\Client Frontend MAIL".
    [12/17/2014 00:28:07.0821] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Client Frontend MAIL' have been modified.
    [12/17/2014 00:28:07.0821] [2] Saving object "MAIL\Client Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
    [12/17/2014 00:28:07.0822] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0824] [2] Ending processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0827] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
    [12/17/2014 00:28:07.0828] [2] User specified parameters: -Identity:'MAIL\Scanner email' -MaxLocalHopCount:'5'
    [12/17/2014 00:28:07.0828] [2] Beginning processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0832] [2] Searching objects "MAIL\Scanner email" of type "ReceiveConnector" under the root "$null".
    [12/17/2014 00:28:07.0840] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0841] [2] Searching objects "MAIL" of type "Server" under the root "$null".
    [12/17/2014 00:28:07.0884] [2] Previous operation run on domain controller 'DC1.contoso.local'.
    [12/17/2014 00:28:07.0912] [2] Processing object "MAIL\Scanner email".
    [12/17/2014 00:28:07.0925] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0927] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0931] [2] Ending processing Set-ReceiveConnector
    [12/17/2014 00:28:07.0933] [1] The following 2 error(s) occurred during task execution:
    [12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [12/17/2014 00:28:07.0965] [1] [ERROR] The following error was generated when "$error.Clear();
    $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
    foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
    " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [12/17/2014 00:28:07.0965] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [12/17/2014 00:28:07.0966] [1] [ERROR] The following error was generated when "$error.Clear();
    $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
    foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
    " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [12/17/2014 00:28:07.0966] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
    [12/17/2014 00:28:07.0967] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___79d82f60693f413588aa8c3a58e90b41 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [12/17/2014 00:28:07.0980] [1] Setup is stopping now because of one or more critical errors.
    [12/17/2014 00:28:07.0980] [1] Finished executing component tasks.
    [12/17/2014 00:28:08.0061] [1] Ending processing Install-BridgeheadRole
    [12/17/2014 00:28:40.0012] [0] CurrentResult setupbase.maincore:396: 0
    [12/17/2014 00:28:40.0013] [0] End of Setup
    [12/17/2014 00:28:40.0013] [0] **********************************************

    Someone already found a fix for this here:
    https://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/#comment-1219
    Just in case this link won't work some day, here was the fix:
    Open ADSI edit on your Domain Controller
    Go to Configuration, and drill down Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Groups, Servers, <Your Server Name>, Protocols, SMTP Receive Connectors
    Find the offending connector and delete it.
    Setup will resume as normal, and recreate the connector after setup completes.

  • Exchange 2013 cant send or receive email

    new server with clean install
    static IP
    firewall is configured for smtp on port 25
    single exchange 2013 server
    checked DNS settings in servers tab
    checked mail connectors per MS KB's
    deleted all connectors and rebuilt only 1 send and 1 receive connector
    still not sending or receiving email they stay stuck in drafts and email never gets delivered coming in
    David Sheetz MCP

    Can users send email to each other, in house? Is the Exchange Server part of a domain, if so, what OS is the Domain Controller? Check list to run through:
    1. Port 25 is forwarded to Exchange Server IP address
    2. Send Connector is using MX Records and using * for the domains
    3. Receive Connector has the appropriate domain listed for the Accepted Domains, ie. Contoso.com not just .local
    4. mailbox username convention has been specified and you clicked the "Apply" link to the right after creating the mailbox username policy
    5. After the above, go into Services and restart the Exchange Mailbox Store

  • Exchange 2013 Relay issue (SMTP Authenticated)

    Hi,
    I installed Exch 2013 and is working great - both incoming mail and outgoing mail work fine in OWA and outlook.
    Problem we are having is SMTP authenticated relay. We install application on all client computers which sends emails externally/internally. 
    Though we had authenticated in application, we are not able to send emails externally. Internally it works fine from application.
    Our backup software stopped sending notifications on failures. Literally we are logging into each and every server and making sure backups are successful.
    We never had a problem with Exchange 2010
    I don't want to create relay and allow my whole ipaddress range (I think that's stupid)
    Can anyone please help?

    Hi,
    You could create a Receive connector on the 2013 Mailbox server, and then configure the Receive connector with the following properties:
    Create/configure a service account for the applications/copier to use.
    Create a new Receive connector with the Usage value 'Custom', and don't assign any permission groups to the connector.
    Specify the IP address(es) of the application servers/copiers as the only remote IP addresses that are allowed to use this Receive connector.
    Use the Add-AdPermission cmdlet to add the ms-Exch-SMTP-Submit permission to the Receive connector for the service account.
    The combination of restricting the IP addresses that the Receive connector listens to, and restricting permissions on the connector so that only the service account can send messages should do the trick.
    For more information, see these topics:
    Add-ADPermission
    Receive Connectors
    Receive Connector Permissions
    Link
    Deepak Kotian.
    MCP, MCTS, MCITP Server / Exchange 2010 Ent. Administrator
    Disclaimer:
    Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
    All the opinions expressed here is mine. This posting is provided "AS IS" with no
    warranties or guarantees and confers no rights.

  • Exchange 2013 DNS for internal and external domain

    Hi All,
    I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
    We have an Active Directory domain myinternaldomain.net, and we have a public domain
    mypublicdomain.com and we have setup email policy to have
    mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
    mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
    hardware LB is out of scope due to budget constrains.
    We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
    that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
    Thanks

    Hi Sccmnb,
    You can easily achieve this using split DNS.
    Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
    Reverse proxy server IP.
    Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
    The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
    SN= mail.mypublicdomain.com
    SAN= autodiscover.mypublicdomain.com
    You don't need to have the active directory domain name present in the certificate.
    Additional  to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
    Some additional Info:
    *Internal vs. External Namespaces
    Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
    based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
    This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
    Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
    *Managing Certificates in Exchange Server 2013 (Part 2)
    *Nice step by step article
    Designing a simple namespace for Exchange 2013
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • SMTP Receive Connector Send Limits

    Hello -
    We are using SQL Server to craft messages and send them to Exchange 2010 to send email out. We usually send out about 1k emails to inside and outside email addresses. Since we migrated to Exchange 2010 we have seen these message start to queue up and not
    go out as fast as they did before in Exchange 2k3.
    We also get this error on the SQL side:
    The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 89 (2013-12-26T09:11:12). Exception Message: Cannot send mails
    to mail server. (The operation has timed out.).
    Is there some place that I need to go to configure the receive connector to allow more emails to go at once?
    Thanks,
    Tark

    I believe there is but, the only other time I have seen a similar issue is as described in this article.
    http://blogs.msdn.com/b/akashb/archive/2009/09/10/increasing-the-number-of-mails-that-can-be-processed-asynchronously-by-a-smtp-agent-simultaneously.aspx
    It's called the MaxInboundConnectionPerSource, and you can check you current setting by running the following Exchange Shell command:
    Get-ReceiveConnector
    Get-ReceiveConnectorGet-ReceiveConnector 'RECIEVE CONNECTOR NAME' | fl
    again that's the only other place  (that I know of) that limits SMTP connections, but your issue is likely to be related to your SQL server.
    Ricardo Fuentes A+ MCP MCDST MCTS MCITP

  • Exchange 2013 Create an smtp relay to allow sending emails to other domains from web application

    Hello,
    We have an exchange 2013 and we want to allow a web application that is outside the organisation to send emails through our sever to external domain.
    Do we have to create an smtp receive or sending connector? How this on has to be configured ?
    Thank you in advance.
    m

    Hello Mehdi,
    be sure that you enable exchange servers permission and externally secured authentication after you create the receive connector.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. My blog:http://msibrahim.wordpress.com/

  • Exchange 2013 SP1 users not receiving quota warning email message

    Hi,
    We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013.  We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
    If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email.  Most of the users do not log into OWA but only uses Outlook.
    It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
    How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
    Thanks,
    Raman

    Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
    Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
    326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
    ========================
    Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
    driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
    submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
    at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
    Raman

  • Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

    Objective:
    We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
    to download and upload mail from the old tennant to the new tennant.
    Background: 
    We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
    the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan.  As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
    vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
    After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
    migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
    Environment:
    1 MS AD domain:
    - Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
    - UPN has been changed to [email protected] to allow for ADFS
    - ADFS has been deployed and SSO works for all users with UPN [email protected]
    - An "On-Prem exchange server" does not yet exist
    1 O365 Account where main tennant FQDN is @corp.com
    - There are 5 registered domains
    -contoso.ca
    -corp.com
    - contoso.legacy.ca
    -deprecated/will be deleted
    -deprecated/will be deleted
    - There are 40 E3 licenses, all using a @corp.com UPN
    - There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
    - No accounts currently use contoso.ca for email
    - O365 was upgraded to 'the latest version' sometime in summer 2013.
    Migration Plan (High Level):
    Setup a local windows server (trial license)  
      Deploy an exchange 2013 server (trial license) on the aforementioned windows server  http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
      Prepare and deploy Dirsync Deployment
    of Dirsync
      Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
    More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
    http://help.outlook.com/en-us/140/ff633682.aspx
      Evaluate total time it took to sync data. 
    Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
      Open a new office365 account under the M plan.
      Plan a 1 hour mail & contoso.ca domain login outage
      temporarily change all user UPN's to match the new tennant
      perform a dirsync to the new tennant
      disable dirsync after all accounts have been auto-created/provisioned
      re-establish UPN + mail access.
      Plan a date and time for the cut over.
      remove the exchange hybrid server from the old tennant. 
      Point MX records directly to the exchange server.
      Cut office 365 service.
      After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
    the new tennant
      fix all user UPN's in the cloud to match their real UPN's.
    This can be done with powershell.
      attach exchange hybrid server to new tennant
      Point MX records to the new tennant 
      Migrate all data from the local exchange server to the cloud under the new plan.
    Current progress (Lab):
    I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
    1x Domain Controller (DC) running windows server 2012 (named DC02)
    1x DC running windows server 2008 R2 (named DC01)
    1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
    Where I am stuck / Problem:
    I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected]
    After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
    the problem. 
    In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
    1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
    2) If I must add them to exchange, I am provided with three choices: 
    - Authoritative Domain
    - Internal Relay Domain
    - External Relay Domain
    Given that the domain is currently in office365 and is authoritative there, which of these applies?
    3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
    process? Would love it if it took into consideration multiple UPN/email addresses.

    Hi,
    Here are my answers you can refer to:
    1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
    http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
    2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
    To determine it, you can firstly check the function of the three types in the following article:
    http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
    3. Here are some reference about the migration from on-premise Exchange server to Office 365:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
    Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
    http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    If you have any question, please feel free to let me know.
    thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2007 Client Access and Receive Connector options not available (EMC)

    We have a SBS2008 server with Exchange 2007
    When I open the EMC and go to Server Configuration --> Client Access, none off the options are available (greyed out). OAW, OWA, ActiveSync are working without any problems. Outlook anywhere enabled shows False,when I try to reanable it I get the following
    error message:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:01
    SERVERNAME
    Failed
    Error:
    The Active Directory object for virtual directory 'IIS://SERVERNAME.domainname.local/W3SVC/3/ROOT/Rpc' on 'SERVERNAME' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create
    it.
    Unexpected Error
    Warning:
    Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately fifteen minutes. To verify that Outlook Anywhere has been enabled, check the application event log on server SERVERNAME.
    Exchange Management Shell command attempted:
    enable-OutlookAnywhere -Server 'SERVERNAME' -ExternalHostname 'mail.domainname.net' -DefaultAuthenticationMethod 'Basic' -SSLOffloading $false
    Elapsed Time: 00:00:01
    Also the receive connectors are not visible from EMC, it's just blank under receive connectors, but mails are received without any problems.
    Does someone know a way to resolve this?

    That worked!
    I created a new account and placed it into the Exchange Organization Administrators role, now I'm able to see all the options normally.
    I also re-added the original account to the EOA role but I still don't see the options there. When I go to Organization Configuration I also get the following error message:
    You do not have permissions to read the security descriptors on CN=servername,CN=Server......DC=domainname, DC=local. It was running command 'get-ExchangeAdministrator'
    So it must be a permissions issue. The strange thing is that under Exchange Administrators I can see my account and it has the role Exchange Organization Administrators.

  • Exchange 2013 Certificates for Hybrid Deployment Clarification

     I have an Exchange 2013 servers (CAS and Mailbox on separate server) which I wanted to setup for Hybrid deployment. I already have a certificate acquired from 3rd party with 3 names (mail, autodiscover and owa). the certificate was installed in the
    CAS server. As per the hybrid deployment documentation I need also to install a certificate in the mailbox server, questions:
    1. Can I use the same certificate for installation in the mailbox server?
    2. Can I also use the same certificate in the Hybrid Configuration wizard for the "certificate to use with securing the hybrid mail transport"?
    3. Do I need to include the primary smtp domain (xxxxx.com) in the certificate since current configuration points to the mail.xxx.com as the certificate common name?

    Hi,
    Here are my answers you can refer to:
    1. It depends.
    The certificate used for hybrid secure mail transport must be installed on all on-premises Exchange 2013 Mailbox and Client Access servers.
    If you're configuring a hybrid deployment in an organization that has Exchange servers deployed in multiple Active Directory forests, you must use a separate third-party CA certificate for each Active Directory forest.
    2. Yes. But we recommend that you use a dedicated third-party certificate for any optional AD FS server, another certificate for the Exchange services for your hybrid deployment, and if needed, another certificate on your Exchange servers for other needed
    services or features.
    3. Yes. Here are the minimum suggested FQDNs that should be included on certificates: domain.com, autodiscover.domain.com, edge.domain.com
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/hh563848(v=exchg.150).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Connect to Exchange 2013 using IMAP/SMTP from the Internet

    Hello,
    I would like to enable connectivity to my exchange server using imap and smtp. my exchange server is using the default configuration for imap and smtp which are port 143 and 25 respectively. I have two exchange servers both with CAS and MB roles
    installed. I also have an edge server on my DMZ. I have also published my OWA using IIS ARR module. I wonder where I should direct my traffic from my firewall to enable IMAP connectivity taking into considerations my two servers with CAS and MB roles are inside
    my network. I also wonder how I can enable redundancy for IMAP connections. Thanks a lot.
    Regards,
    Pooriya
    Pooriya Aghaalitari

    Hi Pooriya,
    When you install Microsoft Exchange Server 2013, IMAP4 client connectivity isn't enabled. We can do the following steps to configure it:
    1. Start two IMAP services: the Microsoft Exchange IMAP4 service and the Microsoft Exchange IMAP4 Backend service.
    Set-service msExchangeIMAP4 -startuptype automatic
    Start-service msExchangeIMAP4
    Set-service msExchangeIMAP4BE -startuptype automatic
    Start-service msExchangeIMAP4BE
    2. Make sure there is an valid certificate which is assigned with IMAP service. Also confirm the Published Exchange server name (For example: mail.domain.com) has been included in this certificate:
    Get-ExchangeCertificate | FL
    3. Configure the external IMAP connection settings:
    Set-ImapSettings -ExternalConnectionSetting {mail.domain.com:993:SSL}
    4. Configure SMTP settings:
    Get-ReceiveConnector "*\client Frontend*" | Set-ReceiveConnector -AdvertiseClientSettings $true -Fqdn mail.domain.com
    5. You must restart IIS service (running IISReset /noforce from the Command Prompt window) after applying all settings.
    For more information about IMAP in Exchange 2013, please refer to:
    http://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Support for OIM11g

    Guru's,
                    I want to know the OIM11g Support for Exchange 2013 Connector, is any one configured the exchange 2013 with OIM?
    Thanks,
    Caddick.

    Oracle Identity Manager
    You can use one of the following releases of Oracle Identity Manager:
    Oracle Identity Manager 11g Release 1 (11.1.1.5.6) or later
    Oracle Identity Manager 11g Release 2 (11.1.2.0.6) or later
    Target systems
    The target system can be any one or a combination of the following:
    Microsoft Exchange 2007 SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2010 RTM, SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2013 RTM (64-bit) For the Exchange 2013 support, Patch 17239236 must be applied on Release 11.1.1.6.0 of the Exchange connector. This Patch can be obtained from My Oracle Support under Patches and Updates.
    Download Exchange-11.1.1.6.0 connector and then Apply patch 17239236 for Exchange 2013

  • Outlook 2013 - Exchange 2013 - Prompts for username and password when EWS basic authentication is enabled

    So we have an Exchange 2013 environment, and a CRM solution that requires basic authentication to EWS internally.  Problem is, after a reboot of our Exchange server, all of our Outlook clients begin prompting for username and password (which nothing
    works) which also starts locking users AD accounts out due to failed login attempts (somehow).  If I disabled basic authentication on EWS, Outlook authenticates as normal using NTLM and there are no issues.  Once Outlook has authenticated, I can
    turn back on basic authentication, and Outlook will be fine until the next time the Exchange server is rebooted.
    Any ideas?

    Hi,
    According to your description, I understand that Outlook client prompted for username and password when Exchange server restart and basic authentication is enabled for EWS.
    If I misunderstand your concern, please do not hesitate to let me know.
    It’s normal. This caused by the difference between basic authentication and NTML authentication:
    Basic, with any version of Outlook prior to 2010, results in a pop up dialog asking for creds. Outlook 2010 makes the 'save this password' actually work, so in an Outlook 2010 or later world, Basic can mean no need to authenticate every time you open/reconnect,
    but in all earlier versions, you will have to enter creds every time.
    NTLM, when used by a client that is domain joined and logged in with cached creds, results in the client simply sending the cached in creds to the server, resulting in what looks like a pretty seamless single sign on experience. However, if you want to do pre-authentication
    at something like TMG, and not let the traffic go all the way to CAS, you need to configure TMG for this.
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    TechNet Community Support

  • Outlook Clients for Exchange 2013 Prompt for Password

    I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem: 
    - Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows: 
    RunspaceId                         : b43cd829-a81f-4b00-bb4d-73389c9df50d
    ServerName                         : EXCH-HTCA13
    SSLOffloading                      : False
    ExternalHostname                   : webmail.first.pt
    InternalHostname                   : exch-htca13.first.pt
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    Can anyone help me identify the problem?

    Hi,
    Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
    In addition, I recommend you refer to the following article:
    Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
    Thanks.
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality,
    safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Niko Cheng
    TechNet Community Support

Maybe you are looking for

  • ITunes 8.0.2.20 Won't Install

    I had iTunes running without problems. Was notified there was an update (8.0.2.20). Took it, it installed, after that, was never able to run iTunes again. I got an error message (can't remember message number now) that a component was missing. Tried

  • Formatting font in email signature

    Is it possible to format the font in my email signature?  At the moment it seems to be locked into a specific font and size and I can't make it smaller (like it is in my Outlook) or see any way to do it in the handset itself.  I inserted it via the d

  • Can I use the ac charger I bought for my mini with my new nano

    Having just bought a Nano, I want to know if I can use the ac charger I bought for the mini to charge it. I don't have enough access to a pc to charge it via the USB cable.

  • ICloud photos sync with today's date instead of date taken

    I just got a new laptop for work and installed iCloud to sync my PhotoStream to it. The photos all synced, but they are displaying a modified date of today instead of the date the photo was originally taken. On my old laptop, the photos seemed to dis

  • CS5 crashes when used in background

    is there a way to prevent ae cs5 from crashing with accidental/intentional background use? after effects *should automatically come to the foreground if I start clicking around on it while it is in the background, but instead it just crashes. at the