similar to: passdb pam and userdb passwd "Authentication failure" errors

Hi, I'm testing/using dovecot as imap proxy, passdb/userdb as passwd-like-file. It seems to function as expected (1). This setup is described in the wiki in AuthSpecials. But I also noticed in the documentation (ImapProxy / FeatLoginProxy pages) that the proxy feature only works with a sql passdb. Maybe I did something strange, but passwd-like-passdb does work..... So I have some

On Fri, 2009-03-13 at 16:18 -0700, Shane W wrote: > The problem may be the shane@ bit. If I delete the sql > entry, the lookup just shows 'shane'. I'm not loging in > with @ but my query does use the username,domain syntax for > instances of virtual users which don't use passwd userdb: > select username,domain,password from users > WHERE username = '%n'

Hi, i still got a little Problem (Thunderbird cant copy my mail to "Gesendet") but besides that i can send and receive mail. ive used: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall there it says that /etc/dovecot/passwd should look like: test:{PLAIN}pass bill:{PLAIN}secret timo at example.com:{PLAIN}hello123 dave at example.com:{PLAIN}world234 joe at elsewhere.org:{PLAIN}whee

Hi all, I'm guessing this is correct behavior, but wanted to make sure... I noticed that for locally delivered messages (between 2 local users inside our domain, so they never leave the server), the first Received: header line content changed after I switched to the dovecot LDA. Before, using postfix/virtual for delivery, the header looked like this: Received: from [192.168.1.25]

For reasons of user privacy and security I usually configure submission servers to not include accurate IP address and HELO information of authenticated users. (Usually replacing it with a private-use domain / IPv6 address.) Dovecot submission (2.3.2) will produce a header something like this (where ?10.22.36.10" is a public IP address) Received: from [192.168.1.184] ([10.22.36.10]) by

Hi there! I have been setuped exim and dovecot. Exim uses dovecot-lda to deliver mails to mailbox. Some configurations of exim: dovecot_virtual_delivery: ? driver = pipe ? command = /usr/libexec/dovecot/dovecot-lda -d $local_part@$domain -f $sender_address ? message_prefix = ? message_suffix = ? delivery_date_add ? envelope_to_add ? return_path_add ? log_output ? user = vmail ? group = vmail ?

Hi, In many mail setups a required feature (for privacy reasons) is to hide the host and IP of clients (in the "Received" header) that use the authenticated submission over port 587. In Postfix that's possible (https://serverfault.com/q/413533/86332), but not very nice to configure especially if you only want want to strip the Received header for port 587 submissions, but not on

Hello Is it possible to setup double backend ? ldap for auth only and SQL for userdb information(quota,maildir etc) ? Now I'm using SQL backend and configuration looks like this: passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetch } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } Can I do something like: passdb { driver = sql args

Hello Timo, I've noticed that when slapd which I'm using as the passdb and the prefetched userdb is restarted I have to restart dovecot. As a matter of fact, if I don't, I get the following error : -- Jul 2 16:38:39 xxxx dovecot: imap-login: Internal login failure: user=<xxxx>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Jul 2 16:38:46 xxxx dovecot:

Hi, I've been running some performance tests - especially delivery (LDA and LMTP) and it seems there's room for improvement. At least it would be nice to get rid of the fork() and pipe to deliver LDA and the fork of the checkpasswd script for userdb lookup. I've tried LMTP to not fork deliver (*), but checkpasswd still takes time (ok, maybe because it's written on perl as of

Hi, I was wondering if any work had been made (out of tree) or has been planned for a mongo driver? If not is it something that would be of any interest for being included? Regards, Damien

Dear all, We are getting closer to the migration of our mailsystem. Now I have a special question. We are successfully using passdb { driver = pam } and that is good. Now, how would I tell dovecot to proxy certain users (the ones not yet migrated) to the old server? My attempts to configure an additional userdb failed since this seems to override the passdb setting. Grateful for any

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 May 2014, Kristof Bajnok wrote: > in my current setup, LDAP authentication + userdb works fine. > > I'd like to integrate Dovecot with Shibboleth. I have a custom module at > the IdP (*) that inserts short-time tokens to an SQL table at user > authentication, and I want Dovecot to use the token table for passdb but >

hi everybody. I wonder if such a scenario is possible. if yes would I configure multiple passdb using ldap driver or within one clause set up multiple args? How would this work? many thanks P.

On 02/17/2015 04:03 PM, lejeczek wrote: > hi everybody. > > I wonder if such a scenario is possible. > if yes would I configure multiple passdb using ldap driver > or within one clause set up multiple args? How would this work? Did you read http://wiki2.dovecot.org/Authentication/MultipleDatabases? Regards, Pascal -- The trapper recommends today: face1e55.1504802 at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 18 Feb 2015, lejeczek wrote: > On 17/02/15 19:36, Pascal Volk wrote: >> On 02/17/2015 04:03 PM, lejeczek wrote: >>> hi everybody. >>> >>> I wonder if such a scenario is possible. >>> if yes would I configure multiple passdb using ldap driver >>> or within one clause set up multiple args?

On 04/10/2015 05:59 AM, Jeroen Massar wrote: > > This can be resolved by commenting out the entries in > auth-system.conf.ext but then I'll have to do that again at package > upgrade time. Comment out the !include auth-system.conf.ext line in 10-auth.conf. > > Hence, would it be a cool option to be able (in the 99-myconfig.conf) > file to put: Actually you mean

On Sex, 10 Abr 2015, Jeroen Massar wrote: > Though indeed simpler than commenting out multiple lines, that file also > gets replaced by a package upgrade. > > Hence does not solve the 'can just upgrade silently' issue. If the file is unchanged then, yes, it gets replaced on upgrades. If it has local changes, however, you'll get a prompt asking what you want to do (keep

On 2015-04-10 14:23, Eduardo M KALINOWSKI wrote: > On Sex, 10 Abr 2015, Jeroen Massar wrote: >> Though indeed simpler than commenting out multiple lines, that file also >> gets replaced by a package upgrade. >> >> Hence does not solve the 'can just upgrade silently' issue. > > If the file is unchanged then, yes, it gets replaced on upgrades. If it > has

Hi, it would be nice to have an option to enable logging for timings without having to go with auth_verbose/auth_debug. If you try to track down if a slowdown for logging in comes from e.g. running out of login workers or if your auth backend is slow it would really help to get just a one line message per userdb/passdb with the timing for this lookup. something like: