Exchange 2013 – Send & Receive Connector Issue.

We have four server roles in our environment i.e. PS-MB1, PS-MB2, PS-CAS1 and PS-CAS2.
As per company policy our limits are:
Sending Inside organization : 3MB Max.
Receiving Inside organization : Unlimited
ß for receiving emails from Inside and
Internet.
Sending Outside organization : 3MB Max.
Receiving from Internet : 35MB Max.
ßIts bounce back emails on Internet larger than 3MB
Commands outputs are mentioned below for your reference:
[PS] C:\Windows\system32>Get-ReceiveConnector
Identity                               
Bindings                               
Enabled
PS-MB1\Default PS-MB1                  
{[::]:25, 0.0.0.0:25}                  
True
PS-MB1\Client Proxy PS-MB1             
{[::]:465, 0.0.0.0:465}                
True
PS-MB2\Default PS-MB2                  
{[::]:25, 0.0.0.0:25}                   True
PS-MB2\Client Proxy PS-MB2             
{[::]:465, 0.0.0.0:465}                
True
PS-CAS1\Default Frontend PS-CAS1       
{[::]:25, 0.0.0.0:25}                  
True
PS-CAS1\Outbound Proxy Frontend PS-CAS1 {[::]:717, 0.0.0.0:717}     
           True
PS-CAS1\Client Frontend PS-CAS1        
{[::]:587, 0.0.0.0:587}                
True
PS-CAS2\Default Frontend PS-CAS2       
{[::]:25, 0.0.0.0:25}                  
True
PS-CAS2\Outbound Proxy Frontend PS-CAS2 {[::]:717, 0.0.0.0:717}      
          True
PS-CAS2\Client Frontend PS-CAS2        
{[::]:587, 0.0.0.0:587}                
True
PS-MB1\Client Application Relay PS-MB1 
{0.0.0.0:25}                           
True
PS-MB1\Exchenge.test                   
{0.0.0.0:25}                  
         False
PS-MB2\Client Application Relay PS-MB2 
{0.0.0.0:25}                           
True
[PS] C:\Windows\system32>get-receiveconnector | ft name, maxmessagesize
Name                                                       
MaxMessageSize
Default PS-MB1                                             
35 MB (36,700,160 bytes)
Client Proxy PS-MB1                                        
35 MB (36,700,160 bytes)
Default PS-MB2                                              35
MB (36,700,160 bytes)
Client Proxy PS-MB2                                        
35 MB (36,700,160 bytes)
Default Frontend PS-CAS1                                   
36 MB (37,748,736 bytes)
Outbound Proxy Frontend PS-CAS1                            
36 MB (37,748,736 bytes)
Client Frontend PS-CAS1                                    
35 MB (36,700,160 bytes)
Default Frontend PS-CAS2                                   
36 MB (37,748,736 bytes)
Outbound Proxy Frontend PS-CAS2                            
36 MB (37,748,736 bytes)
Client Frontend PS-CAS2                                    
35 MB (36,700,160 bytes)
Client Application Relay PS-MB1                            
35 MB (36,700,160 bytes)
Exchenge.test                                              
35 MB (36,700,160 bytes)
[PS] C:\Windows\system32>get-transportconfig | ft maxsendsize, maxreceivesize
MaxSendSize                                                
MaxReceiveSize
3 MB (3,145,728 bytes)                                     
Unlimited
[PS] C:\Windows\system32>get-sendconnector | ft name, maxmessagesize
Name                                                     
  MaxMessageSize
Internet                                                   
35 MB (36,700,160 bytes)
Question: Why ae are facing trouble in receiving 3MB+ size email from internet.

Its not working,
our requirement is
Sending Inside organization : 3MB Max.
Receiving Inside organization : Unlimited
ßfor receiving emails from Inside andInternet.
Sending Outside organization : 3MB Max.
Receiving from Internet : 35MB Max.
ßIts not receving above 3MB from Internet.
Please help.

