similar to: v1.1 max connections per user

Displaying 20 results from an estimated 4000 matches similar to: "v1.1 max connections per user"

2007 Feb 03
1
POP3-Proxy error
Hi, as mentioned in another thread I discovered a crash in the pop3-proxy. It occurs when the remote-pop3-server just drops the connection (in my case courier was hitting the MAXPERIP-Limit). I don't have a corefile yet, but will try to get one. Here the message from the dovecot.log: dovecot: Feb 02 09:30:00 Error: pop3-login: file pop3-proxy.c: line 20 (proxy_input): assertion failed:
2007 Sep 08
3
v1.1.alpha4 released / about dbox
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz.sig Lots of fixes since alpha3. Also includes the dbox rewrite. Currently dbox works properly only in one-message-per-file mode. I'm not actually even sure how good idea it would be to use it with multiple-messages-per-file mode. But I guess it won't hurt to
2018 Mar 29
3
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
Hi everyone, I have installed Tinc-VPN v1.0.19-3 that is the last, versión that there is in Raspbian 7, installed with the apt-get command. I will like know what will be the best way to migrate this version to Tinc-VPN v1.1 Regards, Ramses
2007 Aug 07
1
v1.1.alpha2 released
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz.sig Hopefully the next release can be v1.1.beta1. I'm not aware of any major problems and I think I'm pretty much done with new features (except for dbox). The largest changes since alpha1: * Removed THREAD indexing. It's a bit buggy and I think
2007 Jul 12
3
v1.1 status and benchmarks
v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:
2007 Nov 11
3
v1.1.beta8 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz.sig Changes since beta7: - Added a new "raw" mail storage backend which allows opening files/streams as single mail mailboxes. deliver uses this now instead of opening the incoming mail as a mbox. So deliver should be now faster and it doesn't anymore remove
2018 Mar 31
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 31 de marzo de 2018 17:58:18 CEST, Rafael Wolf <rfwolf at gmail.com> escribió: >Can you just compile the latest from the git repo on to raspian os? > > > >On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > >> El 29 de marzo de 2018 23:41:24 CEST, Ramses ><ramses.sevilla at gmail.com> >> escribió: >> >Hi
2020 Feb 27
2
max number of connections per ip
I have been haunted by the following error message or months, that we see using Thunderbird. Unable to connect to your IMAP server. You may have exceeded the maximum number of connections to this server. If so, use the Advanced IMAP Server Settings dialogue to reduce the number of cached connections. If I change my location, via a VPN, the error message goes away and I can connect. I have
2018 Mar 31
2
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
Can you just compile the latest from the git repo on to raspian os? On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > El 29 de marzo de 2018 23:41:24 CEST, Ramses <ramses.sevilla at gmail.com> > escribió: > >Hi everyone, > > > >I have installed Tinc-VPN v1.0.19-3, that is the last version that > >there is in Raspbian 7,
2007 Oct 27
2
v1.1.beta5 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz.sig APPEND should be working now. Also lots of fixes to handling namespace prefixes and namespaces where virtual separator differs from real separator. zlib plugin now supports opening compressed maildir files. This is done for files that have Z flag. SORT still
2007 Dec 03
0
De-duplication / Single Instance Storage - WAS: Re: Updated v1.1 and summer plans
On 12/2/2007, Timo Sirainen (tss at iki.fi) wrote: > On Sun, 2007-12-02 at 10:02 -0500, Charles Marcus wrote: >> Do you have any idea as to a time frame for when you might be able >> to get to it (Single instance Storage)? Are you thinking post >> v2.0? Even 2.1 or 3.0? > Right now I just want to get v1.1 finished. The main problem with it > is that apparently in
2007 Dec 22
1
v1.1.beta12 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz.sig Still not a release candidate, maybe the next one.. This release fixes a lot of bugs and adds some new sanity checks. Fixes quite a lot of mbox problems. v1.1.beta11 (no other versions) had a potential security hole where memory was free()d multiple times. \Recent
2008 Feb 16
0
v1.1.beta16 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz.sig If all goes well, I'll release v1.1.rc1 in a couple of days. Now's a good time to start testing v1.1 :) Changes since beta15: - Squat is finally working and supports expunging messages from it. I've been stress testing it and can't find any problems
2018 Mar 31
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 29 de marzo de 2018 23:41:24 CEST, Ramses <ramses.sevilla at gmail.com> escribió: >Hi everyone, > >I have installed Tinc-VPN v1.0.19-3, that is the last version that >there is in Raspbian 7, installed with the apt-get command. > >I will like know what will be the best way to migrate this version to >Tinc-VPN v1.1 > > >Regards, > >Ramses Hi everyone,
2018 Mar 31
2
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
Hello Ramses, Am Sat, 31 Mar 2018 17:21:52 +0200 schrieb Ramses <ramses.sevilla at gmail.com>: > Can tell me someone if there is any repository to Raspbian that has Tinc v1.1 > to update a installed Tinc v1.0 from command apt-get? thankfully the Debian package maintainer for tinc (Guus) prepared a package and uploaded it to the "experimental" suite:
2018 Apr 01
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 1 de abril de 2018 3:34:46 CEST, Lars Kruse <lists at sumpfralle.de> escribió: >Hello Ramses, > > >Am Sun, 01 Apr 2018 01:44:01 +0200 >schrieb Ramses <ramses.sevilla at gmail.com>: > >> [..] >> >> Correct? > >in general, this is exactly the right procedure. > > >> I have installed Raspbian 7 (Wheezy). I will have problems doing
2008 Feb 11
1
v1.1.beta15 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta15.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta15.tar.gz.sig It's been a while since the previous beta, so I guess it's time for a new release. I wanted this one to be called v1.1.rc1, but Squat indexes still aren't completely working. My simple tests seem to work OK, but after doing some random
2007 Dec 22
0
v1.1.beta12 deliver crashes (arvids) Ditto!
On Dec 22, 2007, at 5:00 AM, dovecot-request at dovecot.org wrote: (stuff cut out) > Message: 10 > Date: Sat, 22 Dec 2007 11:12:30 +0200 > From: arvids <arvids at mpe.lv> > Subject: [Dovecot] v1.1.beta12 deliver crashes > To: Dovecot Mailing List <dovecot at dovecot.org> > Message-ID: <200712221112.30760.arvids at mpe.lv> > Content-Type: text/plain;
2008 Feb 21
4
v1.1.rc1 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.
2008 Feb 21
4
v1.1.rc1 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.