Victor Duchovni wrote: > On Tue, Dec 14, 2010 at 02:01:31PM +0100, Per Jessen wrote: > >> > The problem is that the SASL user name may well contain >> > white-space, and postmap(1) cannot create indexed tables with keys >> > that contain white-space. You could create the tables with other >> > tools, but then you can't update the files "in place", you have to >> > create a temporary indexed file and rename(2) it into place. This >> > would work with CDB and Berkeley DB, but not with traditional "dbm" >> > files, since you can't atomically rename two files. >> >> Wouldn't this also be the case for smtpd_sender_login_maps ? > > No, the sender is the lookup key. While white-space is also legal > in email addresses, it is far less likely that an email address > localpart will contain white-space. Perhaps we can ignore both > potential issues... > > Does anyone (on this list) have SMTP SASL backends that support login > names with white-space? Or know of sites that do?
Just a quick follow-up - I would have been glad to produce a patch for a check_sasluser_access, but I'm not sufficiently familiar with the postfix code. For my own needs, I have implemented a policy daemon (the coding of which I am far more familiar with). /Per Jessen, Zürich
