We just finished migrating from Exchange 2007 to Exchange 2013 and when I disable a certain receive connector on Exchange 2007 we stop receiving external emails. I have reviewed all of the Exchange 2013 Receive Connectors and everything looks to be fine but the server does not get mail flow. If anyone could assist with this issue that would be great.

Thanks,

Ryan

If someone sends a mail to us requesting a read receipt and the user accepts to send it (regardless of the Client, it's the same in Outlook 2013, Outlook 2010 and OWA), the SMTP FROM is invalid.

Instead of sending "Name <email@domain>" it sends only "Name" which is translated by some following smtp-relays to Name@wrong.Domain.

Seems to be an Error of Exchange 2013. (also documented here: www networksteve com /exchange/topic.php/Microsoft_Exchange_2013_-_Read_receipt/?TopicId=38683&Posts=0 )

Is there a bug fix / Workaround avaliable?

Thank you for your help.

Let's start to use authenticated SMTP clients, servers are configured correctly, are exchange 2007, but we find an unwanted behavior.

If a user is authenticated, the SMTP server does not validate that the smtp address of origin, is that corresponding to the user can put any other mail is dispatched

How limit smtp authenticated user to use his own email address for mail from address???

Thanks

Marcelo

Friends,our ExchangeServer2013server is sendingemailsnormally, butsometarget servers arecomplaining thatour messagesare coming up withthe nameandLANIPof the serverheader.

Look atthe picture thatactually has a momentwhere the Exchangeserverinformsits nameand its IP,how can Iavoid this?

Companies thatare complaining,say itfallsin the spam filterandthendeniesdelivery of the message.

Hold andthank you!

Ivanildo Teixeira Galvão

Hello,

I have two exchange 2013 server running both CAS and MB roles which are also part of a DAG. To secure mail flow in and out of my organization, I am planning to implement reverse proxy in my DMZ. I can easily access my OWA using my DAG name. I wonder if I can configure my reverse proxy machine to access the cluster name/ip. I am also confused about configuring the certificate. Which one of my machines should be used to create the CSR?

Pooriya Aghaalitari

Here's the scenario:

2 Exchange 2013 Servers configured with combined CAS and Mailbox roles.

While simulating an outage on one server (ServerA) by restarting it, any inbound mail (e.g. from the Internet) sits in the "SMTP Delivery to Mailbox" queue in Retry on ServerB until the ServerA is back up.  I would expect the mail to be delivered successfully as the mailbox databases all mounted successfully on ServerB when ServerA went down. 

It's looks almost as if the "SMTP Delivery to Mailbox" queue has somehow cached the active mailbox information, i.e. "When I last checked the mailbox databases were active on ServerA, so I'll keep trying to deliver there".

Any thoughts on what is going on here?

Tony www.activedir.org Blog: www.open-a-socket.com

Hi

I have installed new Exchange server for my company.. but e-mails are not going out from my domain.. I am getting below error.

MX, RDS, Exchange connectivity analyzer all going good.  but e-mail are not going out.

getting below error. if some body can help...

gmail.com    DnsConnectorDelivery    Retry    2    "Saturday, July 05, 2014 1:31:10 PM"    "[{LRT=7/4/2014 12:09:04 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" 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 173.194.75.26:25};{FQDN=gmail.com};{IP=173.194.75.26}]"


hotmail.com    DnsConnectorDelivery    Retry    2    "Saturday, July 05, 2014 1:30:53 PM"    "[{LRT=7/5/2014 1:09:40 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" 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 65.54.188.72:25};{FQDN=hotmail.com};{IP=65.54.188.72}]"

Pooriya Aghaalitari

We use app river to filter out any spam/viruses prior to coming to our Exchange 2013 server.  We are experiencing that some emails are being delayed for 1800 seconds through out the day, a sort of blacklisting by our Exchange server.  Does 1800 seconds or 30 mins ring a bell for anyone, I'm not sure what setting is causing this.  During the blacklist other emails are able to flow without issue.  These messages just seem to be stuck for 30 mins and then get resent and go thru after that timeout period. 

