search for: v2.0

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

http://hg.dovecot.org/dovecot-2.0/ I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :) I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree. Note the new dovecot-master-example.conf, which

Greetings. I see a warning message while compiling OpenMPI and would appreciate it if you tell me what it means. This warning happens with any OpenMPI > 1.6.5. Even before starting a cluster, just "sessionInfo" triggers this warning. I'm pasting in the message from R-3.3.2 (this is MRO). Do the R parallel package cluster functions violate the warnings described here? >

If anyone's interested, I updated my master/config rewrite to latest Dovecot v1.1 tree and added it to hg: http://hg.dovecot.org/dovecot-master-rewrite/ It probably doesn't work, but with the exception of plugins it compiles anyway. :) I'm thinking that maybe after v1.1.0 I could continue with the rewrite and create v2.0 after all instead of v1.2. Just look at how much cleaner

Hi, I've merged the Mercurial repositories for Sieve and ManageSieve for Dovecot v2.0 into one repository: http://hg.rename-it.nl/dovecot-2.0-pigeonhole This simplifies the build process significantly. It also allows tightly integrating the implementation of the script storage with the main Sieve library, enabling the possibility to implement alternate means of script storage, like for

I just saw the S100-FX v2.0 on eBay. I was wondering if anyone has tried it out and what their opinion of it was. ---- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060126/3da2e4e5/attachment.htm

Hello Timo, I'm playing around with the new Dovecot v2.0.beta3 and don't seem to be able to get quotas working from userdb. I didn't change the SQL query which was working for 1.2.10. Feb 20 19:34:06 ubuntu-test dovecot: auth: sql(test,192.168.156.99): SELECT home, mail, uid, gid, concat('*:storage=', quota_limit, 'MB') AS quota_rule FROM users WHERE username =

In Dovecot v2.0 I'm splitting dovecot-example.conf to multiple files. It's probably annoying to have tons of dovecot-*-example.conf files, so what do you think about: 1. Change default sysconfdir from $prefix/etc to $prefix/etc/dovecot (that's what most distros do anyway) 2. Install *.conf files to $sysconfdir/example/ without the "-example" part in any of the config files.

Hi, I'm currently running version v2.0.x in production (using Maildir storage) and it's been working well. I'm interested in moving to version 2.2.x and am preparing a test server to do so. As I have been merging the conf file changes between the two versions I noticed syntax changes for the 90-sieve.conf file. There are now 'locations' and presumably to keep referring to

Hello, i have a problem with the managesieve plugin and a virtual namespace in v2.0. The managesieve plugin complains about an unknown storage driver virtual when i try to log intot the managesieve. I don't know if this is quite a recent problem or if it exists for a while, as i configured the virtual namspace from scratch. (The virtual namespace itself is working.) Jun 28 13:55:54

Hey all, ?I'm feeling spunky... and want to update nut to handle the new v2.0 MIB from CyberPower. I've looked at the cyberpower v0.1 .c/.h and being new to working on nut to this level -- anything anyone has to offer on adding code besides the obvious? like: should the 0.1 and 2.0 coexist somehow? (maybe different files) (also, is there a list of all the parms I can match up from the

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

On October 31, 2017 2:32:36 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > >?I'm feeling spunky... and want to update nut to handle the new v2.0 >MIB from CyberPower. > >I've looked at the cyberpower v0.1 .c/.h and being new to working on >nut to this level -- anything anyone has to offer on adding code >besides the obvious? >

On November 2, 2017 5:31:42 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >On 10/31/2017 01:13 AM, Jim Klimov wrote: >> If the new data is in a separate OID tree, it can quite be a new MIB. >Otherwise you can use the UNIQUE flag and set the preferred (e.g. >newer, more precise) source for a value first in the list of same-named >mappings in existing file - if

On 11/02/2017 01:52 AM, Jim Klimov wrote: > > I believe the main reason for a new set of .c/.h files here would be if the new MIB is defined in a separate subtree. The top-level mapping binds the vendor entry OIDs (often "hidden" so one has to know where to poke). It may also be higher in the list of snmp-ups.h, in case the device also serves the older MIB but you'd prefer the

Hi, all, Please tell me about the patch and description below. https://github.com/dovecot/core/commit/5f46b863383fc94afcd2693ecae8788cb5fdd20c example-config: Use a default uncommented "namespace inbox". https://doc.dovecot.org/configuration_manual/namespace/ There's a default inbox namespace added in 10-mail.conf. If the configuration doesn't explicitly specify a

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then