This is Exchnage 2016 deployment. For some reason out IP has been in banned sending IP lists.

We've tried the O365 Anti-Spam IP Delist Portal.  We first tried this around 5 hours ago.  At which point we were told that in about 30 minutes the IP address would be delisted.  However,  the problem continued,  so we've tried again (and again etc).  Now when we try to delist we get a message saying "The request to delist IP address XXX has been denied and we have escalated your request to Microsoft support.  However, there's no information on turnaround time or how to contact the correct Support team.

This issue is huge for us - we are unable to contact numerous clients and candidates until it's resolved.

We aren't currently Office 365 customers (though we are considering this as a solution). we are right now using Microsoft Exchnage 2016. Is there any other way we can expedite unblocking our IP address.

Hello,

I'm kind of stump here. We're getting, on average an 18 second delay when an internet forum is trying to send an email through the Exchange 2013 server. It happens once awhile but it seems to happen when someone is emailing a new address or an existing address after a few mins. It works fine after you send the initial email and it'll send it under 1 second. We're not experiencing this on our 2010 box.

We direct IP on the forum to the load balancer and one directly to either exchange 2013 box with the same delay.

Here's what we have setup with 2013.
2 server 2012R2
Load Balancer
Internet Forum

This is what we have on our exchange 2010 box:
Server 2008 R2
Internet Forum

Let say that I sent an email from the forum to Server A. I've looked through the log and it's sending through Server B. It's like the message is lost on Server A and vice versa. Same thing happen when I point the forum directly to the load balancer. I've attached the log below. But it works fine after that until someone puts a new address in or wait about a minute. 

What else should I check? I was thinking about turning off Shadow redunanecy and see if that had any effect but I think it would affect all the test emails that I've been sending.

