Receive Connector

Hi,
I am running Exchange Server 2013 and after a reboot all works fine for an undetermined amount of time, then for some reason the receive connector stops working, well I presume it is the receive connector. Using the Microsoft Remote Connectivity Analyzer
I get the following error (See Below). As far as I can tell only a reboot of the Server will resolve this error as I have tried stopping all the Exchange Server's services & restarting them and did not fix the problem. As you could imagine rebooting
the server during the day is almost impossible but also not being able to receive emails is very painful. Any advice would be helpful as at this point I am fresh out of ideas except a re-install and hope it doesn't do it again (not really an option). I have
also deleted the receive connector & re-created it.
Delivery of the test email message failed.
Additional Details
The server returned status code -1 - The operation has timed out.
Exception details:
Message: The operation has timed out.
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
Elapsed Time: 100001 ms.

Hello,
Regrettable the original fault is still there. somewhere between 2 1/2 hours to 3 hours after the server has rebooted it fails the connectivity test & we stop receiving emails same error as above. The only to resolve this issue is to reboot the server
again (almost impossible during working hours). I receive the same error as before, listed above. I have tried deleting the receive connector & re-creating it, have also tried as a frontend connector and a hub connector same thing happens on both.
Curly

Similar Messages

Receive Connectors not working correctly - using random connectors.

I'm having a problem that I thought was DNS related, but I've since flushed the DNS.
What happens is when I try to relay off a Hub server, it always tries to use any random Receive connector, even though my client is explicitly in the Relay connector list.
When I telnet to the HT by hostname on 25, it opens a random receive connector. If I continue to /flush and telnet over and over, it cycles through all the connectors (default, Relay explicit and the others that block the connection).
When I telnet directly to the IP of the Relay connector, it works perfectly.
What would cause the server or client to not use the correct explicit connector all the time?

When you test this - I'm assuming you are coming in from a specific remote IP. What RC should this be hitting?
To troubleshoot this I like to change the banner on all of them so it says "Helo - Connector 1" "Helo - Connector" or something else meaningful like this.
Also enable verbose SMTP send receive logging on all receive connectors. What's in there?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Receive Connector Temporary Server Error. Please Try again later. PRX4

Hi ,
I installated Exchange server 2013 on Windows 2012 R2 Servers..
Topology ;
1 Active Directory Server : Windows 2012 r2 all updates installed.
1 Exchange 2013 Server : Windows 2012 r2 all updates installed.
I configured send Connector settings and I checked Receive connectors Default Frontend Exchange settings. Anonymous users is ok and don't have any problem.
When I send mail Exchange -> Internet mail goes. this is ok.
But when I send mail Internet -> Exchange I am getting this error ;
Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""501 5.5.4 Required arguments not present."" Attempted failover to alternate host, but that did not succeed. Either there
are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx:2525
telnet results are below ;
220 exchange.bulut.email Microsoft ESMTP MAIL Service ready at Tue, 30 Dec 2014
14:12:19 +0200
EHLO bulut.email 250-exchange.bulut.email Hello [xxxxxxxxxxxxxxxxx]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
MAIL FROM:[email protected] 250 2.1.0 Sender OK
RCPT TO:[email protected] NOTIFY=success,failure 250 2.1.5 Recipient OK
DATA354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test from Contosoa
This is a test message
451 4.7.0 Temporary server error. Please try again later. PRX4
QUIT 221 2.0.0 Service closing transmission channel
Thanks. Regards.

Hi,
If the CAS and MBX servers are collocated on the same server the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. This is because two services (FET and Transport Service) can’t listen on the same port.
Refer from this article:
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Please try to create an endpoint for 2525 on default receive connector to test mail flow by the following steps:
EAC -> mail flow -> receive connectors -> Default EXCHANGE
Click Edit then click scoping tab.
Under Network adapter bindings, click
add button to create port 2525 for all available Ipv4/Ipv6 addresses.
Best Regards.

Exchange 2010 Receive Connector intermittently getting an SMTP RSET from sending SMTP servers causing missing user email

