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 08:07:31PM +0200, Guillaume Brogi wrote:
> Hello again,
>
> > > > > i reported the bug to them, so doing nothing might also get you
> > > > > somewhere. :D
> > > > They are usually quite reactive, though I think it's a small team.
> > > >
> > > ok, let's hope the report ac
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
>
Hello again,
> > > > i reported the bug to them, so doing nothing might also get you
> > > > somewhere. :D
> > > They are usually quite reactive, though I think it's a small team.
> > >
> > ok, let's hope the report actually went through (i used their weird
> > contact form, which didn't give muc
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