2017-01-06T20:27:43.039Z,Inbound Proxy Internal Send Connector,08D4366966CE018E,58,192.168.1.1:13117,192.168.1.1:2525,*,,Connection being removed from Cache. Reason : Expired
2017-01-06T20:27:43.039Z,Inbound Proxy Internal Send Connector,08D4366966CE018E,59,192.168.1.1:13117,192.168.1.1:2525,>,QUIT,
2017-01-06T20:27:43.039Z,Inbound Proxy Internal Send Connector,08D4366966CE018E,60,192.168.1.1:13117,192.168.1.1:2525,-,,Remote
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,0,,192.168.1.2:2525,*,,attempting to connect
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,1,192.168.1.1:14667,192.168.1.2:2525,+,,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,2,192.168.1.1:14667,192.168.1.2:2525,<,"220 EXCH13B.domain.corp Microsoft ESMTP MAIL Service ready at Fri, 6 Jan 2017 14:34:30 -0600",
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,3,192.168.1.1:14667,192.168.1.2:2525,*,,Proxying inbound session with session id 08D4366966CE01EC
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,4,192.168.1.1:14667,192.168.1.2:2525,>,EHLO EXCH13A.domain.corp,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,5,192.168.1.1:14667,192.168.1.2:2525,<,250-EXCH13B.domain.corp Hello [x.x.x.x],
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,6,192.168.1.1:14667,192.168.1.2:2525,<,250-SIZE,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,7,192.168.1.1:14667,192.168.1.2:2525,<,250-PIPELINING,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,8,192.168.1.1:14667,192.168.1.2:2525,<,250-DSN,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,9,192.168.1.1:14667,192.168.1.2:2525,<,250-ENHANCEDSTATUSCODES,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,10,192.168.1.1:14667,192.168.1.2:2525,<,250-STARTTLS,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,11,192.168.1.1:14667,192.168.1.2:2525,<,250-X-ANONYMOUSTLS,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,12,192.168.1.1:14667,192.168.1.2:2525,<,250-AUTH NTLM,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,13,192.168.1.1:14667,192.168.1.2:2525,<,250-X-EXPS GSSAPI NTLM,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,14,192.168.1.1:14667,192.168.1.2:2525,<,250-8BITMIME,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,15,192.168.1.1:14667,192.168.1.2:2525,<,250-BINARYMIME,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,16,192.168.1.1:14667,192.168.1.2:2525,<,250-CHUNKING,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,17,192.168.1.1:14667,192.168.1.2:2525,<,250-XEXCH50,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,18,192.168.1.1:14667,192.168.1.2:2525,<,250-XRDST,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,19,192.168.1.1:14667,192.168.1.2:2525,<,250 XSHADOWREQUEST,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,20,192.168.1.1:14667,192.168.1.2:2525,>,X-ANONYMOUSTLS,
2017-01-06T20:34:30.560Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,21,192.168.1.1:14667,192.168.1.2:2525,<,220 2.0.0 SMTP server ready,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,22,192.168.1.1:14667,192.168.1.2:2525,*,,Received certificate
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,23,192.168.1.1:14667,192.168.1.2:2525,*,69A3091DF5713C8A914218F1EC7E03F9A0DAA210,Certificate thumbprint
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,24,192.168.1.1:14667,192.168.1.2:2525,>,EHLO EXCH13A.domain.corp,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,25,192.168.1.1:14667,192.168.1.2:2525,<,250-EXCH13B.domain.corp Hello [x.x.x.x],
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,26,192.168.1.1:14667,192.168.1.2:2525,<,250-SIZE,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,27,192.168.1.1:14667,192.168.1.2:2525,<,250-PIPELINING,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,28,192.168.1.1:14667,192.168.1.2:2525,<,250-DSN,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,29,192.168.1.1:14667,192.168.1.2:2525,<,250-ENHANCEDSTATUSCODES,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,30,192.168.1.1:14667,192.168.1.2:2525,<,250-AUTH NTLM LOGIN,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,31,192.168.1.1:14667,192.168.1.2:2525,<,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,32,192.168.1.1:14667,192.168.1.2:2525,<,250-X-EXCHANGEAUTH SHA256,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,33,192.168.1.1:14667,192.168.1.2:2525,<,250-8BITMIME,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,34,192.168.1.1:14667,192.168.1.2:2525,<,250-BINARYMIME,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,35,192.168.1.1:14667,192.168.1.2:2525,<,250-CHUNKING,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,36,192.168.1.1:14667,192.168.1.2:2525,<,250-XEXCH50,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,37,192.168.1.1:14667,192.168.1.2:2525,<,250-XRDST,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,38,192.168.1.1:14667,192.168.1.2:2525,<,250-XSHADOWREQUEST,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,39,192.168.1.1:14667,192.168.1.2:2525,<,250-XPROXY,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,40,192.168.1.1:14667,192.168.1.2:2525,<,250-XPROXYFROM,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,41,192.168.1.1:14667,192.168.1.2:2525,<,250-X-MESSAGECONTEXT ADRC-2.1.0.0 EPROP-1.2.0.0,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,42,192.168.1.1:14667,192.168.1.2:2525,<,250-XSYSPROBE,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,43,192.168.1.1:14667,192.168.1.2:2525,<,250 XORIGFROM,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,44,192.168.1.1:14667,192.168.1.2:2525,>,X-EXPS EXCHANGEAUTH SHA256 ,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,45,192.168.1.1:14667,192.168.1.2:2525,>,<Binary Data>,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,46,192.168.1.1:14667,192.168.1.2:2525,<,235 <authentication information>,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,47,192.168.1.1:14667,192.168.1.2:2525,*,SMTPSendEXCH50 SendRoutingHeaders SendForestHeaders SendOrganizationHeaders SMTPSendXShadow,Set Session Permissions
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,48,192.168.1.1:14667,192.168.1.2:2525,>,XPROXYFROM SID=08D4366966CE01EC IP=x.x.x.x PORT=50816 DOMAIN=PPDINTRANET SEQNUM=1 PERMS=1073 AUTHSRC=Anonymous,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,49,192.168.1.1:14667,192.168.1.2:2525,<,250 XProxyFrom accepted,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,50,192.168.1.1:14667,192.168.1.2:2525,*,,sending message with RecordId 0 and InternetMessageId <F201A9CB8FF047D782559618350BBBE7@domain.corp>
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,51,192.168.1.1:14667,192.168.1.2:2525,>,MAIL FROM:<intranet@domain.com> SIZE=0 AUTH=<>,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,52,192.168.1.1:14667,192.168.1.2:2525,>,RCPT TO:<c@domain.com>,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,53,192.168.1.1:14667,192.168.1.2:2525,>,RCPT TO:<website@domain.com>,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,54,192.168.1.1:14667,192.168.1.2:2525,<,250 2.1.0 Sender OK,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,55,192.168.1.1:14667,192.168.1.2:2525,<,250 2.1.5 Recipient OK,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,56,192.168.1.1:14667,192.168.1.2:2525,<,250 2.1.5 Recipient OK,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,57,192.168.1.1:14667,192.168.1.2:2525,>,DATA,
2017-01-06T20:34:30.575Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,58,192.168.1.1:14667,192.168.1.2:2525,<,354 Start mail input; end with <CRLF>.<CRLF>,
2017-01-06T20:34:30.857Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,59,192.168.1.1:14667,192.168.1.2:2525,<,"250 2.6.0 <F201A9CB8FF047D782559618350BBBE7@domain.corp> [InternalId=2572685410332, Hostname=EXCH13B.domain.corp] Queued mail for delivery",
2017-01-06T20:34:30.857Z,Inbound Proxy Internal Send Connector,08D4366966CE01ED,60,192.168.1.1:14667,192.168.1.2:2525,*,,successfully added connection to cache. Current cache size is 1

