I can confirm that LibreSSL 2.4.3 works just fine for building 2.2.26.0
On 11/01/2016 09:25 PM, Reuben Farrelly wrote:
I don't believe that is the case.
I have 2.2.26.0 and -git building and running on multiple systems now
(two of which are Gentoo boxes) with LibreSSL-2.5 - and these systems
I don't believe that is the case.
I have 2.2.26.0 and -git building and running on multiple systems now
(two of which are Gentoo boxes) with LibreSSL-2.5 - and these systems do
not have OpenSSL installed. Are you running an old version of LibreSSL
perhaps?
I *think* LibreSSL-2.4 was OK as
On Tue, Nov 01, 2016 at 02:01:28PM -0300, Juan Bernhard wrote:
>
> El 01/11/2016 a las 01:26 p.m., The Doctor escribi?:
> > Getting complaints from people about pop/imap
> >
> > issues.
> >
> > some people are getting repaeted e-mail.
> >
> > Other are not able to delete their e-mails from an
On 11/1/16 6:20 PM, Bryan Holloway wrote:
In case anyone is interested, we finally found the problem:
The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled along
with "plain". This is what was causing the four-second delay, but only
with Outlook clients.
Everything is working
In case anyone is interested, we finally found the problem:
The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled along
with "plain". This is what was causing the four-second delay, but only
with Outlook clients.
Everything is working great now across the board.
Thanks again to
HI,
I’m currently testing the stats module of Dovecot (2.2.26.0 (23d1de6))
Looks like there no statistics under FreeBSD.
Server isn’t busy yet but got at least a few connection open.
Added
mail_plugins = $mail_plugins stats
plugin {
stats_refresh = 30 secs
stats_track_cmds = yes
}
Hi All
I am using Dovecot dovecot2-2.2.25_6 on FreeBSD 11. I am trying to set up
LDAP authentication to Active Director as I had it in version 1 of Dovecot.
My settings are at bottom. When I run doveadm auth test username, I get
back
root@BSD-11:/usr/local/etc/dovecot # doveadm auth test username
Nothing in them from what I can see.
Nov 1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: fs:
root=/home/mrm/mail, index=, indexpvt=, control=,
inbox=/home/mrm/mail/INBOX, alt=
Nov 1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: Namespace
archive: type=private,
Server logs would be appreciated.
Aki
> On November 1, 2016 at 8:30 PM Larry Rosenman wrote:
>
>
> doveadm -D -vv index \#ARCHIVE/\* garners the below for ALL mailboxes
> in the
> namespace:
> doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup
doveadm -D -vv index \#ARCHIVE/\* garners the below for ALL mailboxes
in the
namespace:
doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup
failed: Internal error occurred. Refer to server log for more information.
[2016-11-01 13:25:21]
doveadm(ler): Error: lucene:
OpenSSL v1.0.1 is enough.
Aki
> On November 1, 2016 at 7:46 PM Ruga wrote:
>
>
> Hello,
>
> We cannot upgrade from 2.2.24, because we use libressl and the newer
> dovecot versions demand openssl v1.1.
>
> Please add the new library requirement to the INSTALL file.
>
>
Hello,
We cannot upgrade from 2.2.24, because we use libressl and the newer
dovecot versions demand openssl v1.1.
Please add the new library requirement to the INSTALL file.
All the best.
Original Message
Subject: v2.2.26.0 released
Local Time: 28 October 2016 6:51 PM
El 01/11/2016 a las 01:26 p.m., The Doctor escribió:
Getting complaints from people about pop/imap
issues.
some people are getting repaeted e-mail.
Other are not able to delete their e-mails from an IMAP lcient.
Did you try to delete the dovecots cache? I had the same problem once,
when I
Getting complaints from people about pop/imap
issues.
some people are getting repaeted e-mail.
Other are not able to delete their e-mails from an IMAP lcient.
Current configuration
/usr/dovecot2/sbin/dovecot -n
# 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf
# OS: FreeBSD
> On 1 Nov 2016, at 14.10, Tanstaafl wrote:
>
> On 11/1/2016 3:58 AM, Sami Ketola wrote:
>> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>>> Ok, interesting. So... how does dsync do it? Or would it only work
>>>
On 11/1/2016 3:58 AM, Sami Ketola wrote:
> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>> Ok, interesting. So... how does dsync do it? Or would it only work
>> between two dovecot servers?
>>
>> I'm interested in migrating from other servers
Hello Dovecot users,
It has come to our attention that older Pigeonhole releases will not
work properly anymore with Dovecot v2.2.26.0, while there were no known
issues with 2.2.26. So, make sure you use the new Pigeonhole v0.4.16
release if you upgrade Dovecot to v2.2.26.0.
Regards,
I use redis as quota backend (currently).
After upgrading to 2.2.26.0 I see a ton of "Error: redis: Unexpected
input (state=0): -ERR max number of clients reached" errors.
It looks like either more Redis connections are being made, or Redis
connections don't time out/are reused correctly
On Tuesday 01 of November 2016, Aki Tuomi wrote:
> On 25.08.2016 10:29, Aki Tuomi wrote:
> > On 14.07.2016 10:56, Arkadiusz Miśkiewicz wrote:
> >> 2.2.25 (also happens on 2.2.24). Happens every time I try to make
> >> deliver and only for this user:
> >>
> >> Jul 14 09:52:02 mbox dovecot:
On 2016-10-31 22:04, Timo Sirainen wrote:
Oct 31 10:52:37 imap(x...@.xx): Warning: Locking transaction log
file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31
seconds (syncing)
Oct 31 10:52:37 imap(x...@xxx.xx): Warning: Locking transaction log
file
> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>
> On 10/30/2016 5:32 AM, Sami Ketola wrote:
>> On 28 Oct 2016, at 16.54, Tanstaafl wrote:
>>> Oh... I thought the --useuid option eliminated this problem?
>>>
>>>
On 25.08.2016 10:29, Aki Tuomi wrote:
>
> On 14.07.2016 10:56, Arkadiusz Miśkiewicz wrote:
>> 2.2.25 (also happens on 2.2.24). Happens every time I try to make deliver
>> and only for this user:
>>
>> Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local
>> Jul 14 09:52:02 mbox dovecot:
22 matches
Mail list logo