For our Exchange Server 2013 organisation we use third party software for antispam and antimalware called Trend Micro Scanmail for Exchange. We are having some issues with sending mail from an application with a specific mailbox.

Is it possible to bypass a transport agent for a specific SMTP-address?

[PS] C:\Windows\system32>Get-TransportAgent | fl

RunspaceId            :
Enabled               : True
Priority              : 1
TransportAgentFactory : TrendMicro.SMEX.hookE12TransportAgent.hookE12RoutingAgentFactory
AssemblyPath          : D:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll
Identity              : ScanMail Routing Agent
IsValid               : True
ObjectState           : New

RunspaceId            :
Enabled               : True
Priority              : 2
TransportAgentFactory : TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory
AssemblyPath          : D:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll
Identity              : ScanMail SMTP Receive Agent
IsValid               : True
ObjectState           : New

RunspaceId            :
Enabled               : True
Priority              : 3
TransportAgentFactory : Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory
AssemblyPath          : D:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Rule\Microsoft.Exchange.Me
                        ssagingPolicies.TransportRuleAgent.dll
Identity              : Transport Rule Agent
IsValid               : True
ObjectState           : New

RunspaceId            :
Enabled               : True
Priority              : 4
TransportAgentFactory : Microsoft.Exchange.Transport.Agent.Malware.MalwareAgentFactory
AssemblyPath          : D:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Antimalware\Microsoft.Exch
                        ange.Transport.Agent.Malware.dll
Identity              : Malware Agent
IsValid               : True
ObjectState           : New

RunspaceId            :
Enabled               : True
Priority              : 5
TransportAgentFactory : Microsoft.Exchange.TextMessaging.MobileDriver.TextMessagingRoutingAgentFactory
AssemblyPath          : D:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.MobileDriver.dll
Identity              : Text Messaging Routing Agent
IsValid               : True
ObjectState           : New

RunspaceId            :
Enabled               : True
Priority              : 6
TransportAgentFactory : Microsoft.Exchange.TextMessaging.MobileDriver.TextMessagingDeliveryAgentFactory
AssemblyPath          : D:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.MobileDriver.dll
Identity              : Text Messaging Delivery Agent
IsValid               : True
ObjectState           : New

Signature?

Hello 

I'm not very experienced with Exchange 2013 but I have installed Exchange 2013 sp1

I have managed to add users and are able to connect to exchange server but they cannot send email internally and externally when I send email they are stack in Queue Viewer 

Please help me  

When we send emails over about 15 MB in size to other Exchange servers in our system, or to an external email provider, we sometimes see this error---

----

==

We have checked many network settings (based on information in various forum items about this error), and we think that is not the problem.

This only happens at one of our Exchange locations.     
The other locations can send emails of 25 MB and they are delivered correctly / no errors.
The ping time from the  location sending emails,  to the Exchange location receiving emails,  is 430 ms.
That connection is over the Internet with a VPN.

It seems like Exchange thinks this is taking too long, or too many attempts, or something like that.
   (Since somewhat smaller emails are delivered OK.)

Is there an Exchange configuration parameter in Transport service or similar, that we can change, to tell Exchange to "wait a little longer",   before issuing that error ?

Thanks

Exchange 2013 CU10,  Windows server 2012 Standard, Outlook 2013, 
SMTP,

=======

I have a receive connector in Exchange 2010 that will allow an anonymous relay from a device. The device will only pass the UPN name i.e.  device1   and the 2010 connector will append the defaultdomain setting for both the mail from: and recpt to: 

In 2013 with the exact same defaultdomain setting it will not append the the default domain that is configured. Running Exchange 2013 SP1 Cu11 

Anyone else run across this ? very easy to repro 

Hello,

I would like to get some advise on setting up the SPF record for Exchange on-premises 2013 that has Google Message Security (Postini) as its front-end spam filtering service. 

Domain: mail.domain.com

External IP for mail server: 37.X.X.62

Default Gateway: 37.X.X.61 (Outbound Email) - The external receipts receive the Emails from mail.domain.com (37.X.X.61).

PTR Record:

PTR record is currently setup for the default gateway IP 37.X.X.61, I would also like to add the PTR record for my mail server IP. Is it recommended to have a PTR record published for the mail server IP as well? Technically, 2 IP addresses will be pointing to one PTR record mail.domain.com. 

Thanks!

L.S.

Having an issue with the following:

O365 users mail an on-prem user, and not get the prim alias (company.com) but the on.microsoft.com
On the Exchange server the primairy SMTP is company.com.

What could be the issue? It's the auto-complete on the clients Outlook that makes it on.microsoft.com.

Thanks a bunch gents.

Hello,

We have Exchange 2013. One user send a mail to a particular group, the  mail appears in the sent items folder in outlook (visible in OWA as well). The issue is that the mail is not delivered to recipients and there is no information for this message in the tracking logs. Does it mean message goes to sent items before it is picked up by  the server for delivery? How this can be troubleshooted? 

