Activity for Isync
-
Isync released /isync/1.5.1/isync-1.5.1.tar.gz.asc
-
-
Oswald Buddenhagen committed [ffc088] on isync
release preparation
-
expand NEWS
-
stub out ChangeLog
-
--quiet is not suppressing some notices
-
Dry run results in duplicate emails
-
Path cannot be nested under Inbox
-
as there were no further followups, i'm assuming that the configuration issue was resolved. i had a quick look at the code checking that Path is configured, and found that it should be triggered only if Path is actually referenced somehow, f.ex. via a Pattern. so i'm assuming that this issue was part of the bigger misconfiguration. please post a minimal reproducer if that is incorrect.
-
the results of mbsync -ls -D before updating my .mbsyncrc: isync 1.5.0 called with: '-ls' '-D' Reading configuration file /home/mochan/.mbsyncrc merge ops (in Channel 'icf'): common: OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE far: XOP_HAVE_TYPE,XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE near: OP_CREATE => far: OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE,XOP_HAVE_TYPE,XOP_HAVE_EXPUNGE,XOP_HAVE_CREATE => near: OP_NEW,OP_OLD,OP_UPGRADE,OP_GONE,OP_FLAGS,OP_EXPUNGE,OP_CREATE merge ops (in global...
-
Hi, Thanks for your answer. I configured my mbsync more than a decade ago, so you're right that I don't actually understand what Inbox and INBOX are or ought to be. In my local machine I have a ~/Maildir/ directory with its usual cur/ new/ tmp/ subdirectories, and that is my actual inbox, where I receive nuew mail. Furthermore, I have many subdirectories, such as mbox, mbox2023, mbox2023... where I write emails I have already processed. In my configuration I have a couple of channels to either synchronice...
-
prefix deprecation notices with file name
-
presumably, commit 1e0b661d in master fixes this.
-
Ben Vallack created ticket #84
Dry run results in duplicate emails
-
the mapping looks just fine, no? that it wants to both push and pull is a classic indication that no sync state is present (or has been found, in your case). testing this with dummy accounts seems rather pointless, as that will just sync from scratch anyway. then you can just throw away your maildirs and sync state, and start afresh. so just move the sync state files in place and try with -y (preferably after you install git master). cp -al the local store somewhere, just in case.
-
W_Luis posted a comment on ticket #83
I guess I will make a couple of dummy accounts before testing that. However, I found I made an erroneous interpretation: The 6K+ messages that mbsync would fetch are from mbox, not from INBOX. The outputs of mbsync -l are $ mbsync -c mbsyncrc_new -l emCon INBOX <=> INBOX $ mbsync -c mbsyncrc_new -l emSin mbox <=> INBOX/mbox $ mbsync -c mbsyncrc_new -l ems emSin: mbox <=> INBOX/mbox emCon: INBOX <=> INBOX I also tried to change Path to a link to Maildir, but it didn't work so I reverted my new configuration...
-
whoops, yeah, it obviously should be Near :emlocal:INBOX/. yes, you can (and should) delete the bogus folders. as you're not using SyncState *, you should also clean out corresponding state files from the sync state directory. ah, the SyncState thing is also why it wants to fetch the inbox from scratch - the logical folder names changed, so the state file names don't match anymore. you can simply rename them to match (considering that / is translated to !), but i would recommend that you actually...
-