> > > >
> > > > ? Imho are these just arguments for people not being able to setup
> an
> > > > environment correctly.
> > >
> > > I do not intend to start a flame on this topic, it is just my
> opinion.
> >
> > But writing it down like this is still educating people (incorrectly).
> >
> > > It'
> On 09/05/2023 12:26 EEST Marc wrote:
>
>
> > >
> > > ? Imho are these just arguments for people not being able to setup an
> > > environment correctly.
> >
> > I do not intend to start a flame on this topic, it is just my opinion.
>
> But writing it down like this is still educating peopl
> >
> > ? Imho are these just arguments for people not being able to setup an
> > environment correctly.
>
> I do not intend to start a flame on this topic, it is just my opinion.
But writing it down like this is still educating people (incorrectly).
> It's not about the correct environment (yo
It should also be mentioned that dovecot can act as a SMTP relay in
"front" of Postfix (or any other MTA) and handle the authentication part
of the transaction. This of course implies use of the dovecot
authentication machinery for mail submissions. I don't know much about
it beyond it's existe
postfix can use LDAP for authentication (i.e. SASL) and for
validation("ldap" table).
As best I can tell, postfix cannot use dovecot to validate addresses, if
you want that you will need postfix to talk directly to ldap. GOTCHA:
use the "postconf -m" command to check that the "ldap" table is
On 2023-05-09 11:14, Marc wrote:
so far I had a setup where Dovecot was using a passwd file as
userdb and
passdb. Postfix was then authenticating with Dovecot via SASL
to
validate user accounts.
Now I added an LDAP backend and wou
>
>
> so far I had a setup where Dovecot was using a passwd file as
> userdb and
> passdb. Postfix was then authenticating with Dovecot via SASL
> to
> validate user accounts.
>
> Now I added an LDAP backend and would like to use that for
>
On 09-05-2023 08:58, Moritz Pflanzer wrote:
Thanks Kees. The doveadm command is showing the same behavior as I can see from
postfix where the wrong search filter is used:
docker-openldap-1 | 6459e95f.1a1ad6c2 0x7fe379a98700 conn=1427 op=67 SRCH
base="ou=users,dc=example,dc=com" scope=2 deref
The question about best practices was more a conceptual one. Should dovecot and
postfix talk independently to the LDAP database? Or should dovecot be the
gateway for postfix to get the information out of the LDAP database?
Just my 2 cents, id have postfix talk directly to LDAP to see if a use
You will likely get better results if you let postfix to validate recipients
with LDAP first. This way it can already refuse to accept mail for invalid
recipients, and this reduces backscatter spam.
Aki
> On 09/05/2023 10:11 EEST Moritz Pflanzer wrote:
>
>
> Thanks for the hints. I already
Thanks for the hints. I already followed that guide.
The question about best practices was more a conceptual one. Should dovecot and
postfix talk independently to the LDAP database? Or should dovecot be the
gateway for postfix to get the information out of the LDAP database?
Cheers,
Moritz
> O
Thanks Kees. The doveadm command is showing the same behavior as I can see from
postfix where the wrong search filter is used:
docker-openldap-1 | 6459e95f.1a1ad6c2 0x7fe379a98700 conn=1427 op=67 SRCH
base="ou=users,dc=example,dc=com" scope=2 deref=0
filter="(&(objectClass=posixAccount)(uid=mo
12 matches
Mail list logo
