Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.
Course Of The Month
4 days, 22 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Exchange Relay (Receive Connector) not using Send Connector
Posted on 2013-01-03
We have an receive connector set up to relay messages from certain IP address using Exchange 2010 receive connectors. However, we have come across an issue where an email is being sent through the receive connector to an external email address but it is not using the appropriate send connector.
The send connector being ignored works from a client using Outlook, but the SMTP relay does not seem to be working.
My main question is when using receive connectors to relay message to an external address are send connectors still used or are they bypassed?
If they are not bypassed, what else do you suggest we look at?
The send connector being ignored works from a client using Outlook, but the SMTP relay does not seem to be working.
My main question is when using receive connectors to relay message to an external address are send connectors still used or are they bypassed?
If they are not bypassed, what else do you suggest we look at?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5-
5
11 Comments
relaying processes the message in the normal way so yes it should use a send connector to send the message.
have you checked message tracking to see what happens to the received message?
what makes you think it is 'ignoring' the send connector, as opposed to being bounced by the receieve connector?
have you checked message tracking to see what happens to the received message?
what makes you think it is 'ignoring' the send connector, as opposed to being bounced by the receieve connector?
Active 4 days ago
How are you deciding what Send Connector to use? Message tracking is the key here, because Send Connectors cannot be "ignored". They will be used to send email, but if you have more than one server the email could go out another way as Send Connectors do not belong to a server, they are org wide.
Simon.
Simon.
I will check the message tracking and post the results.
I'm just assuming the send connector is being ignored because when sending to myfakedomain.com messages get sent to a specific smart host. Then the rest of the messages get sent out the Internet Connector.
I appreciate the help folks. I'll post soon.
I'm just assuming the send connector is being ignored because when sending to myfakedomain.com messages get sent to a specific smart host. Then the rest of the messages get sent out the Internet Connector.
I appreciate the help folks. I'll post soon.
Definately need to check the racking logs then as we need to work out where the smarthost is set in your system. Do yo have multiple exchange servers or more than one send connector?
The tracking logs show that some of the messages are using the Internet send connector and some of them are using the Custom connector. The messages I looked at all should fall under the Custom connector's rule set.
However, I noticed that the cost on these connectors are the same. Should the Internet connector's cost be higher than the Customer connector.
FYI - The Internet connector's scope is *
However, I noticed that the cost on these connectors are the same. Should the Internet connector's cost be higher than the Customer connector.
FYI - The Internet connector's scope is *
firstly, the catchall (*) connector should be the highest cost so it is used only when the recipients domain doesnt match any of the other connectors.
secondly, is the custom connector set to use the smarthost you mentioned above?
secondly, is the custom connector set to use the smarthost you mentioned above?
The catch-all connector does have the same cost as the other Custom connector. I will get that changed.
The Custom connector is set to use a smarthost. The Customer connector watches for a certain sender domain and if the domain matches the message is sent to a smarthost. That's the idea anyways.
The Custom connector is set to use a smarthost. The Customer connector watches for a certain sender domain and if the domain matches the message is sent to a smarthost. That's the idea anyways.
Sorry mate, I'm a little confused now.... :-)
Am I right in saying you WANT it to go through the smarthost then?
I'm just assuming the send connector is being ignored because when sending to myfakedomain.com messages get sent to a specific smart host. Then the rest of the messages get sent out the Internet Connector.
The Custom connector is set to use a smarthost. The Customer connector watches for a certain sender domain and if the domain matches the message is sent to a smarthost. That's the idea anyways.
Am I right in saying you WANT it to go through the smarthost then?
If the domain being sent to is myfakedomain.com then the message needs to be sent to a smart host. Every other message needs to be sent out the Internet Connector.
I have changed the Internet Connector to have a higher cost than the customer (smart host) connector and we are testing now.
I have changed the Internet Connector to have a higher cost than the customer (smart host) connector and we are testing now.
Featured Post
Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Servers >> Certificates…
The video tutorial explains the basics of the Exchange server Database Availability groups.
The components of this video include:
1. Automatic Failover
2. Failover Clustering
3. Active Manager
Suggested Courses
Course of the Month4 days, 22 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.