We are also running Symantec Mail Security 7.5 on that ex server.  We have the Antivirus turned on and do not have any spam settings enabled. 

This is the message that app river is showing in their logs:
 rsp: 451 4.7.0 Temporary server error. Please try again later. PRX5
message body rejected, got:451 4.7.0 Temporary server error. Please try again later. PRX5
batch delayed for 1800 seconds

I've searched 451 4.7.0 Temporary server error. Please try again later. PRX5, created host files, manually applied dns entries to the server dns lookups setting and changed the default front end receive connector scoping from any avil ip addy to a specific static ip, but no luck.

Hi,

we have migrated from 2003 Domain Controller to 2008 R2 and transferred all the roles new 2008 R2 Domain Controller we also have exchange 2010 CAS1/HUB1 & CAS2/HUB2 and Mailbox 1 and Mailbox 2 servers in the same LAN 

but after migration I removed the Network of old domain controller and I test the mail connectivity and mail flow internal email are fine but external going outside my organization stucks in the queue and doesn't go until I plugged back the old domain controller which currently ADC

Please someone help to resolve this issue I want all my mail flow to be fine with new migrated domain controller so that I can demote old DC

thanks 

Ehsan 

Hello everybody,

we are running exchange 2013 with cu1 wit 2 CAS (ex01 and ex02) and two MBX-Servers (ex03 and ex04). We are already in a call there with Microsoft. Anyway i'd like to describe the existing Problem here.

We have 4 Databases productive, that only deliver mail (any mails, with/without attachments) when being mounted on ex03.

As soon as they are mounted on ex04 mails with attachments from the outside and from the inside are not being delivered to users Mailboxes and stay in the queue with a '452 4.3.1 Insufficient system ressources' All disks have enough free space, no corresponding eventlog showing a problem because of throtteling. Mails without attachments run just fine.

In the message-tracking Log we see a 'recipientthreadlimitexceeded, intra-organization SMTP Send Connector'. With MS-Support, we tweaked the msexchangedelivery.exe.config with different values for

and Edgetransport.exe.config with

This did not resolve the issue.

We disabled the Anti-Malware-Agent in the Transport. There is Mcafee on the system (as is on the others) with proper exclusions (the others run just fine with that config)

We set tnef to false. I don't know if this caused the issue on the system, setting it back to true did not resolve the issue.

We have all the productive db's now running on ex03. When adding a new DB 'test' on ex04 and putting one test-mailbox on thar db we are able to reproduce the problem without Userimpact.

Well, anyone has an Idea? As i said, MS is right now analysing a trace. I'll keep this thread updated.

Regards

Michael

I got a lot of pending messages in my message trace, some with 1-2 Receive EVENTs but nothing further. Some with 1 Receive EVENT and then 1 DEFER EVENT with the DETAIL of "The last attempt to deliver the message encountered an error".

We are using on-premise exchange 2013 and our outbound connectors have Opportunistic TLS set from day 1. Most messages do get delivered fine and theres no common factor in what gets stuck in this state in terms of senders, attachments, subjects or anything else.

Any ideas?

I have an issue with sending mail via authenticated SMTP in a multi-server environment. My environment is as follows:

• 1x multi role server (hostname EX1)
• 2x mailbox server (hostnames MB1 and MB2)

All are running Exchange 2013. Now to begin, all three are very much in a default configuration, and all core functionality is working perfectly. I have no mailflow issues in or out from the client access server, and as long as one is only using typical exchange connections, every mailbox on every server works fine. Activesync accounts on phones etc. work fine, RPC over HTTPS connections in Outlook work fine. My only issues is a recently discovered one.

For the first time, one of our users has a need to be able to set up their accounts using IMAP and SMTP rather than as an Exchange account. Let's just take this as a given rather than preaching around alternates as I've been left with no option but to get this working.

