|
J posted:Happy 2022 to any suckers like myself still responsible for on-prem exchange, your mail flow is probably down! Fortunately there is a workaround that is easy to do even if you're still drunk. Seriously wtf. Luckily I discovered the problem early in the evening because of external mail flow monitoring. I'm not even sure if this is something that can be fixed by automated self updating. Its kind of amazing that the cause is the variable they use for the definitions serial number is too small when the year rolled over to 2022, and the failurestate is oops no mail flow.
|
#
¿
Jan 1, 2022 17:45
|
|
|
|
| # ¿ May 4, 2024 17:23 |
|
|
Do you get any errors running an autodiscover/Outlook connectivity check on https://testconnectivity.microsoft.com/ ?
|
|
#
¿
Feb 21, 2022 21:52
|
|
|
Yep, Enabling modern auth and disabling legacy auth are two distinct steps. We are running modern auth preferred, but haven't gotten the go ahead to turn off basic yet. If this is working for non-domain joined machines, it sounds like it could be something in your provisioning process that changed. Are the affected boxes in the same OUs/SGs/GPOs as the ones that work?
|
|
#
¿
Feb 21, 2022 23:18
|
|
|
Maybe get a freshly imaged machine before it is domain joined and test. If that works, then join it to the domain and test both local and domain accounts, and then disjoin it from the domain and test one more time.
|
|
#
¿
Feb 22, 2022 00:14
|
|
|
Thanks Ants posted:Is there a reference anywhere to the default permissions on the "Organization Management" role group in Exchange Online? Someone has hosed with ours and I've copied the permissions from another tenant but would prefer to be able to compare them to the defaults / run a PS command to reset it if that exists. You'll want to look at reinstalling the canned RBAC roles. I've never had to do this before, but it could help your situation. Disclaimer here is you could end up with redundant groups and more cleanup after. https://everything-powershell.com/exchange-2019-reset-rbac-to-default/
|
|
#
¿
Nov 22, 2022 20:14
|
|
|
Using an external bulk sender that is already having RBL problems still means those external people will have trouble receiving mail, even if you circumvent the problem with internal recipients. The most reliable way to do this is likely with an internal DL that contains your internal people and mail contacts for the external users. You can hide the DL and contacts from the GAL if needed and sender restrict the DL so that only permitted people can send to it. What kind of problem would creating mail contacts create beyond the obvious object management headache?
|
|
#
¿
Dec 6, 2023 21:41
|
|
|
minusX posted:We have just shy of 11k AD objects for users that don't have internal e-mails (some which might be termed users that were missed mind, but blue collar workers who aren't doing e-mails to/from the company) and adding that many e-mail contacts will be a mess. Plus we're going to run into send limits with that number for sure. Yeah that's a lot. Exchange only counts a DL as one recipient, but you may run in to issues with external email services. If ClickDimensions will let you create a DL on their side that you can email, you could create a local DL with your internal addresses plus a mail contact for that external DL and then sender restrict/hide both. That would get the CEO a single address to email.
|
|
#
¿
Dec 6, 2023 23:01
|
|
|
|
| # ¿ May 4, 2024 17:23 |
|
|
Mierdaan posted:Can/does ClickDimensions add any specific message headers you can whitelist? That may not help with RBL'd MTA's though. In my experience (Mimecast most recently), an email coming from a blacklisted IP is rejected before any header data is accepted.
|
|
#
¿
Dec 7, 2023 22:44
|
|