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

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

Re: moved mails show up as new

[<ko...@gm...>]

Hi, please ignore the previous reply without the mailing list in the To:.

I figured it out.
~/Mail/xx...@gm.../INBOX/cur/1750696320.159179_1.shuttle-fedora,U=1:2,S
should become
~/Mail/xx...@gm.../Spam/cur/1750696320.159179_1.shuttle-fedora:2,S

The previous safeMove function should be...

function safeMove() {
    no_uid_filename=`echo $1 | awk -F/ '{split($NF, arr, ","); split(arr[2], arr2, ":"); printf("%s:%s,%s", arr[1], arr2[2], arr[3])}'`
    mv -f $1 $2/$no_uid_filename
}

Thanks a lot for quick responses!


Oswald Buddenhagen via isync-devel <isy...@li...>
writes:

> On Mon, Jun 30, 2025 at 09:58:01PM +0200, ko...@gm... wrote:
>>For example, it should move like this.
>>
>>~/Mail/xx...@gm.../INBOX/cur/1750696320.159179_1.shuttle-fedora,U=1:2,S
>>~/Mail/xx...@gm.../Spam/cur/1750696320.159179_1.shuttle-fedora
>>
> well, and there is your problem. when you throw away the flags, that's 
> what you get.
>
>
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: moved mails show up as new

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

On Mon, Jun 30, 2025 at 09:58:01PM +0200, ko...@gm... wrote:
>For example, it should move like this.
>
>~/Mail/xx...@gm.../INBOX/cur/1750696320.159179_1.shuttle-fedora,U=1:2,S
>~/Mail/xx...@gm.../Spam/cur/1750696320.159179_1.shuttle-fedora
>
well, and there is your problem. when you throw away the flags, that's 
what you get.

Re: moved mails show up as new

[<ko...@gm...>]

My apologies, I've totally forgot about the subject.

My config is...

```
IMAPAccount xx...@gm...
Host imap.gmx.com
User xx...@gm...
Pass xxx

IMAPStore xx...@gm...-remote
Account xx...@gm...

MaildirStore xx...@gm...-local
Path ~/Mail/xx...@gm.../
Inbox ~/Mail/xx...@gm.../INBOX
Subfolders Verbatim

Channel xx...@gm...
Far :xx...@gm...-remote:
Near :xx...@gm...-local:
Expunge Both
Create Near
SyncState *
Patterns *

Group all
Channel xx...@gm...
```

I move the file with a following bash function.

