We have an Exchange 2013 on-premise server and seem to have an issue with emails sent to internal and external users at the same time.

The issue came to light because someone sent an email to 44 recipients, of which one was internal. None of the external recipients received the email. I checked the delivery report in the EAC and found the internal email marked as 'Delivered' and all of the external ones marked as 'Pending'. I checked the queues and there were none. I did some testing and sent an email to just one of the external addresses on the list, it arrived. I tried sending the email again to all of the recipients, the external ones all showed 'Pending'. I tried it again, but this time excluded the internal email address and all of the 43 external emails were immediately delivered.

So it seems that the issue only arises when we are sending to both internal and external addresses.

I then tried a test email to one internal address and one external address. The Delivery report says that the internal address was delivered immediately, while the external address is 'Pending' and gives more information saying: 'Message delivery is taking longer than expected. There may be system delays. For more information, contact your helpdesk.'. To add further mystery to this, the email was actually delivered.

So, I have two concerns:

First is seems that some emails sent both internally and externally are only arriving internally. This is a huge problem because I don't know how many have been affected. There may be many lost emails we don't know about.

Second, it looks like I can't trust the delivery report. It says pending for some emails which didn't arrive, but it also says pending for some which did arrive. That is no good at all.

For info the server is running Windows Server 2012. I have run a Microsoft Update to check if there are any to apply and the only Exchange one is a spam filter update, which I doubt has any bearing but I will apply when I get chance.

Hi 

I configured auto reply configuration for my email as below

when any user try to send mail to me , he should receive the message  I configured" internal or external message " but he did not 

can any one hep ?

Mahmoud

Hi,

I have new testing lab to play around with which is starting to drive me insane. I have exchange 2013 and outlook 2013. I can receive emails from external domains but I am unable to send emails internally or externally!

Now I would know what to look at if I couldn't send externally, But not being able to send internally has completed confused me!

anyone got any tips where to start troubleshooting for not being able to send internal mail? Once internal mail works I should then be able to get external mail working as well....

Thanks

I've run the wizard and it completed successfully but with errors. Please see link with infohttps://1drv.ms/f/s!AtDLHqM30UysgQU_WszSVbgirr2t

Can you help?

A few things that I want to state right off the bat:

1. While I am an IT technician, I am not an Exchange administrator and have no access to our Exchange servers.
2. When I pose this question to our Exchange administrators I am told that this is a client issue.  I have reason to doubt that answer and so am seeking more objective opinions.
3. I am not trying to solve an existing technical issue.  I am simply trying to collect more information so that I can gain a better understanding of email encryption issues.

Recently, I have seen three cases were a user was having email encryption problems, and in all three cases the issue was caused by an expired default certificate in the address book.  In all three cases:

• The user had one valid certificate listed in AD.
• I opened MMC on the client machine and added the Certificates snap-in, and found only one certificate installed on the machine, and it matched the certificate listed in AD.
• I looked up the user in the address book, did a right-click > Add to Contacts > Certificates button on the ribbon, and found that the default certificate listed for the user was expired.

In one case, the default certificate listed in the address book expired in 2012.

Our Exchange administrators tell me that this is a client issue and that email encryption does not involve the Exchange servers--that the servers simply pass messages back and forth.  But if that expired certificate is not in AD, and it's not installed on the client machine, then where is it coming from?  It has to be coming from somewhere. 

When I'm on the client and click the Publish to GAL button, that certificate gets published to an AD server.  My understanding is that Exchange then queries AD and updates the OAB with new data, which would include new certificate information.  If this is correct, then an Exchange server is involved in the process, and therefore this issue may not be caused by the client.

Am I on to something with my line of reasoning, or is my Exchange administrator correct?  If I am on to something, then I would be interested in knowing the details of what happens from the time I click the Publish to GAL button on the client to the time the new certificate information shows up in the address book.

Thanks in advance for any information that you can provide!

--Tom

Hello, Team!

I think I’ve found a serious issue in last CU releases. This is the case:

