Exchange Server 2013 - Send E-Mail

I am very new to Exchange Server. I managed to install 2013 and I can send e-mail on-premises with no problem. When I follow what I believed to be the step-by-step instructions for connecting a Send Connector so I could send e-mail on-line I
can't get it to work. I set it up and try an e-mail and the e-mail just sits in the drafts folder forever (as in 2 days now). I can't send any other e-mail now either. They just sit in the drafts folder.
Finally I try to delete the on-line draft message and it won't delete. I delete the Send Connector and the draft finally will delete after nearly 10 hours. I can again send on-premises e-mail but nothing else.
Can someone be kind enough to step an old man through the exact process needed in order to set up and send and receive e-mail to the internet?
Greatly appreciated.
dave

It looks to me like I'm going to have to give up. I understand a lot of what you post, but I can't get the same results. (see my attachment). I wish I had some step-by-step tutorials available that I could learn from instead of trying to
fit bits and pieces of a puzzle together without having all of the pieces.
Looking at my previous post. Did I set up the DNS addresses properly on my Domain Server? Am I accessing them correctly from the Exchange Server? I don't know.
Attached is a Word document that shows what I get when I follow your above instructions. I can do the NSLOOKUP, set type=MX and then Rowley.xyz, but then nothing else is the same. If I can't get the same results you do, then I can't go anywhere.
Everyone had to start at the beginning and learn, but I'm totally lost now as to what would be the starting point and each subsequent step.
Thank you for your assistance. If I could get the answers to the DNS questions above I will try again from scratch.
I realize it's not you, it's me, someone who is trying to learn something new without a "guide book" to work from and without a "mentor/instructor". I have purchased and read several books on Server 2012 and Exchange Server 2013,
just to get this far, but no further.
dave

Similar Messages

Exchange server 2013 send and received issue

Hi Support,
I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
2013 working fine. Please give the step check perpoes.

dear Pardeep, you said it was working fine then you did some DNS changes..
i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
Secondly you can verify your config from the below link.
http://www.techieshelp.com/exchange-2013-step-by-step-configuration/
in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange server 2013 mail send and received problem

Hi Support,
I have Install Exchange server 2013 and create mail box and local send received locally but days back i have not able to mail send and received. what setting are required for user mail send and received locally. and how to create mx and txt record for my
domain.

Hi,
According to your description, I know that the Exchange server can send/receive internally at beginning, however doesn’t work now. Please correct me if there is anything misunderstand.
Great checklist from S.Nithyanandham. Additionally, how about sending/receiving via OWA? And any error messages when can’t send and receive?
Please make sure the Message Tracking has been enabled and run following command to output track log and check detail information:
Get-MessageTrackingLog |FL > "c:\Track Search.txt"
For more information about Message Tracking logs, please refer to below article:
http://technet.microsoft.com/en-us/library/bb124926
If you want to communicate externally, you need to contact ISP to register DNS MX record.
Best Regards,
Allen Wang

How to get list of Users[MailBoxes] in Exchange Server 2013 by using EWS Managed API

Hi all,
I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users login name.
I was created Full Access permissions of all users to Admin user account, to access each user Mailbox programatically
i need the list of Mailboxes in exchange server .
MailBox mailbox = new MailBox("user");
Please share your ideas

Hi,
We can run the following command in Exchange Management Shell to get all user mailboxes name and export it to a .csv file:
Get-Mailbox -ResultSize Unlimited | Select Name,Alias,RecipientTypeDetails | Export-Csv c:\Users.csv
If you want to retrieve the list of users by using EWS Managed API, I suggest you can ask a question in Exchange Development forum for more suggestion:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads
Regards,
Winnie Liang
TechNet Community Support

Get list of User Mailboxes in Exchange server 2013 by using EWS managed API

Hi all,
I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users log in name.
i know the command in Powershell to get list, but i need this using code[ ews managed API].
How can i achieve this ?
Please share your ideas

Hi Glen,
i follow your suggested links i wrote below code ,
here i am getting error
The term 'Get-Users' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
SecureString password = new SecureString();
string str_password = "EIS2014!@#";
string username = "[email protected]";
foreach (char x in str_password) { password.AppendChar(x); }
PSCredential credential = new PSCredential(username, password);
WSManConnectionInfo connectionInfo = new WSManConnectionInfo(new Uri("http://ExchangeServer.admin.com/powershell"), "http://schemas.microsoft.com/powershell/Microsoft.Exchange", credential);
//connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Basic;
Runspace runspace = RunspaceFactory.CreateRunspace(connectionInfo);
PowerShell powershell = PowerShell.Create();
PSCommand command = new PSCommand();
command.AddCommand("Get-Users");
command.AddParameter("ResultSize", 50);
powershell.Commands = command;
runspace.Open();
powershell.Runspace = runspace;
var aa = powershell.Invoke();
Please help me.

Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