Hello Folks, 

Having a very strange issue , We have a Cognos Application server (IBM Cognos) through which user used to send an email in bulk with excel attachements so what is happening like there are 10 users so mail is reaching to 8 only not to 2 and then again when application is sending an email then again some other are getting dropped its random not the same everytime. We check the logs / message trace but did not find any issues. and through application they are getting below errors . Its not only external users internal as well. Any pointers and another logs do we need to check..

CNC-SDS-0335 Error returned from SMTP Server. The error message was: [Exception reading response]. The message could not be sent.
CNC-SDS-0335 Error returned from SMTP Server. The error message was: [Connection reset]. The message could not be sent.
CNC-SDS-0335 Error returned from SMTP Server. The error message was: [[EOF]]. The message could not be sent.
CNC-SDS-0410 The email message was not sent . Approximate message size . The mail server returned this error [[EOF]].

IBM is straight forward is saying that Error is related to SMTP so you need to check SMTP server only

I'm running a Hybrid Exchange 2010 / Office 365 environment and am in the process of migrating our users from on-premise to O365.

On my premise Exchange 2010 server, I have some specific Send Connectors setup between my domain and partner domains.

If a mailbox <g class="gr_ gr_17 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="17" id="17">on premise</g> sends to this domain (defined in Send Connector) the message delivers fine. If the mailbox is on O365, the message fails to send with error "#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##" I have added the SPF entries for protection.outlook.com to our public records, and that has populated out, however, the error remains.

The messages are making it from O365 to my premise Exchange, and it is my premise Exchange that is rejecting the message instead of sending it through the connector.

I've already worked with and MSFT in the O365 group. He was unable to help and suggested I try this group instead.

Dears,

Ihave the two Microsoft Server 2012 Data Center with HyperV roles install on both, and the Two nodes servers configure as Fail-over cluster "Share Storage" , and I create two VMs "one per Node and install Exchange server 2016 on both.

My Question is, How to deploy DAG between two of Exchange server 2016 ?

Regards,

Hi....

We are using MS Exchange Server 2013  on MS Windows Server 2012 Standard. 

In queue viewer, I am getting this error for gmail.com ( 451 4.4.0 DNS Query Failed.......)

And if we look at the message , we got the following error(400 4.4.7 Message Delayed) :

It happens only in gmail.com. 

Can someone please help to fix this..?

Thanks in Advance..

Regards,

Hilda

In smtp Logs (frontend) on our mail server i saw that :

2016-12-14T20:20:09.291Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,128,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,>,MAIL FROM:<sender@sender.com> SIZE=0 AUTH=<>,

2016-12-14T20:20:09.291Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,129,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,>,RCPT TO:<recipient@mycompany.com>,

2016-12-14T20:20:09.307Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,130,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,<,250 2.1.0 Sender OK,

2016-12-14T20:20:09.307Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,131,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,<,250 2.1.5 Recipient OK,

2016-12-14T20:20:09.307Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,132,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,>,DATA,

2016-12-14T20:20:09.307Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,133,@IPMYEXSERVER:46772,@IPMYEXSERVER:2525,<,354 Start mail input; end with <CRLF>.<CRLF>,

2016-12-14T20:20:26.916Z,Inbound Proxy Internal Send Connector,08D4080A26D0D42B,134,@IPMYEXSERVER46772,@IPMYEXSERVER:2525,<,550 5.7.1 Sender ID (PRA) Not Permitted,

Any idea to fix that?

Thanks

Hi people.

We have a problem after update Exchange with CU15.  We should update to federate some domains against Office365.  After the update, no server could send alerts or some applications mails.

We make a Receive Connector, Frontend type, with anonymous user validation, but doesn't work.

