On Tue, Mar 23, 2021 at 03:48:58PM +0100, Oswald Buddenhagen wrote:
> On Mon, Mar 22, 2021 at 11:19:24PM +0100, Joel Granados wrote:
> > On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
> > > On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> > > > I indeed went ba
On Mon, Mar 22, 2021 at 11:19:24PM +0100, Joel Granados wrote:
On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> I indeed went back to my original comment and restarted from there. I
> notcied that there is a link
Hello
On Thu, Mar 18, 2021 at 11:03:00PM +0100, Oswald Buddenhagen wrote:
> On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
> > I indeed went back to my original comment and restarted from there. I
> > notcied that there is a link that is created when openssl is installed
> > in de
On Thu, Mar 18, 2021 at 09:09:53PM +0100, Joel Granados wrote:
I indeed went back to my original comment and restarted from there. I
notcied that there is a link that is created when openssl is installed
in debian bullseye /lib/ssl/openssl.cnf -> /etc/ssl/openssl.cnf.
fwiw, it's /usr/lib/ssl/op
I indeed went back to my original comment and restarted from there. I
notcied that there is a link that is created when openssl is installed
in debian bullseye /lib/ssl/openssl.cnf -> /etc/ssl/openssl.cnf.
If I change the name of this link, mbsync (the one installed by debian)
works again.
I'm not
On Fri, Mar 12, 2021 at 09:29:06AM +0100, Joel Granados wrote:
The systems are actually quite different (I forgot to mention it).
well, that kind of defeats the configuration difference based approach.
but that working second system seems to be a side track anyway. you
started out with this:
On Fri, Mar 12, 2021 at 09:29:06AM +0100, Joel Granados wrote:
> This is good to know (not to focus too much on the resolv thing). The
> systems are actually quite different (I forgot to mention it).
Try a fresh Debian installation (container, hosting, etc).
It can confirm mbsync works fine on D
On Thu, Mar 11, 2021 at 03:23:59PM +0100, Oswald Buddenhagen wrote:
> On Thu, Mar 11, 2021 at 02:11:53PM +0100, Joel Granados wrote:
> > /lib -> usr/lib
> > /lib32 -> usr/lib32
> > /lib64 -> usr/lib64
> > /libx32 -> usr/libx32
> > /usr/lib
> > /usr/lib32
> > /usr/lib64
> > /usr/libx32
> >
> ok, th
On Thu, Mar 11, 2021 at 02:11:53PM +0100, Joel Granados wrote:
/lib -> usr/lib
/lib32 -> usr/lib32
/lib64 -> usr/lib64
/libx32 -> usr/libx32
/usr/lib
/usr/lib32
/usr/lib64
/usr/libx32
ok, the system simply aliases /lib* to /usr/lib* (i think that's the new
debian policy), so the "duplicate" fil
On Mon, Mar 08, 2021 at 11:22:31PM +0100, Oswald Buddenhagen wrote:
> On Mon, Mar 08, 2021 at 09:30:07PM +0100, Joel Granados wrote:
> > Clearly there are several links for the libraries on the box that does
> > not work,
> >
> yeah, that seems like a likely problem source.
>
> > question is. How
On Mon, Mar 08, 2021 at 09:30:07PM +0100, Joel Granados wrote:
Clearly there are several links for the libraries on the box that does
not work,
yeah, that seems like a likely problem source.
question is. How can I work around this without fiddling around with my
systems configuration?
that
Hello Oswald
Thx for the response and sorry for taking so long to get back.
On Fri, Feb 05, 2021 at 10:44:12PM +0100, Oswald Buddenhagen wrote:
> On Fri, Feb 05, 2021 at 10:03:46PM +0100, Joel Granados wrote:
> > Any ideas?
> >
> not really. check with ldd what mbsync is linking in both cases.
>
On Fri, Feb 05, 2021 at 10:03:46PM +0100, Joel Granados wrote:
Any ideas?
not really. check with ldd what mbsync is linking in both cases.
ls -l these libraries; i wouldn't be surprised if symlinks are involved.
you could use ltrace to see if there is a difference (also strace, but
that's a lo
Hey fine ppl
My subject is the same as a mail sent by fwoodhead back in 2020-02-11. I
used the same Subject because I got the same message. I did not answer
that thread because I just joined.
My problem is that I get the error in the subject. The (very) freaky
thing is that when I uninstall opens
On Tue, Feb 11, 2020 at 02:49:40PM +, fwoodh...@doctors.org.uk wrote:
I would be very grateful for any pointers.
use the 1.3 branch from git, that should give you clearer ssl errors.
anyway, the output from openssl suggests that the tunnel is botched.
maybe you forwarded to somewhere els
Hi
I have been using mbsync (isync v 1.3.0) to synchronise my work email to
a Maildir on an Amazon Webserver for a while.
I have been using port-forwarding from the location of the IMAP server
(port 993) to port 1993 on the AWS. The port is open as shown by
nc -z localhost 1993 || echo 'no tunn
16 matches
Mail list logo
