I have an on-premise setup consisting of two 2013 Exchange Servers in a clustered DAG.

Recently a sister organization has requested to be able to send mail to us from their mail server, and also have our users be able to email their users back to their mail server.

IMPORTANT - We are in an INTRANET configuration, with direct access between our sites and no INTERNET connectivity. Both sites have their own Domain and their own Mail Servers.

On our domain, our mail domain is the same as our domain name:

Domain name = mydomain.com

Example mailbox = user1@mydomain.com

For our sister domain:

Domain Name = theirdomain.com

Example mailbox = user1@weloveemail.com

I am attempting to set up a Send Connector on our side so that our users can email our sister organization, and the emails keep getting stuck in the queue: "A matching connector cannot be found to route the external recipient"

What I have done:

- Set up an Accepted Domain for "theirdomain.com"

- Set up a Send Connector for *.theirdomain.com

- Restarted Exchange services, as well as Restarted the servers completely

Additional Info - we have a conditional forwarder to our sister domain - "theirdomain.com". I can ping their mailserver mail.theirdomain.com just fine.

What I have also tried:

- Set up an Accepted Domain for "theirdomain.com"

- Set up a Send Connector for *.weloveemail.com

- Restarted Exchange services, as well as Restarted the servers completely

Any help/advice is greatly appreciated! I have looked up multiple articles online including Practical365, etc.

Hi,
We've got unwanted experience with Exchange 2013 mailbox junk e-mail configuration. We've setup an account junk filter settings, that accept e-mails only from senders from safe senders list, with command: 

Set-MailboxJunkEmailConfiguration -Identity "Our Mailbox" -TrustedListsOnly $True -TrustedSendersAndDomains $ListOfEmails

Generally it works fine - if e-mail is sent by sender who is not on the list, that e-mail goes directly to junk e-mails folder. But there is one strange exception - if sender who is not on the list add e-mail address that is on the safe senders list as CC, that e-mail will be accepted and placed in Inbox folder. 

Is there any option or fix to change that behaviour?

Thanks fof help.

I set up a new environment with Exchanger server 2013. I have pass Microsoft Remote Connectivity Analyzer Inbound and Outbound SMTP tests. I can normally receive inbound email. But I cannot successfully send outbound email to any other domain. No matter I sent to gmail.com or outlook.com addresses, I always receive the samebounce back messages. Can anyone help me?

Received: from EX800.cpa-lab.internal (10.231.17.145) by
 EX800.cpa-lab.internal (10.231.17.145) with Microsoft SMTP Server (TLS) id
 15.0.1263.5; Wed, 17 Oct 2018 14:04:14 -0700
Received: from EX800.cpa-lab.internal ([::1]) by EX800.cpa-lab.internal
 ([fe80::75de:598a:55a7:ba2a%15]) with mapi id 15.00.1263.000; Wed, 17 Oct
 2018 14:04:14 -0700
From: Ade Ade <Ade.Ade@ParkingLab.com>
To: "liuzhiyong_1982@outlook.com" <liuzhiyong_1982@outlook.com>
Subject: test
Thread-Topic: test
Thread-Index: AQHUZlz1z46Pv9aibEmbHSxzGHxPIQ==
Date: Wed, 17 Oct 2018 21:04:14 +0000
Message-ID: <1645d88c0abb4ab98496f1f9382b63a8@EX800.cpa-lab.internal>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [::1]
Content-Type: multipart/alternative;
 boundary="_000_1645d88c0abb4ab98496f1f9382b63a8EX800cpalabinternal_"
MIME-Version: 1.0

Stonecold31666

Ive checked header on multipledevices and all show a delay when relaying via on prem.

Not sure what could be causing this, server was working fine doe years then a few weeks ago this started.

what can I check that could be causing this delay?

Hi All,

This is my first post to ms exchange forum am getting  Log onto incoming mail server (POP3): Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance. in my outlook clients, till last Sunday (12.04.15) my exchange was well & good, Monday morning suddenly the problem started like none of our outlook pop3 clients are able to communicate with exchange (rest  IMAP, SMTP & Exchange accounts are working fine). i have tried with all port no but no luck. please help me to get raid of this one.

