Sending Emails With Windows 11 Office 365 (New Outlook)

[lhooker]

Thanks for all the help. I was successful in downloading Outlook Classic. This resolved my problem of not receiving MS Access emails. Thanks again to all ! ! !

 

[lhooker]

Thanks for the help. I was able to download and install Microsoft Outlook Classic successfully. This resolved my issue of not
being able to send MS Access emails. Thanks again to all ! ! !

 

[The_Doc_Man]

As a side note, just to be ultra-cautious...

IF you removed New Outlook before loading Classic Outlook, you might have had this done automatically by the installer program. However, you are on Win11. This is a tiny little nit-picky thing to verify. Do it once and it should be permanent until/unless you change versions of Office.

Click the "Start Button" (squarish window panes, lower left corner) >> Settings >> Apps >> Default Apps >> Mail

From that section of the mail Settings bar you can verify that Classic Outlook IS your default mail utility. You MIGHT see an odd mail entry called MS-UNISTORE-MAIL added by MS for a type of internal messaging mail, but as long as it didn't somehow become the default app for Mail handling, you are OK. That name is actually an ALIAS for whatever you are using as a mail utility.

IF something went wrong and you have NO default mail utility, from that same path, you should be able to define what you wanted to use as MAIL.

 

[CJ_London]

Do be aware that classic outlook will cease to exist (or at least not supported) in I think 2029. Although Classic (i.e. the outlook application) is still available, at some point you won't be able to download it. For individuals like yourself it is not likely to be a major issue but if you are supporting companies who are constantly buying in new devices and installing office, they may not be in a position to install classic earlier that 2029.

So you may need to be thinking about it now. For sending there is CDO which should continue to work since it uses the smtp server which is what your email provider uses. But for receiving emails you typically use POP3 (emails stored on your machine) or imap, mail or a couple of others where the emails are stored on the email providers server. Once the outlook.application is no longer available you will not be able to access them.

Options are being reviewed - Powershell has been mentioned and there is also the Graph API both of which will work with incoming and outgoing emails. But there is quite a learning curve and not necessarily easy to install and implement.

This is not an access problem, but any application that uses outlook automation - word and excel immediately spring to mind.

 

[GPGeorge]

Do be aware that classic outlook will cease to exist (or at least not supported) in I think 2029. Although Classic (i.e. the outlook application) is still available, at some point you won't be able to download it. For individuals like yourself it is not likely to be a major issue but if you are supporting companies who are constantly buying in new devices and installing office, they may not be in a position to install classic earlier that 2029.

So you may need to be thinking about it now. For sending there is CDO which should continue to work since it uses the smtp server which is what your email provider uses. But for receiving emails you typically use POP3 (emails stored on your machine) or imap, mail or a couple of others where the emails are stored on the email providers server. Once the outlook.application is no longer available you will not be able to access them.

Options are being reviewed - Powershell has been mentioned and there is also the Graph API both of which will work with incoming and outgoing emails. But there is quite a learning curve and not necessarily easy to install and implement.

This is not an access problem, but any application that uses outlook automation - word and excel immediately spring to mind.

This is an extremely important point. You have roughly 3 years to identify, develop and deploy the replacement for so-called Classic Outlook. Probably less than that as you can't count on your customers all waiting until the last possible moment to adopt the New Outlook just to support your product.

As this thread has so well illustrated, there are multiple alternatives; it's a matter of picking the one that synchs up best with your current design.

 

[The_Doc_Man]

This is an extremely important point. You have roughly 3 years to identify, develop and deploy the replacement for so-called Classic Outlook. Probably less than that as you can't count on your customers all waiting until the last possible moment to adopt the New Outlook just to support your product.

As this thread has so well illustrated, there are multiple alternatives; it's a matter of picking the one that synchs up best with your current design.

As long as you can get LTSC or retail full-install versions and don't have to upgrade, you can perhaps keep on going. Office 365? If THAT is where you are, then your days are numbered with Outlook Classic.