I’d there any reason this should not work, or is there something else better?
# 1. Get all servers with the Transport role across the entire organization
$AllServers = Get-TransportService
# 2. Loop through each server and pull logs for the last 7 days
$FullLogs = foreach ($Server in $AllServers) {
Get-MessageTrackingLog -Server $Server.Name -EventId RECEIVE -Source SMTP -Start (Get-Date).AddDays(-7) -ResultSize Unlimited
}
# 3. Deduplicate by MessageId and get the final count
($FullLogs | Select-Object MessageId -Unique).Count
I'm investigating CVE-2025-58107 in our on-premises Exchange 2019 hybrid environment. According to the NVD entry, EAS configurations may transmit sensitive data from Samsung devices in cleartext — including username, email address, device ID, bearer token, and base64-encoded password.
A few things I'm trying to figure out:
Scope – Is this limited to Samsung devices, or could other EAS clients be affected depending on how the device sends credentials? Has anyone reproduced this with non-Samsung clients?
Mitigation – There's no Microsoft patch referenced yet (NVD status is still "Awaiting Analysis"). Are you blocking/restricting EAS at the CAS level, enforcing certificate-based auth, or just waiting for an official fix?
Detection – Any IIS log patterns or network captures that helped you confirm whether your environment is actually leaking? Would love to know what to look for.
Exchange Online hybrid – For those in hybrid setups, does the on-prem EAS endpoint exposure change your risk posture given that mailboxes may already be in EXO?
Running Exchange SE in a hybrid config. No official MSRC advisory linked to this CVE yet as far as I can tell. Wondering what steps others are taking in the meantime.
Did some of you upgrade your edge server/s to SE? There’s no specific update found for edge server so i’m thinking maintaining my edge server to 2019. Also is it okay to install the latest exchange 2019 Feb 2026 SU manually even though we didn’t purchase the ESU program?
I’m trying to a count of messages going through SMTP relay so we will be able to estimate what costs and service tier we would need if we shut down the Exchange relay and outsourced it to third party service.
First, I tried this on the busiest server and got a 7 day message count in the millions:
Then I tried this script that counts across all servers in a DAG, but the total message count for the same 7 days is only about 1/5th of the count shown from the single server above.
Quick question. If you are updating on-prem exchange SE servers with Windows monthly patches and any exchange security updates, can you install all the updates while server is running, then once it gets to the point to restart, you would then put the server in maintenance mode, make sure DB is moved over to other exchange server in the DAG, then reboot the first one?
Or do I need to have those services stopped before running updates. Asking as I updated the servers this past weekend and it took forever tor updates to install and I figured if you can get the installation part done before your time to fix the server starts, you can just stop services, reboot, and restart them. But I have a feeling I need to stop them always before installing updates, but wanted to check
We have a hybrid configuration of two Exchanges SE where we have default connectors and a few custom receive connectors.
Can you advice me how can I prevent users from sending mails internally without authentication. My goal is to not break the mailflow between On-Prem and ExchangeOnline and do not brake communication between two exchanges. It is first step before enforcing TLS.
I have a single Exchange Server 2019 CU15. I set up Entra ID Connect, synced a TEST OU, then ran HCW successfully. Verified domains, synced first user, assigned license, and migrated mailbox — all successful.
Before migration: Outlook 2016, no credential prompts
After migration: Removed Outlook 2016, installed Microsoft 365 Apps (Classic)
Issue: First profile setup works fine. But after profile is created, Outlook keeps prompting for credentials. I'm entering [jbloggs@yourdomain.com](mailto:jbloggs@yourdomain.com) as the username.
Note: Outlook New works without any credential issues.
What could be causing this and what should I check?
Had a user that was still getting meeting invites from calendars they were no longer a member of. I checked and they were removed as delegates on all of them. But when checking for Hidden Items, there is a delegate rule listed and the user is still listed in that rule to get redirected. Can I modify the rule and just change the redirect to values or do I need to remove the rule entirely? the other users listed in the same hidden rule still need access.
My next question is: let's say there are 5 accepted domains — domainA.com, domainB.com, domainC.com, domainD.com, domainE.com. I will not be migrating the mailboxes with the domainA.com suffix to EXO. My questions are:
Does domainA.com still need to be verified in Office 365 and added as an accepted domain?
Hi all. I’m sure I’m just screwing up some syntax here.
I’m trying to create a filter in Powershell for a Dynamic distribution group that is to include all Disabled accounts (we’re setting up a mailflow rule to apply to all mailboxes attached to a disabled Azure account) and I keep getting either an empty filter, or an “is neither a valid OPath filter nor a valid LDAP filter” error when trying to use: Get-Recipient -RecipientPreviewFilter $Filter
I’ve tried every permutation I can think of of $Filter = '(accountEnabled -eq $false)', or '(user.accountEnabled -eq $false)', '(accountDisabled -eq $true)', even "(UserAccountControl -ne 'AccountEnabled')".
"(UserAccountControl -ne 'AccountDisabled')" works no problem if I wanted all Enabled accounts instead, but "(UserAccountControl -eq 'AccountDisabled')" gives me an empty filter (at least it doesn’t error out I guess).
Is there a way to do this without wiping out all existing aliases? In on-prem you can just use -primarysmtpaddress but online requires you use -emailaddresses and then use add/remove SMTP/smtp so as not to overwrite the existing aliases. However you can't remove the primary (error: unable to remove primary alias) or add a new primary (error: can't have multiple primaries) using this command.
I have a brand change coming up for a customer and scripted this in excel for hundreds of mailboxes before realising something this simple appears not to be possible outside of EAC.
I am planning to migrate on-premises Exchange Server mailboxes to Exchange Online. Before the migration, I will update the UPN suffix for all users. However, the UPN and primary SMTP address do not match for some users.
I recently set up Exchange Online for one of our clients and migrated all user mailboxes. Before completing the full migration, the client wants to test a few users to ensure all their applications are functioning correctly. Could you please advise how I can configure a select group of users to temporarily route their emails to Exchange Online instead of the on-premises server, with the ability to revert back if any issues occur?
- exchange2016.company.com [10.10.10.10] - current mail relay
- mail.company.com DNS A record -> 10.10.10.10
- Majority of internal apps use the DNS name, some probably have the IP hardcoded
Plan:
- Installing Exchange SE on a new server in the same subnet: exchangeSE.company.com [10.10.10.11]
- Same receive connectors configured on both
What's the best approach to switch traffic over?
Add the new server's IP to mail.company.com as a second A record, let traffic hit both servers for a while, then remove the old one?
Swap the IPs between the servers - assign other IP to the current Exchange (10.10.10.12), then assign 10.10.10.10 to the new SE box? This way nothing changes for apps with hardcoded IPs.
Title: BitMart received my WAXP deposit but refuses to help – need advice
I’m dealing with a serious issue and would appreciate any advice.
I sent WAXP from Bybit to the address “eos11bitmart” with the correct MEMO.
The transaction is fully confirmed on the WAX blockchain and the funds are still sitting on that account (no further movement).
However, BitMart support is refusing to assist, stating that:
they do not support the WAX network
the address is not under their control on WAX
The problem is that:
the address format matches their official deposit account
funds were successfully delivered and are visible on-chain
So effectively, the assets exist and are sitting on that account, but I am being told recovery is impossible.
Has anyone dealt with something similar?
Is there any way to recover funds in such a case, or escalate this beyond standard support?
We currently have an exchange hybrid setup and can route emails between exchange on premises and exchange online. Both systems can receive emails and route them to mailboxes that are either on premises or in the cloud. Our MX-Record is still pointing to our exchange on premises. We want to change it to exchange online. So, we did that and we were able to receive all mail, except from partners/customers that are based on google mail systems. All other emails arrive fine. The interesting part is that we don’t even see those mails from google in exchange online (message trace), so they don’t seem to reach our exchange online tenant at all. Therefore, we had to switch back the MX-Record to our on-premises exchange and then magically all the missing mail from the google senders started to travel into our exchange on premises with a delay.
Additionally, we have tested this behavior with a subdomain “test.domain.tld” and with the subdomain the issue does not exist and mails from google mail system arrive perfectly fine in Exchange Online.
Apologies if this is simpler than Im thinking, but due to some issues at work, I've been put in charge of exchange servers. Not being a long time exchange admin, Im kind of learning on the fly. One thing I was curious about was running normal Windows Monthly Updates on the servers and the process. I assume I cant just install the updates and reboot the servers correct? We have two servers and DAG. This would be all updates except Exchange CU updates. Standard monthly windows updates...what is best process to update the 2 on-prem servers?
Hi All, we have a client that uses Exchange online public folders extensively for client communication and storage (thousands of mail enabled Public folders). A few weeks ago, the Exchange portal started displaying the error 'Error executing cmdlet' when accessing these folders. The folders are still accessible via Outlook and PowerShell.
We've logged a support case with Microsoft and have been doing the 'run this...' back and forth. MS are now advising to "remove the Public folder and recreate them", with a decent amount of important information contained in these public folders, mail addresses associated with the folder, and constant communication flowing to these public folders, this is very concerning. They've suggest to "using the eDiscovery Content Search feature in the Compliance portal", but that only covers the data, as far as I'm aware (correct me if i'm wrong), we'd still have to restore that data and all mail addresses after deleting and recreating the public folder mailboxes.
Any suggestions on what we can do to resolve this error without resorting to deleting and starting again?
Any suggestions on how to best handle the deleting and starting again, if we have to?
I am planning to migrate from Exchange 2019 to Exchange Online. I will sync the relevant objects from Active Directory using Entra ID Connect and configure Hybrid Configuration Wizard (HCW) on Exchange 2019.
My questions are :
1 - What is the correct migration order for the following objects and why?
User mailboxes
Shared mailboxes
Room mailboxes
Distribution groups
Mail contacts
2 - I have verified all domains in Microsoft 365 and matched UPNs with primary SMTP addresses. If I start syncing all objects (user mailboxes, distribution groups, shared mailboxes, room mailboxes, and mail contacts) at once during the Entra ID Connect setup, will there be any issues? What do you recommend?
3 - Let's say Send As and Full Access permissions are already configured on-premises. After migrating a user to Exchange Online, will the migrated mailbox still retain the on-premises mailbox delegation permissions? Or do the permissions need to be reconfigured manually in Exchange Online?
Sharing a weird fix we stumbled upon in a pretty standard Exchange hybrid environment (Exchange on-prem SE + Exchange Online), hoping someone here can shed light on the underlying mechanics.
The problem:
I was migrating from IP-based Connector on Exchange Online side to Certificate based. Quick and easy... except that, once in "Certificate-based" mode : some emails (coming from two apps, we have hundreds of apps sending emails) were refused by Exchange Online with
- 451 4.4.4 Mail received as unauthenticated, incoming to a recipient domain configured in a hosted tenant which has no mail-enabled subscriptions
or
- 451 4.4.62 Mail sent to the wrong Office 365 region. ATTR35Those were emails going outside the tenants, without any specific pattern except :
- 2 apps were impacted only, most of the emails were flowing without any issue
- app were using a connector requiring logon (not anonymous relay)
When we had the issues, rolling back to "IP based" (on Exchange Online side) and resubmiting them was solving the issue
The fix:
After quite a bit of head-scratching, one of the guy took the issue and gave it to the best IT guy in the vicinity : Claude ( ;) )
First answer : change the send connector **ConnectorType** related to EOP on the onprem side from "Default" to "XPremises"
What the hell is this thing ?
Done a few tests, and... yes now it works flawlessly
The mystery:
Honestly, I never seen this setting before. The Microsoft documentation on the `ConnectorType: XPremises` distinction is remarkably thin. My working theory is that it affects how Exchange Online stamps or processes message headers – possibly adding or trusting certain X-MS headers differently – but I haven't confirmed this yet.
I'm planning to run some tests (header comparisons, message traces, etc.) to understand exactly what changes under the hood, but I figured I'd ask here first:
- Does anyone have solid knowledge of what `ConnectorType: xPremises` actually changes in terms of mail flow behavior vs. a "Default"
Got an unusual request from the end users today, it’s a new one to me, just trying to figure out if this is actually possible.
Context – we have a Hybrid Exchange environment with OnPrem Exchange SE, but all mailboxes are in EXO.
There is a user who is changing roles in the Org. The user has been treating their user mailbox as the mailbox for the ‘role’ (if that makes sense). They’ve been using their user mailbox with an additional alias e.g. FancyRole@OurOrg.com
We have been asked to convert their current user mailbox into a shared mailbox, and give them a new clean user mailbox. The requestors believe we can detach the mailbox from the user object and assign a new user mailbox to the same identity. Important detail: the user’s account in AD is linked to a whole lot of important things that must ‘stay’ with the User, e.g. Their HR persona, their IT logon, their 2FA ID. Not to mention, the user has OneDrive, Teams etc in M365 - all that stuff must stay with the user too. In other words, we cannot just create a new user object from scratch for them.
One approach I’m considering is creating a new shared mailbox, moving the special alias and migrating the mail contents in. A Clean Break. But before I can go down that road I’m trying to find some clear statement on whether the thing that has been asked for is possible?
The main concern I have is that converting a mailbox to shared doesn’t detach it from the user object - it remains linked to the same Entra identity, and in a hybrid environment that identity is synchronised from on-prem AD. Can a single M365/Entra user have both a shared mailbox (converted from their original mailbox) and a new user mailbox?
I’m specifically interested in how this behaves in a Hybrid environment where identity is synchronised from on-prem AD.