similar to: Ox Dovecot - dovecot.fi - dovecot-ee repo access

On 23.01.2017 10:37, Raymond Sellars wrote: > Hi > > My question is a little off topic but hoping the community has some insight or advise. > > Has anyone had success in contacting OX dovecot. We previous purchased Dovecot Pro and had access to the dovecot-ee (https://yum.dovecot.fi) repository. Credentials are no longer valid and all attempts (over the months) to reach Ox gain no

Thanks -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] Sent: Friday, 1 September 2017 2:15 AM To: dovecot at dovecot.org; Raymond Sellars Subject: Re: Mixed Autehtnication and password schemes > The above not suggests I can't use DIGEST-MD5 with master password configuration, if using more than one passdb setup. I don't understand why there would be a

Hi Looking for some confirmation/direction on how to achieve the following. We have a requirement to support both SASL PLAIN and DIGEST-MD5 authentication (certification reasons). In addition to this we have an application (webmail) that utilises a master password pattern for access, as the contain web portal provides the necessary authentication. I have access to users passwords in PLAIN text

Hi, Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working. My source of confusion are from 1) http://dovecot.org/oldnews.html I have gone through each release update news. Lots of work and bug fix after v2.2.10

Hello all, I am going for a dovecot director based setup (2 director+ 2 imap), more imap servers will be added later depending on demand/load. Presently I have 12000+ dovecot users with Maildir quota varying from 1 GB to 20GB. (peak hour IOPS 50000+) I am having 2 options in choosing dovecot version. 1) Old stable release. I.e RHEL, with prebuilt binary. This will be having less trouble in

Hi Is it possible to secure the Dovecot SASL auth provider for postfix? https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL I'm currently using the inet option to provide SASL auth to postfix for dovecot. Both installs are on different hosts hence the use of inet rather than unix socket. I'm looking for the best way to secure this channel (rather than just assuming the VLAN is secure

Hi, Do we have expunge command by UID. I have some duplicate messages (same Message-ID but different UID) to be deleted. doveadm search gives me folder GUID and file UID, I want to use this specific information to delete/expunge. E.g. Following command deletes all duplicates, but I want to keep just one. doveadm expunge? -u user1 mailbox INBOX HEADER Message-ID

Hi Looking for some insight into mdbox index file management and recovery from corruptions. I have a two node cluster on NFS with proxy director in front for user stickness. One node (a nominated master) bidirectionally replicates to a 3rd node on a DR site. We periodically get index file corruptions resulting in rebuilds. However the user experience is poor as messages read/deleted from

> On September 1, 2017 at 2:44 AM Raymond Sellars <Raymond.Sellars at orionhealth.com> wrote: > > > Thanks > > -----Original Message----- > From: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] > Sent: Friday, 1 September 2017 2:15 AM > To: dovecot at dovecot.org; Raymond Sellars > Subject: Re: Mixed Autehtnication and password schemes > > > > The

> On August 31, 2017 at 12:41 AM Raymond Sellars <Raymond.Sellars at orionhealth.com> wrote: > > > Hi > > Looking for some confirmation/direction on how to achieve the following. > > We have a requirement to support both SASL PLAIN and DIGEST-MD5 authentication (certification reasons). In addition to this we have an application (webmail) that utilises a master

Hi, I think option-2 below seems better or am I missing something with director concept. 1. As director and back-end in same server (broken) not recommended, I need minimum 4 servers (2 for director, 2 back-end IMAP). Indexes and mail must be in NFS shared storage(not optimal), as a user may land on any of the back-end servers (assuming no static mapping of user from pass DB). 2) Proxy_may

There is now a public reposurgeon repository at: git at gitorious.org:reposurgeon/reposurgeon.git I've tagged 2.0pre9 there, for two purposes: * Charles can verify that I've solved the missing-files problem. * Hartmut can rework the few of his patches I didn't merge into reposurgeon. Charles, our next and final challenge is to generate proper merge commits in the NUT repo

I am pleased to be able to report that reposurgeon's Subversion dump stream parser is now working well enough to produce a live git repo from the NUT history up to r3364. This didn't happen easily. The NUT repo is a wonderful test case, and by that I mean it was a stone bitch to get the stream parser to handle it. One class of problems was due to cv2svn, which did things with the

This is taking longer than I expected, because there is all kinds of cvs2svn-generated ugliness in your back history that tends to crash my tools. Your repo makes a great test case. (Yes, I know, that's like having someone say "Your dog is fantastically ugly!") Current state of things is that I have scrapped my precious approach, which was to put the Subversion tools in a Python

On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: > Hi, > > winter is coming and so I start to clean up some left overs of the year. > > One thing is to use the yum.dovecot.fi repository. > > After installing the current availabel dovecot and dovecot-ee-pigeonhole > package and restarting dovecot I do get the error: > > > doveconf: Fatal: Error in

On 30.10.2015 15:35, G?tz Reinicke - IT Koordinator wrote: > Am 30.10.15 um 11:49 schrieb Teemu Huovila: >> >> >> On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: >>> Hi, >>> >>> winter is coming and so I start to clean up some left overs of the year. >>> >>> One thing is to use the yum.dovecot.fi repository. >>>

>On Mon, Oct 15, 2018 at 08:50:21AM +0000, Raymond Sellars wrote: > > Hi > > Looking for some insight into mdbox index file management and recovery from corruptions. > What version of dovecot and what OS are you running? Is NFS linux/bsd/netapp/etc? [Raymond] Linux 2.6.32-279.19.1.el6.x86_64 Red Hat Enterprise Linux Server release 6.7 (Santiago) - its selectively patched

Am 30.10.15 um 15:44 schrieb Teemu Huovila: > > > On 30.10.2015 15:35, G?tz Reinicke - IT Koordinator wrote: >> Am 30.10.15 um 11:49 schrieb Teemu Huovila: >>> >>> >>> On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: >>>> Hi, >>>> >>>> winter is coming and so I start to clean up some left overs of the year.

Hi, winter is coming and so I start to clean up some left overs of the year. One thing is to use the yum.dovecot.fi repository. After installing the current availabel dovecot and dovecot-ee-pigeonhole package and restarting dovecot I do get the error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve Is the sieve protocol an extra

That is good to know. I was working on the wrong assumption, attempting to create a client certificate on the Windows/Thunderbird side. I am using the SSL Certificate that comes with the distribution, so the conclusion is Thunderbird does not trust it. I have this in my notes from ages ago, for generating my own self-signed certificate: % openssl req -x509 -newkey rsa:4096 -sha256 -keyout