similar to: v2.1.alpha1 released

Displaying 20 results from an estimated 1000 matches similar to: "v2.1.alpha1 released"

2013 Feb 25
2
v2.2.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've
2013 Feb 25
2
v2.2.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've
2008 Sep 10
2
1.2.alpha1: file_dotlock_open() failed with subscription file
Hi *, running dovecot 1.2.alpha1 I find the following messages in the log: Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10
2016 Mar 30
2
Pigeonhole 0.4.13 does not compile against dovecot 2.2.23
On 31/03/2016 02:06, Stephan Bosch wrote: > Hi, > > Op 3/30/2016 om 5:34 PM schreef Juan C. Blanco: >> Hello, I supose that a new version of pigeonhole is on the way because >> version 0.4.13 does not compile against dovecot 2.2.23 >> >> This is the error that I get >> >> gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. >>
2016 Mar 04
6
v2.2.22 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're
2016 Mar 04
6
v2.2.22 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're
2013 Jun 16
5
v2.2.3 released
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole
2013 Jun 16
5
v2.2.3 released
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole
2009 Sep 11
1
ntpd / Time just moved backwards
Hello *, strange happening yesterday. See this logfile lines: Sep 10 20:45:52 seymour ntpd[9104]: synchronized to 192.53.103.108, stratum 1 Sep 10 20:58:07 seymour ntpd[9104]: synchronized to 134.34.3.18, stratum 1 Sep 10 21:21:02 seymour dovecot: dovecot: Fatal: Time just moved backwards by 434 seconds. [ ... ] Sep 10 21:26:36 seymour ntpd[9104]: no servers reachable Sep 10 21:42:56 seymour
2019 Nov 12
2
dovecot -2.2.24 on Fedora 31
On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote: > On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote: [ ... ] > I narrowed the probelem down to the warnings > > Warning: service auth { client_limit=128 } is lower than required under max. load (768) > Warning: service anvil { client_limit=256 } is lower than required under max. load (643) These
2007 Aug 13
2
v1.1.alpha3 released
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz.sig All kinds of fixes and API changes. Previous alphas had some problems with index handling, now I didn't get any errors after almost 24h of stress testing. As a new feature userdb passwd now supports overriding some fields with templates.
2007 Mar 09
2
Convert plugin mbox to maildir has no effect
Convert plugin seems to have no effect with dovecot-1.0.rc26 and my settings. When a user log, maildir creation is successful, but no mbox conversion occur. New incoming mails are dropped into maildir, but I cant access those in Mbox file. I set the following in dovecot.con as describe on wiki. mail_location: maildir:/var/mail/Maildir/%u convert_mail: mbox:/var/mail:INBOX=/var/mail/%u Any
2011 Nov 11
1
undefined symbol: o_stream_switch_ioloop
Hi, running dovecot-2.0.14 under Fedora 14 with kernel 2.6.35.14-103.fc14.i686.PA I've found a strange error in log which I've nerver observed before when startung dovecot: auth-worker: Error: dlopen(/usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so) failed: /usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so: undefined symbol: o_stream_switch_ioloop Dovecot seems to work normal
2010 Jul 27
1
sieve error
Hi, dovecot-2.0-rc3 dovecot-2-0-pigeonhole-4cb55beaca07 when I run 'doveadm config', it prints such error, any help? thanks :) *** glibc detected *** /home/mail/bin/doveconf: munmap_chunk(): invalid pointer: 0x001115fc *** ======= Backtrace: ========= /lib/i686/nosegneg/libc.so.6(cfree+0x188)[0x36e758] /home/mail/lib/dovecot/libdovecot.so.0[0x7db41a]
2019 Jan 08
2
File permissions
Hello, I am mosty done with the upgrade, but there is a problem that keeps me awake at night: file ownership and permissions. It would be most helpful to have the following from Aki's live system: ls -halFR /var/run/dovecot -------------- next part -------------- An HTML attachment was scrubbed... URL:
2008 Dec 02
3
date operations
Un texte encapsul? et encod? dans un jeu de caract?res inconnu a ?t? nettoy?... Nom : non disponible URL : <https://stat.ethz.ch/pipermail/r-help/attachments/20081202/10f66fc6/attachment.pl>
2012 Mar 06
1
dovecot 2.1.1 + pigeonhole + avelsieve
Hello all, I've squirrelmail-webmail-1.4.22, dovecot 2.1.1, dovecot-2.1-pigeonhole-0.3.0 installed and working. But I've problems to get the avelsieve plugin for squirrelmail working with dovecot. The "Message Filters" show up in "Options" of squirrelmail, but "Could not log on to timsieved daemon on your IMAP server ........." dovecot log shows: Mar 6
2017 Aug 25
2
dovecot: config: Error: BUG: Config client connection sent too much data
Hello, Absolutely. Here is the output of doveconf -n: # doveconf -n # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux auth_mechanisms = plain login base_dir = /var/run/dovecot/ dict { expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext } doveadm_password = #
2014 Aug 27
2
Dovecot Replication of Maildirs: Couldn't create lock file ... no such file or directory
Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the
2019 Apr 14
1
permissions for quota-status
Hello! doveconf --version 2.2.36 I want to move to a new server with dovecot but get an error Error: service(quota-status): listen(*, 12340) failed: Permission denied when I define service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 } private]# ll insgesamt 0 srw-rw-rw-. 1 postfix postfix 0 14. Apr 15:05 anvil