User Profile
mderooij
MVP
Joined 10 years ago
User Widgets
Recent Discussions
Re: Out of Office inbox rule in Outlook
The OOF rules are hidden, but they will show up when you do Get-InboxRule -Mailbox <ID> -IncludeHidden The internal OOF has the subject Microsoft.Exchange.OOF.InternalSenders.Global The external OOF has the subject Microsoft.Exchange.OOF.AllExternalSenders.Global You cannot manage them using Set-InboxRule; for that you need Get-MailboxAutoReplyConfiguration and Set-MailboxAutoReplyConfiguration.711Views1like0CommentsRe: Hybrid Mailbox Sending Limit
EXO is in principle not meant for bulk mailing to external recipients. You have three options: 1) Have Exchange on-prem (Hybrid) send directly to external recipients 2) Use multiple accounts when sending (authentication) 3) See if the app can leverage Azure Communication Services for bulk mail - see https://learn.microsoft.com/azure/communication-services/overview While some things are "tolerated" at the moment, the recently announced HVE article provides pointers to where things are going, see https://techcommunity.microsoft.com/t5/exchange-team-blog/public-preview-high-volume-email-for-microsoft-365/bc-p/4104050746Views1like0CommentsRe: Require Help Setting Up An Authenticated SMTP Relay On Premise Server
I think that would be the wisest, as that would put it in EXO's ecosystem, adds options to monitor flow and rules, while connectors with centralized mail-transport configuration would reroute those messages back to on-prem before they get send out.847Views0likes0CommentsRe: Received two forwarded metting emails with smartForward command
EAS' smartForward should forward the instance when you specify InstanceId and the whole series when you omit it. Could you elaborate a bit more on where you are trying to accomplish this and to what back-end (Exchange on-prem + version or Online, etc).400Views0likes1CommentRe: Exchange 2019 owa
Depends on where the redirection takes place - have you configured it in IIS/Exchange, or load balancer / application delivery controller, etc. If you configured IIS/Exchange to perform the redirect, this might help: https://learn.microsoft.com/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/configure-http-strict-transport-security-in-exchange-server?view=exchserver-2019#how-exchange-server-handles-http-connections537Views0likes1CommentRe: Exporting list of all public folders with folder size
Would something like this work for you? It - gets all the public folders - gets their stats - adds a property to the output with the owners joined together by ';' Get-PublicFolder -Recurse -ResultSize Unlimited | Get-PublicFolderStatistics -ResultSize Unlimited | Select-Object Name,TotalItemSize,@{n='Owners';e={ (Get-PublicFolderClientPermission -Identity $_.Identity | Where {$_.AccessRights -like 'Owner'}).User -join ';'}}464Views0likes0CommentsRe: Publishing exchange 2016 via Azure AD proxy
Step by step here https://hedbergtech.se/securing-using-sso-for-outlook-web-app-exchange-control-panel-with-the-azure-ad-applicaton-proxy/ If you use HMA, you might need to enable Kerberos https://mikeparker365.wordpress.com/2018/09/25/how-to-secure-exchange-2016-with-azure-ad-part-1-azure-application-proxy/ https://mikeparker365.wordpress.com/2018/09/25/how-to-secure-exchange-2016-with-azure-ad-part-2-azure-application-proxy/ https://mikeparker365.wordpress.com/2018/09/25/how-to-secure-exchange-2016-with-azure-ad-part-3-azure-application-proxy/925Views0likes0CommentsRe: Impact of TCP KeepAliveTime on increasing mail.que file - Exchange Server 2016
MaxDumpsterTime is not used, unless you are still running Ex2010 somewhere. You configured SafetyNetHoldTime or coming from Ex2010? Default is 2 days. Should stabilize at some point (unless sizing is way off with reality) Sure you are not sending a big spike in mail, mail loops are happening, etc.? Back pressure not holding off processing incoming messages making .que grow? This article might help, measures and metrics to keep an eye on, etc.: https://techcommunity.microsoft.com/t5/exchange-team-blog/transport-database-understand-size-and-troubleshoot/ba-p/11133882KViews1like1CommentRe: RequireSenderAuthenticationEnabled - Distribution Groups - Exchange 2016
- Can I use eDiscovery (on Exchange 2016 or something else) to check all recieveng messages or logs for a longer period? If admin audit logging is enabled, yes. But since it was not at that time, you can't since it will only log future events. - What was the default vaule on Exchange Server 2010 regarding "Require that all senders are authenticated")? IIRC, default is unspecified, which corresponds to $true. Has been like that since Ex2007, same is true for Exchange Online. - Is it possible that for some reason those settings automatically changed? Or is it more possible that the default settings for external emails was not changed when the distribution groups were created? No, there is no policy for that. It requires configuration, either by hand, by some process. Your EXO setting is managed (synced) by AD Connect (msExchRequireAuthToSendTo). - I tried checking event logs, tried with Powershell (Get-DistributionGroup | Where{$_.WhenChanged -gt ((Get-Date).AddMonths(-24))} and Audit log. I can´t find anything regarding changes in the mentiond setting on Exchange 2010 or Exchange 2016. This happens always when you turn audit logging only on when it was needed before. Now your savior might be AD Connect; if it was synced from on-premises after it was changed, AD Connect might provide details on the data it has on the object, or you can look through its logs. Cmdlets like the following might help you parse and filter instead of going through the UI 🙂 Export-ADsyncObject -DistinguishedName 'CN=GroupX,OU=Groups,DC=Contoso,DC=com' -ConnectorName 'ad.contoso.com'3.4KViews1like0CommentsRe: Proxy addresses broken after enabling Azure AD Connect
Send as in SendAs or SendOnBehalf? Send on Behalf replicates through ADConnect- could it be that it has overwritten your configuration in EXO? SendAs should be no problem. Since you mention receiving still works, I assume switching ADConnect on and matching worked out ok.2.8KViews0likes1CommentRe: exchange attribute migration from one AD forest to another
Easiest is if you migrate mailboxes to EXO first; that way changes on-prem won't hit users. Then have a look at this article, https://jaapwesselius.com/2020/11/28/decommission-an-exchange-resource-forest-in-a-hybrid-environment. You can do a lot with Exchange cmdlets (export/import).930Views0likes0CommentsRe: Out Of Office Default Sender Address
Never seen. Messages sent from EOP are routed directly, need to pass on-prem (centralized mail transport) or go through some SaaS mail hygiene appliance/service? Sure there is no address rewriting taking place somewhere? Take an OOF, locate its Message ID and make a message trace with details to see how it was sent and processed.5.8KViews0likes0CommentsRe: Unique Sender IP information details
That's where DMARC can help - configure a DMARC DNS record (reporting) and have receiving MTAs report on received messages and their origin. It's the way to identify hosts that are not on your radar (and should .. or shouldn't). Use dmarcian/valimail/etc to collect and aggregate these stats, however you may need the - temporary - paid option to have reports on the desired detail level.657Views0likes0Comments
Recent Blog Articles
No content to show