similar to: Bug in xi.rename-it.nl/dovecot-2.0.11/debian/watch

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

Hello, is http://xi.rename-it.nl down? Apticron shows me permanently errors. -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- Wenn ein wirklich gro?er Geist in der Welt erscheint, kann man ihn untr?glich daran erkennen, da? sich alle Dummk?pfe gegen ihn verb?nden. (Jonathan Swift)

Hello, Since several days the repo (xi.rename-it.nl (217.119.238.14)) is no longer accessible. I'd found here for Debian/Ubuntu => http://wiki2.dovecot.org/PrebuiltBinaries Is it off, or temporarily down ? Could not connect to xi.rename-it.nl:80 (217.119.238.14). - connect (110: Connection timed out) Bests Regards, Nathan

Hi , i know there were errors reported before with autobuild packs from xi.rename-it.nl , hint was purge and remove old dovecot packs, but at reinstall i ever get such ucfr: Attempt from package dovecot-pop3d to take /etc/dovecot/conf.d/20-pop3.conf away from package dovecot-common ucfr: Aborting. on a few packs ,any idea? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

Hello, http://xi.rename-it.nl/debian/dists/stable-auto/dovecot-2.0 not available? -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- Mit dem Geist ist es wie mit dem Magen: Mann kann ihm nur Dinge zumuten, die er verdauen kann. [Churchill]

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

Hi there, I check my mail-server for debian package-upgrades with Nagios, so everyday I got a mail for 8 "new" dovecot-packages on this server. I think that wasn't so in 2.1 stable-auto, but I'm not sure about that. Maybe someone who uses the 2.1 stable-auto repo could response to this? But 2.2 released only few days ago, maybe the repo-admin hadn't time to change this,

Hi, i have setup with mail_attachment single instance store + replication + zlib and got this bug when i try to replicate one test mailbox: On master1 in mail.log: Apr 10 13:25:22 master1 dovecot: dsync-local(zzz at blabla666.sk): Error: read(/nfsmnt/mailnfs1/attachments1/6b/57/6b57ad34cf6c414662233d833a7801fde4e1cdcb-92b5052558774653a728000013e2b982[base64:18 b/l]) failed: Stream is larger than

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, I testing around with Kolab with LDAP and have some strange problems, with the auto generated packages for Wheezy. On my first test VM, I have 2:2.2.16~rc1-1~auto+4 installed, and everything works as expected. On a new VM I have 2.2.16-1~auto+13_amd64.deb packages and if I include LDAP backend, I get a segmentation fault on /usr/lib/dovecot/auth: root at kolab:/etc/dovecot/conf.d#

Hello dovecot-users, we're running Debian 7.9 with dovecot from Stephan Bosch's repository: deb http://xi.rename-it.nl/debian/ oldstable-auto/dovecot-2.2 main Starting with dovecot 2.2.20-1 build 28, we suddenly discovered that some mails (to be locally delivered) "got stuck". dovecot's log revealed messages like the following one: Dec 29 09:56:50 mailhost dovecot:

I wonder if somebody could help me. If I try clean install of dovecot-common dovecot-imapd dovecot-pop3d from deb http://xi.rename-it.nl/debian stable-auto/dovecot-2.0 main I got: Starting IMAP/POP3 mail server: dovecotdoveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: service(managesieve-login): executable is empty failed! Setting up dovecot-imapd

Hi, The automatic package builder Xi has moved to system within the Dovecot infrastructure. This also means that the repositories are available at a new host name: xi.dovecot.fi. The old host name still works and is a CNAME pointing to the new venue. I expect the old domain to be active for years to come. So, there is no need to update your /etc/apt/sources.list right away. Still, it is a

Hi, The automatic package builder Xi has moved to system within the Dovecot infrastructure. This also means that the repositories are available at a new host name: xi.dovecot.fi. The old host name still works and is a CNAME pointing to the new venue. I expect the old domain to be active for years to come. So, there is no need to update your /etc/apt/sources.list right away. Still, it is a

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

Op 12/9/2015 om 5:44 PM schreef Stephan Bosch: > > > Op 9-12-2015 om 17:32 schreef Timo Sirainen: >> http://hg.dovecot.org/ is no longer being updated. The public >> repository exists now in https://github.com/dovecot/core instead. >> >> I'm not sure yet if we should continue pushing commit emails to >> dovecot-cvs list or if Github's internal

A post last week contained the design document for a shadow page table mechanism. This post contains more information, and a pointer to the code. As a recap, the "XI Shadow Mechanism" is a design for shadow page table code for fully virtualized HVM domains running on a 64-bit Xen hypervisor. This work was undertaken to address a number of goals. These are enumerated in the document

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

Hi, Xi is broken at the moment. This XenServer version won't boot jessie kernel. Can't fix this myself, so this may take some time. Regards, Stephan.

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