similar to: HTTPS for http://xi.dovecot.fi/debian/

Thank you for your report, we'll look into it! Aki > On December 27, 2017 at 8:16 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > This repository does not work with Aptly. > It seems "architecture" line is wrong in InRelease file (needs to be > "Architectures:" instead of "Architecture:"). > And

Op 16-12-2016 om 10:30 schreef Markus Sch?nhaber: > Hi, > > at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can > we expect packages for v2.2.27 to appear there? Actually, there are packages there that have the 2.2.27 release in there, but they are not marked as such. Ever since the git move I haven't finished fixing the automatic version updates. It is still

Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks

You could remove them with sieve in the latest version of pigeonhole. On Mar 24, 2015 7:33 AM, Florent B <florent at coppint.com> wrote: > > I know about RFC's, but that could be an option, not enabled by default.

Hello Florent, How did you proceed with the upgrade? Did you follow the recommended steps guide to upgrade ceph? (mons first, then OSDs, then MDS) Did you interrupt dovecot before upgrading the MDS specially? Did you remount the filesystem? Did you upgrade the ceph client too? Give people the complete scene and someone might be able to help you. Ask on ceph-users list too. Regards, Webert

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable

On Mon, Dec 7, 2015 at 7:20 PM, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I already posted about this issue, but I can't find the old thread. > > I have a cluster of 5 nodes, running Proxmox 4, and Tinc as "virtual > switch" for my nodes : on each node, a bridge "vmbr1" where Tinc is > connected, provides me a secured network

why dont you place a service dependency on your tinc service init/systemd files to depend on your fuse/mount service? On Tuesday, 23 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I have a special setup were hosts files of Tinc are stored in a > directory mounted by fuse and shared across my hosts (Proxmox /etc/pve). > > On boot, sometimes Tinc

Try to disable ExperimentalProtocol. Florent B <florent at coppint.com> 于2018年8月10日周五 下午9:16写道： > > Hi, > > Is it possible to completely disable encryption with Tinc 1.1 ? > > I set in my configuration : > > ExperimentalProtocol = no > Cipher = none > Digest = none > > But it does not seem to disable encryption (same performance). > > Is it possible

hi! What does patched mean in this repo? Does anybody know? Thank you, tamas

Hello! Could it be, that http://xi.rename-it.nl is down? Thanks, Matthias

It's not. In fact it's explicitly telling you that it's *not* forwarding. On 22 December 2015 at 15:55, Florent B <florent at coppint.com> wrote: > Hi, > > I have a lot of messages like this in my Tinc 1.1-git log : > > Sending packet from host5 (MYSELF port 655) to host4 (192.168.0.4 port > 655) via host4 (192.168.0.4 port 655) (UDP) > > Is it expected ?

This smells like https://github.com/gsliepen/tinc/pull/104 - are you sure you're using latest HEAD? How often does this occur? Does it correlate with other events such as nodes joining or leaving? Does it occur more often if you reduce the value of KeyExpire? On 22 December 2015 at 16:10, Florent B <florent at coppint.com> wrote: > Hi, > > With latest Tinc 1.1 git code, I have

seems that you want your others services to depend on tinc, and not to set tinc to stop after the network has stopped On Wednesday, 24 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > On many systems (Debian Jessie, Tinc 1.1 from git) using unit file > provided in git, I can see that when I "reboot", Tinc seems to stop > before others

On 7 December 2015 at 17:20, Florent B <florent at coppint.com> wrote: > I have a cluster of 5 nodes, running Proxmox 4, and Tinc as "virtual > switch" for my nodes : on each node, a bridge "vmbr1" where Tinc is > connected, provides me a secured network for my VMs (connected to that > bridge). > > When I move (hot move) a VM from a host to another, I

Cit?t Aki Tuomi <aki.tuomi at dovecot.fi>: > On 2017-08-27 12:06, Harald Leithner wrote: >> Hi, >> >> It seams that IX didn't Motive Themen Version change. >> >> Thx >> >> Harald > > Try http://xi.dovecot.fi/debian.new/ > > Aki Hi, i always wonder why is anyone using this repository? There is a big warning in the wiki that

Hi, I've updated the archive key for the Xi archive. So, when updating, you will initially get a key error. To fix this, either upgrade the debian-dovecot-auto-keyring package (preferred), or update your key manually from the archive.key located in the repository root. Regards, Stephan.

Hi, i used to use deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.0 main to update dovecot 1.2 with debian lenny. I used the convert script to change my configuration file. Everything works fine but sieve does not work anymore. There is no error in the logs but dovecot simply ignores any filter. I checked the documentation/configuration twice and had still no success. Maybe, this

Hi all, I have two nodes, connected to a switch, using Tinc 1.1 from git. They connect each other with sptps, and to other nodes in the Internet with old protocol because they have Tinc 1.0. There is no problem with remote nodes, but between my 2 local nodes, they see 1518 PMTU. But local network is 1500 MTU !!! So nodes can ping each other but larger data does not go. test1=sllm1 test2=sllm2

Am 07.02.2017 um 12:29 schrieb Stephan Bosch: > > > Op 31-1-2017 om 6:33 schreef Jan Vonde: >> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>>>> I tried adding the following settings but that didn't help: >>>>> ssl_ca =