Similar Messages

  • Exchange 2013 Frontend Receive Connector - cannot telnet port 25

    Hello There,
    I’m going to proceed with migration form exchange 2007 to 2013 but just encounter problem.
    I can telnet port 25 form new Exchange 2013 server but cannot telnet it form any other computer within LAN. 
    We have notice it when I was changing SMTP banner to match RevDNS. If I change Receive Connector to role Hub Transport it is responding on telnet 25 from other servers.
    But correct is to set it up as Frontend Transport.
    There is no AV and Friewall is disable. I can telnet prots form hubtransport role receive connectors.
    Fresh installation and server is fully updated. Please help. 
    Maciej

    multi-role CAS + MBX
    on ESXi 5.1
    I found some topics that this could be related to problem with Network card E1000E and Exchange 2013 
    I did experience vmware host crash during EX2013 installation. But after restart Installation took off when its left and as far as i could tell everything else is working fine. 
    I also used wiershark to check negotiation and it looks like 25 is listening and even establishing conneciton but no baner and disconneciting couple of secconds after it is established. 
    It is 4AM so I hope Im writing it clear :)
    Thanks

  • Exchange 2013 not receiving internal and external emails ..

    I have a coexistence of exchange 2007 and exchange 2013 ..2013 mailboxes where able to receive and send mails (internal and external) but suddenly the mail flow has stopped. 
    Mail flow status
    2013 to 2007 = OK
    2013 to internet = OK
    2013 to 2013 = OK
    2007 to 2013 = FAIL
    Internet to 2013 = FAIL 
    incoming internet mails return the NDR below
    Diagnostic information for administrators:
    Generating server: mydomain.com
    [email protected]
    Remote Server returned '< #4.4.7 smtp;400 4.4.7 Message delayed>'
    What could be a possible reason for this? 
    Cheers guys ..
    ..forever is just a minute away*

    Hi Richard,
    Thank you for your question.
    When there is a coexistence of Exchange 2007 and Exchange 2013, external email will be sent and received by Exchange 2013.
    4.4.7 means message expired, message wait time in queue exceeds limit, potentially due to remote server(your Exchange server ) being unavailable.
    If your organization has correct MX record in ISP. We could refer to the following link to check if MX record is correct:
    http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx
    If we could telnet Exchange server by the following command: telnet mail.domain.com 25
    If there is a receive connector on Exchange 2013 to receive Internet emails, we could create a receive connector to receive message from the Internet by the following link:
    http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured

    Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured.
    [PS] C:\Windows\system32>Get-TransportConfig
    AddressBookPolicyRoutingEnabled                             : False
    AnonymousSenderToRecipientRatePerHour                : 1800
    ClearCategories                                            
    : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                          
    : UseExchangeDSNs
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                        
    : True
    ExternalPostmasterAddress                                   : [email protected]
    GenerateCopyOfDSNFor                                        :
    HygieneSuite                                               
    : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority                               :
    InternalDsnSendHtml                                        
    : True
    InternalSMTPServers                                        
    : {127.0.0.1}
    JournalingReportNdrTo                                       : <>
    LegacyJournalingMigrationEnabled                            : False
    LegacyArchiveJournalingEnabled                              : False
    LegacyArchiveLiveJournalingEnabled                          : False
    RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
    RedirectDLMessagesForLegacyArchiveJournaling                : False
    MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                                            
    : 7.00:00:00
    MaxReceiveSize                                             
    : 50 MB (52,428,800 bytes)
    MaxRecipientEnvelopeLimit                                   : 5000
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                
    : 20 MB (20,971,520 bytes)
    MigrationEnabled                                           
    : False
    OpenDomainRoutingEnabled                                    : False
    RejectMessageOnShadowFailure                                : False
    Rfc2231EncodingEnabled                                      : False
    SafetyNetHoldTime                                          
    : 2.00:00:00
    ShadowHeartbeatFrequency                                    : 00:02:00
    ShadowMessageAutoDiscardInterval                            : 2.00:00:00
    ShadowMessagePreferenceSetting                              : PreferRemote
    ShadowRedundancyEnabled                                     : True
    ShadowResubmitTimeSpan                                      : 03:00:00
    SupervisionTags                                            
    : {Reject, Allow}
    TLSReceiveDomainSecureList                                  : {}
    TLSSendDomainSecureList                                     : {}
    VerifySecureSubmitEnabled                                   : False
    VoicemailJournalingEnabled                                  : True
    HeaderPromotionModeSetting                                  : NoCreate
    Xexch50Enabled                                             
    : True

    hi stephan... lets put in this way... are you sending attachment ...did you checked the max attachment size as mail send size and attachment size are two different things.. please check this for info on different size creteria
    http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
    can you please share the output of below three commands... i doubt your receive connector is not configured properly.
    Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
    Get-SendConnector | Format-List -Property Identity, MaxMessageSize
    Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
    you can also check this link which gives a perfect info on how exchange works for email size... http://rajisubramanian.wordpress.com/2014/01/26/exchange-server-2013-message-size-configuration-detail/
    Mark as useful or answered if my replies helped you solving your query.
    Thanks, Happiness Always
    Jatin
    Skype: jatider2jatin, Email: [email protected]

  • Mails From Exchange 2013 are received as SPAM

    Hello,
    We have Exchange 2013 configured to send and receive mails internally and externally. Everything is going great except the fact that the mails sent FROM our Exchange 2013 are received as SPAM. For example, I send an email from exchange to my gmail account
    (generally to any EXTERNAL receipt). I receive the mail in the SPAM folder.
    Any ideas Please !!

    Hi,
    Firstly, I’d like to recommend you find out exactly what the problem is and resolve it before bothering to delisting from the blacklist.
    And based on my knowledge, there are the following reasons:
    1. Exchange Server is pumping out SPAM emails because a mailbox password was compromised:
    Please figure out which mailbox user is the culprit by looking over event viewer logs and change the password. Then clear email queue and see if any new spam emails are generated, if the change of password stops the flow of SPAM email, we can remove the domain
    name from the blacklist.
    2. One of our computers are infected with a mass mailing worm virus:
    We can check our firewall log
    For information about removing from blacklist, you can refer to the following similar thread:
    http://social.technet.microsoft.com/Forums/en-US/b3b818a6-641a-4264-87ca-fa4183ffc50c/how-to-remove-my-ip-address-fro-blacklist?forum=exchangesvrsecuremessaginglegacy
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 Mail Receiving Issues

    Hi everybody,
    Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
    All functions and rolls are configured and installed but i am having issues receiving external e-mails.
    Almost all of the external mails are being deliverd a half hour to a hour after being sent.
    To start of on the first level.
    I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
    Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
    The Draytek DHCP function is set to off.
    192.168.168.2  (DC) -> 80 (HTTP IIS)
    192.168.168.2 (DC) -> 1723 (RRAS)
    192.168.168.3 (Exchange) -> 25 (SMTP)
    192.168.168.3 (Exchange) -> 443 (SSL)
    My Draytek router is connected through LAN1 to a HP switch (unmanaged).
    The physical server has 3 NIC's, all of these are connected to the HP Switch
    I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
    The network has been configured as following.
    I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
    NIC1is setup for the physical server,
    IP Address: 192.168.168.1
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254 (Draytek address)
    DNS: 192.168.168.254 (Draytek address)
    The Server software firewall has been set to a private network through the local security policy.
    I have setup 2 VM's through the Hyper-V roll.
    The first VM is the Server 2012 R2 Domain controller.
    For this VM I created a virtual switch connected to my second NIC(2).
    I unchecked the box where my host can communicate with the NIC(2).
    The DC has been configured as following:
    Hostname: SERVER
    IP Address: 192.168.168.2
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 127.0.0.1
    I can ping to all the adresses from this server (internal and external).
    The server has been promoted to domain controller with the following rolls.
    ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
    Alle these rolls have been set and working. (all have been tested)
    DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
    A DNS simple and recursive test work fine.
    I did no configuration on the DNS after the DC PROMO.
    So i created users in the AD.
    After that I created a second VM, this one is used for the Exchange.
    I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
    Hostname: SERVER
    IP Address: 192.168.168.3
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 192.168.168.2 (pointing to the DC)
    I joined this server to the domain, everything is working fine.
    Both servers have internet and network.
    Running portscans on 1723 and 80 all work like a charm.
    No its time to install Exchange.
    I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
    Installed de needed API and filters.
    Installed Frameworks 3.5 on both servers.
    And the Exchange installation was succesfull.
    CU3 is also installed.
    I configured the send connector, accepted domains etc.
    Created all needed certificates (self signed)
    Did a portscan on 433 and 25 and they work.
    All the hosting records are set mail.domain.nl etc. and MX records.
    I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
    Connecting through the internet to OWA works perfect and i can login with users.
    Sending e-mail internally works perfect, the messages are being deliverd in an instant.
    Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
    But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
    I did online SMTP checks and e-mail checks, the all come out like it should.
    One message from MX TOOLBOX on the SMTP:
    SMTP Transaction Time
    8.408 seconds - Not good! on Transaction Time
    I have nog other receive connectors setup, just the standard connectors.
    So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
    I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
    I ran the best practices analyzer and get about 23 errors and 20 warnings.
    A lot of services are unhealt like the "ExchangeTransport).
    I have no idea what is causing the issues and read almost every forum.
    Does anyone have a clue what is going on?
    Did i miss something, is there a misconfiguration?
    Best regards,
    Tim

    The mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
    The internal e-mail also works flawless.
    The entire Exchange server just not received this mail in time.
    I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
    I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
    After you asked me about the firewall, i got a hunch..
    It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
    Still the same problem...
    But there was still one ethernet device that could have a firewall, the internet modem!
    This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
    But I was wrong, there was a firewall enabled on the modem!
    All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
    creating the issue on the incomming e-mail.
    I disabled the firewall and all the external e-mails are being received in an instant!
    Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
    Many thanks for your help Kjartan!

  • Tricky Exchange 2013 send issue - im stumped...

    Hi everyone,
    I ran into an issue this morning in my Exchange 2013 SP1 environment today that has me stumped. Like most issues, it just happens. No changes, patches or updates to the system were applied and the system was normal until now. Here is my problem –
    My Outlook users have their own mailboxes, and my company has a Help Desk email box that has its own user account. My users are set up via Exchange / Outlook to have their own mailboxes and full access to Help Desk mailbox in their Outlook .
    Each Outlook client in configured with the users account, and the Help Desk account because users want to be able to hit the FROM button in Outlook and chose whether a reply comes from them personally or the Help Desk mailbox.  This has worked great,
    up until now.
    All of a sudden, you cannot send from the Help Desk account anymore. The mailbox opens up, a user can see and access all the mail and it is receiving email fine. But if a user wants to reply or create NEW email, choses FROM and uses the Help Desk account
    they get this error on sending
    Sending reported error (0x8004010F) Outlook data file cannot be accessed.
    The users regular account works fine.
    I recreated the mail profile, didn’t help the issue. I checked on OWA and if you access the Help Desk account on its own it sends fine.
    If you create an email from your own email account and CC the Help Desk, it sends fine.
    All users have Full Access permission and Send As permission on the server.
    Nothing has changed that I know of and this worked totally fine for almost a year until today, it just stops working.
    Any ideas, I’m totally stumped… I have to apply CU7 still this weekend, maybe that will do something. But as of now I cant even see any real errors as to whats going on here. 
    Ric

    Hi,
    In your case, please check the autodiscover and OAB by using "Test E-mail AutoConfiguration".
    If autodiscover fails, please troubleshoot the autodiscover by directly accessing the autodiscover url via IE and let me know the error code. If autodiscover works, you need to troubleshoot the OAB generation, publishing and downloading issues.
    For OAB generation and publishing issues, you can check the application logs on the CAS and Mailbox servers. For the OAB downloading issue, you can manually access the OAB url via IE and see if there is any error code.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 - Mail receive problem -Help!

    Exchange 2013 SP1 -fresh install -test environment with one test mailbox setup in addition to the Administrator account. Using default Receive Connectors and it is set for Anonymous. Using OWA and Outlook 2010 for testing.
    We can send/receive mail INTERNALLY in both Outlook & OWA between our test user and the Administrator user.
    We can send mail externally from both accounts.
    We are not receiving mail into the Inbox of either OWA or Outlook.
    We are not seeing any authentication issues with Outlook -always shows connected to Exchange. But if we have same problem in OWA then we are just testing with it for now.
    We ran the Microsoft Connectivity Analyzer for both Inbound and Outbound SMTP and it passed with no errors/warnings L
    We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:

    Thank you for replying. Yes the mailbox is at Time Warner and I can use their webmail interface and see the messages I sent to the test user are there.
    No, our domain name is companyname.com  (if you need the actual name..I am not sure if I should send it to you?) and we use
    [email protected] for email.
    Our external A records and MX records are at Network solutions and that is posted here-- but decided to start another thread with more concise information as I learned of it:
    http://social.technet.microsoft.com/Forums/office/en-US/0b18e928-0207-4ab9-bc12-c00a75088bdc/new-deployment-outlook-can-send-but-not-receiving-messages?forum=exchangesvrsecuremessaging
    When I do NSLOOKUP of our domain I get just the two MX records at Time Warner. Not anything with our actual domain name for email in it. I just added the A records for mail.companyname.com and autodiscover at Network Solutions yesterday...but though those
    were only for use externally for OWA, ActiveSync, etc
    Note we do not use Split-DNS on our internal domain either. Our AD name is different than our public domain name - The AD is named with a subdomain: qs.companyname.com
    Lastly, I did not create an MX record at network solutions for mail.domainname.com. Should I do that and set it to a higher priority?

  • Exchange 2013 Sp1 Test-PopConnectivity issues in coexistence

    I'm having issues with Pop3 in a coexistence environment with 2007. The 2013 roles are split- cas servers and mailbox servers.
    If I run "Test-PopConnectivity -ClientAccessServer:cas01 -MailboxCredential:(Get-Credential domain\test.exchange) |fl"
    I get the error "Service MSExchangePOP3 was not found on <mailboxserver>" and a DR Watson is created.
    Ok I know there is a front end and a back end component to Pop3. This error is expecting to find the front end component on a mailbox server? So is it just an issue because the roles are split or is it to do with proxying through the CAS not being enabled?
    Pop3 does not use a send connector- just a receive connector right? So how would it Proxy- if it does
    Confused
    Tony

    Hi,
    Is “cas01” the front end server?
    Did you use the exchange 2013 MailboxCredential to test the Pop Connectivity?
    Make sure the pop is enalbed for users and the pop services are started.
    Proxy and redirection for POP and IMAP:
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Thanks,
    Simon Wu
    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)

  • Exchange: Can send/receive mails from/to every mail server except for Gmail...

    Hello
    I am having the same issue as the user here:
    http://social.technet.microsoft.com/Forums/en-US/3c1e874a-e18a-4b01-ad5e-477acc266ebc/exchange-2013-everything-works-except-outgoing-emails-to-gmail?forum=exchangesvrsecuremessaging
    Same error message... I can send to every mail server around the world except for gmail I get the following error:
    Remote Server at gmail.com (2a00:1450:4001:c02::13) returned '400 4.4.7 Message delayed'
    28.01.2014 12:42:14 - Remote Server at gmail.com (2a00:1450:4001:c02::13) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." 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 2a00:1450:4001:c02::13:25'
    What can be the reason?
    Thanks
    James

    Hello,
    The error means the network is unreachable. We need more information to analyze the reason.
    Please use nslookup command line tool to check if DNS MX record of gmail is correct.
    Please use telnet command line tool to check if you get same error.
    Please check if your server ip address is in blacklist by the link:
    http://mxtoolbox.com/blacklists.aspx (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.)
    Besides, please use get-sendconnector | fl cmdlet to check your send connector configuration.
    If you have any feedback on our support, please click here
    Cara Chen
    TechNet Community Support

  • Exchange 2013 stops receiving external email after about 8 hours

    Hello,
    Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night.  I could not find anything wrong with receive connectors.  Telnet works internally when this
    happens but NO access from public side testing with telnet.  After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
    I dont know what to check or look for at this point.  Very new to exchange 2013.  Any kind of advice would be helpful at this time.
    It is not a firewall issue.  Same firewall and set of rules that we use for other/old mail servers.  We only have 1 exchange server that has all roles.
    Lead Pusher

    OK... Did alot of testing and spent some time with Microsoft's support on the phone.
    I believe there is actually two problems going on in this thread.
    1. Exchange 2013 Admins that have changed the default receive connectors are experiencing a conflict on the scope settings. Make sure that none of the receive connectors are using the same ports, and that you have not modified the security settings in anyway
    unless you really know what you are doing.
    If you are unsure of what the settings should be after you have change them, the only suggestion I have right now, (as I have not taken the time to do screen shots or write down all the default settings) is to install Exchange 2013 on a virtual machine and
    look at them, then change back the settings that do not match.
    2. The Malware Agent has a flaw that is causing the the Microsoft Exchange Transport service to endlessly wait on the Malware Agent to process a message that it just can't handle. (Two reboots of the entire server may be needed to clear this, or sometimes
    you can get away with restarting the Microsoft Exchange EdgeSync service.)
    The Microsoft technician had me perform a sequence of steps that highlighted this. To see if this is infact your problem you can perform the following steps.
    A)  Once the Exchange server stops processing messages, figure out the rough time it stopped processing messages.
    B)  Open the event viewer.
    C)  Under "Windows Logs", right click "Application", select "Filter Current Log...", check "Warning" and "Error", then click "OK".
    D) Scroll down the log to the rough time that your Exchange Server stopped processing messages. You are looking for a slew of errors about the same time from "MSExchange Extensibility" (1051), "MSExchange Transport" (9201), "MSExchange
    Transport" (9201), "MSExchange Extensibility" (1056), "MSExchangeTransport" (10003), and "MSExchange Common" (4999).
    It is the "MSExchangeTransport" (10003) that I believe is the real problem. The Microsoft technician agreed. He did not want to spectulate as to exactly what was going on, but it seems to me that since he had me disable the "Malware Agent"
    for now, that it is indeed the problem. 
    E) So.... Open the Exchange Management Console and type "Disable-TransportAgent", followed by enter. It will prompt "Supply values for the following parameters:". Enter "Malware Agent", press enter again. Type "A",
    for yes to all.
    or
    http://technet.microsoft.com/en-us/library/jj150526.aspx"
    F) Go to run, enter "services.msc". On the window that opens, find "Micorosoft Exchange Transport" and restart it.
    I know this is NOT a fix, but a work around that is less than desired as the Malware Agent is a filter to keep unwanted emails out. I highly recommend running some sort of 3rd party spam/Malware filter that has been fully tested to run with Exchange
    2013 if you do this.
    Microsoft is to contact me back once they can figure out why this is happening, and I believe in the end a patch for Exchange 2013 will be produce to correct the problem.
    In the mean time.... don't waste your money on paying Micorosoft for support, as I have already done this.
    For the individuals who say they are not experiencing trouble, I am going to go out on a limb here and say that either you have a 3rd party software program that is filtering the mail before it reaches the Malware Agent, you have disabled the Malware Agent,
    or you are using another mail server to forward email to your Exchange 2013 server. With either of these cases you are much less likely to see this problem.
    One last issue that a few people may be experiencing, is Exchange 2013, running on Server 2012 that is a VM. Several VM setups have a bug with the VM NIC management interface and Windows Server if you are using the same NIC for both. For example Xen
    Server 5.6 and XEN XCP both have this bug. There is an patch for XEN Server 5.6, but so far nothing for Xen XCP.
    I have spent many hours trying to figure my problems with Exchange 2013 and I will not swear that my entire post is correct, but I have gotten very much closer to a stable mail server after much work. If you feel that anything is incorrect, please reply
    back and let me know why, so that we may all benifit.
    P.S. Sorry for the mis-spellings and what not, I am very tired at the moment, and was forced to use explorer, because this site is not liking Chrome at the moment. (Will not let me login)

  • Outlook 2013 send & receive is very slow or freezes

    Hello. I recently purchased Office 2013 to install on my new laptop at the beginning of February. Everything was working fine up until a couple weeks ago. I am having issues in Outlook 2013, specifically I am not getting emails or when I send
    emails they show as being sent but the customer never receives them. I have 2 email accounts setup and both are scheduled to automatically send and receive every 1 minute but even if I hit send & receive manually nothing works. Eventually the send/receive
    window will open and freeze, showing "processing" or that there are 60 minutes left in trying to receive a message! I have never had an issue like this before and I need it to be fixed so I can continue to communicate with my customers! Please help!

    Does it throw any error code? Make sure the internet/network doesn't have any issues? Check whether the same mailboxes can be accessed in their webmail interfaces (say, OWA) and see you don't face any send/receive issues with that?
    Do check whether you can repro the issue by opening Outlook in safe mode or not (Outlook.exe /safe)? If issue is not reproduced, then I would suspect one of the Outlook add-in may be causing this above issue.
    You can check the send/receive groups. For more info, you can refer:
    http://office.microsoft.com/en-us/outlook-help/why-use-send-receive-groups-HA102749372.aspx
    Let me know how it goes.
    DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

  • Exchange 2013 send as permission not allowed

    We have a Exchange 2013 server and Outlook 2010 clients. I have set full permission on other mailboxes with Powershell and in the ECP I set Send As permission for this user. But when I start Outlook 2010, go to the mailbox of one of the users and try to
    send an email as this user, the Outlook gives the error that send as is not allowed. What could the problem be?

    Hi,
    Please log in the Exchange Admin Center in Exchange 2013 to check whether the permissions are configured properly:
    1. Access ECP URL in IE to logon EAC as an administrator.
    2. Click recipients > Mailbox.
    3. Double-click the userA which is set full access permission and send as permission.
    4. In the User Mailbox window, click mailbox delegation to check whether the userB is listed under Send As and Full Access permission.
    If the permission is configured correctly, please try removing the permission and re-add it to check whether the issue persists.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • 2013 Default Receive Connectors

    I accidentally deleted all my receive connectors and I'm new to Exchange 2013.  Can someone please post up the configuration of the ones created by default on a MB/CAS box?  Thank you so much in advanced!

    I accidentally deleted all my receive connectors and I'm new to Exchange 2013.  Can someone please post up the configuration of the ones created by default on a MB/CAS box?  Thank you so much in advanced!
    Hi,
    Here's you have some of the settings configured on the default receive connectors created during setup. (Single Server with both roles). This should help you configured the most important settings at least.
    [PS] C:\>Get-ReceiveConnector | fl Name,AuthMechanism,RemoteIPRanges,TransportRole,permissiongroups,MaxMessageSize
    Name             : Default EX2013
    AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole    : HubTransport
    PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
    MaxMessageSize   : 35 MB (36,700,160 bytes)
    Name             : Client Proxy EX2013
    AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole    : HubTransport
    PermissionGroups : ExchangeUsers, ExchangeServers
    MaxMessageSize   : 35 MB (36,700,160 bytes)
    Name             : Default Frontend EX2013
    AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole    : FrontendTransport
    PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
    MaxMessageSize   : 36 MB (37,748,736 bytes)
    Name             : Outbound Proxy Frontend EX2013
    AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole    : FrontendTransport
    PermissionGroups : AnonymousUsers, ExchangeServers
    MaxMessageSize   : 36 MB (37,748,736 bytes)
    Name             : Client Frontend EX2013
    AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
    RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole    : FrontendTransport
    PermissionGroups : ExchangeUsers
    MaxMessageSize   : 35 MB (36,700,160 bytes)
    Also see:
    Receive Connectors
    Martina Miskovic

Maybe you are looking for