On Tue, 2008-02-12 at 19:42 -0700, Bryan Rehbein wrote: > I have been following the dbmail development for about a year now and > have finally starting working on migrating email accounts to dbmail. > > I have one major issue: > My users authenticate using their email address as a user name, I would > actually like them to be able to authenticate using any alias and their > password. I'm trying to go for user convenience here, with hopefully no > changes to how my users currently check email (a seamless transition). > Is this possible (I'm using the 2.2.x series). I am using pgsql as the > back end, would I have to implement LDAP for this to work, or is there > something that could be easily done with the code?
It's not possible to do this in LDAP code does not retrieve and compare a password, rather, it looks up the user account then attempts to bind to the LDAP server as that user. This validation strategy allows the LDAP server to maintain a policy of not allowing the password to be retrieved, encrypted or not, at all. In SQL it's not possible because a single alias can resolve to a number of user accounts. Sorry! > I also noticed that dspam has issues with dbmail when delivering via > LMTP due to dbmail returning 215 codes instead of 250 codes. I have > worked around this issue, however, what is the reasoning behind using > 215 instead of 250? 215 is an RFC compliant return value. Dspam is broken if it does not accept that value as indicating a successful delivery. Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