Users are receiving about 95% of their messages from sending SMTP servers. Intermittently, sending SMTP servers send the Exchange 2010 Server a SMTP RSET command for no apparent reason. The RSET Command (by SMTP specification) causes the Exchange 2010 Server
to drop the message. The sending SMTP servers then do not resend the message after asking the Exchange server to drop the message. This means the message is marked as Sent by the sending servers but the dropped messages never show up in the users' Outlook
inbox.
Exchange 2010 Version 14.3 (Build 123.4)
Roles: Hub Transport, Client Access, Mailbox
What is going on?
Exchange Receive Connector log showing a RSET example:
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,1,10.80.120.15:25,65.99.255.73:53479,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,2,10.80.120.15:25,65.99.255.73:53479,>,"220 vpn.a1expediting.com Microsoft ESMTP MAIL Service ready at Thu, 17 Jul 2014 08:47:06 -0400",
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,3,10.80.120.15:25,65.99.255.73:53479,<,EHLO inbound37.exchangedefender.com,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,4,10.80.120.15:25,65.99.255.73:53479,>,250-vpn.a1expediting.com Hello [65.99.255.73],
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,5,10.80.120.15:25,65.99.255.73:53479,>,250-SIZE 52428800,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,6,10.80.120.15:25,65.99.255.73:53479,>,250-PIPELINING,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,7,10.80.120.15:25,65.99.255.73:53479,>,250-DSN,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,8,10.80.120.15:25,65.99.255.73:53479,>,250-ENHANCEDSTATUSCODES,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,9,10.80.120.15:25,65.99.255.73:53479,>,250-AUTH,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,10,10.80.120.15:25,65.99.255.73:53479,>,250-8BITMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,11,10.80.120.15:25,65.99.255.73:53479,>,250-BINARYMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,12,10.80.120.15:25,65.99.255.73:53479,>,250 CHUNKING,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,13,10.80.120.15:25,65.99.255.73:53479,<,MAIL FROM:<[email protected]> SIZE=165270,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,14,10.80.120.15:25,65.99.255.73:53479,*,08D16FD38F3D3355;2014-07-17T12:47:07.370Z;1,receiving message
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,15,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.0 Sender OK,
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,16,10.80.120.15:25,65.99.255.73:53479,<,RCPT TO:<[email protected]> ORCPT=rfc822;[email protected],
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,17,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.5 Recipient OK,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,18,10.80.120.15:25,65.99.255.73:53479,<,RSET,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,19,10.80.120.15:25,65.99.255.73:53479,>,250 2.0.0 Resetting,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,20,10.80.120.15:25,65.99.255.73:53479,<,QUIT ,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,21,10.80.120.15:25,65.99.255.73:53479,>,221 2.0.0 Service closing transmission channel,
Daniel

Hi,
According to the receive connector log, your emails were failed to be deliverd with DNR. If I misudnerstand the meaning, please feel free to let me know. If yes, I'd like to confirm the detail information in the DNR to narrow down the
cause.
Additionally, based on my research, the RSET command performs an SMTP reset, and then aborts the message that is currently being sent. Thus, the log didn't provide more information for troubleshooting. Is there any other error in your event log? please check
the event log when the issue happens again.
Thanks,
Angela Shi
TechNet Community Support

Migrate from 2003 to 2010 - Receive Connector Authentication

I'm in the process of upgrading a remote office from Exchange 2003 to Exchange 2010. Today, we changed the IP's on their firewall so that 2010 Hub Transport is handling mail. Normally, I always create a new Receive Connector for receiving mail
from the internet. I leave it as Anonymous users only and receive on internal IP of the server.
When I send an e-mail from the internet to a 2010 user, the mail is delivered fine, I'm assuming through the new "Anonymous" access connector I created. However, when I send e-mail from the internet to a 2003 user, I get the following NDR
with this error:
Reason: 530 5.7.1 Client was not authenticated
I was able to fix the problem by adding Anonymous authentication to the Default receive connector. I'm wondering why this connector is being chosen over the Internet connector though, and why only for 2003 users? Is it bad to leave the Default
Connector allowing anonymous access? I've always left that connector alone and created a new Internet connector which has seemed to work in the past.

Hi,
According to your description, exchange 2010 like a relay server, and relay the email to exchange 2003 when you send a email from the internet to a 2003 user.
As Ed mentioned, when you add the correct IP address where the traffic comes from on the receive connector, then it would ensure that the correct receive connector would be used.
The following article for your reference:
Resolve 530 5.7.1 Client was not authenticated
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange Server 2010 - Receive Connector for Client Computers

I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
How should/could this be better configured so an application can send if they authenticate?

Hi
For this you need to create a seperate receive connector to be used for Relay in your organizations.
Follow the below steps
1) Create a dedicated Relay Receive Connector
2) Add only the Ip addresses of the applications which needs to relay on Exchange servers
3) You can use either anonymous or authenticated relay according to your relay config
You can follow the below link as well
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
"Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
"SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
After testing DNS that all seems fine, so I don't believe it's a DNS problem.
Any ideas why this would happen?
Thanks,
Matt