1 Multirole server Exchange 2013 SP1 (and older) , one creceive connector from internet to this server, no edge, nothing.

I care about preventing spoofing my company’s email addresses, and remove remove the ms-Exch-SMTP-Accept-Authoritative-Domain-Sender transport permission from anonymous senders.

To do this, we usually simple run powershell command

Remove-ADPermission <ReceiveConnector Name> –user “NT AUTHORITY\Anonymous Logon” –ExtendedRights ms-Exch-SMTP-Accept-Authoritative-Domain-Sender

This command works on Exchange SP1, the client (telnet session, f.e.) which try spoof address of company will be refused. (see screenshot below)

But in Exchange 2013 CU5, CU6 and even CU7 release this revoke permissions DOESN’T WORKS without any errors, softly. I've try Powershell and ADSI but unsuccessfully.

Then we take off permission on connector above, we keep 3 default permissions:

Accept-any-sender

Accept-Routing-Headers

Submit-Message to Server

It is wonderful works only on server SP1, but not on servers with older versions, which have right settings.

The saddest thing is I have information about Office 365 this behavior reproduced too. And I also think what in your lab you could take 15 minutes and play this simply thing....

I found only that information on connector side is diffenent on SP1 and CU5,6,7.

This is normal connection on SP1, when somebody try spoofed address. We can see a 250 AUTH Response on server side, and server refuse fake connection, all right.

And on CU5 and newest versions we doesnt see this code. Maybe auth mechanism miss something?

Any suggestions? On MS connect site a didn't found exchange bugs topic :)

Hi Guys,

I have just setup an brand new Exchange 2013 which working almost 80 % if i may put it that way.

My users are sending e-mails without and problem.The issue i have is users cannot receive e-mails from outside the organisation When we send emails we get bounce back that saysrecipient address rejected: User unknown in
virtual mailbox table'

My Environment

dc on server 2012 r2exchange (both cas and mailboxon one server) on server 2012  r2.

Thanks

Kassoka

I have installed the Connection Filtering agent:

Install-TransportAgent -Name "Connection Filtering Agent" -TransportService FrontEnd -TransportAgentFactory"Microsoft.Exchange.Transport.Agent.ConnectionFiltering.ConnectionFilteringAgentFactory" -AssemblyPath "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.Transport.Agent.Hygiene.dll"

Add-IPBlockListProvider -Name zen.spamhaus.org -LookupDomain zen.spamhaus.org -AnyMatch $true -Enabled $true

Enable-TransportAgent -TransportService FrontEnd -Identity "Connection Filtering Agent"

Restart-Service MSExchangeFrontEndTransport

After this, it doesn't work. Email from ip addresses marked as blacklisted (as can be seen by test-ipblocklistprovider) aren't blocked. Besides, no logging is created in “C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\AgentLog”

Specified cast is not valid. 

You know you're an engineer when you have no life and can prove it mathematically

I'm trying to configure a transport rule in Exchange 2013 to block all emails from the TLD .eu   We get nothing but a TON of spam that is not caught by the Exchange 2013 spam filter, and it's always from a different domain. I have seen guides for 2007 and 2010, but nothing for 2013.

Do I just use the rule "The sender domain is" and use the value ".eu"? I just want to verify this is the correct way to block a TLD.

I am having issue with exchange server 2010

for some reason all email coming from external sources like yahoo & gmail are not being received by any users

outgoing emails are working fine also internal emails are working too its just incoming email are not being received

we don't have any exchange sever experience and don't know how to fix issue id appreciate any guidance in the matter

thank you

Albert  

Hi to all

I am trying to change FQDN on default receive connector

First I used

https://technet.microsoft.com/en-us/library/bb124740(v=exchg.150).aspx

Set-ReceiveConnector "Default Frontend ServerName" -Banner "220 mail.domainname.co.uk"

telnet mail.RecipientDomain.co.uk 25

220 mail.RecipientDomain.co.uk

EHLO SerderDomain.com

250-ExchangeServer2013.RecipientDomain.NET Hello [External IP of RecipientDomain MX record]

