isync-devel — All-purpose list, actually - but RTFM first. Moderated for non-subscribers for SPAM protection.

Re: How to change SyncState without duplicating every message?

[Alan S. <ala...@po...>]

Hello,

On 2025-08-01 01:05, Oswald Buddenhagen via isync-devel <isy...@li...> writes:

> On Thu, Jul 31, 2025 at 12:53:06PM +0200, Alan Schmitt wrote:
>>- is there a way to remove all these duplicate emails?
>>
> any message-id based method will work for most mails. the list archive 
> contains several related threads.

Thank you, I forgot to search the archive. It seems that
https://github.com/kdeldycke/mail-deduplicate or using mutt (I should
really give it a try) is the way to go.

>>- for the last channel to migrate, how can I make sure emails are not
>>duplicated (ideally without having to download them again)?
>>
> by moving the state files from the old to the new location (as per 
> manual), while making sure that no sync is happening during the 
> migration.

I did not see how to do that in the man page
(https://isync.sourceforge.io/mbsync.html, searching for SyncState), but
with this hint I was able to copy the files in .mbsync to their correct
location. Thanks!

Alan

Re: How to change SyncState without duplicating every message?

[Oswald B. <osw...@gm...>]

On Thu, Jul 31, 2025 at 12:53:06PM +0200, Alan Schmitt wrote:
>- is there a way to remove all these duplicate emails?
>
any message-id based method will work for most mails. the list archive 
contains several related threads.

>- for the last channel to migrate, how can I make sure emails are not
>duplicated (ideally without having to download them again)?
>
by moving the state files from the old to the new location (as per 
manual), while making sure that no sync is happening during the 
migration.

How to change SyncState without duplicating every message?

[Alan S. <ala...@po...>]

Hello,

I want to change my configuration to `Syncstate *' for all my
channels. I tried on a couple and it worked great, but after checking
outside of notmuch (which does not show duplicates), I realized every
email is now duplicated, both locally and on the server. I tried a
deduplication tool, but the presence of a different header X-TUID makes
the duplicates different. I have two questions:
- is there a way to remove all these duplicate emails?
- for the last channel to migrate, how can I make sure emails are not
duplicated (ideally without having to download them again)?

Thanks,

Alan

Re: Error about SSL "SSLType is deprecated. Use TLSType instead"

[Antoine F. <an...@qu...>]

On 24/07/2025 09:50, Oswald Buddenhagen wrote:
> On Thu, Jul 24, 2025 at 10:10:31AM +0300,  Berdnikov wrote:
>> On Wed, Jul 23, 2025 at 04:57:51PM +0200, Antoine Fauchié wrote:
>>> I've just reinstalled mbsync on a new Debian installation (12), and I 
>>> can't get mbsync/isync to work on 1.5.1 version.
>>>
>>> The error message:
>>>
>>> Error: mbsync built without OpenSSL; only TLSType None is supported.
>>
>> Very strange, all times I remember Debian has mbsync built with 
>> OpenSSL...
>> What "dpkg -s isync" shows?
>>
> i think the implication is that he installed from source, while not 
> having libssl-dev installed.
> (the package in debian sta(b)le is at v1.4.4.)

Thanks Evgeniy and Oswald,

So yes I've installed isync from source (nothing to show with "dpkg -s 
isync"), and it's better with libssl-dev installed. Is it necessary to 
add this dependence on the documentation (README)?

I have always the warning message:
"/home/a/.mbsyncrc: notice: SSLType is deprecated. Use TLSType instead."

So I switch to "TLSType IMAPS" and I'm good!


Best,
-- 
Antoine

Re: Error about SSL "SSLType is deprecated. Use TLSType instead"

[Oswald B. <osw...@gm...>]

On Thu, Jul 24, 2025 at 10:10:31AM +0300, Evgeniy Berdnikov wrote:
>On Wed, Jul 23, 2025 at 04:57:51PM +0200, Antoine Fauchié wrote:
>> I've just reinstalled mbsync on a new Debian installation (12), and I 
>> can't get mbsync/isync to work on 1.5.1 version.
>> 
>> The error message:
>> 
>> Error: mbsync built without OpenSSL; only TLSType None is supported.
>
> Very strange, all times I remember Debian has mbsync built with OpenSSL...
> What "dpkg -s isync" shows?
>
i think the implication is that he installed from source, while not 
having libssl-dev installed.
(the package in debian sta(b)le is at v1.4.4.)

Re: Error about SSL "SSLType is deprecated. Use TLSType instead"

[Evgeniy B. <bi...@pr...>]

 Hi.

On Wed, Jul 23, 2025 at 04:57:51PM +0200, Antoine Fauchié wrote:
> Hi,
> 
> I've just reinstalled mbsync on a new Debian installation (12), and I can't
> get mbsync/isync to work on 1.5.1 version.
> 
> The error message:
> 
> /home/a/.mbsyncrc: notice: SSLType is deprecated. Use TLSType instead.
> Error: mbsync built without OpenSSL; only TLSType None is supported.

 Very strange, all times I remember Debian has mbsync built with OpenSSL...
 What "dpkg -s isync" shows?
-- 
 Eugene Berdnikov

Error about SSL "SSLType is deprecated. Use TLSType instead"

[Antoine F. <an...@qu...>]

Hi,

I've just reinstalled mbsync on a new Debian installation (12), and I 
can't get mbsync/isync to work on 1.5.1 version.

The error message:

/home/a/.mbsyncrc: notice: SSLType is deprecated. Use TLSType instead.
Error: mbsync built without OpenSSL; only TLSType None is supported.

---

My config:

IMAPAccount qtnm
Host [obsfuscated]
User [obsfuscated]
PassCmd "pass mail"
SSLType IMAPS
PipelineDepth 1

IMAPStore qtnm-remote
Account qtnm

MaildirStore qtnm-local
Path ~/mail/qtnm/
Inbox ~/mail/qtnm/INBOX
SubFolders Verbatim

Channel qtnm
Far :qtnm-remote:
Near :qtnm-local:
# Precision necessary for the patterns, not just `Patterns *`
Patterns INBOX INBOX/* *
Create Both
SyncState *
Sync All
Expunge Both

---

If I run mbsync -a -D:

isync 1.5.1 called with: '-a' '-D'
Reading configuration file /home/a/.mbsyncrc
/home/a/.mbsyncrc: notice: SSLType is deprecated. Use TLSType instead.
Error: mbsync built without OpenSSL; only TLSType None is supported.
merge ops (in Channel 'qtnm'):
   common: OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE,OP_CREATE
   far: XOP_HAVE_TYPE,XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE
   near:
   => far: 
OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE,OP_CREATE,XOP_HAVE_TYPE,XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE
   => near: OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE,OP_CREATE

---

Any idea of what I'm doing wrong?


Best,
-- 
Antoine
an...@qu...

Re: Sync IMAP Mailboxes/Folders via ssh?

[Oswald B. <osw...@gm...>]

On Thu, Jul 17, 2025 at 10:33:36PM +0200, Daniel Tameling wrote:
>  mv $(mlist ./INBOX | mpick -t 'from =~ "@github"') ./github/cur
>
this will preserve the ,U=nnn infixes of the files, which is a very bad 
idea.

Re: Sync IMAP Mailboxes/Folders via ssh?

[Daniel T. <tam...@gm...>]

On Thu, Jul 17, 2025 at 08:31:00AM +0200, Peter P. wrote:
> 
> I am furthermore looking for a scriptable solution that will move all
> email older than X years from one local imap folder to another (which is
> then rsynced to a file server).
> 

I would look at mblaze. It is a collection of tools and contains the mpick command. From the example section of it's man page:
    You can pick mails to move them into another maildir.

          mv $(mlist ./INBOX | mpick -t 'from =~ "@github"') ./github/cur

    A more advanced mpick expression to pick mails in a certain time span, which are flagged as replied or not seen.

          mpick -t 'date >= "2016-01-01" && date < "2017-01-01" && (replied || !seen)'

Best regards,
Daniel

Re: Sync IMAP Mailboxes/Folders via ssh?

[Peter P. <pet...@fa...>]

* Oswald Buddenhagen via isync-devel <isy...@li...> [2025-07-17 11:42]:
> On Wed, Jul 16, 2025 at 09:37:51AM +0200, Peter P. wrote:
> > Can isync sync emails through such connections as well?
> > 
> yes.
> 
> you can run an imap server on the ssh host and have ssh forward the port to
> your local host, which you then connect via isync.
> 
> > Is the "Tunnel" commenad the way to go?
> > 
> also possible.
> one way would be running tcpconnect (or netcat) on the ssh host to connect
> the imap server locally.
> another way is to run an imap server that directly serves on stdio, for
> example panda-imap (yes, it's old, and it's what i use).
Thanks Oswald!
That's good to know!
In fact I am trying to avoid having to install and configure an imap
server to sync two folders between different hosts, as I am much more
familiar with rsync.

best, Peter

Re: Sync IMAP Mailboxes/Folders via ssh?

[Oswald B. <osw...@gm...>]

On Wed, Jul 16, 2025 at 09:37:51AM +0200, Peter P. wrote:
>Can isync sync emails through such connections as well?
>
yes.

you can run an imap server on the ssh host and have ssh forward the port 
to your local host, which you then connect via isync.

>Is the "Tunnel" commenad the way to go?
>
also possible.
one way would be running tcpconnect (or netcat) on the ssh host to 
connect the imap server locally.
another way is to run an imap server that directly serves on stdio, for 
example panda-imap (yes, it's old, and it's what i use).

Re: Sync IMAP Mailboxes/Folders via ssh?

[Peter P. <pet...@fa...>]

* Marton Balazs <ba...@gm...> [2025-07-16 17:10]:
> I use three different machines and sync all my email between them by rsync
> over SSH, so as files rather than via isync. When I boot up a machine I
> rsync down all files, including hundreds of thousands of email, from my
> home server. Some of these emails I only have as maildir files, they are
> not even on any IMAP server. I make sure dot files are synced too, and
> deletions of files also propagate. Once the rsync logs are ok I then launch
> isync to Google and M365 for those mail folders that are on there as well.
> Before closing down the machine I rsync everything, including all email, to
> the home ssh server. Next day I sit at another machine and do the same.
> This has worked reliably for me for several years, the important thing is
> to make sure everything is rsynced with no errors before isync is launched
> to my email providers. This is not exactly answering your question though...
It is to a large extent, thanks for your kind reply Marton!

I am furthermore looking for a scriptable solution that will move all
email older than X years from one local imap folder to another (which is
then rsynced to a file server).

Looking forward to this list memeber's suggestions!
Your help is much appreciated,
best, 
Peter

Re: Sync IMAP Mailboxes/Folders via ssh?

[Marton B. <ba...@gm...>]

[Clients]: I use NeoMutt; yes, operating on local maildir on my {desk/lap}tops.

[On phone/tablet]: I use the official Gmail/M365 apps. I don't move emails while on the phone, just read and, rarely, respond to them. I can also delete from Inbox, that doesn't do harm in the workflow. I don't have a tablet but I guess those could work the same way. I sort Inbox and Sent Mail on my {desk/lap}tops only, and this is propagated up to Gmail/M365 via isync.

[Why]: This seemed easiest. I think of my email as files in my ecosystem, that is local copy on the machine I'm currently on, backed up and synced to my other machines as files via my rsync-ssh server and mirrored from there by further backup ssh servers for additional safety. I find this more reassuring than trusting big corporations with all my messages. I essentially use Gmail/M365 as vehicles to collect Inbox and additional backing up my sorted folders. These latter also allow me to view these archived mails over the phone.

[Out of sync]: Yes, that's true, but working on local maildir I'm out of sync anyway so this doesn't really bother me. I isync my mails many times a day; Inbox, Sent, Spam, Deleted mail in both directions; saved folders only up to Gmail/M365. Local maildirs and Gmail/M365 get in sync with each other at those instances.

If Gmail and M365 go bust right now I only lose the newest few mails in Inbox since I last ran isync. If they decide to delete my emails they can only do harm to my Inbox which doesn't normally has too many emails. If some mails cannot be stored in Gmail or M365 (like in Peter's question) that's no problem as not all sorted maildir folders are synced up. In fact I'm deleting all emails from Google that are more than 4 years old as I'm not paying for extra storage in there. I have the old ones in my maildirs and that's enough. And, as an additional plus, an easy bash script moving everything from "Junk Email" to "Inbox" in my local maildir sorted Microsoft's stupid decision of not letting us turn off their useless spam filter. :-)

Best wishes,
Marton


On Thu, Jul 17, 2025 at 01:29:14AM +0200, H wrote:
> On July 16, 2025 5:09:57 PM GMT+02:00, Marton Balazs <ba...@gm...> wrote:
> >I use three different machines and sync all my email between them by
> >rsync
> >over SSH, so as files rather than via isync. When I boot up a machine I
> >rsync down all files, including hundreds of thousands of email, from my
> >home server. Some of these emails I only have as maildir files, they
> >are
> >not even on any IMAP server. I make sure dot files are synced too, and
> >deletions of files also propagate. Once the rsync logs are ok I then
> >launch
> >isync to Google and M365 for those mail folders that are on there as
> >well.
> >Before closing down the machine I rsync everything, including all
> >email, to
> >the home ssh server. Next day I sit at another machine and do the same.
> >This has worked reliably for me for several years, the important thing
> >is
> >to make sure everything is rsynced with no errors before isync is
> >launched
> >to my email providers. This is not exactly answering your question
> >though...
> >
> >Best wishes
> >Marton
> >
> >On Wed, 16 Jul 2025, 08:41 Peter P., <pet...@fa...> wrote:
> >
> >> Hi list,
> >>
> >> (this might be slightly-OT)
> >>
> >> my employer is forcing me to host all emails, that are older than X
> >> years, somewhere else than on his IMAP server. I am using multiple
> >> clients and isync. I am now thinking of moving certain imap folders
> >from
> >> the employer's server to some network storage, which would only be
> >> accessible through ssh/scp/rsync but not through the imap protocol.
> >>
> >> Can isync sync emails through such connections as well?
> >> Is the "Tunnel" commenad the way to go?
> >>
> >> Thanks for all ideas and advice!
> >> Peter
> >>
> >>
> >> _______________________________________________
> >> isync-devel mailing list
> >> isy...@li...
> >> https://lists.sourceforge.net/lists/listinfo/isync-devel
> >>
> 
> Interesting approach. Which mail client(s) do you then use on the different machines? Am I correct that the mail client(s) accesses the local mail storage on the desktop rather than your mail server?
> 
> How do you handle the mail accounts on phones/tablets?
> 
> Why did you choose approach? It would seem to me that the mail clients on e.g. a phone and the desktop you are currently using will be out of sync?
> 
> 
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sync IMAP Mailboxes/Folders via ssh?

[H <ag...@me...>]

On July 16, 2025 5:09:57 PM GMT+02:00, Marton Balazs <ba...@gm...> wrote:
>I use three different machines and sync all my email between them by
>rsync
>over SSH, so as files rather than via isync. When I boot up a machine I
>rsync down all files, including hundreds of thousands of email, from my
>home server. Some of these emails I only have as maildir files, they
>are
>not even on any IMAP server. I make sure dot files are synced too, and
>deletions of files also propagate. Once the rsync logs are ok I then
>launch
>isync to Google and M365 for those mail folders that are on there as
>well.
>Before closing down the machine I rsync everything, including all
>email, to
>the home ssh server. Next day I sit at another machine and do the same.
>This has worked reliably for me for several years, the important thing
>is
>to make sure everything is rsynced with no errors before isync is
>launched
>to my email providers. This is not exactly answering your question
>though...
>
>Best wishes
>Marton
>
>On Wed, 16 Jul 2025, 08:41 Peter P., <pet...@fa...> wrote:
>
>> Hi list,
>>
>> (this might be slightly-OT)
>>
>> my employer is forcing me to host all emails, that are older than X
>> years, somewhere else than on his IMAP server. I am using multiple
>> clients and isync. I am now thinking of moving certain imap folders
>from
>> the employer's server to some network storage, which would only be
>> accessible through ssh/scp/rsync but not through the imap protocol.
>>
>> Can isync sync emails through such connections as well?
>> Is the "Tunnel" commenad the way to go?
>>
>> Thanks for all ideas and advice!
>> Peter
>>
>>
>> _______________________________________________
>> isync-devel mailing list
>> isy...@li...
>> https://lists.sourceforge.net/lists/listinfo/isync-devel
>>

Interesting approach. Which mail client(s) do you then use on the different machines? Am I correct that the mail client(s) accesses the local mail storage on the desktop rather than your mail server?

How do you handle the mail accounts on phones/tablets?

Why did you choose approach? It would seem to me that the mail clients on e.g. a phone and the desktop you are currently using will be out of sync?

Re: Sync IMAP Mailboxes/Folders via ssh?

[Marton B. <ba...@gm...>]

I use three different machines and sync all my email between them by rsync
over SSH, so as files rather than via isync. When I boot up a machine I
rsync down all files, including hundreds of thousands of email, from my
home server. Some of these emails I only have as maildir files, they are
not even on any IMAP server. I make sure dot files are synced too, and
deletions of files also propagate. Once the rsync logs are ok I then launch
isync to Google and M365 for those mail folders that are on there as well.
Before closing down the machine I rsync everything, including all email, to
the home ssh server. Next day I sit at another machine and do the same.
This has worked reliably for me for several years, the important thing is
to make sure everything is rsynced with no errors before isync is launched
to my email providers. This is not exactly answering your question though...

Best wishes
Marton

On Wed, 16 Jul 2025, 08:41 Peter P., <pet...@fa...> wrote:

> Hi list,
>
> (this might be slightly-OT)
>
> my employer is forcing me to host all emails, that are older than X
> years, somewhere else than on his IMAP server. I am using multiple
> clients and isync. I am now thinking of moving certain imap folders from
> the employer's server to some network storage, which would only be
> accessible through ssh/scp/rsync but not through the imap protocol.
>
> Can isync sync emails through such connections as well?
> Is the "Tunnel" commenad the way to go?
>
> Thanks for all ideas and advice!
> Peter
>
>
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>

Sync IMAP Mailboxes/Folders via ssh?

[Peter P. <pet...@fa...>]

Hi list,

(this might be slightly-OT)

my employer is forcing me to host all emails, that are older than X
years, somewhere else than on his IMAP server. I am using multiple
clients and isync. I am now thinking of moving certain imap folders from
the employer's server to some network storage, which would only be
accessible through ssh/scp/rsync but not through the imap protocol.

Can isync sync emails through such connections as well?
Is the "Tunnel" commenad the way to go?

Thanks for all ideas and advice!
Peter

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Peter P. <pet...@fa...>]

Hi Norm, hi list,

* Norm Wood <nor...@fa...> [2025-07-09 13:06]:
[...]
> One thing I'll mention to possibly help future readers is that I didn't need
> to install the Moriyoshi cyrus-sasl-xoauth2 plugin.  Some linux
> distributions include libkdexoauth2 (in Slackware 15, this is in
> /usr/lib64/sasl2) and this provides the xoauth2 plugin.
Good to know! It seems that Debian stable does not feature such a
package, or I didn't find it (yet).

best, P

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Peter P. <pet...@fa...>]

* Norm Wood <nor...@fa...> [2025-07-09 13:41]:
[...]
> Ah, I wouldn't have picked that up from your list address.  Yes, always good
> to bump into another Fastmail user!
Indeed! :)
P

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Norm W. <nor...@fa...>]

Hi Peter and list,

I just realized that I received some advice off-list from another list 
member.  It helped me resolve the problem, but the conversation about 
how I resolved the problem isn't in the list for future readers.

The problem was in my mbsyncrc.  In the IMAPAccount section, I had set 
the "User" entry as:

    User username@wor...@ou...

This is the form used by my email client for connecting to my work's 
IMAP server.  For mbsync, it just should be

    User username@workdomain

With this change, the authentication error was resolved and mbsync 
started syncing my work email.

I ran into one other problem - my work's IMAP server terminated the 
connection after the sync had partially processed my messages.  To avoid 
this, I added an entry

    PipelineDepth 1

to my IMAPAccount section.

With these changes, I was able to successfully sync with my work email
using mbsync with mutt_oauth2.py.

Regards,
Norm


On 09 Jul, Norm Wood wrote:
>Hi Peter,
>
>Thanks for providing the details of how you set this up with oauth2ms.
>
>I ended up returning to using mutt_oauth2.py, since I was already 
>using it with mutt.  It worked fine after correcting the "User" entry 
>in the IMAPAccount section of my mbsyncrc as pointed out by Marton 
>(and as described in Marton's webpage, a detail that I overlooked).
>
>One thing I'll mention to possibly help future readers is that I 
>didn't need to install the Moriyoshi cyrus-sasl-xoauth2 plugin.  Some 
>linux distributions include libkdexoauth2 (in Slackware 15, this is in 
>/usr/lib64/sasl2) and this provides the xoauth2 plugin.
>
>Thanks for the support, it's appreciated!
>
>Regards,
>Norm
>
>
>On 08 Jul, Peter P. wrote:
>>Hi Norm,
>>
>>* Norm Wood <nor...@fa...> [2025-07-07 19:36]:
>>[...]
>>>appreciate suggestions on how to diagnose the problem further.  After
>>>looking through isync-devel, I've also tried authenticating using the
>>>oauth2ms tool.
>>
>>I had success here with the instructions from
>>https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html
>>and below are my notes from how I did it about two years ago. Perhaps
>>this is helpful? They come without any warranty though.
>>
>>best, Peter
>>
>>------>
>>	sudo aptitude install libsasl2-dev
>>	git clone https://github.com/moriyoshi/cyrus-sasl-xoauth2.git
>>	./autogen.sh
>>	./configure
>>Edit Makefile to have the line
>>	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/sasl2
>>yield
>>	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/x86_64-linux-gnu/sasl2
>>and run
>>	sudo make install
>>which installs libraries into /usr/lib/x86_64-linux-gnu/sasl2
>>Reinstall isync to make it aware of the new sasl plugin(?)
>>	sudo aptitude reinstall isync
>>Get this following tool to fetch oauth2 tokens and copy it into ~/bin
>>	git clone https://github.com/harishkrupo/oauth2ms.git
>>	cd oauth2ms
>>	cp oauth2ms ~/bin/
>>Install requirements via apt
>>	apt install python3-xdg python3-msal python3-gnupg
>>Now I need to create and edit ~/.config/oauth2ms/config.json to yield
>>	{
>>		"tenant_id": "TENANT_ID",
>>		"client_id": "CLIENT_ID",
>>		"client_secret": "CLIENT_SECRET",
>>		"redirect_host": "localhost",
>>		"redirect_port": "5000",
>>		"redirect_path": "/getToken/",
>>		"scopes": ["https://outlook.office.com/IMAP.AccessAsUser.All", "https://outlook.office.com/SMTP.Send"]
>>	}
>>Where TENANT_ID and CLIENT_ID are long strings which I got from the
>>local administrators of that email service.
>>Then I ran oauth2ms and it opened a browser through which I logged in and oauth2ms received a token in return, which got stored as ~/.local/share/oauth2ms/credentials.bin
>>
>>
>>_______________________________________________
>>isync-devel mailing list
>>isy...@li...
>>https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Norm W. <nor...@fa...>]

Hi Christopher,

On 08 Jul, Christopher Snowhill wrote:
>On Mon Jul 7, 2025 at 10:23 AM PDT, Norm Wood wrote:
>> Well, heck, looks like I didn't attached the *cleaned* mbsyncrc.  If a
>> mod could delete the previous message or the mbsyncrc attachment,
>> please, I'll resend it.
>
>You got off slightly lucky, in that you only leaked your Office email
>address, and not the tokens file.

Yes, luckily that was all that leaked.

>Which, by the way, you may have named
>incorrectly in your mbsyncrc?
>
>o364 -> o365 ?

Good catch!  But no, that is a naming from several years ago that I
have just left as-is.

>Also, on your list address, hello, fellow Fastmail user.

Ah, I wouldn't have picked that up from your list address.  Yes, always 
good to bump into another Fastmail user!

Regards,
Norm

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Norm W. <nor...@fa...>]

Hi Peter,

Thanks for providing the details of how you set this up with oauth2ms.

I ended up returning to using mutt_oauth2.py, since I was already using 
it with mutt.  It worked fine after correcting the "User" entry in the 
IMAPAccount section of my mbsyncrc as pointed out by Marton (and as 
described in Marton's webpage, a detail that I overlooked).  

One thing I'll mention to possibly help future readers is that I didn't 
need to install the Moriyoshi cyrus-sasl-xoauth2 plugin.  Some linux 
distributions include libkdexoauth2 (in Slackware 15, this is in 
/usr/lib64/sasl2) and this provides the xoauth2 plugin.

Thanks for the support, it's appreciated!

Regards,
Norm


On 08 Jul, Peter P. wrote:
>Hi Norm,
>
>* Norm Wood <nor...@fa...> [2025-07-07 19:36]:
>[...]
>> appreciate suggestions on how to diagnose the problem further.  After
>> looking through isync-devel, I've also tried authenticating using the
>> oauth2ms tool.
>
>I had success here with the instructions from
>https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html
>and below are my notes from how I did it about two years ago. Perhaps
>this is helpful? They come without any warranty though.
>
>best, Peter
>
>------>
>	sudo aptitude install libsasl2-dev
>	git clone https://github.com/moriyoshi/cyrus-sasl-xoauth2.git
>	./autogen.sh
>	./configure
>Edit Makefile to have the line
>	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/sasl2
>yield
>	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/x86_64-linux-gnu/sasl2
>and run
>	sudo make install
>which installs libraries into /usr/lib/x86_64-linux-gnu/sasl2
>Reinstall isync to make it aware of the new sasl plugin(?)
>	sudo aptitude reinstall isync
>Get this following tool to fetch oauth2 tokens and copy it into ~/bin
>	git clone https://github.com/harishkrupo/oauth2ms.git
>	cd oauth2ms
>	cp oauth2ms ~/bin/
>Install requirements via apt
>	apt install python3-xdg python3-msal python3-gnupg
>Now I need to create and edit ~/.config/oauth2ms/config.json to yield
>	{
>		"tenant_id": "TENANT_ID",
>		"client_id": "CLIENT_ID",
>		"client_secret": "CLIENT_SECRET",
>		"redirect_host": "localhost",
>		"redirect_port": "5000",
>		"redirect_path": "/getToken/",
>		"scopes": ["https://outlook.office.com/IMAP.AccessAsUser.All", "https://outlook.office.com/SMTP.Send"]
>	}
>Where TENANT_ID and CLIENT_ID are long strings which I got from the
>local administrators of that email service.
>Then I ran oauth2ms and it opened a browser through which I logged in and oauth2ms received a token in return, which got stored as ~/.local/share/oauth2ms/credentials.bin
>
>
>_______________________________________________
>isync-devel mailing list
>isy...@li...
>https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Christopher S. <ch...@ko...>]

On Mon Jul 7, 2025 at 10:23 AM PDT, Norm Wood wrote:
> Well, heck, looks like I didn't attached the *cleaned* mbsyncrc.  If a 
> mod could delete the previous message or the mbsyncrc attachment, 
> please, I'll resend it.

You got off slightly lucky, in that you only leaked your Office email
address, and not the tokens file. Which, by the way, you may have named
incorrectly in your mbsyncrc?

o364 -> o365 ?

Also, on your list address, hello, fellow Fastmail user.

>
> Thanks,
> Norm

Hope I helped,
Christopher

>
>
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Peter P. <pet...@fa...>]

Hi Norm,

* Norm Wood <nor...@fa...> [2025-07-07 19:36]:
[...]
> appreciate suggestions on how to diagnose the problem further.  After
> looking through isync-devel, I've also tried authenticating using the
> oauth2ms tool.  

I had success here with the instructions from
https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html
and below are my notes from how I did it about two years ago. Perhaps
this is helpful? They come without any warranty though.

best, Peter

------>
	sudo aptitude install libsasl2-dev
	git clone https://github.com/moriyoshi/cyrus-sasl-xoauth2.git
	./autogen.sh
	./configure
Edit Makefile to have the line
	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/sasl2
yield
	pkglibdir = ${CYRUS_SASL_PREFIX}/lib/x86_64-linux-gnu/sasl2
and run
	sudo make install
which installs libraries into /usr/lib/x86_64-linux-gnu/sasl2
Reinstall isync to make it aware of the new sasl plugin(?)
	sudo aptitude reinstall isync
Get this following tool to fetch oauth2 tokens and copy it into ~/bin
	git clone https://github.com/harishkrupo/oauth2ms.git
	cd oauth2ms
	cp oauth2ms ~/bin/
Install requirements via apt
	apt install python3-xdg python3-msal python3-gnupg
Now I need to create and edit ~/.config/oauth2ms/config.json to yield
	{
		"tenant_id": "TENANT_ID",
		"client_id": "CLIENT_ID",
		"client_secret": "CLIENT_SECRET",
		"redirect_host": "localhost",
		"redirect_port": "5000",
		"redirect_path": "/getToken/",
		"scopes": ["https://outlook.office.com/IMAP.AccessAsUser.All", "https://outlook.office.com/SMTP.Send"]
	}
Where TENANT_ID and CLIENT_ID are long strings which I got from the
local administrators of that email service.
Then I ran oauth2ms and it opened a browser through which I logged in and oauth2ms received a token in return, which got stored as ~/.local/share/oauth2ms/credentials.bin

Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Norm W. <nor...@fa...>]

Hi,

The overview is that I am using mbsync to try to make a local mirror of 
my work email, which is located on outlook.office365.com.  I already 
have a working mutt_oauth2.py setup that I use with mutt to read this 
email via IMAP.  With mbsync, however, using the same mutt_oauth2.py 
setup, the sync fails with an "AUTHENTICATE failed" message. 

I've attached text files of mbsyncrc and diagnostic messages.  I'd 
appreciate suggestions on how to diagnose the problem further.  After 
looking through isync-devel, I've also tried authenticating using the 
oauth2ms tool.  I can provide details of that also, but it failed with 
the same messages. 

This is on a Slackware 15 system, and the SASL framework linked to 
mbsync is Cyrus SASL 2.1.28.

Thanks,
Norm

Re: Outlook XOAUTH2 "AUTHENTICATE failed" message with working mutt_oauth2.py

[Norm W. <nor...@fa...>]

Well, heck, looks like I didn't attached the *cleaned* mbsyncrc.  If a 
mod could delete the previous message or the mbsyncrc attachment, 
please, I'll resend it.

Thanks,
Norm