One sets up an IMAP account in the typical way just fine. A single external DNS FQDN has been set up for our server which is used as both the IMAP server and the outgoing SMTP Server. The issue I experience is that when the mailbox that's being used to authenticate exists on EX1, the client access server, it can send fine. When that mailbox is moved to MB1 or MB2 or indeed if any other mailbox on MB1 or MB2 is used it can no longer send. In both instances the IMAP portion continues to function without issue and the account can receive mail, but cannot send.

When sending I have tried two alternatives:

• If I attempt to send with no authentication then, as I would expect, I receive an NDR stating that I am not allowed to relay.
• If I attempt to send with authentication on I receive password prompts and the sending account refuses to authenticate, even though I'm using known-good credentials, as all I have done is ticket the "use the same details for outgoing as for incoming" box with a working incoming connection as mentioned above

Now whilst my experience here is limited, for me the crux of this comes down to being able to authenticate for outgoing SMTP when the mailbox is on EX1, but NOT being able to authenticate for outgoing SMTP when the same mailbox is moved to MB1.

I'm guessing this is going to turn out to be something obvious, as it feels in my gut like it SHOULD be obvious, but I've been looking at it so long now that I just can't see it. I'm fairly certain from the above that the crux of the issue lies in authentication when the mailbox is on a mailbox server rather than a client access server, but any thoughts on a specific possible cause would be great!

Many thanks in advance.

I'm starting my migration from 2010 to 2013. The one caveat to my plan is that my 2010 CAS Array Certificate expires in September (used for OWA and ActiveSync). I thought I read somewhere that the 2013 CAS will ignore certificate errors on the 2010 CAS array when in proxy mode. Can I get confirmation on this? Otherwise I will have to request a new certificate. Thanks.

Problem routing mail;

I have an internal user with a secure email account. This account routes externally to a smart host via a separate send connector.  The problem I'm seeing is if the user sends email via their secure account to another user who is internal the recipient never receives the message and also if the same user sends to another secure email account in the same organisation they never receive the message either. When the message is sent to an external source the message is sent with no problem.

In message tracking I can see that the message goes external even though the user is internal and the address is accepted in Exchange.  The message seems to be looping but never delivered.

Any advice please...

Hi everyone,

I'm getting a requirements from the customer that they 'd like to have email approval process when using MS Exchange 2013. It means all emails from internal users to external users (outside domain) will be waited for approval from a manager before sending out.

I do research and see that Exchange 2013 has a feature namely "moderated recipient". However, we have to define list of recipients/ distribution group/ dynamic distribution group in advanced. This does not satisfy the requirement in this case.I'm

I'm new to Exchange so I'll be appreciate if someone can give me advices. Thank you so much.

Hello

I have set a receive connector to allow smtp connection from hosts/printer/devices in my lan and our ERP connected through VPN.

I have received complain by colleagues that SOMETIMES the messages sent by ERP doesn't starts

I have set verbose logging for this connector and I have checked the messages with problems and I see the connection, like this

