search for: veggiechinese

I've been trying to upgrade Dovecot-ee package (on EL6/x86_64) from 2.2.15.8-1 to 2.2.16.2-1. It's complaining on these two dependencies: liblz4.so.1 libtextcat.so.0 These would both seem to be related to plugins, and don't seem to be required as package dependencies by the RPM from what I can see from the SRPM. Anyone know what packages I need to satisfy these dependencies?

On Fri, Oct 17, 2014 at 12:08:38PM -0700, Timo Sirainen wrote: > On 17 Oct 2014, at 07:24, Davide <davide.marchi at mail.cgilfe.it> wrote: > > Hi to all, i found that dovecot-ee repository access is free 0,00 $ > > cost; i'm running dovecot community 2.2.13 can i migrate my system > > to dovecot-ee? What are difference between Dovecot-ee and > >

On 03 Apr 2015, at 04:22, Will Yardley <dovecot.org at veggiechinese.net> wrote: > > I've been trying to upgrade Dovecot-ee package (on EL6/x86_64) from > 2.2.15.8-1 to 2.2.16.2-1. It's complaining on these two dependencies: > > liblz4.so.1 > libtextcat.so.0 > > These would both seem to be related to plugins, and don't see...

...Product: Portable OpenSSH Version: 3.4p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: ssh-bugzilla at veggiechinese.net If a user doesn't have read / write permissions to /dev/tty with OpenSSH 3.4p1 on Linux, the error message given is "Host key verification failed"; this error message is misleading and confusing IMHO. dali% ssh -V OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0...

http://bugzilla.mindrot.org/show_bug.cgi?id=471 ------- Additional Comments From djm at mindrot.org 2003-01-19 18:45 ------- What happened when you fixed the permissions of /dev/tty? I bet you were asked to confirm a new host key... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

On Tue, Dec 02, 2014 at 08:34:50AM -0800, Darren Pilgrim wrote: > On 12/1/2014 9:44 PM, Will Yardley wrote: > > On Mon, Dec 01, 2014 at 09:27:48PM -0800, Darren Pilgrim wrote: > >> On 12/1/2014 4:43 PM, Will Yardley wrote: > >>> Can you use both ssl_protocols *and* ssl_cipher_list in the same config > >>> (in a way that's sane)? > >> >

I had some problems the first few times I restarted with ssl-params seeming to hang, but it finally works. I am able to get it to work with just: ssl = required ssl_dh_parameters_length = 4096 ssl_parameters_regenerate = 0 ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 ssl_cipher_list = HIGH+kEECDH:HIGH+kEDH:!3DES:!aNULL:@STRENGTH Thanks for your help! w

On Tue, Dec 02, 2014 at 10:12:22AM -0800, Darren Pilgrim wrote: > On 12/2/2014 10:05 AM, Will Yardley wrote: > > I had some problems the first few times I restarted with ssl-params > > seeming to hang, but it finally works. > > That would have been dovecot generating the 4096-bit DH parameters. It > can take a bit, but Dovecot is quite fast at it. If Dovecot supported

On Thu, Apr 02, 2015 at 02:53:26PM -0600, Eric Broch wrote: > On 4/2/2015 1:22 PM, Will Yardley wrote: > > I've been trying to upgrade Dovecot-ee package (on EL6/x86_64) from > > 2.2.15.8-1 to 2.2.16.2-1. It's complaining on these two dependencies: > > > > liblz4.so.1 > > libtextcat.so.0 > > > > These would both seem to be related to plugins,

This is with dovecot-ee 2.2.18.2 on RHEL6.... To handle backend and frontend on same machine, I'm using the following hack, as previously outlined here: [in director instance config] passdb { # See thread ending in: # http://dovecot.org/pipermail/dovecot/2012-June/083817.html # for why this has to be sql instead of 'static' driver = sql args = /etc/dovecot/dovecot-sql.conf

I know this has been covered somewhat, but I'm still not totally clear. I'm trying to setup a 3 node cluster with 3 directors and 3 backend systems. This post (from 2012) suggests that proxy_maybe should work with director: http://www.dovecot.org/list/dovecot/2012-December/069806.html However, these two posts (from 2013) seem to say that it will not:

Tried mailing the maintainer, but didn't get a response -- anyone know what's happened to the ATrpms repo? Not only is http://atrpms.net/name/dovecot/ empty, but: http://packages.atrpms.net/dist/el6/ seems to return a 404. Some of the mirrors still have the packages, but does anyone know if they're going to continue to build 2.2.x packages? w

I have directors and backend servers running on the same systems (x3). To be able to run doveadm foo with a minimum of fuss (without having to list socket paths explicitly), should it be the director that's the "default"? If so, is it safe to symlink '/var/run/dovecot' to '/var/run/dovecot-director', or should I just make the director's base path /var/run/dovecot

Old: Dovecot 1.1.18 + Squirrelmail 1.4.8 + Imapproxy New: Dovecot 2.2.10 + Squirrelmail 1.4.22 (no Imapproxy) In both, we have: [dovecot config] namespace private { separator = . prefix = Mail. inbox = yes } (The 'Mail' prefix is set this way for compatibility reasons) $imap_server_type = 'dovecot'; $default_folder_prefix = 'Mail.'; $trash_folder

I am using Dovecot 2.2.13, which doesn't yet seem to have the $auth_cache_negative parameter. Should the negative cache value honor $auth_cache_ttl then? I had a problem where some of our ldap systems were reinitialized. Some users, presumably those who tried to login while their records were returning a failure, became unable to login after the records were once again returning normally. I

Can you use both ssl_protocols *and* ssl_cipher_list in the same config (in a way that's sane)? ssl_protocols (>= 2.1) and ssl_cipher_list co-exist, or are they mutually exclusive? I have a Dovecot 2.2.13 system, and I tried setting: I also tried things like ssl_cipher_list = HIGH or ssl_cipher_list = HIGH:!MEDIUM:!LOW however, doing this seems to make v3 still work unless I

When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit # doveconf default_internal_user default_internal_user = dovecot Should dovecot print this warning based on $default_internal_user, or based on root? As root: # ulimit -n 1024 As user dovecot: $ ulimit -n

Couple questions about running doveadm with multiple instances... I have Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and main instance running. When I try to lookup something on the main instance (which is handling user auth) via its auth-userdb socket directly, I get an error: # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser doveadm(root): Error: passdb

I've got a weird split setup where POP3 is currently handled by Courier (courier-imap-3.0.2 distribution), and IMAP is currently handled by the RHEL 5 version of Dovecot (1.0.7) I'm trying to figure out a way to convert the POP3 UIDLs (in cases where the courierpop3dsizelist is newer than dovecot-uidlist, at least) to something that Dovecot will read, or to configure Dovecot's pop3 to

On Mon, Dec 01, 2014 at 09:27:48PM -0800, Darren Pilgrim wrote: > On 12/1/2014 4:43 PM, Will Yardley wrote: > > Can you use both ssl_protocols *and* ssl_cipher_list in the same config > > (in a way that's sane)? > > > Is there a way to exclude these ciphers, while still keeping my config > > easy to parse and avoiding duplicative or deprecated configs? > >