Michael Monnerie wrote:
> On Freitag 26 Juni 2009 Paul J Stevens wrote:
>> Even we do very much the same in our main installation, we use LDAP
>> to extend the user model, so the extra tables would be redundant for
>> us. Also, I fail to understand how the additional tables effect
>> dbmail internals. My business logic builds on ldap, and doesn't
>> require any tweaking of the dbmail code or tables. Most of the
>> delivery process is handled by postfix talking to ldap - no dbmail
>> involved. All the lmtp server needs to be able to do is route a
>> message (that already was verified as destined for a valid user) to
>> the correct user's inbox (or sieve script).
> 
> Can you post your LDAP schema? I guess I really should change and use 
> that. I didn't until now, as I can't see the advantage of LDAP over 
> dbmail (for us). But as you're using it that way, I'd like to change to 
> the same model in order to have the same usage in dbmail-2.3, once we 
> switch.

I don't follow. It's been in dbmail forever. Take a look at dbmail.schema.

To summarize:

objectclass ( 1.3.6.1.4.1.12340.6.2.2.1 NAME 'dbmailUser'
                DESC 'DBMail-LDAP User' SUP top AUXILIARY
                MUST ( uid $ mail )
                MAY ( userPassword $ uidNumber $ gidNumber $ mailQuota $
mailForwardingAddress $ mailHost $
                mailAlternateAddress $ dbmailUID $ dbmailGID $
deliveryMode $  accountStatus ) )

objectclass ( 1.3.6.1.4.1.12340.6.2.2.2 NAME 'dbmailForwardingAddress'
                DESC 'DBMail-LDAP Forwarding Address' SUP top AUXILIARY
                MUST ( mail $ mailForwardingAddress ) )

objectclass ( 1.3.6.1.4.1.12340.6.2.2.3 NAME 'dbmailDomain'
                DESC 'DBMail-LDAP Virtual Domain' SUP top STRUCTURAL
                MUST ( mailDomain )
                MAY ( userPassword $ mailQuota $ mailForwardingAddress $
mailHost $ mailCluster ) )


> And if others you the same scheme, it'l be easier to understand each 
> other or workout features. I've recently expressed our will to provide 
> our web interface. I'm in the process to do that, but it's tricky as 
> it's heavily using our internals. So using a "standard model" should be 
> less pain for the 2.3 adopted version.
> 
> I hope you're able to post your LDAP schema (confidential?), and that I 
> can adopt to use it. Then I could start trying out dbmail-2.3 with that 
> schema already, so migration should be easier also.

There is nothing 2.3-ish about any of this.

-- 
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to