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

Similar Messages

TS3899 When I send an email I get an error message that the receiver does not allow "relaying" it doesn't matter who the recipient si

When I send/forward an email I get an error message that the recipient does not allow "relaying". It doesn't matter who the recipient is.

Go into Settings>Mail, Contacts, Calendars>your account>Outgoing mail Server>SMTP>Primary Server then turn Server ON and fill in both User Name & Password>under Outgoing Mail Server.

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

Internal Open Relay For Entire Network

Hello All,
Sorry if this has been answered, but I haven't seen anything that addresses specifically what I need in the forums.
I have a single Exchange 2010 Server. I've set up a new receive connector called Open Relay and have opened up various I.P. Addresses. What I would like to do is open it up for all of my subnets internally (10.0.0.1/24.) Which is easy enough.
Here's the problem, I only want the Open Relay to work internally, I do not want any of my workstations to be able to relay off the trusted subnets, across those internal subnets YES, but to the outside world, NO. Everything I try gives them rights to relay
both inside and outside, that is a blacklisting just waiting to happen.
This is so that all the scripts that I run remotely on workstations can send me emails with info that I need.
Thanks Eric

Create a receive connector
http://technet.microsoft.com/en-us/library/bb232021.aspx
add the required subnet to allow relay
Get-ReceiveConnector yourconnectorname | get-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights
MAS

Allow relay from application servers

Hi,
Can we allow Relay for cloud application servers. If so, how can it be done. ? Plz let me know.
Thanks

Hi Sree_0507,
If you want to allow anonymous relay, you need to create a new Receive connector on the Hub Transport server and use the Shell to grant the relay permission to anonymous connections.
Depending on your situation, you should only add your application servers IPs instead of the default settings(0.0.0.0 - 255.255.255.255).
Here’s an article for your reference:
Allow Anonymous Relay on a Receive Connector
http://technet.microsoft.com/en-us/library/bb232021(v=exchg.141).aspx
If you have any further questions, please do not hesitate to post back.
Best regards,
Eric

Exchange 2007 Receive Connector

Hi, We are using Exchange Server 2007 and are using Receive Connectors to allow application servers to relay emails both internally and externally. I would like to make sure that the application servers can send email only to the internal users and not outside
users. I would like to know how can I achieve this. Any suggestion would be welcome.
- Fazal Ur Rehman Shah
Fazal Ur Rehman Shah | Senior Consultant

Hi Fazal,
Thank you for your question.
We could refer to the following steps to create transport rule:
Navigate EMC-Organization Configuration-Hub Transport-Transport Rules
Click “New Transport Rule” and type transport rule name which is “Restrict to Internet”
In Conditions, Click “from people” and type
[email protected]
In Conditions, Click “sent to users inside or outside the organization” and choose “Outside”
In Actions, choose “silently drop the message”
Then we could enable this transport rule
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Send and receive connector

Hi Everyone, I have 2 send connectors and 4 receive connectors configured on exchange server 2007.How do i know which send or receive connector i am using for my exchange 2007.I am doing the transition to exchange server 2013. If i create a new send
and receive connector in exchange 2013 without looking back to exchange 2007 will i face any issue.Do guide me how to create it in exchange 2013.

Hi Risingflight,
According to your description, I found that we want to create send and receive connectors for the new Exchange 2013 server with the same settings as the old Exchange 2007 server.
I suggest collecting the settings on EMC from Exchange 2007 server, and doing the same settings on Exchange 2013 server.
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

Receive Connectors for Internal Relays - Before & After 2007-2013 Co-existence

I have just completed the process of migrating from Exchange 2007 Standard SP3 RP10 to Exchange 2013 Standard. I now have Exchange 2013 Standard CU3 installed on two Server 2012 Standard systems. The two new exchange servers are members of a DAG.
With Exchange 2007, I had to include the IP addresses of multi-function devices (MFDs) with scan to e-mail capability in a receive connector in order for the scan to e-mail to work.
Five of the MFDs were on the same subnet as our Exchange 2007 servers, and one MFD was not.
It is on the same subnet as our Exchange 2013 servers.
I created new Receive connectors on our Exchange 2013 servers for this purpose.
The one MFD on the same subnet as the Exchange 2013 servers was mistakenly excluded from a receive connector.
Much to my surprise, it is able to relay mail.
I removed the IP address of one of the other MFDs to see if the fact that it is on a different subnet than the Exchange 2013 servers made a difference.
I replicated our domain controllers to help ensure that a lack of AD replication would not be an issue with this test.
The excluded MFD is still able to relay items.
I have an application on a server. The application relays messages, but the IP address of the server it is on is not included in any receive connectors.
By searching through the SMTPreceive log, I found the IP address of the MFDs I did my scan to e-mail tests from in the log.
I also found the IP address and relayed messages from the application server.
The log indicates that the Default Frontend connector is handling this traffic.
Does Exchange 2013, by default, relay messages from all internal IP addresses?
Does this mean that I don’t need receive connectors for any internal devices (MFDs, servers, etc.).
Our Exchange 2007 servers have been decommissioned. Would I have needed connectors while we were still in a co-existence situation?
Am I likely to need them when we have our next co-existence situation in a few years?

