MAC - Importing Legacy POP On My Computer data
The end is nigh for Legacy thus I did the switch as a test knowing I could still revert. Background: I have long time POP account. In the UBF8T346G9.Office, Outlook, Outlook 15 Profiles, Main Profile: Data folder: 159 GB. Largest folders: Message Attachments: 90 GB Message Sources: 65 GB Messages: 5 GB Before I switching I tried: Export Data to OLM – don't have enough room Delete attachments from multiple emails – can only do one email at a time. Rules can't help After switch it began importing On My Computer data which was hopeful, but it held at 141498 items, and would take days I read. I reverted back to Legacy and will go another way about it when I have a few off days. My question: Apart from deleting years of emails, what's a better way to get the most data out of Legacy, and/or speeding up the import? Get another drive and Export Data to OLM, then manually import? Delete attachment folders directly from Message Attachments folder? Find something like Clean my Mac? ?? Perfect world I get all my in out mail with whatever attachments remain and Calendar data, but I'll take what I can get at this point. Appreciated!
Outlook IMAP in PHP
I'm trying to retrieve inbox mail using IMAP, but I'm encountering the following error. I've attached the code and error details below. Please advise. $imapServer = "{outlook.office365.com:993/imap/ssl/novalidate-cert}INBOX"; $username = '*************'; $password = '*************'; // Use an App Password for security $imapStream = imap_open($imapServer, $username, $password, OP_READONLY, 0, ['DISABLE_AUTHENTICATOR' => 'GSSAPI']); I'm getting this error: A PHP Error was encountered Severity: Warning Message: imap_open(): Couldn't open stream {outlook.office365.com:993/imap/ssl/novalidate-cert}INBOX Filename: controllers/Cron_Controller.php Line Number: 39 Backtrace: File: C:\xampp73\htdocs\WPS2.0_2025_03_04_1847\application\controllers\Cron_Controller.php Line: 39 Function: imap_open File: C:\xampp73\htdocs\WPS2.0_2025_03_04_1847\index.php Line: 348 Function: require_once A PHP Error was encountered Severity: Notice Message: Unknown: LOGIN failed. (errflg=1) Filename: Unknown Line Number: 0 Backtrace Thanks & Regards Kumaresan
View Group membership in outlook app for any user
Earlier version of Outlook Desktop application use to provide Group / DL membership information of any user, within the user property window opened from the Address Book or from any email. But the latest version of Outlook Windows app as well as the Outlook Webapp for Microsoft 365 no longer provide this Group / DL membership info within the User property. Does this require some configuration change at the Admin level (https://learn.microsoft.com/en-us/microsoft-365/enterprise/manage-microsoft-365-groups-with-powershell?view=o365-worldwide#hide-microsoft-365-groups-from-the-global-address-list) ? OR Is there an alternate option available within the new Outlook Windows app to view the Group / DL membership of any user?
Outlook App on phone : distribution lists and distribution groups
A client uses distribution lists (DLs, aka Outlook Contact Groups) to send mailshots Bcc: to external contacts who are members of their club. There are 21 distribution lists, each with typically 300 addressees; some members are in more than one list. They update the lists and add or remove lists using Windows Outlook. A few of the lists are nested, with several child lists being mailable from a parent list as well as individually. All fine. Client happy. They now wish to mailshot from phones as well as from Windows desktop. But Outlook Android and iOS apps don’t support DLs*, whether created on the phone or synched from Exchange. They find Outlook on the Web clunky to use with a phone screen. And the eventual solution must be manageable from Outlook and not need the Exchange Admin Centre (EAC) or Powershell. They were advised (in Microsoft documentation I think) to switch to ‘Microsoft 365 Groups’ which ARE supported by the Outlook app. But Microsoft 365 Groups themselves – with their own Sharepoint site and group calendar as well as mail – are clearly for team-working and collaboration, and managing 21 of them just to distribute mail is NOT the most elegant solution and don't resemble DLs at all. And Microsoft 365 Groups cannot apparently be nested. MSFT has made the wrong assumption that a DL has been superseded by a Group – that a Group contains everything a DL does and more. And that is the problem: Groups with or without Sharepoint libraries and Calendars are clearly designed for Teams. But ‘Traditional’ DLs are also used for mailshots to customers, suppliers and so on. Does anyone want their customers to receive an introductory email saying “Welcome to the XYZ Group…use the group to share messages and files, and to coordinate group events” ? And ‘traditional’ DLs are maintained via Windows Outlook (or Outlook on the web) by clerical staff who should not (and do not want to) be exposed to the fearsome technicalities of EAC or Microsoft 365 AC. Distribution groups (NB not DLs!) sound a more promising solution, but there is no obvious way to create one in Windows Outlook: Groups Yes, but Distribution Groups No. If a Distribution Group is created in EAC, it is then necessary to go via Delivery Management to restrict the specified sender. To resemble sending Bcc: to a DL, there needs to be one nominated sender, and the recipient must be able to reply to the sender but not to see anyone else to whom the email has been distributed (and hence not be able to reply to them). If any of this functionality is available with a Distribution Groups, perhaps someone can enlighten me. My client is now seriously testing WhatsApp, on the basis that even though broadcast lists (=Bcc DLs) are only supported on a single phone, this is an improvement on the Outlook app that doesn’t support them at all. (WhatsApp Groups, =Cc: DLs, are synched over up to 4 devices, including Windows PCs) Since there seems to be nothing relevant in the MSFT Roadmap for the mobile app, suggestions please? * if this is a restriction of EAS, MSFT seems to have been forgotten that much – perhaps most – phone use is now on WiFi-enabled broadband where the bandwidth and latency constraints should not be a problem.
