I have a problem with my exchange server, because one e-mail does not enter the mailbox, even though the Comodo antispam e-mail log has entered our server, after I investigated, there were some irregularities when I used the tracking message there was a HAREDIRECTFAIL status, then under it was a log RECEIVE but with an empty recipient, I think that's the root of the problem, this is different from the next image where after HAREDIRECTFAIL then RECEIVE appears with the same recipient name.

Hi,

We use Exchange Server 2010 standard version. We have one mailbox and one hubcas server.

We frequently have email queue issue from the gateway to hubcas server. The mails used to get held in gateway and not reaching hubcas server. Journaling is enabled for all the messages in each database properties.

Jornaling is done to a mailbox in a database.

Below are the events:

A message with the Internal Message ID 14077388 was rejected by the remote server.  This message will be deferred and retried because it was marked for retry if rejected.  Other messages may also have encountered this error.

Also from queue viewer

Identity: hubserver1\166519\14700652
Subject: subject1
Internet Message ID: <079800ee-617d-409f-bb0a-c944732023b7@journal.report.generator>
From Address: <>
Status: Ready
Size (KB): 533
Message Source Name: Journaling
Source IP: 255.255.255.255
SCL: 0
Date Received: 10/31/2018 9:44:06 PM
Expiration Time:
Last Error: 421 4.4.2 Connection dropped due to ConnectionReset
Queue ID: hubserver1\166519
Recipients:  journaling@journal.domain.com;2;2;421 4.4.2 Connection dropped due to ConnectionReset;0;CN=Outbound to gateway,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=group

Identity: hubserver1\166519\14700652
Subject: subject2
Internet Message ID: <079800ee-617d-409f-bb0a-c944732023b7@journal.report.generator>
From Address: <>
Status: Retry
Size (KB): 533
Message Source Name: Journaling
Source IP: 255.255.255.255
SCL: 0
Date Received: 10/31/2018 9:44:06 PM
Expiration Time:
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.
Queue ID: hubserver1\166519
Recipients:  journaling@journal.domain.com;3;2;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.;0;CN=Outbound to gateway,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domains,DC=group

Please also find the output of below command.

Please let me know how do I resolve this issue.

This issue gets resolved automatically but it happens again after some months.

Hello,

I have an Exchange Server 2013 and i want to configure it to send mail through my antispam.I have configured a custom send connector and then returns the error that i have mentioned in the title.I'll try to explain how i have the system:

All correct. Now i want to send mail through the antispam:

have set a custom send connector redirecting mail to my antispam and the antispam relay outside.In receive connector i have not set anything because mail is already receiving through the antispam.With this setup i get the error: 554 5.4.6 Hop count exceeded - possible mail loop

If i connect directly to the antispam and do a send test, it sends correctly. I think that the problem is in the connectors.

Someone can help me?

Thanks and regards.<span title="Para recibir correo tengo lo siguiente: internet > firewall > antispam en dmz > servidor exchange ">

Hi Everyone,

I have exchange 2010 at the moment (migrating to online next year) and i have task re GDPR purposes to set a 3 to 5 minutes delay across the board to all outgoing emails.

I know how to do this on the outlook level using message rules, but as you know you cant control this using GPO.

So i'm wondering if there's anyway to do this from the server side through the transport rules or something? i have tried and i was searching the internet but cant find any solid answers.

Please let me know your thoughts and if you have a solution.

Thank you,

Kind regards,

Karim,

Hey all, we have a single Exchange 2013 server and we're all connecting through Outlook 2013. Some of my users are having their emails delayed by up to a couple of days. I had one of our maintenance supervisors show me and it actually failed to send while I was there (I was amazed it failed while he was showing me-doesn't always work that way). He tried to send an email four times and it failed each time. Then he forwarded one from his Outbox and two others left with it. I'm not an Exchange guy but I have done basic tasks in it. In my Exchange 2007 server I could enter an email's information like who sent it and who was it sent to and when and I could see the tracking information. I checked the tool box in my 2013 server and I can't find anything like that. Any ideas on what's going on or what to look for?

Thanks,

Joe B

The organization is constantly getting the following error message on Exchange Server 2013 

We are constantly getting this error, kindly let us know how to fix the issue permanently 

==================================================================================================

MSExchangeTransport has detected a storage error on database(Transport Mail Database), DB action (DeemTransient), Process action (Stop) [Microsoft.Isam.Esent.Interop.EsentAttachedDatabaseMismatchException: An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info

at Microsoft.Isam.Esent.Interop.Api.JetInit(JET_INSTANCE& instance)
at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()].

