While syncing, I get the message "Error: channel myaccount: slave inbox
cannot be opened" and messages do not sync. This is a known-good
configuration ("it worked before") that would occasionally, inexplicably
throw this error but could be fixed (now it can't be) by deleting and
recreating the loca
On Sun, Jul 07, 2019 at 12:18:06AM +0200, Oswald Buddenhagen wrote:
the reads and writes on fd 3 are certainly on the ssl-secured imap
server socket, so there is no i/o operation that would actually refer to
the slave mailbox between the progress and error messages. that should
only ever happen w
On Sat, Jul 13, 2019 at 03:11:39PM +0200, Oswald Buddenhagen wrote:
On Fri, Jul 12, 2019 at 07:44:36AM -0400, synflower--- via isync-devel wrote:
M: * 56 EXISTS
M: >>> 17 UID FETCH * (UID)
M: 17 OK UID FETCH done
oh, interesting, this has the same trigger as
https://sourceforge.ne
On Sat, Jul 13, 2019 at 08:07:18PM +0200, Oswald Buddenhagen wrote:
i mean that i need to see the actual unredacted host name (and server
name), so i can judge whether i need to work around it, report it to
them (or direct you to do it), or just make sure that mbsync reports the
fuckup in a sensi
On Fri, Jul 19, 2019 at 12:20:29PM +0200, Oswald Buddenhagen wrote:
On Fri, Jul 19, 2019 at 06:15:32PM +0900, Matt wrote:
(probably with the "Tunnel" keyword, I can use some external servers
as relays if need be).
ssh -q openssl s_client -connect imap.gmail.com:143 -quiet
s_client's -proxy o
On Sat, Jul 20, 2019 at 12:26:57PM +0200, Oswald Buddenhagen wrote:
On Sat, Jul 20, 2019 at 05:55:20AM -0400, synflower--- via isync-devel wrote:
The lack of proxy support in mbsync does seem a glaring omission.
given the available solutions, i'm not sure what exactly would justify
this
While syncing inboxes:
```
Error: channel my-mail, master Drafts: Unable to recover from UIDVALIDITY change
(got 15[...], expected 1).
```
Not sure what to do ... delete the mailboxes on disk and sync from
scratch?
___
isync-devel mailing list
isync-
On Mon, Jan 20, 2020 at 12:52:52PM +0100, Oswald Buddenhagen wrote:
it's not necessary to delete it - emptying should suffice.
be sure that all messages were previously synced - drafts are
typically locally generated. otherwise it's a better idea to empty the
folder on the server instead (assum
On Tue, Jan 21, 2020 at 11:18:42AM +0100, Oswald Buddenhagen wrote:
when you say "emptying", you mean:
`rm -rf /path/to/Maildir/my-email/Drafts/*`
???
more like .../Drafts/*/*
Ah, so don't delete the cur/new/tmp directories, just their contents.
The problem appears to have arisen because th
Compiling the 1.3 branch of isync (the one with the IMAP fixes) on Fedora 30
fails with an error indicating the Date::Parse module is missing, even when it
isn't:
[user@mymachine ~]$ git clone https://git.code.sf.net/p/isync/isync isync-isync
[user@mymachine ~]$ cd isync-isync/
[user@mymachin
On Thu, Feb 27, 2020 at 07:51:04PM +0100, Oswald Buddenhagen wrote:
On Thu, Feb 27, 2020 at 02:55:17PM +, synflower--- via isync-devel wrote:
Compiling the 1.3 branch of isync (the one with the IMAP fixes) on Fedora 30
fails with an error indicating the Date::Parse module is missing, even
On Fri, Feb 28, 2020 at 12:13:28PM +0100, Oswald Buddenhagen wrote:
On Thu, Feb 27, 2020 at 02:55:17PM +, synflower--- via isync-devel wrote:
make[1]: Entering directory '/home/user/isync-isync'
Can't locate Date/Parse.pm in @INC (you may need to install the Date::Parse
On Sat, Feb 29, 2020 at 12:59:34PM +, synflower--- via isync-devel wrote:
this means that the 'log' target is re-executed during installation as
root, which will of course fail, because the cpan installation is
private to the regular user.
try the attached patch.
That fixed
On Tue, Mar 03, 2020 at 09:53:50AM +, synflower--- via isync-devel wrote:
There seems to be a regression -- even though I'm on branch `1.3`, I'm
getting the old "slave inbox cannot be opened" errors again.
Never mind, looks like a problem with my $PATH caused my sy
How about male / female?
...sorry ...
On Mon, Jul 13, 2020 at 10:35:19PM -0700, MGC wrote:
'remote/local' sounds good to me.
--
/gc
On Jul 14 06:57 AM, Roman Bolshakov wrote:
I'm not a fan of the renaming movement solely for sake of
virtual signalling but here it makes sense.
- remote / lo
I am getting this error trying to sync messages for a popular and widely
used European email provider.
Running `mbsync -D my_account` produces the following, which doesn't
seem very helpful:
F: [ 15] Leave fetch_msg
F: [ 7] Callback leave load_box
F: * BAD command line limit exceeded
Error fr
On Tue, Feb 02, 2021 at 02:34:23PM +, synflower--- via isync-devel wrote:
F: [ 15] Leave fetch_msg
F: [ 7] Callback leave load_box
F: * BAD command line limit exceeded
Error from IMAP server: command line limit exceeded
Here's the output from `mbsync -DN`:
6 OK UID FETCH complete
On Tue, Feb 02, 2021 at 06:48:28PM +0100, Oswald Buddenhagen wrote:
On Tue, Feb 02, 2021 at 05:30:46PM +, synflower--- via isync-devel wrote:
7 APPEND "INBOX" (\Answered \Seen) {3xxx}
* BAD command line limit exceeded
Error from IMAP server: command line limit exceeded
(The
On Sun, Mar 21, 2021 at 08:31:21PM +1300, Miles Rout via isync-devel wrote:
However, since updating isync I have started receiving a deprecation
warning about master/slave in favour of far/near. I would rather not go
through all my configuration files on all my various machines just to
change on
19 matches
Mail list logo