Exchange 2013 CU6 with server 2012 Std 64Bit

Thanks,

Murali 

We are facing Multiple issues with our Exchange Server 2013.

1. Every Morning we get the alerts for Database Exchange Database 2013 - edge transport Goes Down & emails stops working for a while

2. Microsoft Exchange Information Store Service goes down daily

3. Recently we have updated the Certificate from Self Signed to SSL Cert from Comodo. It stopped suddenly on all the Phones & then we had to reconfigure the emails on all the Phones which was a high Inconvenience for the users

4. The server has logs saying the low space available on the logical disk: It is indicating 95 MB available on System Reserved Space. Is it concerning?

5. We got Multiple logs similar to 

Process w3wp.exe (EWS) (PID=5004). The budget for user 'Sid~S-XXXX~Ews~false~MacOutlook/14.6.6.160626 (Intel Mac OS X 10.9.5)' is locked out until 24.04.2017 06:25:44.  Max Burst: 300000, Recharge Rate: 1800000, CutoffBalance: 0

This was specifically generated for Mobile users & their emails were not working on the phone during this time.

Please suggest here to get a better resolution & uninterrupted Email services.

I have some issues with mail delays when mails are being sent down from Office 365 to On-Prem Exchange Server. However referring to my previous post in this link, it appears that the issue is from the exchange and was asked to post this question here. 

Could anyone assist me on this matter?

Many thanks.

After changing our public IP we are having problem relaying to one of our domains. Our on-prem exchangeserver (used only for relay) get the following error in the message queue.  

"Last Error: 451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (AS77713200) [HE1EUR04FT016.eop-eur04.prod.protection.outlook.com]". 

It's a scanner that have worked fine prior to the change of public IP change but now all mails from this scanner now gets stuck at  our on-prem Exchange server. Outlook klients have no problem and scanners that send mail to our other domains.

- We have updated our SPF records for all domains.

- Tried to create a IP whitelisting in O365 when sending from the relayserver. 

Regards, 

Magnus

Hi,

We are running a hybrid of Exchange 2013 and Office 365.

We have just added a new domain to our emails, I did this on our local Exchange Server, and then ran the hybrid config tool to push the new domain over to office 365, also added the domain to office 365 and verified it.

Emails are flowing fine on the new domain, and users have the domain as an email address.

Local Distribution groups also have the new domain attached, and are working.

But... the distribution groups that exist only in Office 365, do not have the new domain attached.
If I went to create a new group there is an option to create with the new domain..

But, I cannot figure out how to add the new domain to the exisiting groups.

I have run this command on an Office 365 connected powershell:

Set-EmailAddressPolicy -identity "Default Policy" -EnabledEmailAddressTemplates "smtp:..."

But it just returns: You are not authorized to perform this operation on e-mail address policy "Default Policy"

and I am connecting using Office 365 Global Administrator account.

Does anyone have any ideas how to add the new domain to the exisiting groups, without manually updating all the groups.

Thanks,

Tim Jeens

Hey Guys,

since we upgraded from Exchange 2010 to Exchange 2013 (SP1) any SMTP Receive Connector we create (including the default one) show the same strange behavior. When you send an email (no matter if internal or external) it sometimes takes up to 30 seconds for the exchange server to acknowledge the message. Using the SMTP log I see the following entries:

2014-08-08T08:58:29.053Z,                       MAIL FROM:<test@test.de>,

2014-08-08T08:58:29.053Z,                       SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2014-08-08T08:58:29.053Z,                       receiving message

2014-08-08T08:58:29.053Z,                       250 2.1.0 Sender OK,

2014-08-08T08:58:29.053Z,                       RCPT TO:<fake@mail.de>,

2014-08-08T08:58:29.053Z,                       250 2.1.5 Recipient OK,

2014-08-08T08:58:29.053Z,                       DATA,