==========================================================================

Transport Mail Database: The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport service is shutting down. The exception is Microsoft.Isam.Esent.Interop.EsentAttachedDatabaseMismatchException: An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info

at Microsoft.Isam.Esent.Interop.Api.JetInit(JET_INSTANCE& instance)
at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()

Hello,

We deployed a Exchange Hybrid with O365 and an on-prem Ex2013 Server. We use the option "Centralized mail flow" as configured in the HCW.

Goal is that messages sent from o365 mailbox are routed through the on-prem ex2013 server and then to the external recipient.

When we test this mailflow, we get an error from the Ex2013 server, that the relay is not permitted. error 550 5.7.1

The HCW did not change anything on the Ex2013 receive connector.

I expected that the HCW would make all required modifications needed to allow the Ex2013 to "relay" mails from o365 to external recipients. IS this assumption correct?

Do I need to configure a new receive connector on Exchange to allow this mailflow? If yes, how would the connector be configured?

please any advice on this issue. Thanks

HOD receive OutOfOffice (OOF) from OOF user when he send’s bulk email using Distribution Group.

When assistance send bulk email with "send as" permission Department head receive the email that by design of Exchange.

HOD doesn't want delegate to "send on behalf ", it has to be "send as"

End goal is to stop the OOF message for the email which is send by delegate.

We can’t use transport rule as it stop all the OOF message for Department head email.

Any advice? 

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'm running Exchange 2103, I have two CAS severs and 5 mailbox servers. On my cas servers I receive the following errors in my SMTP SEND Logs:

EHLO options between current server and proxy target do not match : Xrdst. Critical non matching options : Xrdst. Failing over.

The above error occurs on 3 of the 5 mailbox servers. Due to this error all mail is relayed through the 2 mailbox servers.

Any help would be appreciated.

exchange 2010 sp2

hello In my organisationnobody cant send email to all users except some management users 

how come there is 3 users that can send mail to all users . thay are not in the management list   hwo can i prevent them from sending 

thx

We have Exchange 2013. Below are the versions.

Version 15.0 ‎(Build 847.32)‎
Version 15.0 ‎(Build 775.38)‎

Both are mailbox,cas servers

We face outlook disconnection issues.

below are some event IDs

2200

2136

15021

1021

106

We see CPU use high, so increased the processor and also memory and now that is normal. Still we have the issue.

Outlook shows status as disconnected. Somtimes it get connected but still goes disconnected. restarted the servers multiple times.

OWA is working fine.

Below are some screenshots.

The above when tried to modify the front end connector max input value. AD is reachable, restarted also. Same issue exists.

This issue is with one of the outlook clients. Restarted the client multiple times.

The above when trying to open EMS on one of the servers. Restarted, same issue.

Kindly let me know how to resolve this. Please move to necessary forum if this is not the correct forum.

I have two servers with both the mailbox and client access role installed. I have come to realize that Content Filter Agent runs before Transport Rule Agent runs. This affected me because I was using Transport Rules to set an SCL so that when ti went though the Content Filter Agent, the proper requirements would apply. But even though I was setting SCL to 6 when SPF Failed, mail was still going to my users mailbox even thought I have SCL 6 to go to my spam qurantine mailbox. The reason for that was because the Content Filter Agent is running on the OnEndOfData event and the Transport Rule was running on OnResolvedmessage event which occurs after the OnEndOfData event. When I ran Get-TransportPipeline |fl event,transportagents on both my servers to confirm that was the case, not all agents are running on each server. For server 1, I got:

Event           : OnConnectEvent
TransportAgents : {}

Event           : OnHeloCommand
TransportAgents : {}

Event           : OnEhloCommand
TransportAgents : {}

Event           : OnStartTlsCommand
TransportAgents : {}

Event           : OnAuthCommand
TransportAgents : {}

Event           : OnProcessAuthentication
TransportAgents : {}

Event           : OnEndOfAuthentication
TransportAgents : {}

Event           : OnXSessionParamsCommand
TransportAgents : {}

Event           : OnMailCommand
TransportAgents : {Inbound Trust Agent}

Event           : OnRcptCommand
TransportAgents : {}

Event           : OnDataCommand
TransportAgents : {}

Event           : OnEndOfHeaders
TransportAgents : {Inbound Trust Agent}

Event           : OnProxyInboundMessage
TransportAgents : {FrontendProxyAgent}

Event           : OnEndOfData
TransportAgents : {}

Event           : OnHelpCommand
TransportAgents : {}

Event           : OnNoopCommand
TransportAgents : {}