Hi Matt....
To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
Hope this will work
Thanks

Need to stop the pop and Imap receive connectors to be able to start the pop and Imap services in Service Manager

Hello All,
I am hoping that someone else has run across this issue (may have started after CU5 was installed).
Upon every reboot I have found that the "Microsoft Exchange IMAP4" and "Microsoft Exchange POP3" services in the service manager will not start... basic reason in the event viewer is that the ports are already in use.
If I go into the ECP and disable my POP and Imap receive connectors I am able to then start the services.
After the services are started I can then go back to ECP and enable the receive connectors again and everything is fine .
Can anyone shed any light on this?
Thanks in advance ;)
Chris

Hello Winnie,
I bounced the Transport service tonight (adjusting spam filter levels)... so I was able to issue a stop and re-start of the IMAP4 and POP3 services in the service manager.
I stopped both the IMAP4 and POP3 services in service manager.
I issued the start of the services with PowerShell as requested:
PS C:\Users\administrator.XXXXXXXX> Start-service MSExchangePOP3
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
Start-service : Failed to start service 'Microsoft Exchange POP3 (MSExchangePOP3)'.
At line:1 char:1
+ Start-service MSExchangePOP3
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand
Then I first stopped the receive connector in ECP and issued the command:
PS C:\Users\administrator.XXXXXXXX> Start-service MSExchangePOP3
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3
With the receive connector disabled in ECP it was successfully started.... then I enabled the receive connector in ECP and all is fine now
repeated the same with IMAP4
to recap....
If I stop the IMAP4 and/or POP3 service in service manager, I must first disable the IMAP and/or POP receive connector in the ECP, then start the service in service manage.. and then finally go into ECP and enable the receive connector.
Thanks,
Chris
Chris

CU5 failed due to issues with receive connectors

We have a CAS server (mail1, 10.1.0.26) and Mailbox server (mbx1, 10.1.0.25). When I ran the update on the mailbox server, it failed with the following errors (see below). The update completed successfully on the CAS server. It appears
I have a problem with receive connectors. I really could use some help please. Thank you. -Glen
Here are the results of the Get-ReceiveConnector PS script:
Identity
Bindings                                      Enabled
MBX1\Default MBX1                           {0.0.0.0:25}
True
MBX1\Client Proxy MBX1                      {10.1.255.26:25, 0.0.0.0:465}   True
MAIL1\Default Frontend MAIL1              {0.0.0.0:25}
True
MAIL1\Outbound Proxy Frontend MAIL1 {0.0.0.0:717}                              True
MAIL1\Client Frontend MAIL1                {0.0.0.0:587}
True
Here are snippets of the failure results:
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Client Proxy MBX1". A receive connector must have a unique combination of a local IP address & port bindings
and remote IP address ranges. Change at lease one of these settings.
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Default MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote
IP address ranges. Change at lease one of these settings.

Here's the full output from the failure messages:
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.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Client Proxy MBX1". A Receive
connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, 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)".
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.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Default MBX1". A Receive
connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, 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)".

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.

Receive connector anonymous or authenticate

Hi,
Does anyone know a way to set a receive connector to only request authentication in certain circumstances?
Let me explain the scenario: If you have a receive connector that is set to accept general inbound emails from anyone then it will be set to accept emails from any sender address.
However, if someone is trying to spoof the sender address and they use an email address which is valid within your organisation then it would be really useful if it could request authentication at that point, since emails from internal users should only
come from authenticated devices.
Is there any way to do this?
Thanks in advance.
Neil

Hi,
According to your description, there are spoofing emails in your environment. And as far as I know, the authentication of receive connector cannot only work in certain circumstance.
Ｈowever, I recommend the following methods to prevent emails spoofing.
1. Remove ms-Exch-SMTP-Accept-Any-Sender for anonymous users on the receive connector
2. Remove ms-Exch-SMTP-Accept-Authoritative-Domain-Sender for anonymous users on the receive connector
3. Enable Sender-ID validation on the receive connector, with a corresponding TXT (SPF) record in DNS.
http://technet.microsoft.com/en-us/library/ff714972.aspx
4. Enable the Anti-Spam functionality on the mailbox server:
http://technet.microsoft.com/en-us/library/bb201691(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Receive Connector accepting oversized messages