2014-08-08T08:58:29.053Z,                       354 Start mail input; end with <CRLF>.<CRLF>,

2014-08-08T08:58:29.068Z,                       Proxy destination(s) obtained from OnProxyInboundMessage event

2014-08-08T08:58:40.960Z,                       "250 2.6.0 <5160cd2a-9160-4a35-9007-1f9c17761bc0@--------> [InternalId=17776869639170, Hostname=-----------] Queued mail for delivery",

As you can see there’s a delay between 08:58:29 and 08:58:40 where nothing happens. The sending smtp service waits for the server to acknowledge the message – at least that’s what I guess. Since we use this kind of connector a lot for internal mail traffic with non-Outlook clients it is essential to get rid of this issue. For example using Trac Ticket system or Subversion also leads to slow or delayed responses. Creating a ticket in Trac sometimes takes up to a Minute since several emails are created and sent in background processes. We didn’t have this issue with Exchange 2010 and I actually couldn’t find much using google. 

Since there's no error showing it's quite difficult to track down the issue. After I did some researching I tried configuring the receive connector to change this behavior but nothing helped. I tested the following options:

-         MaxAcknowledgementDelay 00:00:00

-         TarpitInterval 00:00:00

-         MessageRateSource None

-         MessageRateLimit unlimited

-         MaxInboundConnectionPercentagePerSource: 20

-         MaxInboundConnectionPerSource 100

 I Also took a look at the Throttling Policies with no luck either. 

Calling the Microsoft support simply led to the typical “we do not support 3^rd party issues”. In fact this is NOT a third party issue but arguing didn't help. I tested every possible solution I found and after weeks I simply dont' have the slightest idea any more, how to solve the problem.

Some information about our Exchange environment:

-         Exchange DAG with 2 servers

-         Windows Server 2012 (latest updates)

-         Exchange 2013 SP1 installed

Disabling DAG members also didn’t help and all the members show the same behavior no matter which connector I choose to use.  

Any hint or idea would be very much appreciated.

Thanks,

Christoph

Hello All,

I have Exchange Servers 2013 CU 13 in my environment and I have created a new website in the IIS to create new owa, ecp virtual directories to user login from internal and external networks. I am planning to upgrade to the Latest CU. As we all know that the new CU upgrade means installation of exchange from scratch. In my case do I have to re-create the new website again after I upgrade to the new CU or will the new website (owa and ecp virtual directories) be available even after the CU upgrade.

Hi,

Greeting all

I want to restrict few mailboxes emails cannot be reply back reply all and forward others, for eg.

user1.abc@abc.com sends email to all organization. others employee cannot reply to him, reply all and forward that email to anyone. I achive this using ADRMS but want to find out from Exchange Transport Rule as well. any guidance will be appreciated. Thank You.

Hi,

We have a hybrid set up of Exchange 2010 and Office 365. If this is not the correct place to post this, please move to the necessary place.

We have added a new domain(domain5.com) in Office 365. We have the same domain in On Premise Exchange also. We have then migrated an on premise Exchange user abc@domain5.com to Office 365. This migrated user can send mails to on premise Exchange. But the reply will not reach Office 365. Exchange on premise users cannot send any mail to this migrated user also.

The mail when tracked reaching one of the on premise hub cas server and staying there.

The migrated user can send and receive mails to other Office 365 users and also other external domains.

Please let me know the steps to resolve this issue.

Hi,

Currently I'm setup my Send Connector to using smtp.gmail.com as Smart Host with a Google Account for Basic Authentication. The problem is the delivered message replace the original sender (my organization domain) with the google account (@gmail.com), how to make the message used the original sender?

Thanks in advance.

Hi Team,

We have an in house application server which is integrated with our exchange 2013 server, we have added the IP of  the application server on receive connector to send emails , recently for some maintenance work we had to restart the Microsoft exchange transport service couple of times on the mailbox server where the receive connector is created.

After restarting the service we have found lot of duplicate emails are being generated, not sure if it is because of the exchange server or the application,i feel its because of the exchange server as we paused and restarted the transport service couple of times after which this issue started.