250-SIZE 104857600

250-DSN

250-ENHANCEDSTATUSCODES

250-STARTTLS

250-AUTH NTLM

250-X-EXPS GSSAPI NTLM

250 8BITMIME

MAIL FROM: User.Name@SerderDomain.com

250 2.1.0 Sender OK

RCPT TO: Recipient.User@RecipientDomain.co.uk

250 2.1.5 Recipient OK

DATA

552 Your email has been blocked: Either sender's domain or email address is in the blacklist

Connection to host lost.

What I have observed when I checked properties/Security of "Default Frontend ServerName " Exchange Server authentication was still checked

Although mail flow was not affected I used to remove custom banner with following as stated in document.

Set-ReceiveConnector "Default Frontend ServerName " -Banner $null

I tried same thing with EMC as per documenthttp://www.oxfordsbsguy.com/2016/02/20/exchange-2013-initial-configuration-settings-how-to-change-the-fqdn-on-the-default-frontend-receive-connector-part-9/

External to internal email flow stopped with the same error “552 Your email has been blocked: Either sender's domain or email address is in the blacklist”

I have put everything back to how it was now we have mail flow.

I would very much appreciate for your help why I am getting these errors in different configurations/

Many thanks in advance.

Regards.

VITP

Hi,

after export and disable mailbox on source (old) exchange 2007 server, I import pst file to new Exchange 2013 server.

But users at outlook - use response or auto substitution, and get massage after sending mail to the migrated user.

IMCEAEX-_O=TECHNO_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=TESTUSER3@domain.local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

and if thay inpute full email address - massage send with no errors.

It like, outlook use cache. I try disable disable caching mode of outlook - but without success.

How I can fix it, the best solution?

Hello! Please help me to solve the problem with Search-MailboxAuditLog and Search-AdminAuditLog (in ECP).I have test environment with EXCHANGE_2013_CU6_RUSSIAN (all exch roles on it) and want to check audit before production use.I was surprised that audit no working, i do that:

1) Enable and check audit for Test mailbox

2) Add Delete Actions to Owner of mailbox (in my case - Test) for fast checking

3) Login to Outlook under Test and delete 1 item, after thatcheck folder statistic for Test mailbox

4) Return to Outlook and delete one more item and see statistic again (for sure)

5) As we can see something write to audit folder, it's good, BUT:<o:p></o:p>Resume:Search-MailboxAuditLog - NO RESULT, with any parameters

Another problem -> Search-AdminAuditLog - HAVE RESULT, but from ECP i don't see it.

My TEST DB have healthy status of indexes, no problem with system mailbox but i have russian exchange. Maybe trouble in different language (not English) wrong parse logs or something else? I really need audit reports in production, it's very serious question, please help!!!

Dear Folks,

we are running Exchange 2010 with Hybrid Setup. We are currently facing an issue with Exchange online users. there is an on premises mailbox, let's say abc-user@domain.com > any email that is received to this on premises mailbox abc-user@domain.com it is forwarded to a distribution group; let's say xyz-group@domain.com. when an Exchange Online user send email to abc-user@domain.com > Exchange online user gets following error message.

"Your message can't be delivered because delivery to this address is restricted.

#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##rfc822;"

Note: Distribution Group has this check enabled and we can't remove that "Require that all senders are authenticated"while there are only few users who are getting NDR/ error message while other Exchange online users are able to send email to on premises mailbox, abc-user@domain.com and email is getting forwarded to distribution group xyz-group@domain.com

please assist on this.

Thanks, Sheeraz

Hello Good People,

Please help me. I just installed fresh exchange 2013 in my organization. Before now, we were using email services from our website hosting company but we decided to host our own exchange in-premises.

The issue we can't receive mails sent from external domain, although we can send from the exchange server internally and externally successfully..

Please note, that on my network, I have one DC and 2 Exchange servers (Both of which has Mailserver and Client Access Roles)

Below is the NDR,

Please help.

Thank you,

Hafeez Azeez

Hello -

