DMARC rejection after Exchange upgrade
I'm having problems with inbound emails getting bounced as Undeliverable due to DMARC rejection. For many years I've had my email come through Fasthosts / Livemail to my own domain (qts.org.uk) with catch-all forwarding set to forward everything to my GMail account. Just recently Fasthosts have upgraded their servers to Exchange and I've started getting DMARC rejections from GMail which start Diagnostic information for administrators: Generating server: exchange2019.livemail.co.uk Total retry attempts: 1 (my gmail email address) t1-hex-xprelay.gem.livemail.co.uk Remote Server returned '550 5.7.26 Message rejected by DMARC policy by gmail.com. Please use your own email address as the sender, instead of (sender's email address). [MSG0009]' Which bounce from Fasthosts / Livemail back to my GMail address. My own domain has SPF, DMARC, and DKIM configured I've done a little digging and it appears to only affect senders from originating domains with DMARC set to reject. So either GMail has coincidentally become much more strict (possible) or Fasthosts are somehow failing to forward emails fully transparently. I have spoken to Fasthosts and logged the issue with them and was not impressed so I hope the experts here can offer a solution I can forward to them.
Dynamic Distribution Group with no Disabled Accounts
Hi I'm trying to build a few Dynamic Distribution Lists in Exchange Online and want to only include Active Users (i.e., users that are marked "Active" in Azure AD). I've tried using the UserAccountControl attribute (-eq 514 or -ne 514 - both are returning the same results, which is strange), but it still includes user accounts that are disabled. This is how my recipient filter looks like: RecipientType -eq 'UserMailbox' -and UserAccountControl -ne 514 What's the best way to achieve this in Exchange Online? Thanks Taranjeet Singh
Both The Owner & I Have Requested Assistance Regarding A Domain Transfer But Have Had No Updates.
Both the owner & I have requested assistance in regards to a domain transfer. There is a phantom account holding our already verified domain.... We have lost a full month of service for over 150 users due to the errors on Microsoft's side. Please answer one of our cases so that we can finish up the migration. We were not anticipating such a difficult experience. One of the cases is registered to the associated email. Thanks. Microsoft 365 Migrations Microsoft Entrasinged pdf files get blocked when user is sending from shared mailbox
Hi, in exchange environment, I have my email account and also I have shared mailbox linked. I can sent the singed pdf file attached to email from my email but when I send it from shared mailbox, I get the following message everytime: "From: email address removed for privacy reasons <email address removed for privacy reasons> Subject: Executable File Violation You attempted to send a message that contained an executable file. Our company policy prohibits the sending of executable files via email. The message was not delivered." We have symantec spam filter in organization, which I think is causing that error, or it can be exchange policy which is more restrictive (on default or someone configured it so), I wonder if it is possible to address this issue and let the singed pdf flow from shared mailbox. What can I do to fix it? From where should I fix it - exchange management / shared mailbox policies or where do I find that options to configure correctly? Thanks George
Able to Sign in with a Distribution List – How is this Possible?
Hi everyone, I've come across an unusual issue and I'm hoping someone here might have an explanation for it. Normally, it's not possible to sign in with a Distribution List (DL) since it doesn't function as a regular user account. However, I noticed that with a specific email address, I am actually redirected to the login page instead of receiving an error message. To verify, I tested another distribution list within the same environment, and as expected, I was unable to sign in. This makes me wonder why this particular DL behaves differently. Does anyone know under what circumstances signing in with a distribution list might be possible?FolderId's not unique without factoring in case-sensitivity, PowerShell issues...
Hello, I like using Get-/Set-/Add-/Remove-MailboxFolderPermission cmdlets. One of my favorites. There are times when there are special characters in the folder names, so I use the FolderId instead. For example: Add-MailboxFolderPermission -Identity "User1:LgAAAAC5KVkA/5dLTL13II/kvsaqAWCosJLoiFIBRbYcQ3Ny3l9TAAAAfag/AAAB" -User "User2" -AccessRights FolderVisible,ReadItems This has been fantastic to save the day in those cases. My latest issue though is that there turn out to be many duplicate FolderId's if we disregard case-sensitivity. If I import a CSV which has UN-tampered FolderId's (case-preserved and confirmed) with Import-Csv, and then to this: Add-MailboxFolderPermission "User1:$($csv[0].FolderId)" -User "User2" -AccessRights FolderVisible, ReadItems ... the actual folder to be updated with this new permission entry (ACE) may be the one I intended, or it may be one of the other folders with a matching FolderId (ignoring case-sensitivity). What I've found is that it is possible but difficult to bounce back from that problem state. You need to report all permissions before and after and verify the differences are only the intended changes. Super tedious, effectively a dangerous exercise overall. I don't see any alternative solutions for this problem. MFCMAPI I think, as well as Outlook/OWA, are definite workarounds. Wondering if there is anything in-built with the *-MailboxFolderPermission / *-MailboxFolderStatistics cmdlets that can help PowerShell here?
IMAP Healtset ImapDeepTestMonitor unhealthy on Exchange 2016 CU 23
Hi, Since couple of weeks, our SCOM reported IMAP.Protocol errors on one of my 4 Exchange nodes. After checking, the Monitoring Probe causing problem for IMAP is "IMAP.Protocol\ImapDeepTestProbe" When I run the command "Invoke-MonitoringProbe -Identity:"IMAP.Protocol\ImapDeepTestProbe" -Server:MY_SERVER" I received the answer below: "WARNING: No mailboxes were found to use in the DeepTest probe" I Googled this error but found nothing with this specific warning but more with CTP probe. I followed the official https://learn.microsoft.com/en-us/exchange/management/health/troubleshooting-imap-health-set?redirectedfrom=MSDN Unfortunately it did not solve the problem. I finally decided to recreate all Monitoring Mailboxes from scratch. The recreation of these mailboxes solved temporarily the problem but it came back finally, and even worst, it is now on all my Exchange nodes. IMAP is working well, it is just the Exchange health monitoring that does not work as expected and generate SCOM alerts. Did someone have the same problem? Thanks in advance for your help!!Out of Office sending internal message to external recipients
Hi folks We're running Exchange Online. Our users run Outlook clients and are given the option to set separate internal and external Out of Office automatic replies. However, it appears that only the internal replies are being sent - even when responding to external users. I've tested this with a number of accounts and this appears to be a company-wide issue, and I think the issue sits with something on the Exchange side. I have tried switching off auto-responses on Outlook and also in OWA, and then setting up the OOF within the EAC. Same occurs. Any ideas? Cheers Matt