Somebody knows about connector changes in the Cumulative Update for Exchange 2013?

Thanks a lot!

Eduardo 

Dear Exchange-experts,

I can't send to other domains than mine domain, and I also don't recieve e-mails from other domains. My DNS records are correct. My ISP blocks port 25 by default so I obtained to use now port 2525 for smtp. 

What can I do?

Kind regards,
Ruben

Hi!

Our Exchange 2013 Server trying to send messages to a domain but in the queue viewer it says "Last Error: 454 4.7.1 Relay Access Denied". We are not trying to relay anything through their email system. We are just replying to their emails but stays in our exchange queue. We used our ISP E-Mail Server as a smarthost and it worked but now it is also not working. We are using DNS Resolution in our Exchange with send connector.

Any Suggestions?

Dear all,

I have a exchange 2013, all emails are stuck in the draft in OWA and it didn't sent

also in the queue all emails didn't go through

transport log shows the following

failed to connect, Winsock error code, 10061, win32 error code 10061

any help?

Mohamed Azoz

testing EXCHANGE 2016 DEV

example:

Identity: EX1\29075\6682969112595
Subject: Undeliverable: Check Worrying Off Your List. Start the New Year Right With Term Life.
Internet Message ID: <dd7874ca-23af-4f9b-a5ff-1ad86613c862@EX1.DOMAIN.LOCAL>
From Address: <>
Status: Ready
Size (KB): 14
Message Source Name: DSN
Source IP: 255.255.255.255
SCL: -1
Date Received: 1/8/2017 4:10:56 PM
Expiration Time: 1/10/2017 4:10:56 PM
Last Error: 400 4.4.7 Message delayed
Queue ID: EX1\29075
Recipients:  Haven_Life_Teamm@yourself.bpounce.us;2;2;[{LRT=};{LED=400 4.4.7 Message delayed};{FQDN=};{IP=}];0;CN=Send connector,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=JC,DC=LOCAL;0

I have scanned for a virus and non found. Who is sending these??

We have random emails mostly, it looks like just spam that keep getting jammed up in the "Journaling Queue" with the following error;

“Last Error: 400 4.4.7 The server responded with: 550 5.6.2 SMTPSEND.BareLinefeedsAreIllegal; message contains bare linefeeds, which cannot be sent via DATA. The failure was replaced by a retry response because the message was marked for retry if rejected.”

I have followed the "Bare linefeeds clogged" question earlier and I'm continuing to get these messages on a daily basis even after changing the BareLinefeedRejectionEnabled to $true.  These were the connectors that I updated (which are all of them)

• FrontendTransport
  Set-ReceiveConnector "FSRM-SMTP" -BareLinefeedRejectionEnabled $true
  Set-ReceiveConnector "SERVERNAME\Client Frontend SERVERNAME" -BareLinefeedRejectionEnabled $true
  Set-ReceiveConnector -Identity "SERVERNAME\Default Frontend SERVERNAME" -BareLinefeedRejectionEnabled $true
• HubTransport
  Set-ReceiveConnector "Client Proxy SERVERNAME" -BareLinefeedRejectionEnabled $true
  Set-ReceiveConnector "Internal-Relay" -BareLinefeedRejectionEnabled $true
  Set-ReceiveConnector "SERVERNAME\Default SERVERNAME" -BareLinefeedRejectionEnabled $true
  Set-ReceiveConnector "Outbound Proxy Frontend SERVERNAME" -BareLinefeedRejectionEnabled $true

I have to manually "Remove (without sending NDR)" and I would like to find a resolution so I don't need to monitor and worry that emails are jamming up in this queue anymore.  Any ideas?

EX2013 Std. Ver 15.0 (build 1210.3)

PennyM

Hi!

I have a customer who would like to use contacts to relay mails to external partners working for him. The problem is that when we send mails to this contact the sender receives a NDR with the code 550 5.4.4. We have been able to trace the problem back to the NoSpamProxy being used in the DMZ, because we can see the following in the logs:

If you think your to small to make a differnce, try going to bed with a mosquito in the room...

Hi 

We have enable message tracking for 40days, but MSGTRKMD files automatically deleted after 20 to 25 days once it rechaed the all file size near 1GB.

due to this we are unable to see complete delivery information about the messages.

thanks

Hello All,

I am having problem connecting to our Exchange 2013 from Outlook 2016 application running on external PC (outside LAN) or internal PC but not joined to Domain using auto-discovery. However there is no issue connecting to Exchange from Domain joined PC, auto-discovery working fine and connects to Exchange.

