Hi All,

We have an on premises server hosting 6 domain names. 4 of these work perfectly for send receive however 2 (the same 2) will not send with mail stuck in the queue but will receive.

The 2 that will not send and are stuck in the queue get error 452 which is usually due to resources however all resources are fine. We have checked the domains to ensure they are not on any block lists etc.

The 6 domains have worked perfectly for over 18 months and the 2 that started to fail to send both failed at around the same time.

There are no issues we can see in the event viewer.

Can anyone shed any light on where else we can look...???

Many thanks.

We are at the tail end of our co-existence migration from exchange 2007 to 2013 and have noticed recently that all external mail is flowing through our old 2007 server.  Is there a way to test and see which receive/send connectors are in use when external email comes in?  We can see that the mail hits our SPAM firewall, and is routed to our edge servers, then sent from the edge to our old 2007 mail server which then transfers the item to our 2013 mail server.

Another question would be do we even need to forward the mail from the SPAM firewall to the Edge or should it go directly to the mail servers?

Also, could there be some kind of edge subscription on the old server that is affecting the mail flow?

Any suggestions/help would be greatly appreciated.

I am attempting to use the following to export some of the properties of email address policies to CSV using EMS;

Get-EmailAddressPolicy | Select Name,LdapRecipientFilter,RecipientFilterApplied,IncludedRecipients,EnabledEmailAddressTemplate,EnabledPrimarySMTPAddressTemplate | Export-Csv C:\Temp\temp.csv

When I do that, it creates a CSV with the appropriate fields, but the EnabledEmailAddressTemplate property (that returns the appropriate information in EMS) returnsMicrosoft.Exchange.Data.ProxyAddressTemplateCollection for a value, not the expected SMTP addressing.

Hi 

i need u r help please inform How To Disable outlook  to All Users and Single user  Exchange 2010 / 2013

Satish Chaturvedi Mob-9990806001

Relatively new to admining an exchange server and my setup was inherited. I have multiple users reporting that we have a delay in the early morning hours and I am just trying to isolate and either explain or resolve the issue. We are running exchange 2010 on server 2008.

Here is an actual description I got from a user:

"Noticed some odd behavior around 3 to 4 am where automated emails are executing, but being held up somewhere in the email process. As of today, script finished at 3:05am, but email did not get to inbox until 4:27am"

Any help would be greatly appreciated.

HI,

I am trying to get a hybrid system working but am hitting a snag with The Remote Connectivity Analyser. When I run it I get the error below.

It does the same on mail.*****.co.uk so I am stuck. My mailserver has a different name but I have DNS records for both the names that fail.

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.*****.co.uk:443/Autodiscover/Autodiscover.xml for user admin@*****.co.uk. The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. 

	Additional Details
	A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown. HTTP Response Headers: Connection: close Content-Length: 315 Content-Type: text/html; charset=us-ascii Date: Wed, 27 Apr 2016 21:49:26 GMT Server: Microsoft-HTTPAPI/2.0 Elapsed Time: 112 ms.

I have a user who has turned off read receipts in her mailbox. However, anytime she sends an email she gets a read receipt. I've already checked the registry key and the value is set correctly. I also created multiple hub transport rules thinking this would be the easy fix but that didn't work either.  The mail profile has been recreated and so has the Windows profile. I'm now out of options. Has this problem been reported before? Is there an update that can help resolve this issue?

We're using Exchange 2013

Hi All,

After migrated to exchange 2013, everything has been working fine for about four weeks than, suddenly  below warning message started to get logged every 15 min in the Event log... Email flow is still OK, no updates or any other changes have been done on the Server. Any help would be greatly appreciated.

Exchange 2013 CU8  Mailbox Server  + CAS Server running on the same Hyper-v VM.

The Event Details  “The SMTP availability of the Receive connector Default Mailbox Delivery was low (0 percent) in the last 15minutes."

Tried to increase the mailbox deliveries throttling values by following commands. issue still there

Set-MailboxTransportService -MaxConcurrentMailboxDeliveries 50

Set-TransportService -MaxConcurrentMailboxDeliveries 50

Issue is still there?

Thank you in advance.

Hello,