function safeMove { s=${1##*/}; s=${s%%,*}; mv -f $1 $2/$s; }

For example, it should move like this.

~/Mail/xx...@gm.../INBOX/cur/1750696320.159179_1.shuttle-fedora,U=1:2,S
~/Mail/xx...@gm.../Spam/cur/1750696320.159179_1.shuttle-fedora

Then I run...

mbsync all
notmuch new

Then on the remote(web interface from the provider) the mail is moved to
spam folder successfully but it's unread. Running mbsync and notmuch new
again does not detect any change while the message is read locally on notmuch.


Regards,
Koh


Oswald Buddenhagen via isync-devel <isy...@li...>
writes:

> On Sun, Jun 29, 2025 at 11:39:13PM +0200, kohnish--- via isync-devel wrote:
>>Is there a way to send SEEN command when a mail is moved to another 
>>folder?
>>
> there is no such command.
> however, isync synchronizes the \Seen flag by default, so things should 
> just work.
> presumably, something is wrong with your setup. please post your config 
> file.
>
> ps: always use a meaningful subject, and don't put the list in bcc. it's 
> pure luck that i didn't just delete your mail from the spam folder.
>
>
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: moved mails show up as new

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

On Sun, Jun 29, 2025 at 11:39:13PM +0200, kohnish--- via isync-devel wrote:
>Is there a way to send SEEN command when a mail is moved to another 
>folder?
>
there is no such command.
however, isync synchronizes the \Seen flag by default, so things should 
just work.
presumably, something is wrong with your setup. please post your config 
file.

ps: always use a meaningful subject, and don't put the list in bcc. it's 
pure luck that i didn't just delete your mail from the spam folder.

[<ko...@gm...>]

Hi,

Is there a way to send SEEN command when a mail is moved to another folder?
The issues are basically described here, and it happens with other email
providers like GMX.
https://sourceforge.net/p/isync/mailman/message/36409933/
https://stackoverflow.com/questions/52218254/isync-mbsync-on-gmail-marks-mail-as-new-after-move-to-another-folder

Regards,
Koh

Re: Option for separate authorization ID

[Oswald B. <os...@us...>]

On Mon, Jun 02, 2025 at 07:43:35PM +0200, Jonathan Schöbel wrote:
>I filed that change against 1.3.0 since that is what I have installed 
>on Debian 11.  If it is going to be packaged it would be nice to also 
>provide another backport for this Debian version.
>
if you're building from source, you can (and should) use 1.5 (or 
master). the actual debian package won't backport feature patches 
anyway.

>I kept the behaviour, that the AUTHZID is duplicated instead of being
>omitted as se[e]ms to be the intended way (RFC4616), since a problem
>was documented.  Is that still relevant?
>
dunno. you'd have to examine the history of that plugin.

>+\fBAuthor\fR \fIauthorization id\fR
>+Specify the author name on the IMAP server.
>
that name is meaningless, especially with that description.

i always have to think hard to untangle authentication and 
authorization, so i would use more intuitive keywords.

a short (though not necessarily obvious) keyword would be "AsUser".
"ActingUser" would be a slightly more verbose variant; "LoginUser" could 
be provided as an alias for "User" for congruence.
maybe you can come up with something even better. note that in master 
you need to consider UserCmd. congruence matters.

implementation-wise, it might make sense to actually split user from 
loginUser, to make the fallback chains coherent. consider the possible 
mixing of configured, scripted, and interactive input.

thanks

Re: Error performing SASL authentication step: SASL(-1): generic failure: Unable to find a callback: 32775

[Tamas P. <tk...@gm...>]

Hi Bence and Marton,

It turns out that the issue was not OAUTH2 per se (oauth2ms works fine,
in the meantime I managed to set up oama too), but cyrus-sasl-xoauth2
installing into the wrong directory:

https://github.com/moriyoshi/cyrus-sasl-xoauth2/issues/15

which was easy to fix. Now my setup is working. Thanks!

best

Tamas

On Thu, Apr 03 2025, Marton Balazs wrote:

> About a year ago an update on Arch broke oauth2ms for me. I moved to oama and it works fine.
> https://github.com/pdobsan/oama
>
> Best wishes,
> Marton
>
> On Thu, Apr 03, 2025 at 05:47:28PM +0200, Bence Ferdinandy wrote:
>> 2025. ápr. 3. 17:41:45 Tamas Papp <tk...@gm...>:
>> 
>> > I have just switched from Debian to Fedora, and I am trying to get
>> > e-mail working with mbsync, 1.5.0 (but I also get the same error with
>> > master).
>> > 
>> > The relevant excerpt from my .mbsync (the whole config used to work, and
>> > is unchanged) is
>> > 
>> > IMAPAccount ihs-account
>> > Host outlook.office365.com
>> > User "tp...@ih..."
>> > PassCmd "/home/tamas/bin/oauth2ms"
>> > AuthMechs XOAUTH2
>> > TLSType STARTTLS
>> > # Increase timeout to avoid o365 IMAP hiccups
>> > Timeout 120
>> > PipelineDepth 50
>> > 
>> > The relevant oauth2ms script above works fine, insofar that it spits out
>> > a token.
>> > 
>> > Then running mbsync -V ihs I get
>> > 
>> > Reading configuration file /home/tamas/.mbsyncrc
>> > Channel ihs                                                  
>> > Opening far side store ihs-remote...
>> > Resolving outlook.office365.com...
>> > Opening near side store ihs-local...
>> > Connecting to outlook.office365.com (52.98.250.162:143)...
>> > Connection is now encrypted
>> > Logging in...
>> > Authenticating with SASL mechanism XOAUTH2...
>> > Error performing SASL authentication step: SASL(-1): generic failure:
>> > Unable to find a callback: 32775
>> 
>> Maybe you are missing cyrus-sasl-xoauth2
>> ?
>> 
>> 
>> > 
>> > best
>> > 
>> > Tamas
>> > 
>> > 
>> > _______________________________________________
>> > isync-devel mailing list
>> > isy...@li...
>> > https://lists.sourceforge.net/lists/listinfo/isync-devel
>> 
>> 
>> _______________________________________________
>> isync-devel mailing list
>> isy...@li...
>> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error performing SASL authentication step: SASL(-1): generic failure: Unable to find a callback: 32775

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

About a year ago an update on Arch broke oauth2ms for me. I moved to oama and it works fine.
https://github.com/pdobsan/oama

Best wishes,
Marton

On Thu, Apr 03, 2025 at 05:47:28PM +0200, Bence Ferdinandy wrote:
> 2025. ápr. 3. 17:41:45 Tamas Papp <tk...@gm...>:
> 
> > I have just switched from Debian to Fedora, and I am trying to get
> > e-mail working with mbsync, 1.5.0 (but I also get the same error with
> > master).
> > 
> > The relevant excerpt from my .mbsync (the whole config used to work, and
> > is unchanged) is
> > 
> > IMAPAccount ihs-account
> > Host outlook.office365.com
> > User "tp...@ih..."
> > PassCmd "/home/tamas/bin/oauth2ms"
> > AuthMechs XOAUTH2
> > TLSType STARTTLS
> > # Increase timeout to avoid o365 IMAP hiccups
> > Timeout 120
> > PipelineDepth 50
> > 
> > The relevant oauth2ms script above works fine, insofar that it spits out
> > a token.
> > 
> > Then running mbsync -V ihs I get
> > 
> > Reading configuration file /home/tamas/.mbsyncrc
> > Channel ihs                                                  
> > Opening far side store ihs-remote...
> > Resolving outlook.office365.com...
> > Opening near side store ihs-local...
> > Connecting to outlook.office365.com (52.98.250.162:143)...
> > Connection is now encrypted
> > Logging in...
> > Authenticating with SASL mechanism XOAUTH2...
> > Error performing SASL authentication step: SASL(-1): generic failure:
> > Unable to find a callback: 32775
> 
> Maybe you are missing cyrus-sasl-xoauth2
> ?
> 
> 
> > 
> > best
> > 
> > Tamas
> > 
> > 
> > _______________________________________________
> > isync-devel mailing list
> > isy...@li...
> > https://lists.sourceforge.net/lists/listinfo/isync-devel
> 
> 
> _______________________________________________
> isync-devel mailing list
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error performing SASL authentication step: SASL(-1): generic failure: Unable to find a callback: 32775

[Bence F. <be...@fe...>]

2025. ápr. 3. 17:41:45 Tamas Papp <tk...@gm...>:

> I have just switched from Debian to Fedora, and I am trying to get
> e-mail working with mbsync, 1.5.0 (but I also get the same error with 
> master).
>
> The relevant excerpt from my .mbsync (the whole config used to work, 
> and
> is unchanged) is
>
> IMAPAccount ihs-account
> Host outlook.office365.com
> User "tp...@ih..."
> PassCmd "/home/tamas/bin/oauth2ms"
> AuthMechs XOAUTH2
> TLSType STARTTLS
> # Increase timeout to avoid o365 IMAP hiccups
> Timeout 120
> PipelineDepth 50
>
> The relevant oauth2ms script above works fine, insofar that it spits 
> out
> a token.
>
> Then running mbsync -V ihs I get
>
> Reading configuration file /home/tamas/.mbsyncrc
> Channel ihs                                                  
> Opening far side store ihs-remote...
> Resolving outlook.office365.com...
> Opening near side store ihs-local...
> Connecting to outlook.office365.com (52.98.250.162:143)...
> Connection is now encrypted
> Logging in...
> Authenticating with SASL mechanism XOAUTH2...
> Error performing SASL authentication step: SASL(-1): generic failure: 
> Unable to find a callback: 32775

Maybe you are missing cyrus-sasl-xoauth2
?


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

Error performing SASL authentication step: SASL(-1): generic failure: Unable to find a callback: 32775

[Tamas P. <tk...@gm...>]

I have just switched from Debian to Fedora, and I am trying to get
e-mail working with mbsync, 1.5.0 (but I also get the same error with master).

The relevant excerpt from my .mbsync (the whole config used to work, and
is unchanged) is

IMAPAccount ihs-account
Host outlook.office365.com
User "tp...@ih..."
PassCmd "/home/tamas/bin/oauth2ms"
AuthMechs XOAUTH2
TLSType STARTTLS
# Increase timeout to avoid o365 IMAP hiccups
Timeout 120
PipelineDepth 50

The relevant oauth2ms script above works fine, insofar that it spits out
a token.

Then running mbsync -V ihs I get

Reading configuration file /home/tamas/.mbsyncrc
Channel ihs                                                   
Opening far side store ihs-remote...
Resolving outlook.office365.com...
Opening near side store ihs-local...
Connecting to outlook.office365.com (52.98.250.162:143)... 
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism XOAUTH2...
Error performing SASL authentication step: SASL(-1): generic failure: Unable to find a callback: 32775

best

Tamas

Re: Unable to sync my fastmail due to mismatched UIDVALIDITY

[Amulya M. <amu...@fa...>]

Ok, I deleted the files in /home/relma2/.local/state/isync, and now
mails are syncing! However, it's only fetching mails from March 23 and
before, and not all my emails between March 23 and now. I encountered
this issue before with mbsync, how do I fix this so it gets ALL my
emails?

Unable to sync my fastmail due to mismatched UIDVALIDITY

[Amulya M. <amu...@fa...>]

I am trying to sync my Fastmail account to a maildir with mbsync. It was working fine until today; when some weird UID of my Trash folder changed. I tried deleting and regenerating my maildir; but now I'm getting a new error:

```
Maildir notice: no UIDVALIDITY in /home/relma2/.mail/amu...@fa.../Inbox, creating new.
Error: channel fastmail-labels, near side box INBOX: Unable to recover from UIDVALIDITY change.
Error: channel fastmail-labels: near side box Archive cannot be opened anymore.
Error: channel fastmail-labels: near side box Drafts cannot be opened anymore.
Error: channel fastmail-labels: near side box Sent cannot be opened anymore.
Error: channel fastmail-labels: near side box Spam cannot be opened anymore.
Error: channel fastmail-labels: near side box Trash cannot be opened anymore.
```

This is my `isyncrc` file:
```
# Fastmail (Personal) Account
IMAPAccount fastmail
Host imap.fastmail.com
User amu...@fa...
AuthMechs LOGIN
PassCmd "secret-tool lookup aerc isync-mbsync"
TLSType IMAPS
CertificateFile /etc/ssl/certs/ca-certificates.crt

IMAPStore fastmail-remote
Account fastmail

MaildirStore fastmail-local
SubFolders Verbatim
Path ~/.mail/amu...@fa.../
Inbox ~/.mail/amu...@fa.../Inbox

Channel fastmail-labels
Far  :fastmail-remote:
Near :fastmail-local:
Patterns * !Imported* !Mailspring* !WPI
Create Both
Sync New Gone Flags

```

Did Fastmail change something about UID's? How do I fix this?? How does it "know" what UIDVALIDITY to generate, and how do I refresh that?

Re: mbsync ignores --dry-run

[inwit <in...@si...>]

On 26/03/2025, 12:45, Oswald Buddenhagen via isync-devel wrote:
> i suppose i could have it print "dry run; no modifications will be
> made." at the start.
That'd be clearer, yes.