Jul 31 2022 06:52 AM - edited Jul 31 2022 07:06 AM
Until recently I have collected email from the server using Outlook2016 using POP but, in preparation for Basic Authentication being deprecated in October, I switched to using Exchange on Outlook, because it is the only method that Outlook supports with Modern Authentication. However I notice that this strips off the actual address that emails are sent to and replaces this with my primary address. So all alias email addresses, which were retained by POP collection, are lost when using Exchange. How can this be fixed?
The reason I use alias addresses in the first place is to simply and quickly identify compromised online accounts. So, for example, when I opened an Amazon account I linked that to an alias email address, amazon@mydomain, rather than my primary email@mydomain. If I ever get spam addressed to amazon@mydomain then I know the account has been compromised, either by hackers or by Amazon selling my details (I’m not suggesting Amazon would, but some companies certainly do, possibly by their financial administrators when being wound up). So my primary email has, literally, hundreds of alias addresses and, over the years, this has successfully identified several online breaches.
However this simple security procedure won’t work any longer due to Exchange replacing the “To” address with my primary address. So, when I now get an email from Amazon, even legitimate ones, it appears in Outlook2016 to be sent to email@mydomain instead of only the alias amazon@mydomain address that Amazon know about. Apparently, this is a well known bug in Outlook and Exchange which has remained uncorrected for years. 😞
Can anyone suggest a fix to ensure Outlook respects the original, alias, “To” address these emails are sent to, when collecting email by Exchange, just as it did with POP or IMAP?
Aug 01 2022 06:28 AM
Aug 01 2022 06:36 AM
Aug 01 2022 06:38 AM
Aug 01 2022 07:42 AM
Aug 01 2022 07:47 AM
Aug 01 2022 01:35 PM
Aug 02 2022 12:13 AM
Jul 31 2022 07:57 AM
Solution