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
(25) |
Aug
(1) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
From: ossi <os...@us...> - 2025-09-25 16:37:49
|
commit e13b9399c18fe714f9e759a791974fdf9206886a Author: Oswald Buddenhagen <os...@us...> Date: Tue Mar 25 17:54:59 2025 +0100 make imap_msgs test actually return non-zero on failure src/tst_imap_msgs.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/tst_imap_msgs.c b/src/tst_imap_msgs.c index f1df3d9..18f2965 100644 --- a/src/tst_imap_msgs.c +++ b/src/tst_imap_msgs.c @@ -90,8 +90,10 @@ verify( uint *in, const char *name ) break; } } - if (fails) + if (fails) { dump_messages(); + exit( 1 ); + } } static void |
From: ossi <os...@us...> - 2025-09-25 16:37:48
|
commit 388e926e9e691c639d9ad832bc146af1cbcbf57c Author: Oswald Buddenhagen <os...@us...> Date: Tue Aug 5 10:52:40 2025 +0200 clarify that maildir message moves should preserve the flag field src/mbsync.1.in | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/mbsync.1.in b/src/mbsync.1.in index f48dad7..1a15b10 100644 --- a/src/mbsync.1.in +++ b/src/mbsync.1.in @@ -845,8 +845,9 @@ Mutt always does that, while mu4e needs to be configured to do it: .in -4 .br The general expectation is that a completely new filename is generated -as if the message was new, but stripping the \fB,U=\fIxxx\fR infix is -sufficient as well. +as if the message was new, except that the flag suffix (\fB:2,xxx\fR) +needs to be preserved. +But stripping the \fB,U=\fInnn\fR infix is sufficient as well. . .SH INHERENT PROBLEMS Changes done after \fBmbsync\fR has retrieved the message list will not be |
From: ossi <os...@us...> - 2025-09-25 16:37:47
|
commit 23624e0fad12486515639b438b07d8e61f3dee72 Author: Oswald Buddenhagen <os...@us...> Date: Fri Aug 1 10:35:26 2025 +0200 mention that plain --debug excludes driver-all as well amends 4cc5ad5a. src/mbsync.1.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/mbsync.1.in b/src/mbsync.1.in index 032918b..f48dad7 100644 --- a/src/mbsync.1.in +++ b/src/mbsync.1.in @@ -112,7 +112,8 @@ Enable debugging categories: \fBs\fR, \fBsync\fR - print synchronization debug info .in -4 All categories except \fBcrash\fR implicitly enable \fIverbose\fR mode. -Without category specification, all categories except net-all are enabled. +Without category specification, all categories except net-all and driver-all +are enabled. .TP \fB-q\fR, \fB--quiet\fR Suppress progress counters (this is implicit if stdout is no TTY, |
From: ossi <os...@us...> - 2025-09-25 16:37:45
|
commit e46fee23df79275cd897d51214a27391d3b822d6 Author: Oswald Buddenhagen <os...@us...> Date: Wed Mar 19 15:30:59 2025 +0100 fix conditional on undefined value on some config syntax errors if the first token on a line was an unterminated escape/quote, we'd branch based on an uninitialized 'comment' variable. amends 725a122e. src/config.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/config.c b/src/config.c index 3ea4837..6a98297 100644 --- a/src/config.c +++ b/src/config.c @@ -73,8 +73,8 @@ get_arg( conffile_t *cfile, int required, int *comment ) while ((c = *p) && isspace( (uchar)c )) p++; if (!c || c == '#') { - if (comment) - *comment = (c == '#'); + if (comment && c) + *comment = 1; if (required) { error( "%s:%d: parameter missing\n", cfile->file, cfile->line ); cfile->err = 1; @@ -313,7 +313,6 @@ int getcline( conffile_t *cfile ) { char *arg; - int comment; if (cfile->rest && (arg = get_arg( cfile, ARG_OPTIONAL, NULL ))) { error( "%s:%d: excess token '%s'\n", cfile->file, cfile->line, arg ); @@ -322,6 +321,7 @@ getcline( conffile_t *cfile ) while (fgets( cfile->buf, cfile->bufl, cfile->fp )) { cfile->line++; cfile->rest = cfile->buf; + int comment = 0; if (!(cfile->cmd = get_arg( cfile, ARG_OPTIONAL, &comment ))) { if (comment) continue; |
From: ossi <os...@us...> - 2025-09-25 16:37:44
|
commit d0e9ea471e2ce27cbb04b78cacaad81055468df1 Author: Oswald Buddenhagen <os...@us...> Date: Thu Sep 25 13:53:49 2025 +0200 fix crash in mkdir_p() with invalid path if the user specified Inbox as a non-existing path in a directory they can't write to, we'd hit the root and crash due to a null pointer deref. REFMAIL: CAEJTn2UzcnD_p=ogAcaci8Pecb8pDk=2qi...@ma... src/util.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/util.c b/src/util.c index 121ab0a..c110188 100644 --- a/src/util.c +++ b/src/util.c @@ -796,6 +796,8 @@ mkdir_p( char *path, int len ) if (!mkdir( path, 0700 ) || errno == EEXIST) return 0; char *p = memrchr( path, '/', (size_t)len ); + if (!p) + return -1; // mkdir() already set errno *p = 0; if (mkdir_p( path, (int)(p - path) )) { *p = '/'; |
From: Oswald B. <osw...@gm...> - 2025-09-04 06:27:41
|
On Wed, Sep 03, 2025 at 11:34:25PM +0800, yueqr wrote: >(gdb) bt >... > that backtrace makes no sense at all; the stack is probably corrupted. >I've noticed some mention from mail list that varlingd may helped for more >information, but I need some more time to know how to work with varlingd. > valgrind --tool=memcheck --num-callers=80 mbsync [...] if libc is actually to blame in any way, it would make sense to install the libc-dbgsym package (or whatever debug symbol packages are called on your distro). |
From: yueqr <yu...@gm...> - 2025-09-03 15:34:48
|
Since I've checked last time segmentation fault in mail list at 2024, I got some idea about how to get fault information. Since my majority doesn't make any sense in CS knowledge, I have no more idea about how to get more information. if any more specific information need to be offer, please inform me. uname -a Linux gentoo 6.16.4-gentoo-dist #1 SMP PREEMPT_DYNAMIC x86_64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz GenuineIntel GNU/Linux I'v specified CFLAGS with emerge(compiling) on isync: -g3 -pipe, and below are how emerge actually did it: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -g3 -pipe -pipe -std=c11 -pedantic -Wall -Wextra -Wshadow -Wcast-qual -Wformat=2 -Wformat-signedness -Wformat-nonliteral -Wstrict-prototypes -Wno-overlength-strings -c -o util.o util.c And same options for all other src files. Here is what `mbsync -a -debug`: isync 1.5.1 called with: '-a' '--debug' Reading configuration file /home/moonsea/.config/isyncrc merge ops (in Channel 'gmail-inbox'): common: OP_EXPUNGE,OP_CREATE far: XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE near: => far: OP_EXPUNGE,OP_CREATE,XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE => near: OP_EXPUNGE,OP_CREATE ...... F: 2 OK yu...@gm... authenticated (Success) F: >>> 3 COMPRESS DEFLATE F: 3 OK Success F: >>> 4 ENABLE UTF8=ACCEPT F: * ENABLED UTF8=ACCEPT F: 4 OK Success F: >>> 5 NAMESPACE F: * NAMESPACE (("" "/")) NIL NIL F: 5 OK Success F: [ 1] Callback enter connect_store, sts=0 pattern 'INBOX' (effective 'INBOX'): no Path, INBOX F: [ 4] Enter list_store, flags=1 F: >>> 6 LIST "" "*" F: [ 4] Leave list_store F: [ 1] Callback leave connect_store F: * LIST (\HasNoChildren) "/" "INBOX" F: * LIST (\HasChildren \Noselect) "/" "[Gmail]" F: * LIST (\All \HasNoChildren) "/" "[Gmail]/All Mail" F: * LIST (\Drafts \HasNoChildren) "/" "[Gmail]/Drafts" F: * LIST (\HasNoChildren \Important) "/" "[Gmail]/Important" F: * LIST (\HasNoChildren \Sent) "/" "[Gmail]/Sent Mail" F: * LIST (\HasNoChildren \Junk) "/" "[Gmail]/Spam" F: * LIST (\Flagged \HasNoChildren) "/" "[Gmail]/Starred" F: * LIST (\HasNoChildren \Trash) "/" "[Gmail]/Trash" F: 6 OK Success F: [ 4] Callback enter list_store, sts=0 [Gmail]/Trash [Gmail]/Starred [Gmail]/Spam [Gmail]/Sent Mail [Gmail]/Important [Gmail]/Drafts [Gmail]/All Mail INBOX F: Called get_caps, ret=0x7 N: Called get_caps, ret=0 F: Enter select_box, name=INBOX F: Leave select_box, ret=0 N: Enter select_box, name=INBOX N: Leave select_box, ret=0 N: Called get_box_path, ret=/.mail/gmail/INBOX Opening far side box INBOX... F: [ 5] Enter open_box F: >>> 7 SELECT "INBOX" F: [ 5] Leave open_box Opening near side box INBOX... N: [ 6] Enter open_box *** mbsync caught signal 11. Starting debugger ... GNU gdb (Gentoo 16.3 vanilla) 16.3 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://bugs.gentoo.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /proc/493/exe... (No debugging symbols found in /proc/493/exe) Attaching to program: /proc/493/exe, process 493 Reading symbols from /usr/lib64/libssl.so.3... (No debugging symbols found in /usr/lib64/libssl.so.3) Reading symbols from /usr/lib64/libcrypto.so.3... (No debugging symbols found in /usr/lib64/libcrypto.so.3) Reading symbols from /usr/lib64/libz.so.1... (No debugging symbols found in /usr/lib64/libz.so.1) Reading symbols from /usr/lib64/libc.so.6... (No debugging symbols found in /usr/lib64/libc.so.6) Reading symbols from /lib64/ld-linux-x86-64.so.2... (No debugging symbols found in /lib64/ld-linux-x86-64.so.2) [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib64/libthread_db.so.1". 0x00007fb4feeba00a in ?? () from /usr/lib64/libc.so.6 (gdb) bt #0 0x00007fb4feeba00a in ?? () from /usr/lib64/libc.so.6 #1 0x00007fb4feeba021 in ?? () from /usr/lib64/libc.so.6 #2 0x00007fb4fef1856b in wait4 () from /usr/lib64/libc.so.6 #3 0x000055a061eef7b9 in ?? () #4 <signal handler called> #5 0x000055a061ec8847 in ?? () #6 0x000055a061ec8862 in ?? () #7 0x000055a061ec8862 in ?? () #8 0x000055a061ec8862 in ?? () #9 0x000055a061edeb2e in ?? () #10 0x000055a061ee07fe in ?? () #11 0x000055a061ed0913 in ?? () #12 0x000055a061ecfaa3 in ?? () #13 0x000055a061ed09c2 in ?? () #14 0x000055a061ee4390 in ?? () #15 0x000055a061ef33dd in ?? () #16 0x000055a061ef3181 in ?? () #17 0x000055a061ef2dd7 in ?? () #18 0x000055a061ed024b in ?? () #19 0x000055a061edac0b in ?? () #20 0x000055a061edabb4 in ?? () #21 0x000055a061ed2d6d in ?? () #22 0x000055a061ed745f in ?? () #23 0x000055a061ece188 in ?? () #24 0x000055a061ece2ac in ?? () #25 0x000055a061ece385 in ?? () #26 0x000055a061ecf1a6 in ?? () #27 0x000055a061ec94ec in ?? () #28 0x000055a061ec952c in ?? () #29 0x000055a061ef219d in ?? () #30 0x000055a061ef1086 in ?? () #31 0x00007fb4fee513eb in ?? () from /usr/lib64/libc.so.6 #32 0x00007fb4fee5149b in __libc_start_main () from /usr/lib64/libc.so.6 #33 0x000055a061ec6465 in ?? () `equery belong /usr/lib64/libc.so' told me the socket file is belong to glibc-2.42-r1, so seems compatibility with current version of glibc? I've noticed some mention from mail list that varlingd may helped for more information, but I need some more time to know how to work with varlingd. If any more specific information need to been known, please inform me. |
From: Alan S. <ala...@po...> - 2025-08-01 08:00:16
|
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 |
From: Oswald B. <osw...@gm...> - 2025-07-31 23:05:22
|
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. |
From: Alan S. <ala...@po...> - 2025-07-31 11:11:21
|
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 |
From: Antoine F. <an...@qu...> - 2025-07-24 11:14:06
|
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 |
From: Oswald B. <osw...@gm...> - 2025-07-24 07:50:44
|
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.) |
From: Evgeniy B. <bi...@pr...> - 2025-07-24 07:24:33
|
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 |
From: Antoine F. <an...@qu...> - 2025-07-23 16:16:51
|
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... |
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 |