I am trying to enable Exchange priority queuing.  I've gone through this article https://technet.microsoft.com/en-us/library/jj891104(v=exchg.150).aspx and completed the steps without an issue.  #2 in the "How do you know if this worked" section, it says to test out, send an email as high priority that is larger than the max high priority value, which by default is 250KB and it should instead send as a normal email.   Well I did this, and when I receive it on the other end, its still a high priority email.  This leads me to believe that things are not working right.

Maybe this is normal behavior and the article is wrong?  Can someone help?

Thanks!

I am having issue with exchange server 2010

for some reason all email coming from external sources like yahoo & gmail are not being received by any users

outgoing emails are working fine also internal emails are working too its just incoming email are not being received

we don't have any exchange sever experience and don't know how to fix issue id appreciate any guidance in the matter

thank you

Albert  

Hello friends, I need you guys help.
My Exchanbge 2013 CU13 server running on Windows Server 2012 R2 does not receive mail only from hotmail.com and live.com and outlook.com

I'm with this problem almost two months already opened several called to Hotmail support team, and believe me, even by phone I talked to them and explained the problem. But strangely enough they do not know explain what is happening and simply close the call.

My IP is not listed in any blacklists, my SPF is correct, my reverse DNS is correct .....

The email comes to my server, but from what I read in the receipt log, it enters a sort of a queue and is not delivered to the User.

In my desperation, I even installed a enovo ambient, an Exchange zero and auditioned to believe, the same problem happens only see my receipt log:

