similar to: v2.0.13 released

Displaying 20 results from an estimated 3000 matches similar to: "v2.0.13 released"

2011 Aug 01
2
Update 2.0.12 -> 2.0.13 is broken
Hello, today I tried to update 2.0.12 to 2.0.13, but I got those messages, only: Aug 1 10:20:27 mail dovecot: master: Dovecot v2.0.13 starting up (core dumps disabled) Aug 1 10:20:33 mail dovecot: imap-login: Login: user=<***@***.**>, method=PLAIN, rip=192.168.1.99, lip=192.168.1.1 , mpid=5123, TLS Aug 1 10:20:33 mail dovecot: imap-postlogin: Error: script-login: Error: user ***@***.**:
2011 May 13
2
Upgraded 2.012 to 2.0.13 postlogin error
I've just upgraded to Dovecot 2.0.13 from 2.0.12 When I authenticate via telnet it closes the connection and the logs show: May 13 16:59:16 master: Info: Dovecot v2.0.13 starting up (core dumps disabled) May 13 16:59:40 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth May 13 16:59:40 auth: Debug: passwd-file /usr/local/etc/dovecot/master-users: Read 1 users May 13
2011 Aug 25
2
Virtual user and post-login 2.0.13
Hi I tried several variants of suggestions but I can't get it working dovecot-info.log: =========== Aug 25 17:37:48 imap-login: Info: Login: user=<vuser>, method=PLAIN, rip=192.168.1.xx, lip=192.168.1.xx, mpid=11264 Aug 25 17:37:48 imap(vuser): Info: Post-login script denied access to user vuser dovecot.log ======== Aug 25 17:31:28 imap-postlogin: Error: script-login: Error: user pmp
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
2011 Sep 01
15
v2.1.alpha1 released
http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make
2011 Sep 01
15
v2.1.alpha1 released
http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make
2011 Jul 22
1
Bug report v2.0.13 - CentOS x86_64 - NFS - mbox
Greetings to all. It's my first post to the list. We just completed a migration from qpopper to dovecot for our IMAP and POP3 services. We have a rather large mail environment (we are the biggest provider in Greece). So, here are the details: - Keep getting errors like these in our production environment Jul 22 00:18:21 pop01 dovecot: master: Error: service(pop3): child 4078 killed with
2011 Nov 13
1
Dovecot v2.0.13 unix_listeners
Could somebody be able to explain to me what the various unix_listeners do in the Dovecot 2.x configuration (specifically in 10-master.conf). Currently, for postfix to use for local delivery, I have: service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } and for auth I have: service auth { unix_listener
2012 Jun 22
2
dsync error: "Mailboxes don't have unique GUIDs"
I'm getting an error backing up mailboxes. I'm using the mirror command: dsync -fvo mail_home=/home/users/bob mirror ssh vmail at 10.1.4.1 dsync -o mail_home=/home/.incoming_mail_migrations/users/bob dsync-remote(vmail): Error: Mailboxes don't have unique GUIDs: 1ef6ee37c694894d783100000581a675 is shared by INBOX and INBOX dsync-remote(vmail): Error: command BOX-LIST failed
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
2012 Feb 24
1
v2.0.13 problems after kernel patch for CVE-2011-1083 applied on Centos 5
Greetings, This email is both a request for assistance/help and a heads-up. [8irgehuq] CVE-2011-1083: Algorithmic denial of service in epoll. After ksplice automatically installed the above patch on our mail servers, most/all IMAP/POP3 connections began experiencing time-outs trying to connect, or extreme timeouts in the auth procedure. dovecot: imap-login: Disconnected (no auth attempts):
2011 Aug 24
3
Dovecot rejecting Vpopmail User 89
I'm working to get Dovecot 2.0.13 working along with qmail, Vpopmail and Squirrelmail on a Debian 6.0.2 system, Dovecot compiled, not from a package. Vpopmail has a widely known assigned user/group ID of 89 and is the owner of all the mail folders. Regardless of value of first_valid_uid (1, 89, other), Dovecot denies Squirrelmail connection, saying it can't allow access to UID 89.
2015 Dec 22
2
allow_nets=local in passdb gets "auth: Panic"
Hi, I have the following configuration in my dovecot.conf for Dovecot 2.2.21: passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = allow_nets=local,127.0.0.1,10.255.1.0/24 } This triggers "auth: Panic" on POP3/IMAP logins as the below: Dec 22 14:57:39 localhost dovecot: auth: ldap(u0000,::1,<oiF8SHYngqsAAAAAAAAAAAAAAAAAAAAB>): allow_nets:
2019 Jul 01
14
RFC: Complex in LLVM
Hey all, I volunteered to put together a proposal regard complex in LLVM. Consider the following to be a strawman meant to spark discussion. It's based on real-world experience with complex but is not expected to cover all use-cases. Proposal to Support Complex Operations in LLVM ---------------------------------------------- Abstract Several vendors and individuals have proposed
2012 Nov 27
6
v2.1.11 soon
Just to let you know: I'm planning on releasing v2.1.11 today/tomorrow. If you wish to get something fixed for it, ask quickly. :)
2013 Nov 14
3
[PATCH] btrfs-progs: mkfs: extend -O syntax to disable features
A way of disabling features that are on by default in case it''s not wanted, eg. due to lack of support in the used kernel. Signed-off-by: David Sterba <dsterba@suse.cz> --- mkfs.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/mkfs.c b/mkfs.c index cd0af9ef8b4f..f825e1b6bc2d 100644 --- a/mkfs.c +++ b/mkfs.c @@ -1168,7 +1168,11 @@ static int
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
2004 Oct 06
4
Checking if an element is part of a vector
Hi! I want to know if a given element <- ('c64') is part of a vector<- ('c64', 'amiga', 'atari'). Does a function exist for this which gives back a logical value? thankx db
2019 Oct 22
4
Complex proposal v3 + roundtable agenda
Ahead of the Wednesday’s roundtable at the developers’ conference, here is version three of the proposal for first-class complex types in LLVM. I was not able to add Krzysztof Parzyszek’s suggestion of a “cunzip” intrinsic returning two vectors as I could not find examples of intrinsics that return two values at the IR level. The Hexagon intrinsics declared to return two values do not actually
2006 May 10
2
Speex echo canceller on TI C55 DSP
> misc.c provides the ability to override some functions, including the > allocation and printing. fftwrap.c uses speex_alloc, then calls > kiss_fftr_alloc, which calls kiss_fft_alloc, which calls KISS_FFT_MALLOC, > which is defined as malloc in kiss_fft.h. It would make it more consistent > to define KISS_FFT_MALLOC as speex_alloc. That is the only change that I > would