Regards

ITfolk

TechGUy,System Administrator.

Hi All,

i am suffering some issues in Exchange 2013, one is that we enabled BlankSenderBlocking but some logs in SMTPSend can still be found, like below,

2018-10-16T06:57:17.751Z,internet,08D633031798F54E,0,,104.47.44.33:25,*,,attempting to connect
2018-10-16T06:57:17.938Z,internet,08D633031798F54E,1,192.168.1.249:16299,104.47.44.33:25,+,,
2018-10-16T06:57:18.141Z,internet,08D633031798F54E,2,192.168.1.249:16299,104.47.44.33:25,<,"220 SN1NAM04FT027.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Tue, 16 Oct 2018 06:57:17 +0000",
2018-10-16T06:57:18.141Z,internet,08D633031798F54E,3,192.168.1.249:16299,104.47.44.33:25,>,EHLO XXXX,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,4,192.168.1.249:16299,104.47.44.33:25,<,250-SN1NAM04FT027.mail.protection.outlook.com Hello [XXXX],
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,5,192.168.1.249:16299,104.47.44.33:25,<,250-SIZE 49283072,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,6,192.168.1.249:16299,104.47.44.33:25,<,250-PIPELINING,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,7,192.168.1.249:16299,104.47.44.33:25,<,250-DSN,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,8,192.168.1.249:16299,104.47.44.33:25,<,250-ENHANCEDSTATUSCODES,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,9,192.168.1.249:16299,104.47.44.33:25,<,250-STARTTLS,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,10,192.168.1.249:16299,104.47.44.33:25,<,250-8BITMIME,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,11,192.168.1.249:16299,104.47.44.33:25,<,250-BINARYMIME,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,12,192.168.1.249:16299,104.47.44.33:25,<,250-CHUNKING,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,13,192.168.1.249:16299,104.47.44.33:25,<,250 SMTPUTF8,
2018-10-16T06:57:18.329Z,internet,08D633031798F54E,14,192.168.1.249:16299,104.47.44.33:25,>,STARTTLS,
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,15,192.168.1.249:16299,104.47.44.33:25,<,220 2.0.0 SMTP server ready,
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,16,192.168.1.249:16299,104.47.44.33:25,*,,Sending certificate
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,17,192.168.1.249:16299,104.47.44.33:25,*,"XXXX",Certificate subject
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,18,192.168.1.249:16299,104.47.44.33:25,*,"XXXX",Certificate issuer name
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,19,192.168.1.249:16299,104.47.44.33:25,*,18000000073AE206A4A4035CFF000000000007,Certificate serial number
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,20,192.168.1.249:16299,104.47.44.33:25,*,B4C98EBE5B8711B4CF1C2E376B4513B343F8ED22,Certificate thumbprint
2018-10-16T06:57:18.517Z,internet,08D633031798F54E,21,192.168.1.249:16299,104.47.44.33:25,*,XXXX;AutoDiscover.GZ-SPI.COM;CH1;GZ-SPI.COM;58.63.56.194;192.168.1.245;MB;owa.gz-spi.com,Certificate alternate names
2018-10-16T06:57:18.923Z,internet,08D633031798F54E,22,192.168.1.249:16299,104.47.44.33:25,*,,Received certificate
2018-10-16T06:57:18.923Z,internet,08D633031798F54E,23,192.168.1.249:16299,104.47.44.33:25,*,73B89750FA406F7D4F7E43A9355A9D271079E938,Certificate thumbprint
2018-10-16T06:57:18.923Z,internet,08D633031798F54E,24,192.168.1.249:16299,104.47.44.33:25,>,EHLO XXXX,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,25,192.168.1.249:16299,104.47.44.33:25,<,250-SN1NAM04FT027.mail.protection.outlook.com Hello [XXXX],
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,26,192.168.1.249:16299,104.47.44.33:25,<,250-SIZE 49283072,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,27,192.168.1.249:16299,104.47.44.33:25,<,250-PIPELINING,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,28,192.168.1.249:16299,104.47.44.33:25,<,250-DSN,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,29,192.168.1.249:16299,104.47.44.33:25,<,250-ENHANCEDSTATUSCODES,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,30,192.168.1.249:16299,104.47.44.33:25,<,250-8BITMIME,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,31,192.168.1.249:16299,104.47.44.33:25,<,250-BINARYMIME,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,32,192.168.1.249:16299,104.47.44.33:25,<,250-CHUNKING,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,33,192.168.1.249:16299,104.47.44.33:25,<,250 SMTPUTF8,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,34,192.168.1.249:16299,104.47.44.33:25,*,,sending message with RecordId 121869697024043 and InternetMessageId <XXXX>
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,35,192.168.1.249:16299,104.47.44.33:25,>,MAIL FROM:<> SIZE=11709,
2018-10-16T06:57:22.954Z,internet,08D633031798F54E,36,192.168.1.249:16299,104.47.44.33:25,>,RCPT TO:<XXXX>,
2018-10-16T06:57:23.189Z,internet,08D633031798F54E,37,192.168.1.249:16299,104.47.44.33:25,<,250 2.1.0 Sender OK,
2018-10-16T06:57:23.189Z,internet,08D633031798F54E,38,192.168.1.249:16299,104.47.44.33:25,<,250 2.1.5 Recipient OK,
2018-10-16T06:57:23.189Z,internet,08D633031798F54E,39,192.168.1.249:16299,104.47.44.33:25,>,BDAT 6715 LAST,
2018-10-16T06:57:25.220Z,internet,08D633031798F54E,40,192.168.1.249:16299,104.47.44.33:25,<,"250 2.6.0 <XXXX> [InternalId=14401025411291, Hostname=SN1NAM04HT164.eop-NAM04.prod.protection.outlook.com] 12325 bytes in 0.142, 84.476 KB/sec Queued mail for delivery",
2018-10-16T06:57:25.220Z,internet,08D633031798F54E,41,192.168.1.249:16299,104.47.44.33:25,>,QUIT,
2018-10-16T06:57:25.423Z,internet,08D633031798F54E,42,192.168.1.249:16299,104.47.44.33:25,<,221 2.0.0 Service closing transmission channel,
2018-10-16T06:57:25.423Z,internet,08D633031798F54E,43,192.168.1.249:16299,104.47.44.33:25,-,,Local