2016-09-15T22:47:12.639Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B8,20,127.0.0.1:25,127.0.0.1:19268,-,,Local
2016-09-15T22:47:36.092Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,0,*********:25,65.55.116.103:64646,+,,
2016-09-15T22:47:36.092Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,1,*********:25,65.55.116.103:64646,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-09-15T22:47:36.092Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,2,*********:25,65.55.116.103:64646,>,"220 SRV-EMAIL.*********.com.br Microsoft ESMTP MAIL Service ready at Thu, 15 Sep 2016 19:47:35 -0300",
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,3,*********:25,65.55.116.103:64646,<,EHLO BLU004-OMC3S28.hotmail.com,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,4,*********:25,65.55.116.103:64646,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,5,*********:25,65.55.116.103:64646,>,250-SRV-EMAIL.*********.com.br Hello [65.55.116.103],
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,6,*********:25,65.55.116.103:64646,>,250-SIZE 37748736,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,7,*********:25,65.55.116.103:64646,>,250-PIPELINING,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,8,*********:25,65.55.116.103:64646,>,250-DSN,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,9,*********:25,65.55.116.103:64646,>,250-ENHANCEDSTATUSCODES,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,10,*********:25,65.55.116.103:64646,>,250-STARTTLS,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,11,*********:25,65.55.116.103:64646,>,250-X-ANONYMOUSTLS,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,12,*********:25,65.55.116.103:64646,>,250-AUTH NTLM,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,13,*********:25,65.55.116.103:64646,>,250-X-EXPS GSSAPI NTLM,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,14,*********:25,65.55.116.103:64646,>,250-8BITMIME,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,15,*********:25,65.55.116.103:64646,>,250-BINARYMIME,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,16,*********:25,65.55.116.103:64646,>,250-CHUNKING,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,17,*********:25,65.55.116.103:64646,>,250 XRDST,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,18,*********:25,65.55.116.103:64646,<,STARTTLS,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,19,*********:25,65.55.116.103:64646,>,220 2.0.0 SMTP server ready,
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,20,*********:25,65.55.116.103:64646,*,,Sending certificate
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,21,*********:25,65.55.116.103:64646,*,CN=SRV-EMAIL,Certificate subject
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,22,*********:25,65.55.116.103:64646,*,CN=SRV-EMAIL,Certificate issuer name
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,23,*********:25,65.55.116.103:64646,*,69E1A67D7F03ADA6408BF42E947FCB89,Certificate serial number
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,24,*********:25,65.55.116.103:64646,*,5D91AA7DB66F81C48DE7C8C8AAB5365E238920FD,Certificate thumbprint
2016-09-15T22:47:36.108Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,25,*********:25,65.55.116.103:64646,*,SRV-EMAIL;SRV-EMAIL.*********.com.br,Certificate alternate names
2016-09-15T22:47:36.201Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,26,*********:25,65.55.116.103:64646,*,,"TLS protocol SP_PROT_TLS1_2_SERVER negotiation succeeded using bulk encryption algorithm CALG_AES_256 with strength 256 bits, MAC hash algorithm CALG_SHA_384 with strength 384 bits and key exchange algorithm CALG_ECDHE with strength 384 bits"
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,27,*********:25,65.55.116.103:64646,<,EHLO BLU004-OMC3S28.hotmail.com,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,28,*********:25,65.55.116.103:64646,*,,Client certificate chain validation status: 'EmptyCertificate'
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,29,*********:25,65.55.116.103:64646,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,30,*********:25,65.55.116.103:64646,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,31,*********:25,65.55.116.103:64646,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,32,*********:25,65.55.116.103:64646,>,250-SRV-EMAIL.*********.com.br Hello [65.55.116.103],
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,33,*********:25,65.55.116.103:64646,>,250-SIZE 37748736,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,34,*********:25,65.55.116.103:64646,>,250-PIPELINING,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,35,*********:25,65.55.116.103:64646,>,250-DSN,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,36,*********:25,65.55.116.103:64646,>,250-ENHANCEDSTATUSCODES,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,37,*********:25,65.55.116.103:64646,>,250-AUTH NTLM LOGIN,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,38,*********:25,65.55.116.103:64646,>,250-X-EXPS GSSAPI NTLM,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,39,*********:25,65.55.116.103:64646,>,250-8BITMIME,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,40,*********:25,65.55.116.103:64646,>,250-BINARYMIME,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,41,*********:25,65.55.116.103:64646,>,250-CHUNKING,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,42,*********:25,65.55.116.103:64646,>,250 XRDST,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,43,*********:25,65.55.116.103:64646,<,MAIL FROM:<tecnologiawell@outlook.com> SIZE=4798,
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,44,*********:25,65.55.116.103:64646,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,45,*********:25,65.55.116.103:64646,*,08D3DDA0C4CC52B9;2016-09-15T22:47:36.092Z;1,receiving message
2016-09-15T22:47:36.217Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,46,*********:25,65.55.116.103:64646,>,250 2.1.0 Sender OK,
2016-09-15T22:47:36.233Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,47,*********:25,65.55.116.103:64646,<,RCPT TO:<administrador@*********.com.br>,
2016-09-15T22:47:36.233Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,48,*********:25,65.55.116.103:64646,>,250 2.1.5 Recipient OK,
2016-09-15T22:47:36.233Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,49,*********:25,65.55.116.103:64646,<,BDAT 4798 LAST,
2016-09-15T22:47:36.248Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,50,*********:25,65.55.116.103:64646,*,,Ignored X-OriginatorOrg header value 'outlook.com' because session capabilities do not allow it
2016-09-15T22:47:36.264Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,51,*********:25,65.55.116.103:64646,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
2016-09-15T22:47:36.561Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,52,*********:25,65.55.116.103:64646,>,"250 2.6.0 <BN3PR0701MB113831B2F4857BFF5D3B86B5D1F00@BN3PR0701MB1138.namprd07.prod.outlook.com> [InternalId=38654705692, Hostname=SRV-EMAIL.*********.com.br] Queued mail for delivery",
2016-09-15T22:47:36.577Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,53,*********:25,65.55.116.103:64646,<,QUIT,
2016-09-15T22:47:36.577Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,54,*********:25,65.55.116.103:64646,>,221 2.0.0 Service closing transmission channel,
2016-09-15T22:47:36.577Z,SRV-EMAIL\Default Frontend SRV-EMAIL,08D3DDA0C4CC52B9,55,*********:25,65.55.116.103:64646,-,,Local

Silvio Tavares - Analista de Sistemas