Lmtp w/ Postfix and LDAP: change mailbox name when saving mail.
kbah at linuxmail.org
Wed Jan 21 12:01:14 EST 2009
I need to know then how things are processed when mail arrives, from the Cyrus point of view, of course.
First Postfix searches the user on LDAP, like this:
on my LDAP server the fields are:
mail = username at domain.org
uid = username~domain.org
mailRoutingAddress = username~domain.org at domain.org (uid is the "user part")
My question is, how Cyrus decides what is the mailbox name, from what Postfix gives or it just looks the user part of the email? I mean, Cyrus knows the destination email is username at domain.org, then it assumes the mailbox name is "username"? Or it uses the "user part" of whatever Postfix gave(?), because if this is true, Cyrus should be using the user part of the mailroutingaddress field..?
Right now Postfix is using Dovecot LDA, and the mailbox names are as expected.
I'm trying to understand how Cyrus decides the mailbox name, how can I debug it? I think Postfix is correctly configured to what I want it to do (mailbox name = uid field from LDAP or "user part of mailroutingaddress").
> ----- Original Message -----
> From: "Dan White" <dwhite at olp.net>
> To: "k bah" <kbah at linuxmail.org>
> Cc: Info-cyrus at lists.andrew.cmu.edu
> Subject: Re: Lmtp w/ Postfix and LDAP: change mailbox name when saving mail.
> Date: Wed, 21 Jan 2009 09:16:08 -0600
> Dan White wrote:
> > sasl_ldapdb_uri: ldap://ldap.example.org
> > sasl_ldapdb_mech: GSSAPI
> > sasl_ldapdb_canon_attr: uid
> > #sasl_canon_user_plugin: ladpdb
> > #imap_sasl_canon_user_plugin: ldapdb
> > #pop3_sasl_canon_user_plugin: ldapdb
> > #nntp_sasl_canon_user_plugin: ldapdb
> > #sieve_sasl_canon_user_plugin: ldapdb
> > lmtp_sasl_canon_user_plugin: ldapdb
> On second thought, this probably won't do anything useful, since
> the user is not authenticating to LMTP.
> A Postfix regex map (or LDAP map) may be able to convert the
> recipient before it gets handed off to LMTP.
> - Dan
Antennas 100 kHz to 26 GHz (COTS) Commercial- Industrial-Government.
Powered by Outblaze
More information about the Info-cyrus