When reply massaging in Hebrew I'm getting encoding error massage, after investigating the issue I understood that I need to disable UTF-8 characters on OWA, I found the following syntax: Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -OutboundCharset AlwaysUTF8

How can I use this syntax to not use UTF-8?

Regards,

Dvir

Hi All,

I would like to know if it's possible to setup a kind of buffer for outbound mails.
We would like to be able to have a copy of the mails and, if needed, we can resend the e-mails.

I've looked into the following options, but it seems they're not what we're looking for:

- Catch All mailbox: get's a copy, but resending e-mails as the Catch-All mailboxuser, not the original sender
- Journalling: same as the above.

Are there any other options?

Thanks in advance.

Kind regards,

Matthijs

Hi,

I've spent the past few days reading up on the Hybrid mode facility and I got the Remote connectivity facility running okay after a few blips. I also managed to get the wizard to run through until I get to the last bit about

HCW8064 -
The HCW has completed, but was not able to perform the OAuth portion of your Hybrid configuration. If you need features that rely on OAuthhttps://technet.microsoft.com/library/dn497703(v=exchg.150).aspx, you can try running the HCW again or manually configure OAuth using these manual stepshttps://technet.microsoft.com/library/dn594521(v=exchg.150).aspx.
https://support.microsoft.com/kb/3089172

It says its not important so I carried on.

I am a bit confused though about what it can and cant do.

I am in a school by the way.

I have Azure syncing with O365 and all the students and staff are listed. When I look at the mailboxes on the O365 tab there aren't any... when I try and logon it doesn't work. I thought the beauty of this was that it offered a single point of access to your mailbox.

I have tried to move a user (I will be keeping the majority on my premises) which comes up with the error.

Data migrated:                        
Migration rate:                        
Error:                        MigrationRecipientNotFoundException: A recipient wasn‎'t found for "boysboarding@*********.co.uk" on the target. Create a recipient of the appropriate type for this migration on the target and try again.

So I tried again but this time I assigned a license in the admin console. This allows me to logon to office 365 but with an empty mailbox?? I know there are mail items in there when I login on my premises. if I try and migrate the users mailbox I get

Migration rate:                        
Error:                        InvalidRecipientTypeException: Unsupported recipient type ‎'Mailbox‎' provided. Only ‎'Mailuser‎' is supported for this migration type.

Its taken me ages to even get to this stage and now I am stuck

Dear Microsoft Community,

I have an issue and am in dear need of help:

Exchange 2013 CU11

Sent Mails get stuck in Drafts folder when sent from OWA
In Outlook they go to the Sent Mail folder but do not reach the Queue.
Only Users from Particular Databases at random times apparently are affected and only sporadically and for short periods of time (1-2 hours) after which everything stars working fine again.
If I move a Mailbox to one of the affected Databases the user starts exhibiting the Issue. Also if I move Mailbox to a database without problems the issue stops.
All databases are affected at random unrelated to the server they are on. There is one server where the Issue occurs more often than on the others.
It matters not if Mails are sent to external or internal addresses.
Only outgoing mails affected Incoming works fine.

Issue appeared immediately after an unexpected restart of the servers related to a storage outage.
I have correlated the issue with an Event:
Does anyone know what the MailSubmissionWatermarksProbe is about?
========================================================================

Log Name:      Microsoft-Exchange-ManagedAvailability/Monitoring
Source:        Microsoft-Exchange-ManagedAvailability
Date:          4/20/2016 3:52:12 PM
Event ID:      4
Task Category: Monitoring
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      S1EX2k13
Description:
Watermarks for one or more database(s) have been below the age threshold of 01:00:00 for last 02:00:00.

 Last Reported Database: Database1 
 Last Event Counter: 378203086 : 4/20/2016 1:39:33 PM 
 Watermark(s): MailboxTransportSubmissionAssistant : 377652258 : 4/20/2016 7:58:03 AM 
 Exception: Watermarks are behind for database 'Database1' 

 Diagnostic Command: Invoke-MonitoringProbe -Identity 'EventAssistants\MailSubmissionWatermarksProbe\Database1' -Server S1EX2k13 

 Command to get all unhealthy watermarks monitors: Get-ServerHealth -Identity 'S1EX2k13' -HealthSet 'EventAssistants' | ?{$_.Name -match 'MailSubmissionWatermarksMonitor' -and $_.AlertValue -ne 'Healthy'}

