Oswald Buddenhagen writes:
> On Sun, Jul 16, 2023 at 02:05:51AM +, hus...@alshehhi.io wrote:
>> Is there a way to find the offending message?
> probably the easiest way is to add -DN to the mbsync arguments. then you
> can directly grep for the message's content.
Thank you. -DN does the
On Mon, Jul 17, 2023 at 01:01:42PM +0100, Abdul-Lateef Haji-Ali via isync-devel
wrote:
Today, I start experiencing issues when mbsync connects to an Outlook
server.
Socket error on outlook.office365.com (52.98.236.146:993): timeout.
However, other clients seem to be able to connect to the
Hello,
Today, I start experiencing issues when mbsync connects to an Outlook server.
The relevant part in my config is (used to work flawlessly until today):
Host outlook.office365.com
Port 993
CertificateFile /etc/ssl/cert.pem
This is the output when running `mbsync -VD hw`:
isync 1.5.0
