Exchange 2013 installed on Server 2012r2. We use POPcon to retrieve our messages from our host.
The problem we have is receiving messages 2mb or larger. All other messages are received without any problems.
I have updated the receive connecter(s) limit to 500mb and each mailbox to 100mb.
Grateful for any help.
Well mail is now flowing, but Outlook 2013 fails to connect. Well it sets the profile up fine but when I fire up OL it "says "Cannot start MS Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The information store could not be opened"
Does anyone have any ideas please?
I have added a picture as a signature by using html in the disclaimer transport rule by appending the following
<!DOCTYPE html>
<html>
<head>
<style>
img {
width:100%;
}
</style>
</head>
<body>
<img src="https://picturelink.domain" alt="HTML5 Icon" style="width:60px;height:60px;">
</body>
</html>
I added exception for messages that have the words RE: or FW: to solve duplicate signiture problem, but sometimes users remove these words from the subject and the result is double sign.
Is there any way to add exception if the message already have the html signiture ??
Hello
Since couple of days my External IP is being blocked by 'Spamhaus'/CBL saying my exchange server is sending spam.
Since we have only few users in system, i check there sent box and did not find anything suspicious.
Then i checked MSGTRK log on exchange server.
There i found couple entries which are surely spam, but i do not know how they are coming to exchange server.
Couple of things in logs:
are these are incoming mail or outgoing? If incoming then Spamhaus
following is few records from log:
| #Fields: date-time | source-context | source | event-id | recipient-address | recipient-status | reference | message-subject | sender-address | return-path | directionality | original-client-ip | original-server-ip | custom-data | ||||
| 2016-01-20T12:44:08.748Z | No suitable shadow servers | SMTP | HAREDIRECTFAIL | WinterOskar9047@sanketindia.in | AW: Rechnung Nr.20605838 | Juergen.Lauer@huk-coburg.de | Juergen.Lauer@huk-coburg.de | Incoming | S:DeliveryPriority=Normal;S:AccountForest=sanket.local | ||||||||
| 2016-01-20T12:44:08.858Z | 08D318DF94203457;2016-01-20T12:44:08.716Z;0 | SMTP | RECEIVE | WinterOskar9047@sanketindia.in | AW: Rechnung Nr.20605838 | Juergen.Lauer@huk-coburg.de | Juergen.Lauer@huk-coburg.de | Incoming | 193.201.183.161 | 192.168.2.56 | S:FirstForestHop=mail1.sanket.local;S:ProxiedClientIPAddress=193.201.183.161;S:ProxiedClientHostname=smtp1.huk-coburg.de;S:ProxyHop1=mail1.sanket.local(192.168.2.56);S:DeliveryPriority=Normal;S:AccountForest=sanket.local | ||||||
| 2016-01-20T12:44:08.921Z | Failure | DSN | DSN | Juergen.Lauer@huk-coburg.de | <9da94b51ffb645339e1c7fdbe3454516@SMXRF105.msg.hukrf.de> | Unzustellbar: AW: Rechnung Nr.20605838 | postmaster@sanket.local | <> | Originating | S:DeliveryPriority=Normal;S:OriginalFromAddress=Juergen.Lauer@huk-coburg.de;S:AccountForest=sanket.local | |||||||
| 2016-01-20T12:44:08.921Z | AGENT | AGENTINFO | WinterOskar9047@sanketindia.in | AW: Rechnung Nr.20605838 | Juergen.Lauer@huk-coburg.de | Juergen.Lauer@huk-coburg.de | Incoming | 193.201.183.161 | 192.168.2.56 | S:AMA=SUM|v=0|action=|error=|atch=0;S:AMA=EV|engine=M|v=0|sig=1.213.3458.0|name=|file=;S:CompCost=|AMA=0;S:DeliveryPriority=Normal;S:AccountForest=sanket.local | |||||||
| 2016-01-20T12:44:08.921Z | ROUTING | FAIL | WinterOskar9047@sanketindia.in | '[{LRT=};{LED=550 5.1.1 RESOLVER.ADR.RecipNotFound; not found};{FQDN=};{IP=}]' | <b739d4a0-c35f-4eb0-bee1-336340042baf@mail1.sanket.local> | AW: Rechnung Nr.20605838 | Juergen.Lauer@huk-coburg.de | Juergen.Lauer@huk-coburg.de | Incoming | S:DeliveryPriority=Normal;S:AccountForest=sanket.local | |||||||
| 2016-01-20T12:44:09.090Z | AGENT | AGENTINFO | WinterOskar9047@sanketindia.in | Unzustellbar: AW: Rechnung Nr.20605838 | postmaster@sanket.local | <> | Originating | S:AMA=SUM|v=0|action=|error=|atch=2;S:AMA=EV|engine=M|v=0|sig=1.213.3458.0|name=|file=;S:CompCost=|AMA=0|ETR=0;S:DeliveryPriority=Normal;S:OriginalFromAddress=Juergen.Lauer@huk-coburg.de;S:AccountForest=sanket.local |
hi everybody,
i am trying to create another transport rule on an exchange server 2007 in powershell.
this rule is supposed to check the mail header for certain texts. in that case it should forward
the message as bcc. it is part of a bigger script to automate the creation of project mailboxes.
$short = "test_02" $shortCollector = "test_02.collector" #create transport rule - >replyTo< $Condition1 = Get-TransportRulePredicate HeaderContains $mywords = @($short + "@mycompany") $mywords = $mywords + "cn=$short" $Condition1.messageHeader = @($mywords) $Action1 = Get-TransportRuleAction BlindCopyTo $ADOCollector = get-mailbox $shortCollector | select -expand userprincipalname $Action1.Addresses = @(get-mailbox $shortCollector) $RULE_name = $short + " out(replyTo)" New-TransportRule -name $RULE_name -Condition @($Condition1) -Action @($Action1)
it does not work as intended as i get another error like
...Cannot convert the "System.Object[]" value of type "System.Object[]" to type"Microsoft.Exchange.MessagingPolicies.Rules.Tasks.HeaderName".
any ideas how i can convert correctly?
thank you - best regards
marc
Hi All
We have a lot of transport rules and one of them with predicate:
Name : AttachmentProcessingLimitExceeded
LinkedDisplayText : when an attachment processing limit is exceeded<a id="AttachmentProcessingLimitExceeded"></a>
How co configure Limits for This Predicate or Transport for processing? ( We have a lot of messages with false positive )
P.S Exchange 2013 CU10
Best Wishes, Andrew Golubenkoff
Hello All,
I was inquiring about the criteria used to determine the DIRECTIONALITY field (incoming, originating, outgoing) of message tracking logs for Exchange Server 2013. Unfortunately, the whitepaper (linked below) does not describe this. Any insight into
how this is determined would be helpful. Thanks.
https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.150%29.aspx
I was administering an Exchange server for multiple email domains that was previously receiving forwards from various internet email hosts until the site had reliable internet with a static IP, updated the internet MX record, etc. Once that happened, we reconfigured the 'accepted domains' from 'External Relay' to Authoritative.
Unfortunately now all email is rejected when it's addressed to email addresses that are not that user's primary address:
5.1.0 - Unknown address error 550-'No Such User Here"'
So let's say I have employee John Smith with the following email addresses:
With the previous configuration, John Smith would receive emails that match any of those three addresses. Since flipping over to Authoritative, he's only receiving the bolded primary address!
Any and all insight would be appreciated!
hello guys,
i have problem with exchange 2013 - 2007 mailflow.
recently i added exchange 2013 to our exchange organization everything seems to work fine , well at least for 2 days now exchange 2013 users cant send email to exchange 2007 users and exchnage 07 cant send to exchange 13.
all messages are stuck in queue of both servers.
any help would be appreciated
thanks!
Situation: Domain:A and Domain:B
Server 1: Win2012 + Exchange2013 + Domain A
Server 2: Win2012R2 + Domain B
user victor@domainA has mailbox now the same uservictor@domainB wonts to use in one logon the both.
so he wants to choise from wich account he sends email.
I tried to make a linked mailbox but I got this error: The value "victor@prinfotech.com" of property "UserPrincipalName" is used by another recipient object "". Please specify a unique value.
What went wrong.
Hi there.
A user marked a folder properties that it should delete items older then 7 days, but those items still stays in that folder.
Any suggestion why this not working?
bostjanc
Hi all,
In my Exchange 2013 system there is one user that cannot receive any email although messages come to Exchange queue, here example log
As you can see, I sent her a message from my gmail , Exchange received my message but cannot delivery to user's mailbox, I cannot find it in Toolbox >> QueueViewer and I don't know where it is ...
Please give me some advice to fix this issue, thank you very much
Hi, we've recently switched our anti spam filter to Mimecast and I've started noticing in the 'Bounce' section an email every couple of minutes being caught as undeliverable, shown below. This was most likely happening before, but our previous anti spam
filter was useless!
I'm aware of the HealthMailboxes and from my understanding they should be receiving these emails, rather than attempting to send them externally. I've managed to catch one of these emails and it contains the following content:
Delivery has failed to these recipients or groups: HealthMailbox3ac30e4d99434adaa06f83ce3062fb1f@OurDomain.co.uk The email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: mailserver2.OurDomain.lan HealthMailbox3ac30e4d99434adaa06f83ce3062fb1f@OurDomain.co.uk Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found' Original message headers: Received: from mailserver2.OurDomain.lan (192.168.0.10) by mailserver2.OurDomain.lan (192.168.0.10) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Mon, 25 Jan 2016 11:15:44 +0000 Received: from InboundProxyProbe (127.0.0.1) by mailserver2.OurDomain.lan (127.0.0.1) with Microsoft SMTP Server id 15.0.1130.7 via Frontend Transport; Mon, 25 Jan 2016 11:15:44 +0000 X-MS-Exchange-ActiveMonitoringProbeName: OnPremisesInboundProxy_2 X-Exchange-Probe-Drop-Message: FrontEnd-CAT-250 Subject: Inbound proxy probe Message-ID: <1125c87ee52942dea2fd46d60221eec2@mailserver2.OurDomain.lan> From: <inboundproxy@contoso.com> To: Undisclosed recipients:; Return-Path: inboundproxy@contoso.com Date: Mon, 25 Jan 2016 11:15:44 +0000 MIME-Version: 1.0 Content-Type: text/plain
The listed mailbox does exist and contains the SMTP address. I've followed steps to rebuild the mailboxes and they are recreated as expected, but then within moments of them all being recreated the issue starts happening again.
Our system contains 3 mailbox servers all members of a DAG, each containing a copy of 4 databases. They are all running Exchange 2013 CU10.
Thanks for any help.
We have a child domain set up in AD for external users to access our Sharepoint resources, as part of this their external email address is added to the 'proxyAddresses' attribute to allow email notifications, etc.
We then find, for some of these accounts at least (doesn't appear to happen straight away), we can't email them normally through Outlook. Users receive the following message:
'420 4.2.0 Recipient deferred because there is no Mdb'
The Exchange system is obviously picking up the external address in the child domain and trying to deliver the message to it. These users do not have mailboxes within Exchange which is why the above message is being generated.
Is there anything I can do to get Exchange to ignore the child domain? At present the only way to fix this seems to be to delete the AD account for this user so Exchange goes back to delivering the email as normal.
Thanks for any help, this has been annoying me a couple of years now (we had this problem with Exchange 2010 as well, now fully migrated to 2013 CU10).
Afternoon,
following the examples from https://technet.microsoft.com/en-us/library/aa997185%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396 it should be really easy to get the edge server to rewrite the domain on its way out but I can't seem to get it working.
New-AddressRewriteEntry -Name "Domain Change" -InternalAddress mydomain.co.uk -ExternalAddress newdomain.co.uk -OutboundOnly $true
I was hoping this would rewrite my email mike@mydomain.co.uk and change it through the edge server by this policy to mike@newdomain.co.uk
I have tried single recipients as well but can't get it to apply this rule.
The Transport Agent is running and confirmed by using Enable-TransportAgent "Address Rewriting Outbound Agent"
.: Lister :.
We are in a Office365-Exchange 2013 Hybrid environment today, slowing migrating users to the cloud.
We seem to receive a lot of spoofed emails and was looking for some tips/tricks to get a better hold of this. Usually these are emails that are sent to internal folks from senior publicly noticed figures such as the CEO, CFO etc.
The emails look legit, even have the correct alias@contoso.com addresses displayed unless you actually dig into the headers to see different.
All our email is scanned by Microsoft EOP as they are our MX record holders then passed thru to our On-Premises mail users.
Is it possible to tighten security by setting the on-premises and MSOL servers to never accept or block email sent from the outside when being sent from alias1@contoso.comto alias2@contoso.com?
Thanks in advance.
Hey there,
We have our Exchange environment configured to deliver all mail through a send connector that authenticates with our ISP's reputable mail server for mail delivery, in order to avoid having to deal with trust and blacklisting ourselves directly. We discovered the other day, that while we have an agreement with them to not cap our daily message sending (where their average user is), we are still subject to a 200 message/30min limit, after which subsequent message are rejected/bounced with the below error:
Remote Server returned '550 User has exceeded outgoing limit G_SPAM_USER_MAX or send_limit(200)
and if our server continues to try to send mail, we eventually start getting:
451 4.4.0 SMTPSEND.SuspicousRemoteServerError; remote server disconnected abruptly; retry will be delayed
I started looking at send connector configuration options, as well as Message throttlinghttps://technet.microsoft.com/en-us/library/bb232205(v=exchg.150).aspx
but I'm not sure the best way (if there is any) to accommodate for this. I was hoping for configuration options that would allow me to setup the existing send connector to work around this limitation by queuing, either before the limit is reached, or after by reacting differently to the 550 send limit response, but so far I'm not seeing anything like that.
I get the feeling from the Message Throttling article that I should be looking at this more from a per-user standpoint, and throttling message sending for each user, which would likely resolve the issue as the limit is only an issue of someone tries to send an excessive mass email, but I'm not sure.
Can anybody give me a swift kick in the right direction on this? Or maybe a couple different directions if there are options on how to address this? Thanks!
Hi, I am working my way through a migration project and I feel like i am very close to being able to bring my W2012/Ex2013 server into production. I have moved a couple mailboxes over to the new server running W12/E13 and they can send out email, but email will not make it to the mailboxes. I have a hosted spam filter (barracuda) where I can see email for recipient, the email has been delivered to the correct mail server, but has not made it to the mailbox. I still have the W2008/Ex2010 server in production and most mailboxes are there. Any ideas on what might be causing the mail to get hung in the queue. I can see it in the queue.
Sally
I have two customers who can't send me pdf attachments larger than 100kb without them failing or being delayed up to 24hours. Everyone else can send the same or larger attachments through just fine.
Things I have tried to fix the problem :
Disable spam filtering
Disable tarpitting
increase timeout to 2:30:00
Verify MTU is set correctly
Whitelist the IP Address of the sender
Some logs of a file that didn't go through:
2016-01-25T21:37:47.387Z,EXCHANGE01\Default EXCHANGE01,address,0,10.0.1.19:25,x.x.x.x:60062,+,,
2016-01-25T21:37:47.387Z,EXCHANGE01\Default EXCHANGE01,address,1,10.0.1.19:25,x.x.x.x:60062,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-01-25T21:37:47.402Z,EXCHANGE01\Default EXCHANGE01,address,2,10.0.1.19:25,x.x.x.x:60062,>,"220 exchange01.domain.local Microsoft ESMTP MAIL Service ready at Mon, 25 Jan 2016 15:37:46 -0600",
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,3,10.0.1.19:25,x.x.x.x:60062,<,EHLO Zixserver,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,4,10.0.1.19:25,x.x.x.x:60062,>,250-exchange01.domain.local Hello [x.x.x.x],
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,5,10.0.1.19:25,x.x.x.x:60062,>,250-SIZE,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,6,10.0.1.19:25,x.x.x.x:60062,>,250-PIPELINING,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,7,10.0.1.19:25,x.x.x.x:60062,>,250-DSN,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,8,10.0.1.19:25,x.x.x.x:60062,>,250-ENHANCEDSTATUSCODES,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,9,10.0.1.19:25,x.x.x.x:60062,>,250-STARTTLS,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,10,10.0.1.19:25,x.x.x.x:60062,>,250-X-ANONYMOUSTLS,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,11,10.0.1.19:25,x.x.x.x:60062,>,250-AUTH NTLM,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,12,10.0.1.19:25,x.x.x.x:60062,>,250-X-EXPS GSSAPI NTLM,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,13,10.0.1.19:25,x.x.x.x:60062,>,250-8BITMIME,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,14,10.0.1.19:25,x.x.x.x:60062,>,250-BINARYMIME,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,15,10.0.1.19:25,x.x.x.x:60062,>,250-CHUNKING,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,16,10.0.1.19:25,x.x.x.x:60062,>,250-XEXCH50,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,17,10.0.1.19:25,x.x.x.x:60062,>,250-XRDST,
2016-01-25T21:37:47.434Z,EXCHANGE01\Default EXCHANGE01,address,18,10.0.1.19:25,x.x.x.x:60062,>,250 XSHADOW,
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,19,10.0.1.19:25,x.x.x.x:60062,<,STARTTLS,
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,20,10.0.1.19:25,x.x.x.x:60062,>,220 2.0.0 SMTP server ready,
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,21,10.0.1.19:25,x.x.x.x:60062,*,,Sending certificate
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,22,10.0.1.19:25,x.x.x.x:60062,*,CN=exchange01,Certificate subject
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,23,10.0.1.19:25,x.x.x.x:60062,*,CN=exchange01,Certificate issuer name
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,24,10.0.1.19:25,x.x.x.x:60062,*,****,Certificate serial number
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,25,10.0.1.19:25,x.x.x.x:60062,*,****,Certificate thumbprint
2016-01-25T21:37:47.465Z,EXCHANGE01\Default EXCHANGE01,address,26,10.0.1.19:25,x.x.x.x:60062,*,exchange01;exchange01.domain.local,Certificate alternate names
2016-01-25T21:37:47.543Z,EXCHANGE01\Default EXCHANGE01,address,27,10.0.1.19:25,x.x.x.x:60062,*,,"TLS protocol SP_PROT_TLS1_0_SERVER negotiation succeeded using bulk encryption algorithm CALG_AES_128 with strength 128 bits, MAC hash algorithm CALG_SHA1 with strength 160 bits and key exchange algorithm CALG_RSA_KEYX with strength 2048 bits"
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,28,10.0.1.19:25,x.x.x.x:60062,<,EHLO server,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,29,10.0.1.19:25,x.x.x.x:60062,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,30,10.0.1.19:25,x.x.x.x:60062,>,250-exchange01.domain.local Hello [x.x.x.x],
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,31,10.0.1.19:25,x.x.x.x:60062,>,250-SIZE,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,32,10.0.1.19:25,x.x.x.x:60062,>,250-PIPELINING,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,33,10.0.1.19:25,x.x.x.x:60062,>,250-DSN,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,34,10.0.1.19:25,x.x.x.x:60062,>,250-ENHANCEDSTATUSCODES,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,35,10.0.1.19:25,x.x.x.x:60062,>,250-AUTH NTLM LOGIN,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,36,10.0.1.19:25,x.x.x.x:60062,>,250-X-EXPS GSSAPI NTLM,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,37,10.0.1.19:25,x.x.x.x:60062,>,250-8BITMIME,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,38,10.0.1.19:25,x.x.x.x:60062,>,250-BINARYMIME,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,39,10.0.1.19:25,x.x.x.x:60062,>,250-CHUNKING,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,40,10.0.1.19:25,x.x.x.x:60062,>,250-XEXCH50,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,41,10.0.1.19:25,x.x.x.x:60062,>,250-XRDST,
2016-01-25T21:37:47.574Z,EXCHANGE01\Default EXCHANGE01,address,42,10.0.1.19:25,x.x.x.x:60062,>,250 XSHADOW,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,43,10.0.1.19:25,x.x.x.x:60062,<,MAIL FROM:<****> SIZE=278779,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,44,10.0.1.19:25,x.x.x.x:60062,*,address;2016-01-25T21:37:47.387Z;1,receiving message
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,45,10.0.1.19:25,x.x.x.x:60062,<,RCPT TO:<recipient@domain.net> ORCPT=rfc822;*****@*****,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,46,10.0.1.19:25,x.x.x.x:60062,<,DATA,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,47,10.0.1.19:25,x.x.x.x:60062,>,250 2.1.0 Sender OK,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,48,10.0.1.19:25,x.x.x.x:60062,>,250 2.1.5 Recipient OK,
2016-01-25T21:37:47.605Z,EXCHANGE01\Default EXCHANGE01,address,49,10.0.1.19:25,x.x.x.x:60062,>,354 Start mail input; end with <CRLF>.<CRLF>,
2016-01-25T21:37:47.683Z,EXCHANGE01\Default EXCHANGE01,address,50,10.0.1.19:25,x.x.x.x:60062,-,,Remote