On Wed, Mar 22, 2017, at 01:04 AM, Aki Tuomi wrote:
>
> On 22.03.2017 10:03, Leon Kyneur wrote:
> > Hi
> >
> > I am trying to configure the last_login plugin with LDAP dictionary
> > which is causing dict service to crash. Not sure if this is a bug or
> &
Hi
I am trying to configure the last_login plugin with LDAP dictionary
which is causing dict service to crash. Not sure if this is a bug or
some configuration parameter I'm getting wrong?
Running latest dovecot but was having the same problem in earlier
version 2.2.25
# dovecot --version
2.2.28
I am also seeing this error since updating to 2.2.25. I do believe it's
only occurring on CRAM-MD5, DIGEST-MD5 and NLTM auth.
# dovecot --version
2.2.25 (7be1766)
Jul 26 02:10:57 auth-worker(11499): Info:
ldap(username,192.168.10.9,): unknown user - trying
the next passdb
Jul 26 02:10:57 auth
Hi,
Trying to understand what the version numbers mean. I typically build
from the stable tarball and then apply patches as needed.. however since
2.2.25 this hasn't been working (not sure if it worked before or never
really looked closely TBH).
http://dovecot.org/releases/2.2/dovecot-2.2.25
Thanks Timo
I will apply this patch and let you know if I encounter any more issues.
On 11/07/16 17:09, Timo Sirainen wrote:
On 10 Jul 2016, at 17:44, Leon Kyneur wrote:
Recently updated to 2.2.25. Noticed a migration script I've been previously
running fine started giving me the e
Recently updated to 2.2.25. Noticed a migration script I've been
previously running fine started giving me the errors below.
Remove server doesn't log any failure. doveconf -n attached.
+ /bin/doveadm -o mail_fsync=never backup -R -u u...@domain.com imapc:
dsync(u...@domain.com): Panic: file md
You sure you're not returning multiple password attributes from LDAP?
Aki
pass_attrs = 'mail=user, userPlaintextPassword=password_noscheme,
=proxy=y, =pass=%{ldap:userPlaintextPassword}, =host=%{ldap:mailstoreHost}'
I am returning the same password attribute into different fields :
pass
ssing queries are no long async.
I don't really see the downside given the upside is auth is not crashing
and causing password prompts for all my customers...
On 09/07/16 15:26, Leon Kyneur wrote:
Hi
Recently enabled support for encrypted passwords on my proxies -
CRAM-MD5, DIGEST-MD5,
Hi
Recently enabled support for encrypted passwords on my proxies -
CRAM-MD5, DIGEST-MD5, NTLM and APOP to support some new users. Most
users are working perfectly though every so often I see this happening
in the logs:
Jul 09 06:32:51 auth: Error:
ldap(u...@domain.com,192.168.10.90,): Mult
Hi Timo,
Testing now and noticed the following error on a POP user:
Jul 01 12:50:08 pop3-login: Info: Login: user=,
method=PLAIN, rip=192.168.4.145, lip=10.0.0.4, mpid=52302, secured,
session=<+lRmC4o2yubLhgGR>
Jul 01 12:50:08 pop3(u...@domain.com): Info: Disconnected: Logged out
top=0/0, ret
On 14/06/16 23:15, Karsten Heiken wrote:
Hi Leon,
You should be able to add multiple userPassword attributes to your directory:
userPassword: {CRAM-MD5}xxx
userPassword: {DIGEST-MD5}
userPassword: {SCRAM-SHA-1}
userPassword: {NTLM}
Did try this, didn't end end well.
Jun 14 12:5
Hi Karsten,
You should be able to add multiple userPassword attributes to your directory:
userPassword: {CRAM-MD5}xxx
userPassword: {DIGEST-MD5}
userPassword: {SCRAM-SHA-1}
userPassword: {NTLM}
Karsten
Did try this, didn't end end well.
Jun 14 12:59:43 auth: Error:
ldap(leonkyn.
Hi,
Trying to solve the problem of supporting multiple auth mechanisms +
proxy and really don't want to store user passwords in plain test and
fine to do master user to backend.
I had the crazy thought I could do something like the following:
For each user Store supported password schemes as
On 02/05/16 21:43, Timo Sirainen wrote:
On 02 May 2016, at 16:40, Leon Kyneur wrote:
On 02/05/16 16:51, Timo Sirainen wrote:
On 02 May 2016, at 03:47, Leon Kyneur wrote:
Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24
release.
However I'm tryi
On 02/05/16 16:51, Timo Sirainen wrote:
On 02 May 2016, at 03:47, Leon Kyneur wrote:
Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24
release.
However I'm trying to configure these from the userdb lookup and it doesn't
appear to be working.
if I
Was excited to see that wildcards are now possible on autoexpunge in the
2.2.24 release.
However I'm trying to configure these from the userdb lookup and it
doesn't appear to be working.
if I set in 15-mailboxes.conf
mailbox Trash/* {
...
autoexpunge = 10m
}
everything works..
however if
2.2.23 seems to have broken doveadm backup, was previously working fine
on 2.2.22
[root@S613 lkyneur]# doveadm -v backup -u em.mck ...
doveadm(root): Error: User doesn't exist
[root@S613 lkyneur]# doveadm user em.mck
field value
uid vmail
gid vmail
home/srv/vmail/eftel/xxx.com/20
While doing pop3 migrations with dsync I am getting an error:
dsync(u...@domain.net): Error: pop3_migration: 2 POP3 messages have no
matching IMAP messages (first POP3 msg 2638 UIDL
fb3d6f3299541e695a28585f5803ed1c) - set
pop3_migration_ignore_missing_uidls=yes to continue anyway
dsync(u...@do
On 22/02/16 18:56, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 21 Feb 2016, Leon Kyneur wrote:
Date: Sun, 21 Feb 2016 10:51:21 +
From: Leon Kyneur
To: Dovecot Mailing List , Timo Sirainen
Subject: Re: Automatically inferring %d on multi-domain virtual
very intrigued by your solution Timo, have attempted something similar in
the past to no avail.
When I tried I was unable to retain the user@domain when setting the domain
as extra field - protected is new to me and can't find documentation - but
also doesn't work :(
# cat passwd.domains
10.100.1
Hi Tom,
Looks like you are missing 'mailbox' keyword:
namespace/inbox/mailbox/Drafts/autoexpunge=3d
Regards,
Leon
On Tue, Feb 9, 2016 at 12:51 PM Tom Johnson wrote:
>
> > On Feb 7, 2016, at 10:59 AM, Timo Sirainen wrote:
> >
> > You can override any mail-related setting from userdb. So for
Just realized my mistake.. (should read more carefully).
* Long variable names can be used like %{long_name} or with L modifier:
%L{long_name} .
So by changing %Ddomain_first to %D{domain_first} fixed my issue.
On Wed, Feb 3, 2016 at 5:03 PM Leon Kyneur wrote:
> Hi,
>
> Wondering
Hi,
Wondering why it's not possible to do the following in ldap args file:
base = ou=People,dc=%Ddomain_first,o=ISP
however this does work:
base= ou=People,dc=%Dd,o=ISP
is it intentional that modifiers do not work on long names?
Thanks
Leon
handling around this? (if this is
the actual issue)
On Fri, Jan 15, 2016 at 2:25 PM Leon Kyneur wrote:
> Hi
>
> I'm migrating some mailboxes from an old dovecot system where mailboxes
> are stored maildir uncompressed. I enabled zlib on the new system and
> migrated an account:
>
Hi
I'm migrating some mailboxes from an old dovecot system where mailboxes are
stored maildir uncompressed. I enabled zlib on the new system and migrated
an account:
doveadm -o mail_fsync=never backup -R -u tonyg imapc:
when the account connects to the new system after a while i'm seeing the
foll
Hi
As my mail infrastructure grows I'm now looking at the possibility of
running all my doveadm commands from a central location.
Wondering if there is a way to configure an inet_listener on doveadm and
have a client elsewhere connect to it?
Have seen the inet_listener for replication but not su
Yes that seems to work just fine! Thanks
On Tue, Jun 30, 2015 at 7:02 PM Steffen Kaiser <
skdove...@smail.inf.fh-brs.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, 29 Jun 2015, Leon Kyneur wrote:
>
> > I have a configuration that works some
I'm wondering if there is a way I can dynamically generate an LDAP default
value by using variables.
I have a configuration that works something like this on my front end proxy:
pass_attrs = mail=user,\
=nopassword=y,\
=proxy=y,\
=host=mail.%d
The above works perfectly well even though it
In your schema.XML check you have defined:
On 05/03/2015 7:11 PM, "Kevin Laurie" wrote:
> Hello,
> My dovecot constantly runs into this error.
> I want to fix this one last time, I am tired of troubleshooting so
> please someone give me a lasting and proper solution for this error. I
> think i
Hi,
I'm trying to migrate a large number of users to a new Dovecot
cluster. The existing mail system allows a user to authenticate with a
bare username if they have connected to the correct local IP on the
server.
e.g.
imap.somedomain.com = 1.1.1.1
imap.anotheromain.com = 2.2.2.2
charlie@somedom
30 matches
Mail list logo