When sending from a Mobile device via the ActiveSync service the device fails to send.
Some devices may return an error indicating that “The message that was sent to the server was rejected because the message was too large”. (Apple iPad iOS). Not all mobile devices behave this way and may just keep the message in the outbox folder and retried until removed from the folder.
CAUSE
Ther are number of reasons, couple of them listed below.
CAUSE 1
First one I have found is ActiveSync limit set to 10MB (%ExchangeInstallPath%ClientAccess\Sync\web.config maxRequestLength=”10240″)
CAUSE 2
A global IIS restriction preventing uploads larger than 49152 Bytes.
IIS 7.5 sets a default value of 49152 Bytes for the “UploadReadAheadSize” value which limits the amount of bytes allowed in the entity body of a request and the number of bytes a Web server will read into a buffer and pass to an ISAPI extension.
Diagnosis:
Navigate within IIS to the “Sites” node.
Determine the ID for the “MailEnable Protocols” website
Next navigate to the IIS log files path: C:\inetpub\logs\LogFiles
Locate the W3SVC(ID) folder, where ID is the number of the website ID above in step 2.
Sort the log files by “Date Modified’ and then open the latest log files in respect to the date/time you sent the message from the mobile device.
The above log snippets report a 413 error in the line which indicates the “Request Entity is too large”.
CAUSE 3
Incorrect authentication settings in Exchange Server Virtual Directory.
RESOLUTION – 1
Change the limit set on web.config, note this settings below for Frontend backed servers with different CAS and Mailbox server. For single server web.config is located in
C:\Program Files\Microsoft\Exchange Server\v14\ClientAccess\Sync\web.config has the following lines of code:
<system.web> <!– Allow maximum 10 megs of content –> <httpRuntime madRequestLength=”10240″ />
maxAllowedContentLength="30000000 bytes" Not present by default (see comments).
bytes
Mailbox
%ExchangeInstallPath%ClientAccess\Sync\web.config
maxRequestLength="10240"
kilobytes
Mailbox
%ExchangeInstallPath%ClientAccess\Sync\web.config
<add key="MaxDocumentDataSize" value="10240000">
bytes
Comments on ActiveSync limits
By default, there is no maxAllowedContentLength key in the web.config files for ActiveSync. However, the maximum message size for ActiveSync is affected by the maxAllowedContentLength value that is applied to all web sites on the server. The default value is 30000000 bytes (30 MB). To see these values for ActiveSync on Client Access Servers and Mailbox servers in IIS Manager, perform the following steps:
Do one of the following steps:
On Client Access servers, open IIS Manager, navigate to Sites > Default Web Site and select Microsoft-Server-ActiveSync.
On Mailbox servers, open IIS Manager, navigate to Sites > Exchange Back End and select Microsoft-Server-ActiveSync.
Verify Features View is selected, and double-click Configuration Editor in the Management section.
Click the dropdown arrow in the Section field, navigate to system.webServer > security and select requestFiltering.
In the results, expand requestLimits, and you’ll see maxAllowedContentLength and the default value 30000000 (bytes).
To change the maxAllowedContentLength value, enter a new value in bytes, and click Apply. You need to change the value on Client Access servers and on Mailbox servers. After you change the value in IIS Manager, a new maxAllowedContentLength key is written to the corresponding web.config file (%ExchangeInstallPath%FrontEnd\HttpProxy\Sync\web.config on Client Access servers, and %ExchangeInstallPath%ClientAccess\Sync\web.config on Mailbox servers).
To change the maximum message size for ActiveSync clients, you need to change the value of maxRequestLength in the web.config file on Client Access servers and Mailbox servers, MaxDocumentDataSize in the web.config file on Mailbox servers, and maxAllowedContentLength in IIS Manager on Client Access servers and Mailbox servers.
RESOLUTION – 2
Open a Windows command prompt with administrator rights and navigate to the following location: C:\inetpub\AdminScripts
Run the following command: cscript adsutil.vbs set w3svc/14/uploadreadaheadsize 51200000
Where “14” in the above command is the website ID
RESOLUTION – 3
Check the virtual directory authentication settings in the Exchange server for EWS (Default Web Site), it should be Integrated windows authentication only and for
Microsoft-Server-ActiveSync (Default Web Site) authentication set to Basic authentication and ignore client certificate
If you are an Exchange administrator, then using the Set-MailboxAutoReplyConfiguration Exchange PowerShell command is the supported and native way to go to enable Automatic Replies without logging on to the mailbox itself.
So onto the printer side. Open the webpage to configure the device (Enhanced web Service, shortened from here on as EWS)
EWS > Connectivity > SMTP
Which will show you this (normally I would pre-fill this with your settings, but since I don’t know your settings because of your SMTP server not showing them on its website, I’m using GMAIL as my example.
Basically:
1. Device Email and SMTP AUTH user name have to match
2. The 2 password boxes are pretty self-evident.
3. Validation Type absolutley needs to be set to On Device
4. SMTP server address is whatever Media Temple says to use from the link above, the port number too, and the Connection Security (maybe called Encryption) too.
Of course the SMTP server name can be the IP address or the hostname of the server, but to use the hostname, you have to make sure DNS is correct on the printer EWS > Connectivity > Ethernet > DNS > Edit
And if HTTPS is enabled on the printer, or SSL/TLS/STARTTLS is being used for Encryption, then the time must be correct to within 3 minutes EWS > System > Date& Time
If you set it up correctly and get odd faults (017-714 for instance, try updating the firmware, the launch firmware has issues with SHA-2), you can get the latest firmware right here
“From” email in HESK settings (General tab) is set to your Office365 email address
“From” name in HESK settings (General tab) is NOT set to an email address – Microsoft security policies will reject sending emails if the From name is an email address
» POP3 fetching
To fetch mail from Office365 server enter these details:
Open up SSMS RUN AS ADMINISTRATOR and connect here:\\.\pipe\MICROSOFT##WID\tsql\query
Open a query window, run this query:
SELECT TOP 1000 [Id],[Name] FROM [RDCms].[rds].[Server]
Look at the list of servers in the NAME column. Find your dead server and note the ID number in the ID column. For this example, lets say my id is “5”. The ID for your system will most likely be different so don’t just copy and paste the below commands, make sure you change the ID to what you actually need to remove.
—-MAKE SURE YOU HAVE A DATABASE BACKUP OR SYSTEM CHECKPOINT OR SYSTEM BACKUP OR SOMETHING BEFORE PROCEEDING—-
Run the following query to remove the dead SESSION HOST server from the database:
use RDCms; delete from rds.RoleRdsh where ServerID = ‘5’;
I also needed to remove the server from the rds.Server table:
use RDCms; delete from rds.Server where Id = ‘5’;
Note, the above covers the session host role. If you have a server with other roles there are other tables you can look at and delete by id. Just right-click on the table (after drilling down in object explorer in to the RDCms database) and “Select Top 1000 rows” to see if your server ID is listed there.
You can use the following powershell command from an elevated powershell prompt (before and after to confirm the server is gone) to list out RDS servers:get-RDServer
—
Conclusion: Once everything is deleted out of the DB, close SSMS and then close and re-open Server Manager. Now you can get to your Remote Desktop Services management screen and get on with your life!
I can’t seem to download emails on my iPhone, can sign into OWA and get it working on any version on Outlook, but it won’t download email on iPhone.
I’m able to successfully configure the email on phone but when I go into the mail app, and try to download the emails, I get an error “the connection to the server failed”.
FIX: Issue was the DCs weren’t replicating. Once I forced it to replicate in Sites and Services, emails started coming in automatically.
Description: PowerShell cmdlet to view inbox rules is Get-InboxRule. First grab all mailboxes in the organisation and store the UserPrincipalName in a variable. Here we are storing it in a variable called “Users”
Then for each user we are going to get the InboxRule and select several attributes:
MailboxOwnerID
Name
Description
Enabled
RedirectTo
MoveToFolder
ForwardTo
The entire list of attributes we can grab per mailbox is:
Enabled
Identity
InError
ErrorType
Name
Priority
RuleIdentity
SupportedByTask
Legacy
BodyContainsWords
ExceptIfBodyContainsWords
FlaggedForAction
ExceptIfFlaggedForAction
FromAddressContainsWords
ExceptIfFromAddressContainsWords
From
ExceptIfFrom
HasAttachment
ExceptIfHasAttachment
HasClassification
ExceptIfHasClassification
HeaderContainsWords
ExceptIfHeaderContainsWords
FromSubscription
ExceptIfFromSubscription
MessageTypeMatches
ExceptIfMessageTypeMatches
MyNameInCcBox
ExceptIfMyNameInCcBox
MyNameInToBox
ExceptIfMyNameInToBox
MyNameInToOrCcBox
ExceptIfMyNameInToOrCcBox
MyNameNotInToBox
ExceptIfMyNameNotInToBox
ReceivedAfterDate
ExceptIfReceivedAfterDate
ReceivedBeforeDate
ExceptIfReceivedBeforeDate
RecipientAddressContainsWords
ExceptIfRecipientAddressContainsWords
SentOnlyToMe
ExceptIfSentOnlyToMe
SentTo
ExceptIfSentTo
SubjectContainsWords
ExceptIfSubjectContainsWords
SubjectOrBodyContainsWords
ExceptIfSubjectOrBodyContainsWords
WithImportance
ExceptIfWithImportance
WithinSizeRangeMaximum
ExceptIfWithinSizeRangeMaximum
WithinSizeRangeMinimum
ExceptIfWithinSizeRangeMinimum
WithSensitivity
ExceptIfWithSensitivity
ApplyCategory
ApplySystemCategory
CopyToFolder
DeleteMessage
DeleteSystemCategory
ForwardAsAttachmentTo
ForwardTo
MarkAsRead
MarkImportance
MoveToFolder
PinMessage
RedirectTo
SendTextMessageNotificationTo
StopProcessingRules
MailboxOwnerId
IsValid
ObjectState
RunspaceId
Description
Finally, export the information to a CSV. The -Append parameter is necessary so it doesn’t overwrite the csv file as it moves onto the next mailbox.
PowerShell Script :
NOTE: To run in Office 365 you must first connect to Office 365
