Re: STARTTLS issue with sieve
Am 10.07.2017 um 08:52 schrieb Heiko Schlittermann: Andreas Oster (Mo 10 Jul 2017 08:23:17 CEST): … Hello Heiko, removing the CA and intermediate certificates from the server certificate and adding the CA certs to the ca-certificates.crt resolved my issue. According to what Peter wrote, I'd put the root CA to your ca-certificates, but let the intermediate cert in the certificate chain sent by the server. (That's what the intermediate certs are good for, isn't it?) Yes, that's exactly how you should do it. Heiko Alexander
Re: Master auth only
Citát Aki Tuomi :
On July 10, 2017 at 1:45 PM azu...@pobox.sk wrote:
Citát Aki Tuomi :
>> On July 10, 2017 at 12:33 PM azu...@pobox.sk wrote:
>>
>>
>> Hi,
>>
>> i'm trying to configure Dovecot proxy with user authentication on
>> proxy side only, so backends will authenticate using master password
>> (proxy is configured to send it). The problem is that Dovecot, on
>> backends, is telling me that i need to configure at least one auth
>> mechanism:
>>
>> auth: Fatal: No passdbs specified in configuration file. LOGIN
>> mechanism needs one
>>
>>
>> The master auth is correctly configured.
>>
>> I want to accomplished to have user database only on one place
>> (=proxy). Any hints?
>>
>> azur
>
> Can you show your backend doveconf -n?
>
> Aki
Here it is:
https://pastebin.com/C8dTUm5k
Try adding another entry after the first passdb (order matters)
passdb {
driver = static
args = nopassword
deny = yes
skip = authenticated
}
Aki
This seems to be working, thank you. Can you explain me why it's needed?
Re: Master auth only
> On 10 Jul 2017, at 12.33, azu...@pobox.sk wrote:
>
> Hi,
>
> i'm trying to configure Dovecot proxy with user authentication on proxy side
> only, so backends will authenticate using master password (proxy is
> configured to send it). The problem is that Dovecot, on backends, is telling
> me that i need to configure at least one auth mechanism:
>
> auth: Fatal: No passdbs specified in configuration file. LOGIN mechanism
> needs one
>
>
> The master auth is correctly configured.
>
> I want to accomplished to have user database only on one place (=proxy). Any
> hints?
In the config sample provided in another mail you have configured master *user*
passdb but
in this mail you talk about master password passdb? which one it is?
I think for what you are trying to achieve, master password auth is more
suitable. So change your
passdb to something like this:
passdb {
driver = static
args = password=masterpassword
}
simple as that.
Sami
Re: Master auth only
> On July 10, 2017 at 1:45 PM azu...@pobox.sk wrote:
>
>
>
> Citát Aki Tuomi :
>
> >> On July 10, 2017 at 12:33 PM azu...@pobox.sk wrote:
> >>
> >>
> >> Hi,
> >>
> >> i'm trying to configure Dovecot proxy with user authentication on
> >> proxy side only, so backends will authenticate using master password
> >> (proxy is configured to send it). The problem is that Dovecot, on
> >> backends, is telling me that i need to configure at least one auth
> >> mechanism:
> >>
> >> auth: Fatal: No passdbs specified in configuration file. LOGIN
> >> mechanism needs one
> >>
> >>
> >> The master auth is correctly configured.
> >>
> >> I want to accomplished to have user database only on one place
> >> (=proxy). Any hints?
> >>
> >> azur
> >
> > Can you show your backend doveconf -n?
> >
> > Aki
>
>
>
> Here it is:
> https://pastebin.com/C8dTUm5k
Try adding another entry after the first passdb (order matters)
passdb {
driver = static
args = nopassword
deny = yes
skip = authenticated
}
Aki
Re: Master auth only
Citát Aki Tuomi : On July 10, 2017 at 12:33 PM azu...@pobox.sk wrote: Hi, i'm trying to configure Dovecot proxy with user authentication on proxy side only, so backends will authenticate using master password (proxy is configured to send it). The problem is that Dovecot, on backends, is telling me that i need to configure at least one auth mechanism: auth: Fatal: No passdbs specified in configuration file. LOGIN mechanism needs one The master auth is correctly configured. I want to accomplished to have user database only on one place (=proxy). Any hints? azur Can you show your backend doveconf -n? Aki Here it is: https://pastebin.com/C8dTUm5k
Re: Master auth only
> On July 10, 2017 at 12:33 PM azu...@pobox.sk wrote: > > > Hi, > > i'm trying to configure Dovecot proxy with user authentication on > proxy side only, so backends will authenticate using master password > (proxy is configured to send it). The problem is that Dovecot, on > backends, is telling me that i need to configure at least one auth > mechanism: > > auth: Fatal: No passdbs specified in configuration file. LOGIN > mechanism needs one > > > The master auth is correctly configured. > > I want to accomplished to have user database only on one place > (=proxy). Any hints? > > azur Can you show your backend doveconf -n? Aki
Master auth only
Hi, i'm trying to configure Dovecot proxy with user authentication on proxy side only, so backends will authenticate using master password (proxy is configured to send it). The problem is that Dovecot, on backends, is telling me that i need to configure at least one auth mechanism: auth: Fatal: No passdbs specified in configuration file. LOGIN mechanism needs one The master auth is correctly configured. I want to accomplished to have user database only on one place (=proxy). Any hints? azur
Re: Return extra fields from passwd userdb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 7 Jul 2017, Michele Petrella wrote:
Output of dovecot -n:
# 2.2.29.1 (e0b76e3): /var/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.18 (29cc74d)
# OS: Linux 3.10.55-gentoo i686 SuSE Linux 7.1 (i386)
userdb {
default_fields = quota_rule=*:bytes=%$
driver = passwd
}
I have problems in return extra fields from passwd userdb. My users are
partially in passwd files and partially in LDAP. Users who use mail are in
LDAP db.
If I use "default_fields = quota_rule=*:bytes=100M" in userdb,
if I use "default_fields = quota_rule=*:bytes=%{userdb:quotabytes}" in
userdb,
1) default_fields supplies default values, if the userdb does not return
them. Hence, you cannot reference a LDAP result.
2) the userdb section cannot merge two databases together. You said "Users
who use mail are in LDAP db", so you would one userdb with driver ldap.
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEVAwUBWWNARHz1H7kL/d9rAQJVAAf+KNHBAcZZgpc8q3AAnDOPj43xtbGzF3/E
FSsuGJkswVVmkwckrmOQkehFS0M3PthvHcr9UmCutvw5Wzk9F0E6cm+V4z/Iu4g/
YmbHVt6dKiydn7yG7NpW7rf5j/ae2SB+uEvkvEXewr/XGuFNuCMcLSa9VpK7eAp5
mp0+/oJIh7aTU1+SKcKJQVr+kGHuzDVXAGyXupekF070slAWfm4Y7fpp6Ui8rTxO
TTsGoZyi6ieWX6Vl729Io+xxCIbz6qtUpSkByJP389zA09HSt9EOUZlQaZJ32J6o
sCC+JPxnuKMKCr4UlxGDT+JqXEHv8rZCf+QGLJ+U4e1y2oTTGkmUMw==
=Av+G
-END PGP SIGNATURE-
Re: pigeonhole-0.4.14
Op 7/9/2017 om 1:44 PM schreef j.emerlik: > Sure ! I believe you already showed the scripts that sieve_before and sieve_default point to. But, what does this user have in ~/.dovecot.sieve? Do you also have an example of a message that is failing? Regards, Stephan.
