Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. Try the few "risky" areas on the left pane here: https://portal.azure.com/#blade/Microsoft_AAD_IAM/SecurityMenuBlade/RiskyUsers
  2. Finally got this working, it looks like the issue was Microsoft blocking the SMTP AUTH as it was deemed "Risky". I had to log into Azure portal and manually mark it as safe, then after about an hour it started to work with Automatic authentication selected.
  3. I had deleted the duplicate folder in OWA but when loading Outlook again they reappeared but I just looked and at the moment I only have one Detected Items folder in Outlook so perhaps whatever was causing this is now resolved!
  4. I updated to 7.2 (was on 7.1), closed Outlook, disabled both those options, applied, opened Outlook and when selecting one of the Detected Items folders it was fine but when selecting the other it crashed Outlook again. I can't say if the flashing has been fixed as I only had a few minutes spare to test this for you.
  5. This is something I had noticed myself but have also had several customers call about, it started within the past month. I noticed that when in Outlook (Office 365 install), the "Detected Items" folder in the left pane will flash/flicker randomly and is also duplicated 2 or 3 times. It gets even stranger when I click the "Detected Items" folder, if I click one of the instances it opens an empty folder but if I click the other instance then Outlook rapidly flicks between the two instances forcing me to have to restart Outlook so I can get into another mail folder or do anything and in some cases even crashes Outlook. I know this folder is used by Eset so though the logical place to start would be here. I have logged into OWA and deleted all instances of the Detected Items folder but multiples are recreated when I next open Outlook and the same behaviour is observed. So far I have only noticed this when using Endpoint Security.
  6. Is anyone able to confirm the TLS version used for notifications? I'm running out of ideas so wondered if it is using TLS 1.0/1.1?
  7. Any more ideas? When I get time I will try migrating my DB to a fresh VA but not likely to have time for a while yet,
  8. Thanks for the reply but I have already generated a new app password and tried an existing app password that I use for other reporting services. That was the thread I used to get the Auth type and was the first time I have seen outlook.office365.com used as the server so tried that too but no use.
  9. I have been having trouble setting up SMTP using an Office 365 exchange mailbox. I have searched this forum and found numerous threads where people had issues and checked working configs against my own and just can't work out what is wrong. My current config: I have MFA enabled and have generated an app password, the same account works fine on other devices where I set up SMTP. I have tried using outlook.office365.com as the server too, also tried port 25, TLS and a few auth types but nothing works. Any ideas where I am going wrong? I know the login credentials are valid so it is as if it's the auth type or perhaps my VA is somehow using an old TLS standard which Microsoft have now blocked? I have no outbound firewall. Thanks
  • Create New...