On Sun, Mar 15, 2015 at 02:42:00PM +0100, A. Schulze wrote:
> Thomas Preissler:
> The logging is right, but SSLv3 isn't used.
> Today it's not uncommon that application /log/ SSLv3, where they /mean/ TLS1.x
>
> Some days ago where TLSv1 became available there wasn't a great
> difference between
Hello Dovecot users,
The rc2 release had a couple of new, rather small, but very annoying
bugs. First of all, the path for a file storage wasn't actually
normalized, due to a stupid last-minute change before the release. This
caused the personal script to be skipped with a warning when there were
I need to implement quota.
I read as much as I could including
http://wiki2.dovecot.org/HowTo/SimpleVirtualInstall
But my current /etc/passwd file does not have the password in it as
shown in dovecot docs ... there is an x where the password should be.
I created a program that creates a passwd fi
On 16 Mar 2015, at 22:36, Timo Sirainen wrote:
>
>> So we had to apply the attached patch to our Source based Dovecot Cluster.
>>
>> Could you please make a configurable Parameter for our Patched value?
>>
>> That would be great to get this parameter Configurable.
>
> That's the wrong solution
On 3/15/2015 4:08 PM, Wouter de Geus wrote:
> Hej folks,
>
> Today I upgraded from Dovecot 2.2.15 to 2.2.16 and while I was at it also
> went from pigeonhole 0.4.5 to 0.4.7-rc2.
> After upgrading I started getting these errors in the dovecot-deliver-error
> log:
> =
> lda(t...@domain.nl): Err
On 3/16/2015 7:14 PM, Stephan Bosch wrote:
> On 3/16/2015 6:30 PM, Василий Севостьянов wrote:
>> pigeonhole-version: line 9: info: DEBUG: Sieve name is Pigeonhole Sieve.
>> pigeonhole-version: line 14: info: DEBUG: Sieve version 0.4.7.rc2.
>>
>> 2015-03-16 20:16 GMT+03:00 Robert Schetterer :
>>> Am
On 16 Mar 2015, at 19:24, Andre Helwig wrote:
>
> Hi list,
> we had a lot of trouble with our Dovecot Replicating-Cluster
> installation authenticating against LDAP Service.
>
> We ran in a timeout and what happened was that we got more and more
> search requests running against on our ldap serv
Hi everyone,
I installed all-new server postfix+amavis+dovecot and pigeonhole.
Clients, thunderbird and roundcube creates sieve scripts ok and changed
ones are seen by eatch other, so server at 4190 accepts the scripts and
ensure they are created.
But filters onto new mail isn't applied. Exam
Hej folks,
Today I upgraded from Dovecot 2.2.15 to 2.2.16 and while I was at it also went
from pigeonhole 0.4.5 to 0.4.7-rc2.
After upgrading I started getting these errors in the dovecot-deliver-error log:
=
lda(t...@domain.nl): Error: sieve: file storage: Failed to normalize active
script
On 3/16/2015 6:30 PM, Василий Севостьянов wrote:
> pigeonhole-version: line 9: info: DEBUG: Sieve name is Pigeonhole Sieve.
> pigeonhole-version: line 14: info: DEBUG: Sieve version 0.4.7.rc2.
>
> 2015-03-16 20:16 GMT+03:00 Robert Schetterer :
>> Am 16.03.2015 um 18:08 schrieb Василий Севостьянов:
pigeonhole-version: line 9: info: DEBUG: Sieve name is Pigeonhole Sieve.
pigeonhole-version: line 14: info: DEBUG: Sieve version 0.4.7.rc2.
2015-03-16 20:16 GMT+03:00 Robert Schetterer :
> Am 16.03.2015 um 18:08 schrieb Василий Севостьянов:
> > dovecot version:
> > 2.2.16 (3d8a054a93a9)
> >
> > s
Hi list,
we had a lot of trouble with our Dovecot Replicating-Cluster
installation authenticating against LDAP Service.
We ran in a timeout and what happened was that we got more and more
search requests running against on our ldap server.
And on the dovecot site the process got killed after a co
Am 16.03.2015 um 18:08 schrieb Василий Севостьянов:
> dovecot version:
> 2.2.16 (3d8a054a93a9)
>
> sieve configuration:
> plugin {
> sieve = ~/.dovecot.sieve
> sieve_dir = ~/sieve
> }
>
> For each of the users, ~/.dovecot.sieve is a symlink to
> ~/sieve/roundcube.sieve
>
> Until yesterday,
dovecot version:
2.2.16 (3d8a054a93a9)
sieve configuration:
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
For each of the users, ~/.dovecot.sieve is a symlink to
~/sieve/roundcube.sieve
Until yesterday, everything was working find. But starting from yesterday's
update, the log is
After doing some digging through old mailing list threads, I fonud the
following information on the 'path' directive for dicts.
http://www.dovecot.org/list/dovecot/2009-April/038922.html
It looks like paths are hard coded per plugin, and you simply select one
of the hard coded paths (this is w
Switching to official dovecot-ee version solved my sync/backup issues, also on
Ubuntu. The 12.04 package works on 14.04. It's free and should update fine.
Backup your config files first (dovecot and postfix if you use that)!
http://shop.dovecot.fi/home/8-dovecot-ee-repository-access.html
As it usually happens, I found out the answer after reading my own mail
to mailing list multiple times. I knew it had to be simple.
Somehow, I managed to screw up config and mail_plugin section had the
entry "192.168.1.100" instead of "tcp:192.168.1.100". Replication
appears to be working now (at
Sorry to post to the list again, but just to confirm that I am seeing
same problem with 2.2.16 that I compiled from sources.
Same error message appears in the log, can't figure out what in the
setup makes replication break.
Philipp, can you tell me which auth backend are you using? passwd-file,
S
Philipp,
I already tried explicitly specifying port, it does not make any
difference. I tried quite many 'obvious' (to put it this way)
configuration changes and tried changing many things in setup, but it
would be too much to list all of them in a post.
Basically, I was hoping that someone would
I have been fighting, for 2 days, with a Dovecot setup and I now
officially need help :)
Basically, I am trying to setup replication between 2 identical Dovecot
servers, on different physical servers (different hostnames/etc, of
course), and although I've managed to solve many problems I can't
ove
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 13 Mar 2015, E.B. wrote:
I thought I read that anything from dovecot.conf can be overridden in a
userdb lookup. Or a passdb lookup with "userdb_" prefix.
But I tried for fun change log_path but it never worked. Is that because
logging is spe
I tried to look at a dovecot.index.log and it was unreadable in a text
editor. I didn't see anything in the wiki link about how to view the log.
It's not supposed to be human readable -- the point of this exercise was to
check whether your indices are really out of date. You can perhaps comp
On 03/15/2015 12:37 AM, Stephan Bosch wrote:
On 3/12/2015 11:53 PM, Stephan Bosch wrote:
On 3/12/2015 11:56 AM, Olaf Hopp wrote:
On 03/12/2015 12:02 AM, Stephan Bosch wrote:
Please do. I cannot reproduce this so far.
Since E.B. still got an obscure debug message about metadata not being
up t
23 matches
Mail list logo