Thank you.

Hello,

We have Exchange server 2013 roll up 10. From internal network we use recieve connector for printers and scanner and then we can send e-mail accepted domains and external domains without problem.

Also our e-arsiv system works external network. We need to send e-mail via our exchange server. I created one user then create one connector ı have added our server public IP but we can not send e-mail. 

issue is

"Sending email failed with Caused by: javax.mail.MessagingException: [EOF]

"

Also ı run this powershell but nothing changed

Add-ADPermission "name of connector" -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

How can we solve this problem?

Thanks.

Murat ER Microsoft Certified Systems Administrator

Hello All,

We are running 2000 mailboxes in Zimbra and planning to move Emailing-Infrastructure on Microsoft Exchange Servers. 

We have planned to install Exchange 2016 Sp1 Servers and set up co-existence between Zimbra & Exchange.

Please help with following Queries.

1/  Which third-party tool is worthy ( Cheap & Best) for Zimbra to Exchange Migration.

2/  We dont want to move MX record, which is currently Pointed to Zimbra. We will move MX record once all users will migrated to Exchange2016. How can we achieve the mail-flow between Zimbra to Exchange2016 and vise-versa. 

Regards, Rohit

we have 3 exchange 2013 servers, recently our team deployed a new FAX server, when fax server sent an email to EX1 replay directory it is delivering to recipient,  but if fax arrives to EX2 replay directory it was getting struck there only and not delivering to any where. same case as EX3 too. Emails are pilled up in EX2 and Ex3 .But if i copy EX2 email to EX1 Replay directory email is getting delivered to recipient. Currently PAM hosted on EX1. Suspecting is there any issue with Ex2,EX3 replay directory?

Hi everyone,

i have problem i cannot receive email from particular domain, i has been checked the log i will post bellow please help me to solve the issue:

14:47:03.950Z,mailserver\Client,08D2F8098021CFCF,1,173.16.200.100:25,153.2.232.136:30659,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2016-04-06T14:47:03.950Z,mailserver\Client,08D2F8098021CFCF,2,173.16.200.100:25,153.2.232.136:30659,>,"220 mailserver.domain.com Microsoft ESMTP MAIL Service ready at Wed, 6 Apr 2016 17:47:03 +0300",
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,3,173.16.200.100:25,153.2.232.136:30659,<,EHLO magma10.ups.com,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,4,173.16.200.100:25,153.2.232.136:30659,>,250-mailserver.domain.com Hello [153.2.232.136],
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,5,173.16.200.100:25,153.2.232.136:30659,>,250-SIZE,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,6,173.16.200.100:25,153.2.232.136:30659,>,250-PIPELINING,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,7,173.16.200.100:25,153.2.232.136:30659,>,250-DSN,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,8,173.16.200.100:25,153.2.232.136:30659,>,250-ENHANCEDSTATUSCODES,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,9,173.16.200.100:25,153.2.232.136:30659,>,250-STARTTLS,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,10,173.16.200.100:25,153.2.232.136:30659,>,250-AUTH NTLM,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,11,173.16.200.100:25,153.2.232.136:30659,>,250-8BITMIME,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,12,173.16.200.100:25,153.2.232.136:30659,>,250-BINARYMIME,
2016-04-06T14:47:04.621Z,mailserver\Client,08D2F8098021CFCF,13,173.16.200.100:25,153.2.232.136:30659,>,250 CHUNKING,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,14,173.16.200.100:25,153.2.232.136:30659,<,STARTTLS,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,15,173.16.200.100:25,153.2.232.136:30659,>,220 2.0.0 SMTP server ready,
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,16,173.16.200.100:25,153.2.232.136:30659,*,,Sending certificate
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,17,173.16.200.100:25,153.2.232.136:30659,*,CN=mail.domain.com,Certificate subject
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,18,173.16.200.100:25,153.2.232.136:30659,*,"CN=GeoTrust DV SSL CA - G4, OU=Domain Validated SSL, O=GeoTrust Inc., C=US",Certificate issuer name
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,19,173.16.200.100:25,153.2.232.136:30659,*,02E6E0,Certificate serial number
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,20,173.16.200.100:25,153.2.232.136:30659,*,E790262288D9D92EC4F366FF102B96BA5BD3B0BB,Certificate thumbprint
2016-04-06T14:47:04.808Z,mailserver\Client,08D2F8098021CFCF,21,173.16.200.100:25,153.2.232.136:30659,*,mail.domain.com;mailserver.domain.com;autodiscover.domain.com,Certificate alternate names
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,22,173.16.200.100:25,153.2.232.136:30659,<,EHLO magma10.ups.com,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,23,173.16.200.100:25,153.2.232.136:30659,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,24,173.16.200.100:25,153.2.232.136:30659,>,250-mailserver.domain.com Hello [153.2.232.136],
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,25,173.16.200.100:25,153.2.232.136:30659,>,250-SIZE,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,26,173.16.200.100:25,153.2.232.136:30659,>,250-PIPELINING,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,27,173.16.200.100:25,153.2.232.136:30659,>,250-DSN,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,28,173.16.200.100:25,153.2.232.136:30659,>,250-ENHANCEDSTATUSCODES,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,29,173.16.200.100:25,153.2.232.136:30659,>,250-AUTH NTLM LOGIN,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,30,173.16.200.100:25,153.2.232.136:30659,>,250-8BITMIME,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,31,173.16.200.100:25,153.2.232.136:30659,>,250-BINARYMIME,
2016-04-06T14:47:06.025Z,mailserver\Client,08D2F8098021CFCF,32,173.16.200.100:25,153.2.232.136:30659,>,250 CHUNKING,
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,33,173.16.200.100:25,153.2.232.136:30659,<,MAIL FROM:<prvs=09018d05a2=aebada@ups.com>,
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,34,173.16.200.100:25,153.2.232.136:30659,*,08D2F8098021CFCF;2016-04-06T14:47:03.950Z;1,receiving message
2016-04-06T14:47:06.618Z,mailserver\Client,08D2F8098021CFCF,35,173.16.200.100:25,153.2.232.136:30659,>,250 2.1.0 Sender OK,
2016-04-06T14:47:07.195Z,mailserver\Client,08D2F8098021CFCF,36,173.16.200.100:25,153.2.232.136:30659,<,RCPT TO:<amit@domain.com>,
2016-04-06T14:48:13.060Z,mailserver\Client,08D2F8098021CFCF,37,173.16.200.100:25,153.2.232.136:30659,>,250 2.1.5 Recipient OK,
2016-04-06T14:49:24.229Z,mailserver\Client,08D2F8098021CFD6,0,173.16.200.100:25,50.31.57.60:45926,+,,