2014-07-10T10:18:03.910Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,0,192.168.1.10:25,10.20.100.103:11421,+,,
2014-07-10T10:18:03.910Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,1,192.168.1.10:25,10.20.100.103:11421,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-07-10T10:18:03.910Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,2,192.168.1.10:25,10.20.100.103:11421,>,"220 MYSERVER.MYDOMAIN.COM Microsoft ESMTP MAIL Service ready at Thu, 10 Jul 2014 12:18:02 +0200",
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,3,192.168.1.10:25,10.20.100.103:11421,<,EHLO MYDOMAIN.COM,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,4,192.168.1.10:25,10.20.100.103:11421,>,250-MYSERVER.MYDOMAIN.COM Hello [10.20.100.103],
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,5,192.168.1.10:25,10.20.100.103:11421,>,250-SIZE 36700160,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,6,192.168.1.10:25,10.20.100.103:11421,>,250-PIPELINING,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,7,192.168.1.10:25,10.20.100.103:11421,>,250-DSN,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,8,192.168.1.10:25,10.20.100.103:11421,>,250-ENHANCEDSTATUSCODES,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,9,192.168.1.10:25,10.20.100.103:11421,>,250-AUTH,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,10,192.168.1.10:25,10.20.100.103:11421,>,250-8BITMIME,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,11,192.168.1.10:25,10.20.100.103:11421,>,250-BINARYMIME,
2014-07-10T10:18:03.930Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,12,192.168.1.10:25,10.20.100.103:11421,>,250 CHUNKING,
2014-07-10T10:18:03.950Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,13,192.168.1.10:25,10.20.100.103:11421,<,MAIL FROM:<MY.SENDER@MYDOMAIN.COM> ENVID=F04DA23DB7F11EE482836E540E7E14B4,
2014-07-10T10:18:03.951Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,14,192.168.1.10:25,10.20.100.103:11421,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-07-10T10:18:03.951Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,15,192.168.1.10:25,10.20.100.103:11421,*,08D14D1483BAF781;2014-07-10T10:18:03.910Z;1,receiving message
2014-07-10T10:18:03.951Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,16,192.168.1.10:25,10.20.100.103:11421,>,250 2.1.0 Sender OK,
2014-07-10T10:18:03.971Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,17,192.168.1.10:25,10.20.100.103:11421,<,RCPT TO:<MY.RECIPIENT@MYDOMAIN.COM> NOTIFY=FAILURE ORCPT=rfc822;MY.RECIPIENT@MYDOMAIN.COM,
2014-07-10T10:18:03.971Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,18,192.168.1.10:25,10.20.100.103:11421,>,250 2.1.5 Recipient OK,
...
2014-07-10T10:18:04.052Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,25,192.168.1.10:25,10.20.100.103:11421,<,DATA,
2014-07-10T10:18:04.052Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,26,192.168.1.10:25,10.20.100.103:11421,>,354 Start mail input; end with <CRLF>.<CRLF>,
2014-07-10T10:18:04.109Z,MYSERVER\MYCONNECTOR,08D14D1483BAF781,27,192.168.1.10:25,10.20.100.103:11421,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
2014-07-10T10:18:05.585Z,MYSERVER\Default Frontend MYSERVER,08D14D1483BAF783,0,10.1.1.5:25,10.254.2.15:1052,+,, 

.

We recently migrated to a new AD domain with a new Exchange 2013 box.  Prior to that we were on Exchange 2007 in a different domain.  We use postini for our spam/virus filtering. 

Since we've moved to the Exchange 2013 solution, we have started having issues with some (not all) Google apps hosted domains.  The firewall and IP of the server stayed the same regardless of the change.  I looked into routing all of our outbound mail (or just specific domains) through Postini to help with this issue, but their instructions work for 2007 and 2010 - not 2013.  I tried setting it up with their directions, but modifying it for 2013, but that was a big failure.  We are seeing message delayed codes returned.

Remote Server returned '400 4.4.7 Message delayed'

I did some research through Google Apps, but the only thing I found is a server reboot, which does nothing.

I have it working right now by routing everything for these Google Apps hosted domains by creating a separate send connector that routes through smtp.google.com as a smart host (using a gmail ID and password) but that's only going to work for so many messages before it bombs, and we won't even get a notification.

Any suggestions?

Hello,

I am running Exchange Server 2013 CU5, and the receive connector keeps timing out. The problem only exists after the server has been running for somewhere between 2 to 3 hours. After reboot all will work for the 2 to 3 hours and then we stop getting emails. If I run the Microsoft Connectivity test it returns error code 1, time out error, reboot the server and all is fine again for a while. I have tried deleting the receive connector & re-creating it as both a Hub connector and a frontend connector and it makes no difference. The fault originally occurred why I was running Exchange server 2013 Std, I they upgraded to SP1 then to CU5 in an effort to resolve the issue, but this did not work. Any suggestions would be welcome as I have no idea on what to try next.

Thanks

Curly