Event           : OnReject
TransportAgents : {}

Event           : OnRsetCommand
TransportAgents : {}

Event           : OnDisconnectEvent
TransportAgents : {}

Event           : OnSubmittedMessage
TransportAgents : {RMS Decryption Agent, Malware Agent, Text Messaging Routing Agent, RMS Encryption Agent, Journal
                  Agent}

Event           : OnResolvedMessage
TransportAgents : {Prioritization Agent, Transport Rule Agent, Index Routing Agent}

Event           : OnRoutedMessage
TransportAgents : {RMS Encryption Agent, Prelicense Agent, Journal Agent, Redirection Agent}

Event           : OnCategorizedMessage
TransportAgents : {Journal Report Decryption Agent, Outbound Trust Agent}

and for server 2 i got: 

Why would they be different if both servers have the same roles? One thing I thought was that I had not enabled antispam on server 1 but I know I did. I ran the powershell command on both servers. 

On a second note, does anyone know how I can get the Transport Agent to run before the Content Filter Agent?

Good day.

I have Exchange 2016 CU8 installed. Two nodes setup with DAG. It works fine until I tried to enable the Malware Agent. Once it is enabled and Exchange transport service is restarted, all emails are stucked in submission queue with "Last Error: Message deferred by categorizer agent.".

I tried to use Set-MalwareFilteringServer to bypass the scanning but mail flow still not working.

However as soon as I disabled Malware agent, the mailflow is back working right away. 

Any suggestion? Why malware agent doesn't work well?

Thanks!

I have Exchange Server 2013 with CU 21 and added TLS 1.2 registries on my Exchange Servers. Recently ran Exchange HCW, I am unable to receive mails from office 365 mailboxes using TLS 1.2. I have third party certificate while validating out bound connector on office 365 it shows following error " The validation is failed with error "450 4.4.317 Cannot connect to remote server [Message=451 4.4.0 Socket error SocketError]" when i am enabling TLS on connector settings".

Hi.

Whenever a user sends an e-mail from a mail-enabled public folder, we get event ID 2009 in the eventlog on the server.

Here is an example:

[Process:Microsoft.Exchange.RpcClientAccess.Service PID:8508 Thread:21] Error occurred while resolving the Active Directory object for from email address field: '/CN=Mail Public Folder/CN=Version_1_0/CN=e8220731-f0fa-4ddc-8468-b4c0b03fd014/CN=00000000F9EEE5CC0E1CEA4399F554BE45C282950100553B1102F06969459294143534D98B4D0001030A79E30000'. Audit log will not be generated for this case. Exception details:
Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The Active Directory user wasn't found.
   at Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.FromProxyAddress(IRecipientSession session, String proxyAddress, RemotingOptions remotingOptions)
   at Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.FromProxyAddress(ADSessionSettings adSettings, String proxyAddress, RemotingOptions remotingOptions)
   at Microsoft.Exchange.Data.Storage.ExchangePrincipal.FromProxyAddress(ADSessionSettings adSettings, String proxyAddress)
   at Microsoft.Exchange.Data.Storage.COWAudit.GetSubmitEffectiveMailboxOwner(MailboxSession session, CallbackContext callbackContext)

The mails are sent correctly, but transport rules are not applied to them. So as we have some transport rules that copy mails with specific recipients, this is a problem.

The only references I can find to this error are related to not being able to send to the folder, and does not seem to apply to my situation.

Hello folks,

We moved our datacenter over the weekend and our public IPs.  We have a destination NAT rule that translates our assigned public IP for mail to (for example) 96.68.102.139 to our internal Exchange server IP.

However, when our server initiates communication, it is seen on the internet as coming from our firewall IP: 96.68.102.140.

Our MX record matches the .139, but our TXT (SPF) record is set to .140.  Like I said the source IP from exchange initating to the internet is .140.

Do we need a source NAT rule for exchange to match its .139 assignment and also our TXT record?

Thanks

Hi,

We have some DGs which only allows to send mails "Only Senders inside my organization". But when external recipients sends mails to this group, they don't receive a NDR. We need to get a NDR when external recipients sends mails to these DGs.

 Please advise.

Regards,

Kavindu

Hi,

What are the free tools available in tracking an email.

Scenarios:

1- Exchange Server to Exchange Server(inside domain)(2 Mailbox severs(2013))

2- Exchange Server to Office 365(Hybrid setup)- Not the email tracking of Exchange admin center.

3- Exchange Server to outside domain like gmail(once the mail handed over to Exchange Server edge transport to outside any server if that does not reach gmail, where do we check)

Thank you.