@gjacobse said in Server 2008 Exchange 2010: Event 1009:

Nearly all of the Exchange issues I deal with right now really come from O365.

However I was asked about Exchange Mail Submission server that was throwing Event 1009, and effectively stopping mail flow. What he found via forum (not ML) searching was 'a back pressure issue, but the Event Log wasn't logging in back pressure messages'

While it's been four years since directly touching a Exchange system, the term 'back pressure' is not one I have heard before.

However, looking up Exchange Event 1009 give me a few options including limited disk space.

Has anyone come across the term 'Back Pressure' with Exchange in the past?

Yes, it is when the server is running out of space or resources for delivery of incoming emails

https://docs.microsoft.com/en-us/exchange/mail-flow/back-pressure

@romo @Tim_G has written about this as below:
https://www.timothygruber.com/office-365/extend-ad-schema-exchange-2016-attributes-not-synchronizing/

Something to take in mind to remove the last Exchange.

I had the same problem:

Microsoft includes a command-line utility with Certificate Services called certutil. This utility performs various operations on certificate files, including converting them to and from base64 format.

Note that this command is run on your certificate server, which, in your environment, may be different from your Exchange server. If so, you need to copy the binary .req file to the certificate server, or make it accessible via a shared network folder or removable storage device.

Open a command prompt on the certificate server and navigate to the folder where your binary .req file is, then type the following command:

certutil -encode yourbinaryinputfile yourasciioutputfile

Example:
certutil -encode der.exchange.example.com.req pem.exchange.example.com.req
You can then open the output file in Notepad and confirm that it is in the correct format to upload to your certifying authority.

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

When you fire that power shell script off, if you go back to the sync manager, you'll see it does all 6 things. 🙂

Yep, that's how I confirmed it!

eJwqC0f.png

This picture doesn't really say much, and now that they've fixed their inbound TLS issue, perhaps the unencrypted number will be a lot smaller from now on... just thought I'd share what they shared.

Sigh - OK apparently I was adding the account in the wrong way.
Inside Outlook
File > Account Settings > Account Settings > choose your account and click change > More settings > Advanced Tab > Add > type in the name of the account.

Instead I was adding another account at the root level, the same as my own account under
File > Account Settings > Account Settings

Here is an article I found that helped me fix it.
http://www.it.northwestern.edu/collaborate/how-to/outlook2010-delegate-mailbox.html

@coliver said in Problems with Exchange 2010 and NginX reverse proxy:

@JaredBusch said in Problems with Exchange 2010 and NginX reverse proxy:

[10:54 jbusch ~]$ sudo dnf copr enable a15/NGINX-extras [sudo] password for jbusch: You are about to enable a Copr repository. Please note that this repository is not part of the main Fedora distribution, and quality may vary. The Fedora Project does not exercise any power over the contents of this repository beyond the rules outlined in the Copr FAQ at <https://fedorahosted.org/copr/wiki/UserDocs#WhatIcanbuildinCopr>, and packages are not held to any quality or security level. Please do not file bug reports about these packages in Fedora Bugzilla. In case of problems, contact the owner of this repository. Do you want to continue? [y/N]:

Well at least you are adequately warned.

That was on my Fedora 25 (Korora) desktop. SO I know I cannot install it anyway.