========================================================================
Also the submission service restarts about once or twice per hour on all servers.
========================================================================

Event ID:      7031
Computer:      S1EX2k13
Description:
The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

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

DNS is fine and configured correctly. 
There is no Backpreasure.
There is enough space.
No performance issues.
I've been unable to corelate any other Event to the issue.

LG,


Alex D

Hi

I configured successfully Azure RMS in my organisation. Now I got a new requirement from the security team to protect all existing data in my Exchange DBs with RMS. For Files and Sharepoint I can use the bulk tool, but for Exchange I cant find a solution. For my understanding every emails need to get through the transport service to protect it and its not possible to do it direct on the store level. Is there any solution to protect existing files with RMS in my Exchange organisation?

Thanks for your help!

Regards
Joerg

Hi Guys,

Some confusion in RPC Client Access Server & Client Access Server.

How to Work RPC Client Access Server

Satish Chaturvedi Mob-9990806001

Dear Forum Users,

I have a problem with Mail server Exchange 2013 that running with both CAS and MB. The power cut off make machine accidentally shutdown, and After starting up machine, Mail server is not able to Send/Received email. not working both internal and external. Please kindly advise me about idea of problem that possible happen, i never meet this problem before. thank you in Advance. 

Regards,

SAM

Sokneang SAM

Hello,

the problem happens after you update to CU9 from CU8: authenticated emails from computer running WSUS and File Server Resource Manager (that autenticate using the computer account) are not running anymore. Before they was running.

This is the debug of the SMTP conversation AT THE CU8 -- RUNNING

2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,0,10.0.0.2:25,10.0.0.1:51258,+,,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,1,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,2,10.0.0.2:25,10.0.0.1:51258,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 08:11:38 +0200",
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,3,10.0.0.2:25,10.0.0.1:51258,<,EHLO ITMILDC999,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,4,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,5,10.0.0.2:25,10.0.0.1:51258,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,6,10.0.0.2:25,10.0.0.1:51258,>,250-SIZE,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,7,10.0.0.2:25,10.0.0.1:51258,>,250-PIPELINING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,8,10.0.0.2:25,10.0.0.1:51258,>,250-DSN,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,9,10.0.0.2:25,10.0.0.1:51258,>,250-ENHANCEDSTATUSCODES,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,10,10.0.0.2:25,10.0.0.1:51258,>,250-AUTH NTLM,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,11,10.0.0.2:25,10.0.0.1:51258,>,250-8BITMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,12,10.0.0.2:25,10.0.0.1:51258,>,250-BINARYMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,13,10.0.0.2:25,10.0.0.1:51258,>,250 CHUNKING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,14,10.0.0.2:25,10.0.0.1:51258,<,AUTH ntlm,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,15,10.0.0.2:25,10.0.0.1:51258,>,334 <authentication response>,
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,16,10.0.0.2:25,10.0.0.1:51258,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,17,10.0.0.2:25,10.0.0.1:51258,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,18,10.0.0.2:25,10.0.0.1:51258,*,,Proxy session was successfully set up. Outbound session will now be proxied
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,19,10.0.0.2:25,10.0.0.1:51258,>,235 2.7.0 Authentication successful,
2015-06-23T06:11:39.763Z,ITMILEX999\Internal,08D27B82C2B20D7C,20,10.0.0.2:25,10.0.0.1:51258,-,,Local

This is the debug after upgrading to CU9 -- BROKEN

