Try making a view for dspam that filters dbmail_aliases with "where deliver_to not like '[EMAIL PROTECTED]'" or so.
On Wed, 2006-05-31 at 14:31 +0300, Alex wrote: > mysql> select * from dbmail_aliases; > +------------+-----------------------+------------+-------------+ > | alias_idnr | alias | deliver_to | client_idnr | > +------------+-----------------------+------------+-------------+ > | 1 | [EMAIL PROTECTED] | 3 | 0 | > +------------+-----------------------+------------+-------------+ > > I'm using postfix to check for local users. Now I want dspam to use this > table as it's user database too. > > Postfix uses only the alias column. dspam on the other hand the alias > and the deliver_to column. The alias is the username for dspam, that it > get's from the mail and deliver_to the uid on unique user. Very > convenient -- one user can and usually has many aliases. That way I > don't have to use address rewriting or whatever. > > Now this table ain't that good idea anymore, be cause the deliver_to > column is used for external forwarding too. Correct? The solution would > be to generate a table for dspam each time I modify dbmail's userbase, > that's what I'm planning to do now. > > It just be very convenient, if postfix, dspam and dbmail used the same > table and I wouldn't have to worry about keeping things in sync. Any > suggestions or apparent problems? > > Alex > > PS: What is client_idnr column used for, it's "0" in all my dbmail installs? > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail -- Jesse Norell - [EMAIL PROTECTED] Kentec Communications, Inc.