Hi. Weird thing...
Exchange 2010 SP3 UR5. Organization was 5.5 --> 2003 --> 2010.
Current settings are:
Global Transport max send/receive size = 20MB
Receive connector max size = 10MB
User mailbox Message Size Restrictions = not set
Distribution Lists user is a member of's Message Size Restrictions = not set
User received a number of messages ranging from 16MB to almost 20MB.
How is this even possible - shouldn't the Receive Connector's smaller limit apply here? What am I missing?
Screenshots of RC configured for 10MB and Message tracking showing it pass a 16MB message:

Hi,
From your description, I would like to clarify the following thing for troubleshooting:
The Receive Connectors are configured at the Server Level which means that if you have a group of Hub Transport behind a Load Balancer, all servers must be configured the same way related to limits, otherwise, you will experience weird issues.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Receive connector to allow relay for localhost

I have set up a relay receive connector to allow anonymous relay from another exchange server (send mails with Send-MailMessage cmdlet ) and it works just fine, but trying to send same mail from localhost falls into default receive connector and returns
authentication error. Adding anonymous users to permission groups in default receive connector it works, but it's not what I want. Is there a way to make the relay connector work for localhost too avoiding the overlap between connectors ?

Hi,
Let’s begin with the following article:
http://blogs.visendo.com/post/2009/12/23/Configuring-Exchange-2007-Relay-Settings-for-Exchange-Connector.aspx
“If you are using the localhost alias as the server name, be sure to include the loopback address (127.0.0.1) in the range.”
Thus, we can try to add 127.0.0.1 in the list of "receive mails from remote servers " setting.
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.
Thanks,
Angela Shi
TechNet Community Support

Configuring Receive Connectors for External Notifications while still displaying Site Name

This is closely related to the issue we 'resolved' in
this blog
Our SharePoint notifications would not display the Site Name in the Display Name. i.e. If an Expense Request was approved, we wanted the display name of the email to come from "Accounting"
To resolve, we went to the receive connector and made sure only "Anonymous Users" was checked under Permission groups. The workflows and notifications immediately started displaying the site they originated in the Display Name, but...
All notification emails going to external users (outside our primary domain) ceased. We has to check 'Exchange Servers' under permission groups and then we lost the display name but gained email to external users.
Does anyone know how to get both working at the same time?
Thanks!!
Devster

Hi
Devster,
Check outgoing email settings in SharePoint Central Admin > System Settings
Let us know your results, thanks
Regards,
Pratik Vyas | SharePoint Consultant |
http://sharepointpratik.blogspot.com
Posting is provided AS IS with no warranties, and confers no rights
Please remember to click Mark As Answer if a post solves your problem or
Vote As Helpful if it was useful.

HT Receive Connectors and certificates

What are the default certificates that should be installed on Exchange 2010 HT role (and show up in EMC)? How do I reset the certs and start fresh (or at least check if there are conflicts or invalid certs)? My Exchange Connectivity Analyzer test succeeds
at every step except the last (unexpected response error). I can telnet to port 25 on the server (from LAN) and the firewall is open; netstat -an shows 25, 110, 143, etc. ports listening. What is the best and quickest way to reset the HT role without removing
and reloading Exchange 2010 SP3? Does Exchange 2010 HT SMTP connector require a default self signed certificate?
My existing Exchange 2007 is working fine and I have tried the migration two times now with glitches each time. I cannot do a side-by-side deployment but only a weekend cut-over deployment. Any tool besides Best Practices Analyzer that can identify where
SMTP receive is breaking down? I can send and receive mail from internal users to internal users. I can send mail to external users. I cannot receive mail from external users. Is this an issue with TLS or other authentication settings? MX record updates with
external DNS are slow but I have tried several settings. How do I confirm correct internal DNS settings for Exchange 2010 to receive and route mail? Event logs don't seem to give many clues. Can you tell I'm grasping and flailing a little here with this deployment?
Many Thanks in advance for any expert assist from someone who had these issues and resolved them.
Configuring Postfix was *almost* more fun ... at least I got it working!
--musicalsysadmin

Hi,
According to your description, I understand that you cannot receive email from external users in your Exchange 2007 co-existence with Exchange 2010 environment.
To narrow down the issue, please do the following checks:
1. Please check whether there is any NDR in the external sender’s mailbox.
2. We also need to know if the user is facing issues for all internet domains or just some specific domains.
3. Since your Telnet result for port 25 seems to be proper, please confirm there is no error or warning in the Telnet processing.
4. Check your receive connector in your environment:
Get-ReceiveConnector | FL
If possible, please post the results here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Receive Connector

Similar Messages

Maybe you are looking for