2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,0,10.0.0.2:25,10.0.0.1:51489,+,,
2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,1,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.196Z,ITMILEX999\Internal,08D27B9E1BAF1B57,2,10.0.0.2:25,10.0.0.1:51489,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 09:34:11 +0200",
2015-06-23T07:34:12.462Z,ITMILEX999\Internal,08D27B9E1BAF1B57,3,10.0.0.2:25,10.0.0.1:51489,<,EHLO ITMILDC999,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,4,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,5,10.0.0.2:25,10.0.0.1:51489,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,6,10.0.0.2:25,10.0.0.1:51489,>,250-SIZE,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,7,10.0.0.2:25,10.0.0.1:51489,>,250-PIPELINING,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,8,10.0.0.2:25,10.0.0.1:51489,>,250-DSN,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,9,10.0.0.2:25,10.0.0.1:51489,>,250-ENHANCEDSTATUSCODES,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,10,10.0.0.2:25,10.0.0.1:51489,>,250-AUTH NTLM,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,11,10.0.0.2:25,10.0.0.1:51489,>,250-8BITMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,12,10.0.0.2:25,10.0.0.1:51489,>,250-BINARYMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,13,10.0.0.2:25,10.0.0.1:51489,>,250 CHUNKING,
2015-06-23T07:34:12.744Z,ITMILEX999\Internal,08D27B9E1BAF1B57,14,10.0.0.2:25,10.0.0.1:51489,<,AUTH ntlm,
2015-06-23T07:34:12.791Z,ITMILEX999\Internal,08D27B9E1BAF1B57,15,10.0.0.2:25,10.0.0.1:51489,>,334 <authentication response>,
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,16,10.0.0.2:25,10.0.0.1:51489,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,17,10.0.0.2:25,10.0.0.1:51489,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,18,10.0.0.2:25,10.0.0.1:51489,*,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,19,10.0.0.2:25,10.0.0.1:51489,*,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 10.0.0.2:465"
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,20,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:26.965Z,ITMILEX999\Internal,08D27B9E1BAF1B57,21,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user',
2015-06-23T07:34:32.282Z,ITMILEX999\Internal,08D27B9E1BAF1B57,22,10.0.0.2:25,10.0.0.1:51489,>,535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,23,10.0.0.2:25,10.0.0.1:51489,<MAIL FROM:<FSRM @ contoso.com>,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,24,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '530 5.7.1 Client was not authenticated',
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,25,10.0.0.2:25,10.0.0.1:51489,>,530 5.7.1 Client was not authenticated,
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,26,10.0.0.2:25,10.0.0.1:51489,-,,Local

Ciao,

Luca

Hi, please can you let me know how you have protected against the "Autodiscover Enumeration Vulnerability".  My current thoughts are around using an irule on an F5 LTM but am unsure if there is a smarter way?

many thanks

T

Tul Golan

Hello,

I changed the ssl ucc cert provider from godaddy to comodo and installed the new cert. All services are asigned to the new cert. Almost all emails on the receive connector work fine.

But the samsung printer and hrs.de seem to have problems negoatiating tls.

Patch level is CU11

checktls.com works with no errors.

Receive connector log shows this:

0:57214,+,,
1:57214,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2:57214,>,"220 Mail1.XXXXXXXX.com Microsoft ESMTP MAIL Service ready at Sat, 30 Apr 2016 15:18:59 +0200",
3:57214,<,EHLO SEC001599DDC76E,
4:57214,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
5:57214,>,250-Mail1.XXXXXXXX.com Hello [192.168.1.202],
6:57214,>,250-SIZE,
7:57214,>,250-PIPELINING,
8:57214,>,250-DSN,
9:57214,>,250-ENHANCEDSTATUSCODES,
10:57214,>,250-STARTTLS,
11:57214,>,250-X-ANONYMOUSTLS,
12:57214,>,250-X-EXPS GSSAPI NTLM,
13:57214,>,250-8BITMIME,
14:57214,>,250-BINARYMIME,
15:57214,>,250-CHUNKING,
16:57214,>,250-XEXCH50,
17:57214,>,250-XRDST,
18:57214,>,250 XSHADOWREQUEST,
19:57214,<,STARTTLS ,
20:57214,>,220 2.0.0 SMTP server ready,
21:57214,*,,Sending certificate
22:57214,*,"CN=mail.XXXXXXXX.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated",Certificate subject
23:57214,*,"CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB",Certificate issuer name
24:57214,*,69BXXXXXXXXDE03,Certificate serial number
25:57214,*,043XXXXXXXX5E1A,Certificate thumbprint
26:57214,*,mail.XXXXXXXX.com;autodiscover.XXXXXXXX.com;mail1.XXXXXXXX.com;mail3.XXXXXXXX.com,Certificate alternate names
27:57214,*,,TLS negotiation failed with error BadBindings
28:57214,-,,Local