Re: [Dovecot] LMTP: userdb lookup - user-filter with variables
Am 31.07.2013 14:05, schrieb Burckhard Schmidt:
I tried to use dovcots lmtp instead of dovecot-lda.
postfix has in master.cf ... dovecot-lda -f ... -d ${user} to separate
the user part from user@hostname.domain.
So lookup of user succeeds in userdb (LDAP) done by dovecot-lda.
I have always local addresses like to=user@hostname.domain
postfix/lmtp[6579]: [ID 197553 mail.info] B3CDA66A16:
to=h0094...@mailstore4.hu-berlin.de
With lmtp the userpart must be separated also. I tried user_filter
(LDAP) with %n, %Ln, %8n without success: userdb lookup:
user@hostname.domain doesn't exist)
Missing charachters @.- in auth_username_chars prevents
user@host.domain to be a valid address at all.
dovecot-2.1.17
I used doveadm user h0094slk and
doveadm user h0094...@mailstore4.hu-berlin.de
for my tests.
userdb {
driver = ldap
args = /usr/dovecot/etc/ldapuser.conf
}
and ldapuser.conf with
...
user_filter = ((uid=%n) (objectClass=cmsAccount))
user_attrs = homeDirectory=home
I modified user_filter like uid=%Ln or uid=%8u
success for doveadm user h0094slk (because nothing to split)
userdb: h0094slk
home : /home/p0094/h0094slk
but no success for
doveadm user h0094...@mailstore4.hu-berlin.de
userdb lookup: user h0094...@mailstore4.hu-berlin.de doesn't exist
It looks for me like user_filter do not use variables at this point?
What I'm missing?
--
Mit freundlichen Grüßen --- Burckhard Schmidt
Abteilung Systemsoftware und Kommunikation
ZE Computer- und Medienservice der Humboldt-Universität zu Berlin
Postanschrift: Unter den Linden 6, 10099 Berlin
Standort: Rudower Chaussee 26; 12489 Berlin
Tel.: +49-30-2093-70058 Fax: +49-30-2093-2959
Mail: bschm...@cms.hu-berlin.de
Re: [Dovecot] LMTP userdb lookup
On 2012-10-16 4:57 PM, l...@airstreamcomm.net l...@airstreamcomm.net wrote: Doveconf -n: # 2.1.1: /etc/dovecot/dovecot.conf Ummm... latest is 2.1.10... try upgrading again... ;)
Re: [Dovecot] LMTP userdb lookup
On 10/4/12 9:58 AM, Timo Sirainen wrote:
On 4.10.2012, at 17.41, l...@airstreamcomm.net wrote:
protocol lmtp {
userdb {
..
}
}
protocol !lmtp {
userdb {
..
}
}
Forgot to mention I am running 2.0.17.
The above works in v2.1.
And I am getting the following error:
auth: Fatal: No passdbs specified in configuration file. PLAIN
mechanism needs one
From a previous post it appears that Dovecot cannot run without a global
lookups specified:
http://www.dovecot.org/list/dovecot/2012-March/064407.html
Per the suggestion in the old post I created an empty passwdfile and included
it in the auth-passwdfile which seems to have alleviated the issue, however
this seems like a sub-optimal solution. Is this still the case, or is there a
way to tell Dovecot that there is no global lookups?
The !lmtp version avoids that fatal problem. So the solution is: upgrade.
Timo,
I upgraded to 2.1 and configured as recommended, however I am still
getting an error:
auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism
needs one
Doveconf -n:
# 2.1.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-279.5.2.el6.x86_64 x86_64 CentOS release 6.3 (Final)
auth_debug = yes
auth_verbose = yes
disable_plaintext_auth = no
mail_debug = yes
mail_fsync = always
mail_location = maildir:~/Maildir
mail_nfs_index = yes
mail_nfs_storage = yes
mbox_write_locks = fcntl
mmap_disable = yes
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
service imap-login {
inet_listener imap {
port = 143
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
service pop3-login {
inet_listener pop3 {
port = 110
}
}
ssl_cert = /etc/pki/dovecot/certs/mail.crt
ssl_key = /etc/pki/dovecot/private/mail.key
protocol !lmtp {
passdb {
args = /etc/dovecot/imappop.conf.ext
driver = sql
}
userdb {
args = /etc/dovecot/imappop.conf.ext
driver = sql
}
}
protocol lmtp {
passdb {
args = /etc/dovecot/lmtp.conf.ext
driver = sql
}
userdb {
args = /etc/dovecot/lmtp.conf.ext
driver = sql
}
}
Re: [Dovecot] LMTP userdb lookup
On 10/3/12 3:58 PM, Timo Sirainen wrote:
On 3.10.2012, at 22.26, l...@airstreamcomm.net wrote:
Is it possible to have separate userdb lookups for LMTP and POP/IMAP?
protocol lmtp {
userdb {
..
}
}
protocol !lmtp {
userdb {
..
}
}
Forgot to mention I am running 2.0.17.
I separated all the userdb passdb lookups into their own protocol
configuration like so:
protocol imap {
userdb { .. }
passdb { .. }
}
protocol pop3 {
userdb { .. }
passdb { .. }
}
protocol lmtp {
userdb { .. }
}
And I am getting the following error:
auth: Fatal: No passdbs specified in configuration file. PLAIN
mechanism needs one
From a previous post it appears that Dovecot cannot run without a
global lookups specified:
http://www.dovecot.org/list/dovecot/2012-March/064407.html
Per the suggestion in the old post I created an empty passwdfile and
included it in the auth-passwdfile which seems to have alleviated the
issue, however this seems like a sub-optimal solution. Is this still
the case, or is there a way to tell Dovecot that there is no global
lookups?
Re: [Dovecot] LMTP userdb lookup
On 4.10.2012, at 17.41, l...@airstreamcomm.net wrote:
protocol lmtp {
userdb {
..
}
}
protocol !lmtp {
userdb {
..
}
}
Forgot to mention I am running 2.0.17.
The above works in v2.1.
And I am getting the following error:
auth: Fatal: No passdbs specified in configuration file. PLAIN
mechanism needs one
From a previous post it appears that Dovecot cannot run without a global
lookups specified:
http://www.dovecot.org/list/dovecot/2012-March/064407.html
Per the suggestion in the old post I created an empty passwdfile and included
it in the auth-passwdfile which seems to have alleviated the issue, however
this seems like a sub-optimal solution. Is this still the case, or is there
a way to tell Dovecot that there is no global lookups?
The !lmtp version avoids that fatal problem. So the solution is: upgrade.
Re: [Dovecot] LMTP userdb lookup
On 3.10.2012, at 22.26, l...@airstreamcomm.net wrote:
Is it possible to have separate userdb lookups for LMTP and POP/IMAP?
protocol lmtp {
userdb {
..
}
}
protocol !lmtp {
userdb {
..
}
}