Hi,
We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
Return massage
"This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
Thanks,
Gayan

1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
2) Disable unwanted Add-Ins in outlook that may open many sessions
3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

Hi!
For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
The machine is virtualized on Hyper-V.
I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
either. Outlook says disconnected.
When running the Exhchange Connectivity Analyzer, I get the following:
- Receive: Connection was successful but no banner was received.
- Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
Mailflow was working perfectly at the time of the backup.
Help is much appreciated!
UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
The following error was generated when "$error.Clear();
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
              $dispname = "Microsoft Exchange";
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                  $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($arbUsers.Length -ne 0)
                    $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
              else
                if ($mbxs[0].DisplayName -ne $dispname )
                   set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
                  Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                  set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                  # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                  # This can be remove after BUG(O15#2555914) is fixed.
                  if ($sysMbx.RetentionPolicy -eq $null )
                     $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                     set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
              else
                Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
            else
              write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
The solution for me was to restore the corrupted arbitrary mailboxes using this
LINK. It is for 2010 but Works on 2013.
I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 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
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

Hello Guys
I have a mailflow issue, hoping someone can help with detail description, below is the setup
Exchange server 2010 SP3 with all roles in one server
Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
queue ..
Can someone please provide detailed solution what needs to be configured?
MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Hi,
1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
I think I need to create a receive connector in the 2013 to receive from 2010 ?
No need ,by design exchange 2013 cas server default frontend receive connector will be having an
entire ipv4 and ipv6 segment and anonymous connection is checked by default.
I think I also need to create a send and receive connector for 2013 users to each other?
No need , an intra organisation send connector and the default receive connectors in exchange will be used
for internal mail flow between the exchange 2013 users.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
Example
[email protected]
[email protected]
[email protected]
I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email
Thank you
Benhur

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Exchange Server 2013 does not deliver mail as they arive.

I need Help and guidance on this problem. I have installed Exchange server 2013 with SP1 on Server 2012. Install Went perfect no error. It on a server with 2 TB storage. 16G
memory. Exchange 2013 is the only application running on the box. DNS service is also running on the box. I can see the mail arrive in the mail Box Queue with the Queue Viewer and they would just sit there and then after a 15 to 30 min delay it release the
mail to the mail boxes. The only error or warning I am seeing in the logs are the 6002 warning. Any suggestion would be greatly appreciated.

Please share message header of one of the delayed message. It will help to narrow down the issue.
Do you see any connection failures in connectivity logs.
Do you have multiple 2013 servers in your exchange environment ?
Lets fix it.
Received: from Xchngsvr.A.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
Transport; Fri, 25 Apr 2014 13:31:33 -0400
Received: from Xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 25 Apr
2014 12:30:44 -0400
Received: from xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server id 15.0.847.32 via Frontend
Transport; Fri, 25 Apr 2014 12:30:37 -0400
Received: from mia0vm-cass03.colo.sonicwall.com ([208.17.117.5])
by
xchngsvr.a.com (SonicWALL 7.4.5.1391)
with ESMTP id 201404251630370000228;
Fri, 25 Apr 2014 12:30:38 -0400
Received: from mail1.fieldsolutions.com ([98.129.95.107])
by
mia0vm-cass03.colo.sonicwall.com (SonicWALL 7.4.4.8439)
with ESMTP id
201404251631070343409; Fri, 25 Apr 2014 09:31:07 -0700
Received: from localhost (localhost [127.0.0.1]) by mail1.fieldsolutions.com
(Postfix) with ESMTP id F32731031781
for <[email protected]>; Fri, 25 Apr 2014
11:31:06 -0500 (CDT)
MIME-Version: 1.0
To: <[email protected]>
From: Field Solutions <[email protected]>
Subject: WIN#: 649890 NEW Signage - Reply-To: <[email protected]>
Content-Type: multipart/alternative;
boundary="=_747eac72d0ea92652b25d7d469d7165b"
Message-ID: <[email protected]>
Date: Fri, 25 Apr 2014 11:31:06 -0500
X-Mlf-KeyWords: preapproved,dollars$$$,pay,toner,expectations,fl,dollars,guarantee,voltage,confi
X-Mlf-Language-Detected: NoLanguageFilter_English
X-Mlf-Connecting-IP: 50.244.134.141
X-Mlf-Country-Code: US
X-Mlf-Rules: rn;7.24
X-Mlf-Rules-Pos-Features: WORD_voltage_2.97;WORD_configuration_2.51;WORD_inputs_2.50;WORD_documentation_2.
X-Mlf-Rules-Neg-Features: WORD_preapproved_-1.85;SUBJ_dollars$$$_-1.74;SUBJ_pay_-1.56;WORD_toner_-1.53;WOR
X-Mlf-Sliderbars: N4,B4,S4,L4,Q4,G4,A4,I4
X-Mlf-Version: 7.4.4.8439
X-Mlf-Threat-History: nothreat
X-Mlf-Threat-Detailed-History: nothreat;none;none;none
X-Mlf-UniqueId-History: i201404251631070343409
X-Mlf-Connecting-IP: 208.17.117.5
X-Mlf-Country-Code: --
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;none;cloud-nj
X-Mlf-UniqueId: i201404251630370000228
Return-Path: [email protected]
X-MS-Exchange-Organization-Network-Message-Id: 5ea15b9c-561d-4a2a-d03e-08d12ebad75d
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: Xchngsvr.a.com
X-MS-Exchange-Organization-AuthAs: Anonymous
There is only one Exchange server in the Organization