The problem is, when I try to setup Exchange profile by entering name, email address and password, it tries to find Exchange server through auto-discovery and after few seconds it prompts for entering password where my email-address is shown as user-name. Even after I put my password correctly, it still opens-up the same password prompt window. It keeps on coming again and again, no matter how many times I put my correct password.

Sometime, though, it throws another message "An encrypted connection to your mail server is not available. Click next to attempt using an unencrypted connection.". Then selecting unencrypted connection, eventually it fails and give me option to choose Activesync or IMAP/POP3.

From Domain-joined PC and when logged-into Domain, Auto-discovery seems working fine because Outlook 2016 can find the Exchange and able to create profile and connect to server without any issue. It does not prompt for any password since I am already logged-into domain. Also from Smart-phones, Outlook or other Email clients can be setup to connect to Exchange and no issue with that. Only with computers which are not on domain. Not sure what is causing this.

I tried using Activesync, but got to know its for lite-version of email clients and not for full-featured client which Outlook is.

My guess, the issue is lying somewhere in Exchange configuration the way authentication is being handled for outside domain. I don't think its an issue with Outlook application, I have tried it on different PCs with 2016 and 2013 version of Outlook, same result.

I have had lots of time spent to troubleshoot this issue, no luck ye. I will appreciate any advice which may help to resolve the issue.

Hi

we have Exchange server 2013. when our iphone users modifies (only one occurance) a reoccuring meeting invite and send, its sending two notifications to attendees. one is original meeting invite and other one is modified one. next time when they modifies one more occurance of the same meeting series, its sending three notifications. one is original, second is first modified notification and third is last modified one. its keep on increasing, when they try to modify single ocurance. problem is not only with any particular reoccuring meeting invite. can someone help on this?

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.

<g class="gr_ gr_19 gr-alert gr_gramm gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="19" id="19">Hi</g> team exchange!

I want to ask team a question about message log:

Currently, I am using barracuda mail gateway device to email gateway, I have configured routing exchange via barracuda, but I only get messages log on barracuda when I send from local domain to external domain but I don't see messages log on barracuda when I send from local domain to local domain, can you help me guideline configure on mail exchange to route both local <g class="gr_ gr_619 gr-alert gr_gramm gr_run_anim Grammar multiReplace" data-gr-id="619" id="619">domain</g> when it send with <g class="gr_ gr_722 gr-alert gr_gramm gr_run_anim Style multiReplace" data-gr-id="722" id="722">together ,</g> on barracuda can get this message log.

Thank <g class="gr_ gr_792 gr-alert gr_gramm gr_run_anim Grammar multiReplace" data-gr-id="792" id="792">many</g> help.

Hi all!

I have an issue in my on-premises Exchange 2013 environment (CU13). Let me explain the situation before:

we have an automatic incident generation system that, if you send an email to it, open a Support Ticket on behalf of the sender. It happened that for 8 hours this mechanism ignored mails, so for 8 hours users send support mail without having a support case opened. I have these mail in the inbox of the mailbox, and I need to resubmit to the Incident System's recipient.

I tried to convert the .msg into .eml format using MFCMAPI and then place the file into PuckUp folder in the Exchange server, but after some seconds the file is renamed in .bad and then not processed. It seems that the file is not formatted in a good way or something is missing in the SMTP headers, but I'm not able to find what's wrong.

I then tried to use the Search-Mailbox command piped with "Export-Message $_.Identity | AssembleMessage -Path ("c:\temp\jm\mail\"+ $i +".eml")}" but the Search-Mailbox cmdlet needs a destination pst or a destination mailbox, otherwise it fails.

Do you guys have some suggestion on how to:

- convert the unprocessed messages from the mailbox in the EML format that can be processed and sent by Transport service;

or

-  export the messages with search-mailbox and then use the AssembleMessage cmdlet;

or

- achieve this goal using another way.

Thanks!

Hello,

I'm looking for some assistance with transport rules.  I have several rules setup that I need to add an exclusion to.  We have email coming in from a couple specific hosts that I need to exclude from the rule.  Unfortunately there are no 'exclude if email comes from specific host' rules to use.  I thought I might be able to use the match text in message header rule, but I can't find any (good) documentation on how to even use that rule.

If anyone knows of a way to exclude emails from a transport rule by host name or IP I'd appreciate some assistance.

Thanks,

Bill