You can subscribe to this list here.
2004 |
Jan
(123) |
Feb
(24) |
Mar
(11) |
Apr
(7) |
May
(6) |
Jun
(6) |
Jul
(1) |
Aug
(1) |
Sep
(35) |
Oct
(24) |
Nov
(3) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(2) |
Feb
(6) |
Mar
(13) |
Apr
(17) |
May
(3) |
Jun
(11) |
Jul
(12) |
Aug
(4) |
Sep
(4) |
Oct
(4) |
Nov
|
Dec
(28) |
2006 |
Jan
(35) |
Feb
(21) |
Mar
(23) |
Apr
|
May
(16) |
Jun
(2) |
Jul
(8) |
Aug
(27) |
Sep
(2) |
Oct
(12) |
Nov
(22) |
Dec
(6) |
2007 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
(5) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
(1) |
2008 |
Jan
|
Feb
(11) |
Mar
(2) |
Apr
(14) |
May
|
Jun
|
Jul
(2) |
Aug
(11) |
Sep
(2) |
Oct
(5) |
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
(5) |
Mar
(2) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
(2) |
Feb
(32) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(14) |
Nov
(4) |
Dec
(1) |
2011 |
Jan
(8) |
Feb
|
Mar
(41) |
Apr
(42) |
May
|
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2012 |
Jan
|
Feb
(4) |
Mar
(5) |
Apr
(10) |
May
(2) |
Jun
(2) |
Jul
(15) |
Aug
(8) |
Sep
(101) |
Oct
(35) |
Nov
(17) |
Dec
(6) |
2013 |
Jan
(19) |
Feb
(18) |
Mar
(18) |
Apr
(67) |
May
(17) |
Jun
(4) |
Jul
(21) |
Aug
(10) |
Sep
(33) |
Oct
(33) |
Nov
(97) |
Dec
(81) |
2014 |
Jan
(39) |
Feb
(30) |
Mar
(10) |
Apr
(34) |
May
(7) |
Jun
(27) |
Jul
(33) |
Aug
(24) |
Sep
(9) |
Oct
(52) |
Nov
(23) |
Dec
(24) |
2015 |
Jan
(55) |
Feb
(51) |
Mar
(39) |
Apr
(74) |
May
(63) |
Jun
(33) |
Jul
(19) |
Aug
(21) |
Sep
(28) |
Oct
(11) |
Nov
(25) |
Dec
(26) |
2016 |
Jan
(39) |
Feb
(19) |
Mar
(36) |
Apr
(8) |
May
(3) |
Jun
(18) |
Jul
(20) |
Aug
(30) |
Sep
(12) |
Oct
(33) |
Nov
(145) |
Dec
(52) |
2017 |
Jan
(22) |
Feb
(43) |
Mar
(44) |
Apr
(71) |
May
(14) |
Jun
(10) |
Jul
(7) |
Aug
(30) |
Sep
(10) |
Oct
(39) |
Nov
(7) |
Dec
|
2018 |
Jan
(17) |
Feb
(21) |
Mar
(10) |
Apr
(19) |
May
(8) |
Jun
(9) |
Jul
(12) |
Aug
(3) |
Sep
(17) |
Oct
(9) |
Nov
(14) |
Dec
|
2019 |
Jan
(10) |
Feb
(6) |
Mar
(17) |
Apr
(2) |
May
(15) |
Jun
(15) |
Jul
(43) |
Aug
(12) |
Sep
(21) |
Oct
(7) |
Nov
(35) |
Dec
(5) |
2020 |
Jan
(110) |
Feb
(19) |
Mar
(12) |
Apr
(7) |
May
(22) |
Jun
(20) |
Jul
(48) |
Aug
(112) |
Sep
(12) |
Oct
(5) |
Nov
(19) |
Dec
(4) |
2021 |
Jan
(22) |
Feb
(54) |
Mar
(39) |
Apr
(5) |
May
(5) |
Jun
(36) |
Jul
(23) |
Aug
(31) |
Sep
(29) |
Oct
(2) |
Nov
(63) |
Dec
(50) |
2022 |
Jan
(23) |
Feb
(15) |
Mar
(3) |
Apr
(15) |
May
(21) |
Jun
(262) |
Jul
(59) |
Aug
(24) |
Sep
(18) |
Oct
(8) |
Nov
(23) |
Dec
(24) |
2023 |
Jan
(13) |
Feb
(3) |
Mar
(24) |
Apr
(3) |
May
(6) |
Jun
(13) |
Jul
(9) |
Aug
(32) |
Sep
(4) |
Oct
(2) |
Nov
(11) |
Dec
|
2024 |
Jan
(23) |
Feb
(15) |
Mar
(16) |
Apr
(17) |
May
(2) |
Jun
(5) |
Jul
(34) |
Aug
(48) |
Sep
(24) |
Oct
(12) |
Nov
(43) |
Dec
(34) |
2025 |
Jan
(7) |
Feb
(1) |
Mar
(30) |
Apr
(4) |
May
|
Jun
(5) |
Jul
(19) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Oswald B. <osw...@gm...> - 2025-07-18 07:02:25
|
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. |
From: Daniel T. <tam...@gm...> - 2025-07-17 20:33:45
|
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 |
From: Peter P. <pet...@fa...> - 2025-07-17 10:10:13
|
* 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 |
From: Oswald B. <osw...@gm...> - 2025-07-17 09:41:49
|
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). |
From: Peter P. <pet...@fa...> - 2025-07-17 06:31:15
|
* 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 |
From: Marton B. <ba...@gm...> - 2025-07-17 00:45:40
|
[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 |
From: H <ag...@me...> - 2025-07-16 23:42:30
|
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? |
From: Marton B. <ba...@gm...> - 2025-07-16 15:10:22
|
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 > |
From: Peter P. <pet...@fa...> - 2025-07-16 07:41:03
|
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 |
From: Peter P. <pet...@fa...> - 2025-07-09 21:50:34
|
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 |
From: Peter P. <pet...@fa...> - 2025-07-09 21:29:55
|
* 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 |
From: Norm W. <nor...@fa...> - 2025-07-09 11:58:37
|
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 |
From: Norm W. <nor...@fa...> - 2025-07-09 11:41:39
|
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 |
From: Norm W. <nor...@fa...> - 2025-07-09 11:21:19
|
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 |
From: Christopher S. <ch...@ko...> - 2025-07-08 09:51:19
|
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 |
From: Peter P. <pet...@fa...> - 2025-07-08 06:19:32
|
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 |
From: Norm W. <nor...@fa...> - 2025-07-07 17:36:19
|
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 |
From: Norm W. <nor...@fa...> - 2025-07-07 17:31:20
|
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 |
From: <ko...@gm...> - 2025-07-01 19:26:21
|
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 |
From: Oswald B. <osw...@gm...> - 2025-06-30 21:55:45
|
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. |
From: <ko...@gm...> - 2025-06-30 19:58:14
|
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 |
From: Oswald B. <osw...@gm...> - 2025-06-30 07:08:59
|
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. |
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 |
From: Oswald B. <os...@us...> - 2025-06-03 08:02:50
|
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 |
From: Tamas P. <tk...@gm...> - 2025-04-08 09:10:51
|
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 |