On Fri, Feb 12, 2021 at 5:19 PM Stefano Zacchiroli <z...@debian.org> wrote: > > Hi Sudip, thanks for your reply, > > On Fri, Feb 12, 2021 at 05:00:04PM +0000, Sudip Mukherjee wrote: > > Thanks for the report. Can you please paste your offlineimaprc file > > after removing any sensitive information, and I can try to reproduce > > the error in my setup. > > in fact, it turns out this is a duplicate of #981063, which I failed to > identify initially because it didn't have the actual final error in the > message. The workaround in that bug report worked for me.
Thanks for confirming, I was expecting that. > > I've tried to merge the bugs, but it failed with an error on locking a > spool file on the BTS server. (I've just tried again.) > > FWIW, I think #981063 should be severity serious and fixed in time for > bullseye. Yes, I have raised a PR to upstream with a proper fix and will wait till Monday before uploading here. https://github.com/OfflineIMAP/offlineimap3/pull/51 -- Regards Sudip