checked in EMS as below result,

[PS] C:\Windows\system32>Get-TransportConfig | Format-List InternalSMTPServers
InternalSMTPServers : {192.168.1.245, 192.168.1.249}

[PS] C:\Windows\system32>Get-SenderFilterConfig | Format-List Enabled
Enabled : True

[PS] C:\Windows\system32>Get-SenderFilterConfig | Format-List BlankSenderBlockingEnabled
BlankSenderBlockingEnabled : True

could anyone help on this? Thanks.

Best Regards,

Liang Zhihua

When a customer from one company tries to email us, the email is not delivered and the customer eventually gets an NDR that shows the email failed with the following:

Status: 4.4.7
X-Supplementary-Info: < #4.4.7 SMTP; 403 4.7.0 encryption too weak 0 less than
 128>

The customer is saying that our mail server is the problem.  Our mail server is a Windows SBS 2011 server with Exchange 2010 w/SP3, rollup 22

What do I need to do to receive these emails?

Thanks,

Dale

Dale

Greettins

IE:

3 MBX-CAS Exchange 2013

2 Edge servers Exchange 2013

No Edge Sync configured

Issue:

One of the MBX server had storage issue and the frontend transport service stoped. 

The send-connector, on the Edge servers (Edge --> MBX direction), has the 3 MBX servers on smarthost and smarthosstring setting

The queue on the Edge servers for the MBX servers start to increase, and the messages weren't sent to any MBX server.

The fact of this MBX server is the first one on the smarthost setting of the send-connector is the reason for the messages won't delivered for the other MBX servers?

I tried to find any explanation this situation, but I couldn't find it

Can you help me?

thank you in advance