See my comments regarding bug #477. Your configuration will either
*crash* or *drop all mail* with aliases of the form @domain -> @domain2.
This will be fixed, it'll just take a few days of thinking and coding.

I would like to be able to support the configuration that you're
suggesting below. Everyone interested should please continue discussion
so that we get some good ideas and issues out on the table! :-)

Aaron

On Sat, 2006-12-16 at 10:19 +0100, Michael Monnerie wrote:
> On Freitag, 15. Dezember 2006 19:08 Marc Dirix wrote:
> > Ultimately you should let your MTA do a sql lookup before accepting
> > the message.
> 
> Yes, and the problem is, in postfix (MTA) I do the correct lookup:
> 
> query = SELECT (case when count(dbmail_aliases.alias) > 0 then 'OK' when 
> count(dbmail_aliases.alias) = 0 then 'REJECT' END) AS access
>    FROM dbmail_aliases left join zmi_domains on zmi_domains.client_idnr 
> = dbmail_aliases.client_idnr
>    WHERE substring (dbmail_aliases.alias from 1 for position('@' in 
> dbmail_aliases.alias)) || zmi_domains.domain='%s'
> 
> where I have extended dbmail (based on 
> http://www.dbmail.org/dokuwiki/doku.php?id=domain_alias_spam_bounce ):
> CREATE TABLE zmi_domains (
>    client_idnr     INT8 NOT NULL,
>    domain          VARCHAR(80) UNIQUE NOT NULL,
>    pridomain       VARCHAR(80) DEFAULT NULL,
>    comment         text,
>    CONSTRAINT zmidom_pk PRIMARY KEY(domain),
> );
> 
> In that table, there is:
>  client_idnr |    domain     |  pridomain   | comment
> -------------+---------------+--------------+---------
>         1001 | datamatix.eu  |              |
>         1001 | datamatix.net | datamatix.eu |
> 
> Which means that datamatix.net is an alias domain of datamatix.eu. This 
> domain alias is also defined in dbmail_aliases:
> alias_idnr |           alias         |   deliver_to  | client_idnr
> -----------+-------------------------+---------------+-------------
>         11 | @datamatix.net          | @datamatix.eu |        1001          
>         10 | [EMAIL PROTECTED] | 1002          |        1001
> 
> So dbmail should really know that user [EMAIL PROTECTED] is 
> valid, but [EMAIL PROTECTED] is not, because [EMAIL PROTECTED] is not 
> defined. My PostgreSQL select does that correctly, just dbmail itself 
> seems confused.
> 
> Again, I'm wondering if others do not have this problem? An alias 
> domain, where not existing aliases should be REJECTed at MTA level. And 
> how to solve this?
> 
> mfg zmi
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to