IMAP Mail Migration
Hello Microsoft Community, We are currently performing a mailbox migration from Google Workspace (Gmail) to Microsoft 365 Exchange Online using the IMAP migration method. The customer's environment is configured for split routing/coexistence, where both Google Workspace and Microsoft 365 are actively being used during the migration process. Mail flow is functioning as expected; however, we are experiencing extremely slow migration performance. For example, a mailbox containing approximately 10 GB of data is taking nearly two weeks to migrate, which is significantly impacting the overall project timeline. We would appreciate guidance on the following: Is this migration speed expected when using the IMAP migration method from Google Workspace to Exchange Online? Does Exchange Online enforce any throttling limits that can affect IMAP migration throughput? Can split routing or coexistence between Google Workspace and Microsoft 365 impact IMAP migration performance? Is there a recommended number of concurrent mailbox migrations or migration batch size for optimal performance? Are there any Google Workspace-side limitations, API restrictions, or throttling settings that should be reviewed? What Microsoft-recommended configurations or best practices can help improve IMAP migration speed? If higher migration throughput is required, does Microsoft recommend an alternative migration approach instead of IMAP? If split routing/coexistence must remain active throughout the migration project, what is the recommended Microsoft-supported migration method? We are trying to identify whether the bottleneck is on the Exchange Online side, Google Workspace side, or related to the coexistence configuration. Any troubleshooting guidance, performance recommendations, or Microsoft documentation references would be greatly appreciated.Using a scanner device with HVE
Has anyone had any success in setting up a scanner device with HVE? Everything I've read about the HVE option allows for a scanner to send to HVE, but as I've had no luck in getting my Brother ADS-2800 to communicate with HVE. I've confirmed the settings multiple times, but keep getting the same error when I attempt a test email from the scanner. " Communication over the network using SSL was unsuccessful. The SSL settings may not be configured to match the server settings. Confirm the send e-mail server "Port" and the setting for "SSL/TLS". We'd like to use these scanners for sending into a pre-designated internal mailbox. In theory it should work - in practice however, different story.
Issue with certificate renewal for exchange Edge Transport Server
Hello team, I have come across a very particular problem I deployed 2 exchange server 2019 with one edge transport server When we are renewing the Certificates with wildcard certificate on both mailbox server ,and on edge transport server ,it is impossible for me to renew the edge subscription It says the cerificate is in "doublon" (repetitive) on one of the Exchange servers.I have always been using same certificate on exchange server be it edge or mailbox I tested a bogus different certificate on mailbox and on edge,only then th e edge sync works Did anybody come across this issue. Thanks
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
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.
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?
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!!
