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
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
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 |
From: Marton B. <ba...@gm...> - 2025-04-03 20:36:43
|
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 |
From: Bence F. <be...@fe...> - 2025-04-03 16:23:38
|
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 |
From: Tamas P. <tk...@gm...> - 2025-04-03 15:40:22
|
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 |
From: Amulya M. <amu...@fa...> - 2025-03-31 19:28:30
|
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? |
From: Amulya M. <amu...@fa...> - 2025-03-31 19:21:18
|
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? |
From: inwit <in...@si...> - 2025-03-26 11:49:50
|
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. |
From: Oswald B. <osw...@gm...> - 2025-03-26 11:45:09
|
On Wed, Mar 26, 2025 at 12:35:34PM +0100, inwit wrote: > > >On 26/03/2025, 12:30, Oswald Buddenhagen via isync-devel wrote: >> yes, due to the re-consolidation of the output format, there is now no >> distinction between "would" and "did" in the output, as it's just >> numbers. >Understood. They're just numbers but there's no distinction between >"would" and "did" in those numbers, correct? I mean, the only difference >is the time it takes to finish the job, right? > yes. and the actual effect, obviously. i suppose i could have it print "dry run; no modifications will be made." at the start. |
From: inwit <in...@si...> - 2025-03-26 11:36:02
|
On 26/03/2025, 12:30, Oswald Buddenhagen via isync-devel wrote: > yes, due to the re-consolidation of the output format, there is now no > distinction between "would" and "did" in the output, as it's just > numbers. Understood. They're just numbers but there's no distinction between "would" and "did" in those numbers, correct? I mean, the only difference is the time it takes to finish the job, right? |
From: Oswald B. <osw...@gm...> - 2025-03-26 11:30:24
|
On Wed, Mar 26, 2025 at 12:23:55PM +0100, inwit wrote: >On 26/03/2025, 11:49, Oswald Buddenhagen via isync-devel wrote: >> such a bug was fixed in 1.5.1. >Is it possible that in this last version it doesn't explicitly say what "would have" done in the final summary? > assuming i understand your question correctly ... yes, due to the re-consolidation of the output format, there is now no distinction between "would" and "did" in the output, as it's just numbers. |
From: inwit <in...@si...> - 2025-03-26 11:24:31
|
On 26/03/2025, 11:49, Oswald Buddenhagen via isync-devel wrote: > On Wed, Mar 26, 2025 at 11:08:26AM +0100, inwit wrote: >>I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in >>v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter >>my mailboxes, both far and near. >> > such a bug was fixed in 1.5.1. Is it possible that in this last version it doesn't explicitly say what "would have" done in the final summary? |
From: Oswald B. <osw...@gm...> - 2025-03-26 10:49:42
|
On Wed, Mar 26, 2025 at 11:08:26AM +0100, inwit wrote: >I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in >v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter >my mailboxes, both far and near. > such a bug was fixed in 1.5.1. did you confirm with `mbsync -v` that you are actually using that? does adding -D (or -Dd more specifically) make it actually dry? if not, please mail me a log (with -D) of a minimal reproducer (with config file, and sync only one small box). On Wed, Mar 26, 2025 at 11:40:40AM +0100, inwit wrote: >Update: it appears that the command line --pull flag is also ignored. :( > please post your config file and the actual command line you used. |
From: inwit <in...@si...> - 2025-03-26 10:40:55
|
Update: it appears that the command line --pull flag is also ignored. :( |
From: inwit <in...@si...> - 2025-03-26 10:33:31
|
Hi, I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter my mailboxes, both far and near. I've asked a colleague to try and they've confirmed this. I think this might be an important bug, with potentially harsh consequences on users. Regards, |
From: ossi <os...@us...> - 2025-03-25 17:09:30
|
The branch 'wip/includecmd', previously at 07a1225, has been rewound by 2 revision(s) and subsequently fast-forwarded by 5 revision(s) to aeac8e4. |
From: ossi <os...@us...> - 2025-03-21 10:25:49
|
The branch 'wip/includecmd', previously at 9e9aa1b, has been rewound by 1 revision(s) and subsequently fast-forwarded by 1 revision(s) to 07a1225. |
From: Christopher S. <ch...@ko...> - 2025-03-21 03:28:12
|
On Thu Mar 20, 2025 at 1:59 AM PDT, Oswald Buddenhagen via isync-devel wrote: > On Wed, Mar 19, 2025 at 07:53:38PM -0700, Christopher Snowhill wrote: >>I am attempting to move messages between folders, and it is deleting >>from the inbox and uploading to the Archive folder. However, while the >>upload works, deletion is failing: >> >>IMAP command 'UID STORE 13345 +FLAGS.SILENT (\Deleted)' returned an >>error: Permission denied >> > this looks very much like fastmail intentionally blocking the operation. > you may need to enable destructive actions in the settings. it could be > even a folder setting. > > Yeah, I discovered it's apparently designed to purge any messages that get flagged for deletion, automatically. I'm supposed to have Expunge disabled for Fastmail. > _______________________________________________ > isync-devel mailing list > isy...@li... > https://lists.sourceforge.net/lists/listinfo/isync-devel |
From: Oswald B. <osw...@gm...> - 2025-03-20 08:59:52
|
On Wed, Mar 19, 2025 at 07:53:38PM -0700, Christopher Snowhill wrote: >I am attempting to move messages between folders, and it is deleting >from the inbox and uploading to the Archive folder. However, while the >upload works, deletion is failing: > >IMAP command 'UID STORE 13345 +FLAGS.SILENT (\Deleted)' returned an >error: Permission denied > this looks very much like fastmail intentionally blocking the operation. you may need to enable destructive actions in the settings. it could be even a folder setting. |
From: Christopher S. <ch...@ko...> - 2025-03-20 03:11:24
|
I am attempting to move messages between folders, and it is deleting from the inbox and uploading to the Archive folder. However, while the upload works, deletion is failing: IMAP command 'UID STORE 13345 +FLAGS.SILENT (\Deleted)' returned an error: Permission denied |
From: ossi <os...@us...> - 2025-03-19 17:55:47
|
The branch 'wip/includecmd' has been created at 9e9aa1b. |
From: Akshay H. <lis...@ak...> - 2025-03-15 20:49:38
|
Hi! Just wanted to update this thread to mention how much I've been enjoying the new output from isync 1.5.1. Thank you so much! -- Akshay |
From: Oswald B. <osw...@gm...> - 2025-03-14 19:42:23
|
On Fri, Mar 14, 2025 at 02:33:35PM -0400, Amulya Mohan wrote: >I am using aerc for viewing the emails, and the emails display -- there >is simply a large gap in what emails were being fetched. > i'm assuming you're talking about your client side here. for debugging, you need to access the imap mailbox directly. thunderbird allows you to view the UIDs (optional column "order arrived" or similar), which you can use to correlate isync's output with the mailbox. if that is different from what isync sees, then something truly weird is going on. if it's the same, then compare the webmailer view with the thunderbird view. if it's still the same, then your mails are simply arriving with a lag. if it's different, then fastmail is somehow delaying the imap view. >I have attached the mbsync -D log and the isyncrc. > there is nothing obviously wrong in the log. everything that is advertized by the server is also downloaded. |
From: Amulya M. <amu...@fa...> - 2025-03-14 18:33:56
|
I am using aerc for viewing the emails, and the emails display -- there is simply a large gap in what emails were being fetched. I have attached the mbsync -D log and the isyncrc. |
From: Oswald B. <osw...@gm...> - 2025-03-14 10:08:46
|
On Thu, Mar 13, 2025 at 11:11:23PM -0400, Amulya Mohan wrote: >How do I get the emails from between March 04 and 1 hour ago? > have you tried an interactive imap client (say, thunderbird) to see whether the mails are exposed via email at all? if not, then there is nothing isync can do about it. if the mails are visible, then run mbsync with -D and mail me the log along with the config file. |