Hi Cara. Thank you for the response.
If I understand you correctly, you are saying that the MFDs are able to relay because the Default Frontend connector allows them to.
That makes sense for the one MFD that was not included in the customised connector I created.
Thank you for helping me sort that out.
By analysing the Front End Transport logs at the following location on my server, I determined that the included MFDs were using the customised connector I had created.
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive
If I removed the IP address for one of those MFDs, it was still able to relay, but it was doing that through the Default Frontend connector.
That makes sense. As explained near the end of the following article, Exchange uses the most specific connector.
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
The one that includes the specific IP address of the MFD will be used, but if the IP address is not specified in any connectors, The Default Frontend connector will automatically be used by
the device.
I believe that I now understand how the have the relaying from MFDs is taking place, but I am not certain how some applications are completing their relaying.
Another department in my organisation has their own network.
I have a customised receive connector that includes the IP addresses of two application servers on their network.
Applications on these servers relay messages through the Exchange server on my network.
The headers on the relayed messages suggest that the messages are being relayed by the Default Frontend connector.
The logs for that connector, however, do not contain any entries for the two IP address.
The message tracking logs suggest that the Default <servername> connector is relaying for these applications.
If the most specific connector is supposed to handle the relaying, why is that not happening in this case?
Also, two other application servers from this network are not included in any customised connectors I have created.
The logs show that they are relaying mail through the Default Frontend connector.
If I understand you correctly, you are saying that this should not be happening, as applications and external users require a customised connector, rather than a built-in connector.
If I have mis-understood you, please clarify this for me.
Thanks!!

I just purchased an ipad and I can receive e-mail but I can't send or reply. I get a message that the e-mail is in the outbox because the server won't allow 'relaying.' What do I need to do?

I just purchased an ipad2 and I can receive e-mails but I can't reply to or forward them. I also can't send a new e-mail. I receive a message that the e-mail has been placed in the outbox because the server won't allow 'relaying.' On my laptop, using the same e-mail server, I am fine. What can I do to make the ipad2 e-mail function properly?

Contact whoever manages your email server and ask them what ports and security to use for SMTP from remote locations. ISPs and email admins often require different SMTP settings when sending email when not connected to the server's or ISP's network.

HT1430 I receive emails but when I try to send emails, I get a box that says that the "recipient was rejected by the server because it does not allow relaying"

I can receive emails over AOL but cannot send them. When I do, I get a box that says "recipient was rejected by the server because it does not allow relaying"

That's because you did not enter your screen name and password for the outgoing (SMTP) mail server on the phone. Or if you did they got erased. Go to Settings for the account and enter them.

Just got an Iphone - Receives email but can't send email to anyone ( POP ). Error Message : "The recepient ... was rejected by the server because it does not allow relaying."

Just got an Iphone - Receives email but can't send email to anyone ( POP ). Error Message : "The recepient ... was rejected by the server because it does not allow relaying." Please help............

Hi johnnytoo!
I know it's aggravating when you need to send an email and it doesn't go through! I have a link that provides step by step information from Apple's website that should resolve this for you.
http://support.apple.com/kb/TS3899
Please post back with your results, and have a good day!
Christina B
VZW Support
Follow us on Twitter @VZWSupport

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.

I can receive emails from three different accounts but can't send a photo. It says the server doesn't allow relaying???

I can receive emails from three different accounts but can't send a photo from them. It says the server doesn't allow relaying???

I have a hard time describing this exactly, so I copied this from another thread. This seems to be a recent issue with AOL email accounts on the iPad the past few days. I have two AOL accounts and they work fine. See if this works for you.
+If you cannot send, under the smtp server your user name and password must be entered even though the prompt tells you it is optional. As a mobile device the port used is different from the one I would normally use if at home and therefore validation is required by use of the password. The normal port for the smtp server is 110 but to use on a mobile unit like the iPad port 587 is used.+
The big thing is to make sure that your username and password are filled in - Select your email account in the Mail setting and tap on the arrow next to the smtp server under the Outgoing Mail Server and then tap on the arrow next to smtp server under the Primary Server and fill in the information in there.
Some times you have to resort to deleting the account and starting over again.

Receive connector to allow relay for localhost

Similar Messages

Maybe you are looking for