Emails cannot be fetched from MS365

With no changes having been done from our side to the configuration in either Zammad or MS365, Zammad stopped fetching emails from Microsoft this morning.

I tried to re-authenticate but to no avail - the final message remains AUTHENTICATE failed even though I was clearly able to log in to Microsoft with these credentials.

I also tried rebooting the server and updating to the latest package (I’m on Ubuntu 20.04 and installed Zammad by package) but that didn’t help either.

This is what I could find in production.log about it.

(eval):1:in `eval_job_method'
lib/background_services/service/process_scheduled_jobs/job_executor.rb:48:in `eval'
lib/background_services/service/process_scheduled_jobs/job_executor.rb:48:in `eval_job_method'
lib/background_services/service/process_scheduled_jobs/job_executor.rb:23:in `execute'
lib/background_services/service/process_scheduled_jobs/job_executor/continuous.rb:16:in `block in run_loop'
lib/background_services/service/process_scheduled_jobs/job_executor/continuous.rb:15:in `times'
lib/background_services/service/process_scheduled_jobs/job_executor/continuous.rb:15:in `run_loop'
lib/background_services/service/process_scheduled_jobs/job_executor/continuous.rb:8:in `run'
lib/background_services/service/process_scheduled_jobs/job_executor.rb:10:in `run'
lib/background_services/service/process_scheduled_jobs/manager.rb:84:in `block in start_in_thread'
lib/application_handle_info.rb:19:in `use'
lib/background_services/service/process_scheduled_jobs/manager.rb:82:in `start_in_thread'
lib/background_services/service/process_scheduled_jobs/manager.rb:73:in `block (2 levels) in start'
lib/background_services/service/process_scheduled_jobs/manager.rb:72:in `block in start'
I, [2023-08-11T08:38:32.364638#22585-112600]  INFO -- : fetching imap (outlook.office365.com/acct1@example.ch port=993,ssl=true,starttls=false,folder=INBOX,keep_on_server=true,auth_type=XOAUTH2)
I, [2023-08-11T08:38:32.374614#22585-112080]  INFO -- : ProcessScheduledJobs running...
I, [2023-08-11T08:38:32.388123#22585-112080]  INFO -- : Running job thread for 'Check 'Channel' streams.' (Channel.stream) status is: sleep
I, [2023-08-11T08:38:32.394982#22585-112080]  INFO -- : Running job thread for 'Generate 'Session' data.' (Sessions.jobs) status is: sleep
I, [2023-08-11T08:38:32.395074#22585-112080]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2023-08-11T08:38:32.395146#22585-112080]  INFO -- : Running job thread for 'Check channels.' (Channel.fetch) status is: sleep
I, [2023-08-11T08:38:32.396463#22585-112080]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2023-08-11T08:38:32.477893#22589-230700]  INFO -- : Started POST "/api/v1/integration/smime" for 87.239.202.134 at 2023-08-11 08:38:32 +0000
I, [2023-08-11T08:38:32.487364#22589-230700]  INFO -- : Processing by Integration::SMIMEController#search as JSON
I, [2023-08-11T08:38:32.487457#22589-230700]  INFO -- :   Parameters: {"ticket"=>{"group_id"=>"1", "owner_id"=>"1259", "state_id"=>"4", "priority_id"=>"2", "my_task"=>""}, "article"=>{"body"=>"[FILTERED]", "type"=>"note", "internal"=>true, "form_id"=>"657730717", "shared_draft_id"=>"", "subtype"=>"", "in_reply_to"=>"", "to"=>"", "cc"=>"", "subject"=>""}}
I, [2023-08-11T08:38:32.505806#22589-230700]  INFO -- : Completed 200 OK in 18ms (Views: 0.2ms | ActiveRecord: 7.6ms | Allocations: 5576)
E, [2023-08-11T08:38:32.792716#22585-112600] ERROR -- : Can't use Channel::Driver::Imap: #<Net::IMAP::NoResponseError: AUTHENTICATE failed.>
E, [2023-08-11T08:38:32.792820#22585-112600] ERROR -- : AUTHENTICATE failed. (Net::IMAP::NoResponseError)
app/models/channel/driver/imap.rb:124:in `block in fetch'
app/models/channel/driver/imap.rb:582:in `timeout'
app/models/channel/driver/imap.rb:122:in `fetch'
app/models/channel.rb:56:in `fetch'
app/models/channel.rb:30:in `fetch'

Because of the “NoResponseError”, I assume this is an issue with Microsoft that will go away by itself at some point but I can’t say for sure. Maybe someone here has a recommendation.

Hi @vic. It seems to be an issue on Microsoft’s side, it should be fine after the issues are resolved there.

1 Like

Same Problem here, fetching via IMAP not working. Sending via SMTP works.

same problem here. location switzerland. we wait for microsoft

problems of microsoft seems to be solved. mail fetching works again

1 Like

Thanks for keeping us updated!

Indeed, the issue seems to have been resolved, Zammad is fetching emails again.

I’m curious, do we have any explanation from Microsoft about this? It’s been almost a full work day, after all.

Microsoft published the following Information:

EX666988, betroffener Dienst: Exchange Online, betroffenes Feature: E-Mail and calendar access, aktueller Status: Service restored

Published Time: 11.08.2023 16:31:58

Titel: Einige Benutzer konnten möglicherweise nicht mit der IMAP4-Verbindungsmethode in Exchange Online auf ihr Postfach zugreifen

Auswirkungen auf den Benutzer: Benutzer konnten möglicherweise nicht über die IMAP4-Verbindungsmethode in Exchange Online auf ihr Postfach zugreifen.

Weitere Informationen: Alle anderen Verbindungsmethoden waren von diesem Problem nicht betroffen.

Endgültiger Status: Der Fix wurde erfolgreich abgeschlossen, und zuvor betroffene Benutzer haben bestätigt, dass die Auswirkungen behoben wurden.

Ausmaß der Auswirkungen: Die Auswirkungen waren spezifisch für Benutzer, die über die betroffene Infrastruktur gehostet wurden, und können sich auf alle Benutzer ausgewirkt haben, die versucht haben, über die IMAP4-Verbindungsmethode (Internet Message Access Protocol) in Exchange Online auf ihr Postfach zuzugreifen.

Startzeit: Donnerstag, 10. August 2023 um 18:35 Uhr UTC

Endzeit: Freitag, 11. August 2023 um 14:11 Uhr UTC

Hauptursache: Ein Konfigurationsproblem im Rahmen einer kürzlich vorgenommenen Änderung zur Verbesserung der Benutzerfreundlichkeit für die IMAP4-Verbindungsmethode verursachte versehentlich Zugriffsprobleme auf die Postfächer der Benutzer.

Nächste Schritte:

  • Wir überprüfen unsere Verfahren zur Aktualisierung der IMAP4-Konfiguration, um zu verhindern, dass dieses Problem erneut auftritt.

Dies ist das letzte Update für dieses Event.

Published Time: 11.08.2023 15:52:40

First Publication about the issue was on Friday, 09:56

1 Like

Please don’t post german in this community the next time.
Below you’ll find a google translated version for those who don’t speak german.

EX666988 Affected service: Exchange Online Affected feature: E-Mail and calendar access Current status: Service restored

Published Time: 11.08.2023 16:31:58

Title: Some users might not be able to access their mailbox using the IMAP4 connection method in Exchange Online

Impact on the user: Users might not be able to access their mailbox using the IMAP4 connection method in Exchange Online.

Additional Information: All other connection methods were unaffected by this issue.

Final Status: The fix completed successfully and previously affected users have confirmed that the impact has been resolved.

Impact magnitude: The impact was specific to users hosted on the affected infrastructure and may have impacted all users attempting to access their mailbox over the Internet Message Access Protocol (IMAP4) connection method in Exchange Online .

Start time: Thursday, August 10, 2023 at 18:35 UTC

End Time: Friday, August 11, 2023 at 14:11 UTC

Root Cause: A configuration issue as part of a recent change to improve the user experience for the IMAP4 connection method inadvertently caused inadvertent access issues to users’ mailboxes.

Next Steps:

We are reviewing our IMAP4 configuration update procedures to prevent this issue from reoccurring.
This is the last update for this event.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.