Re: Humble question
Den tors 16 mars 2023 kl 20:41 skrev Oswald Buddenhagen < oswald.buddenha...@gmx.de>: > On Thu, Mar 16, 2023 at 04:38:27PM +0100, Henrik Frisk wrote: > >and finally this > > > >116 UID STORE 8910 +FLA8 OK STORE completed. > > > well, this is just more garbage. > it appears that some bytes from the data stream are just dropped, but it > will be tough to figure out where that happens - could be somewhere in > the server, or in mbsync at any point. > > you can try limiting PipelineDepth as a workaround. > > if you post the -Dn log from the connection setup i might see more > options for workarounds. > > Thanks! It's attached to this mail > you could try mbsync master to see whether it works better (it contains > two known bugs, but is otherwise stable (i don't remember what they are; > the project currently has no priority. but i use it every day). note > that running the new version upgrades the store in a > backwards-incompatible way, so you should make a copy first, so you can > roll back). > > Ok, I will try that tomorrow. I've just recently moved to a mac from linux so I have mbsync currently installed via brew, but I will try to compile it tomorrow and see it that makes a difference. Thanks again! /Henrik ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Humble question
On Thu, Mar 16, 2023 at 04:38:27PM +0100, Henrik Frisk wrote: and finally this 116 UID STORE 8910 +FLA8 OK STORE completed. well, this is just more garbage. it appears that some bytes from the data stream are just dropped, but it will be tough to figure out where that happens - could be somewhere in the server, or in mbsync at any point. you can try limiting PipelineDepth as a workaround. if you post the -Dn log from the connection setup i might see more options for workarounds. you could try mbsync master to see whether it works better (it contains two known bugs, but is otherwise stable (i don't remember what they are; the project currently has no priority. but i use it every day). note that running the new version upgrades the store in a backwards-incompatible way, so you should make a copy first, so you can roll back). ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Advice on email backup
On Thu, Mar 16, 2023 at 04:26:03PM +0100, H wrote: I also realized that I, in addition, have several zipped Thunderbird mail archives that I also ought to "dump" into this to-be consolidated mail archive. It is my understanding that Thunderbird (I have been using version 59) uses the mboxrd format. you can configure your active account as imap, and the backup as a local box (i'm not a regular TB user, but i imagine it can't be that hard to re-import it). then you just drag over the mails. you'd still need some method of de-duplication, though. However, you wrote that the 'D~=' sequence in mutt would de-duplicate based on message-ID which you said "should be good enough". Could you shed some further light on this last statement so I know what the limitations are? it would fail if you created edited duplicates of some mails without changing the message-id. that would be somewhat unexpected ... ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Humble question
Den tors 16 mars 2023 kl 15:20 skrev Oswald Buddenhagen < oswald.buddenha...@gmx.de>: > On Thu, Mar 16, 2023 at 02:39:24PM +0100, Henrik Frisk wrote: > >IMAP command 'UID STORE 9154 +FLAGS.SILENT (\Deleted)' returned an error: > >UID STORE 9154 +FLAG516 UID STORE 9290 +FLAG12 OK STORE completed. > > > looks like a garbage response from the server. > try adding -Dn to the command line for some more context. > > Ah, thanks! This is the result: There are 5000+ of similar to these: * 1 FETCH (UID 6612 FLAGS (\Seen \Deleted)) * 2 FETCH (UID 6622 FLAGS (\Deleted)) 5000 of these: (5019 in progress) >>> 5026 UID STORE 14618 +FLAGS.SILENT (\Deleted) and ending with this a few of these lines (5057 in progress) >>> 5064 UID FETCH 14662 (BODY.PEEK[]) and finally this 116 UID STORE 8910 +FLA8 OK STORE completed. The Deleted directory on the server is empty by the way. /Henrik ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Advice on email backup
On 03/15/2023 06:57 AM, Oswald Buddenhagen wrote: > On Tue, Mar 14, 2023 at 08:37:27PM +0100, H wrote: >> I have never used mutt - do I install it on one of my workstations and then >> access the mail backup directory on the server over whatever suitable >> connection? >> > via imap. possible, but i wouldn't do that. > >> Or, do I install it on my server and run it there after ssh-ing into the >> server? >> > also possible, and if the server's mail store is directly supported by mutt, > you could access it that way - at the risk of messing it up. an imap > connection to localhost would be safer. > > but the way i'd recommend is to install it on the machine with the primary > backup and use it to access the isync'd maildir directly. > isync was originally written by the same guy as mutt, to be used together. as > i do to this day. > >> When you say ",U=xxx" infixes does this include the entire ",Uxxx:y,S/RS" >> part of the filename? >> > no. in perl terms, /,U=\d+/ > >> If I understand you correctly I need to remove this infix part from each >> file in the older backup directories /before/ folding them into the >> "up-to-date clone"? This means that the message files in the "up-to-date >> clone" will still have the infix part in the filename whereas the message >> files pushed from older mail backups into that directory will not. >> > correct > >> Of what importance is this infix part of the filename? >> > these are unique message ids added by isync. they are mailbox-specific, so > you need to remove them from moved in "foreign" messages. > > > > ___ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel Thank you for your explanations. Being not familiar with Maildir format etc., I did some digging and now believe I have some additional understanding of the ",U=xxx" part, the identifier chosen by isync to make sure that the message has a unique identifier. The beginning of the filename contains the date and time it was downloaded together with the hostname of the computer to which it was downloaded followed by an underscore and another identifier (possibly Q, the delivery number? as described in https://en.wikipedia.org/wiki/Maildir). The last part ":2,S/RS" is the status of the message and obviously needs to be preserved. The filename itself though does not seem to have any particular meaning besides needing to being unique to the message. I did download and install mutt to the server where the backup(s) reside and quickly realized the learning curve is somewhat steep... I have not yet connected to localhost for archive access though. The same Wikipedia page as above also lists names of some other MUAs that I may look into. If anyone has additional suggestions I would gratefully accept those - I have been using Thunderbird to manage my several email accounts. I also realized that I, in addition, have several zipped Thunderbird mail archives that I also ought to "dump" into this to-be consolidated mail archive. It is my understanding that Thunderbird (I have been using version 59) uses the mboxrd format. I think I have seen an import/export utility that I hope might be able to export into Maildir format which I can then "dump" into my archive for subsequent de-duplication. I have set aside time two weeks from now to do this. The other message from Evgeniy suggests that some messages might not be de-duplicated due to having different identifiers in the email header. However, you wrote that the 'D~=' sequence in mutt would de-duplicate based on message-ID which you said "should be good enough". Could you shed some further light on this last statement so I know what the limitations are? Thank you. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Humble question
On Thu, Mar 16, 2023 at 02:39:24PM +0100, Henrik Frisk wrote: IMAP command 'UID STORE 9154 +FLAGS.SILENT (\Deleted)' returned an error: UID STORE 9154 +FLAG516 UID STORE 9290 +FLAG12 OK STORE completed. looks like a garbage response from the server. try adding -Dn to the command line for some more context. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Humble question
Hi, I realize this is the devel list and that my question is misplced here, but since I couldn't find anything else I post my question here. On the IMAP account below I get the error: I first get the worning: Warning: lost track of 36 pulled message(s) and then: C: 0/1 B: 0/19 F: +0/0 *0/5109 #0/0 N: +0/36 *0/0 #0/0 IMAP command 'UID STORE 9154 +FLAGS.SILENT (\Deleted)' returned an error: UID STORE 9154 +FLAG516 UID STORE 9290 +FLAG12 OK STORE completed. The local maildir is not updated. This is on a MacOS M1 and isync 1.4.4 uinstalled with brew. I have another account on the same machine that works fine. Thanks for any suggestions. /H IMAPAccount fsdata Host imap.fsdata.se User xxx PassCmd "security find-generic-password -s fsdata -a xxx -w" Port 993 SSLType IMAPS SSLVersions TLSv1.2 AuthMechs PLAIN SystemCertificates no CertificateFile ~/.maildir/certificates/root-certificates.pem IMAPStore fsdata-remote Account fsdata MaildirStore fsdata-local SubFolders Verbatim Path ~/.maildir/fsdata/ Inbox ~/.maildir/fsdata/INBOX Channel fsdata Far :fsdata-remote: Near :fsdata-local: Patterns * Create Near Sync All Expunge Both Remove None SyncState * ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