Mail receives OK but will not send for smtp account. Exchange server receives/sends OK

mail receives OK but will not send for smtp account. Exchange server receives/sends OK I'm away from home, using a family-member's wireless network that has always worked OK in the past. Today, the same problem occured while waiting in a hospital waiting lounge. Any ideas?

The outgoing mail server may be rejecting mail from your network address. Typically that happens when your mail service provider is also your ISP, and you connect to it from another network. The SMTP server will allow connections without a password from anywhere, but it will only relay mail from within the ISP's network. It could also be that your account on the server has expired or been suspended.
If you need to send mail from outside your ISP's network, use an independent mail service provider. I don't have a specific recommendation.

Mails struck in Drafts folder after Transport Agent installed in Exchange Server 2013

Hi all,
I created Transport Agent and installed successfully in exchange server 2013.
After that mails are struck in drafts folder.
I thought because of My Custom transport Agent , then i Uninstall Transport agent.
but still no use.
I restart Microsoft Exchange Transport Service and restart my server also.
Here is the code i used
public sealed class MyAgentFactory : RoutingAgentFactory
public override RoutingAgent CreateAgent(SmtpServer server)
return new MyAgent();
public class MyAgent : RoutingAgent
public MyAgent()
this.OnSubmittedMessage += new SubmittedMessageEventHandler(this.MySubmittedMessageHandler);
public void MySubmittedMessageHandler(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
e.MailItem.Message.Subject = "This message passed through my agent: " + e.MailItem.Message.Subject;
I search in google about mails struck in drafts folder, all replies are
restore Default Receive Connectors. How can i restore it.
here is the link i see
http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

Hi Martina
Miskovic,
Here I am facing some weird situation.
Mails again stuck in Drafts folder.
i didn't installed anything. just checking again after some
time gap .
I tried again by restarting all services
, but no use.

Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years. However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
level, or as a (sophisticated) user. I have never tried to deploy either from scratch before. My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
software as Windows XP back when it was new. And even NetWare once.
When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements. For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
storage. There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
and phones, a secure file store, and not much else. If Exchange didn't need it, I would not need to install Active Directory, for example. We have no direct need for its services.
So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else. And it appears
I ought to be able to do it without virtualizing any of it. However, I have spent the last three or four days fighting one mysterious issue after another. I had Remote Access VPN working and fairly stable very quickly (although it takes a very
long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me. But I've always been able to get it back after scrounging through the
logs to find out what is bothering it. I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time). At one point I even received a number of e-mails
on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
But then Exchange Server just stopped. There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
the server or remotely).
So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
a single Windows Server 2012 server? And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)? If it can be done, can anyone provide any pointers on what
the pitfalls are that may be causing my problems? I am happy to provide whatever additional information anyone might like to help figure it out.
Thanks!

An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
should be back to normal.

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Exchange Server 2013 - Send E-Mail

Similar Messages

Maybe you are looking for