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 Sat, Jul 13, 2019 at 01:48:39PM -0400, synflower--- via isync-devel wrote:
> On Sat, Jul 13, 2019 at 03:11:39PM +0200, Oswald Buddenhagen wrote:
> >please reveal the imap greeting line (initial server response) from the
> >log, and the actual server dns if it is a custom server implementation
>
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.net/p/isync/bu
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.net/p/isync/bugs/48/
please reveal the imap greeting line (initial server resp
\Seen Sent \*)]
M: 19 OK [READ-WRITE] SELECT
M: >>> 20 UID FETCH * (UID)
M: 20 OK UID FETCH done
M: [ 35] Callback enter open_box, sts=0, uidvalidity=1552378503
Error: channel myaccount: slave inbox cannot be opened.
MBSYNCRC
# myaccount
IMAPAccount myaccount
Host mail.myhost.com
U
On Sat, Jul 06, 2019 at 02:05:45PM -, synflower--- via isync-devel wrote:
> Here's the relevant strace output from when the error occurs:
>
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 mail
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 de
/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
~ >> mbsync oe:INBOX
C: 0/1 B: 0/1 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
IMAP error: mailbox name INBOX contains server's hierarchy delimiter
Error: channel oe: master INBOX cannot be opened.
C: 1/1 B: 1/1 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
~ &
On Mon, Aug 15, 2016 at 10:30:30AM +0200, meyers wrote:
> C: 0/1 B: 0/0 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
> *** IMAP Warning *** Password is being sent in the clear
>
consider enabling ssl ...
> C: 0/1 B: 1/6 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
> IMAP error: malformed NEXTUID status
>
it w
>> [...}
>> folder layout:
>>
>> INBOX
>>
> and no subfolders?
Yes, no subfolders
>
>> Sent
>> Drafts
>> Spam
>> Trash
>>
>
> we need to dig a bit deeper. what version of mbsync are you using? if
> it's 1.2+, run "mbsync -DMn -l oe", otherwise "mbsync -V -l oe".
~ >> mbsync -v
isync 1.3.0
I f
On Sun, Aug 14, 2016 at 06:05:23PM +0200, meyers wrote:
> > On Sun, Aug 14, 2016 at 01:32:29PM +0200, meyers wrote:
> >
> >> IMAP error: mailbox name INBOX contains server's hierarchy delimiter
> >> Error: channel oe: master INBOX cannot be opened.
> >>
> On Sun, Aug 14, 2016 at 01:32:29PM +0200, meyers wrote:
>
>> IMAP error: mailbox name INBOX contains server's hierarchy delimiter
>> Error: channel oe: master INBOX cannot be opened.
>>
>> Any hints?
>>
> post your config file and the server
On Sun, Aug 14, 2016 at 01:32:29PM +0200, meyers wrote:
> IMAP error: mailbox name INBOX contains server's hierarchy delimiter
> Error: channel oe: master INBOX cannot be opened.
>
> Any hints?
>
post your config file and the se
Hi ,
I'm using mbsync for mail syncing for years now. But with a new email
account it fails with this message:
IMAP error: mailbox name INBOX contains server's hierarchy delimiter
Error: channel oe: master INBOX cannot be opened.
Any hints?
Rega
14 matches
Mail list logo