Thanks

Exchange 2013 version :

Enterprise
Version 15.0 (Build 1130.7)

2 CAS servers

4 Mailbox servers

Hybrid Exchange and EOP is used for on-premise exchange

Mails get stuck in the Submission queue with error : A storage transient failure has occurred during content conversion.

Changed RemoteDomain setting 'TNFEEnabled' from $Null to $False -> NOK

Changed RemoteDomain TNFEEnabled from $False to $True -> OK, but external receipients are receiving mails with 'Winmail.dat'

Current setting TNFEEnabled = $Null

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

We have attached transport rule (attached) which doesn't work after Exchange 2013 CU9 upgrade.

Recreated the rule but no luck

SAH

Hi Team,

I have this simple query trying to figure out exact answer of it.

When a person send an email of 1 MB to 10 people the mail is delivered to respective database where recipients mailbox is stored.

Now if out of those 10 people forwards same message to 10 more people.

So what I would like to understand is complete storage process.

How much space it will take for example stated above is it going to take 20 MB ? I know it will not but would like to know from you experts.

What happens when any one forwards email to some one else.. how message id changes.. how pointers are created.. how much space will be utilized.

Please help.

Thanks

Abhishek

Abhishek Saxena

Dear all

My setup is like this:

Edge transport in Parent domain, three exchange servers in parents domain, (2 = exch 2007 and 1= exch 2013) where the primary exchange 2007 has been migrated to 2013.

the connection between the Parent and Child is a VPN connection

In the child domain, I had one exchange which has been migrated to 2013.

Mail flow Issue:

I am able to send and receive email from internet to my parent domain with no problem through the edge running on exchange 2007 SP3 (all exchange server 2007 have SP3)

I am able to send email to internet via different ISP on the child domain, and am able to receive emails from internet to child domain via edge at the Parent domain.

I am able to send email from my parent domain to my child domain,

BUT

I am not able to send email from my child domain to my parent domain, they are all queuing on the exchange server 2013 on the child domain.

I need guidance on what could be blocking the mail from from the child domain to parent domain

Hope my explanation is clear, 

Thanks Team in advance.

Regards

Michael

Our AD domain is ad.domain.com and our email uses the top level domain of domain.com.  However when a user sends an email to user1@ad.domain.com it eventually bounces back with a delivery failed message after a few days of retrying.  When an email is sent to user1@new.domain.com (which is not setup anywhere in exchange or DNS) it immediately bounces back.

Domain.com is set as the accepted domain for exchange as well.  I'm assuming that because our active directory domain is ad.ccrsb.ca that the system thinks its a valid mail domain and tries to send mail to it.  I'm wondering if anyone knows a way to have email sent to @ad.domain.com to immediately bounce back to the user just like sending to another invalid mail domain.  We don't want email sent to ad.domain.com to go through to the users at all because that will not stop users from sending to the bad addresses.

Thanks in advance,

Matt

Hello, everybody!

Sometimes we receive messages with double zipped executables. For example, there is attachment named "report.zip" with file "report_new.zip" inside. And file "report.exe" in "report_new.zip".

How can I tune my Exchange to check double zipped executables?

Thx