Change the query it uses (in a sql/ldap lookup), you can include the
user in it as well.
you can set the query in the config file.
Aaron Stone wrote:
> This doesn't yet help with a single huge domain, though. For that we need
> to partition based on the localpart.
>
> On Fri, Mar 30, 2007, Curtis Maurand <[EMAIL PROTECTED]> said:
>
>
>>> Can it? Point me to some docs and/or sample configs. If this can be made
>>> to work, then we really would have a single namespace horizontally
>>> scalable setup that we could recommend.
>>>
>>>
>> look at the transport maps in postfix.
>>
>> In my configuration its
>>
>> transport_maps = hash:/etc/postfix/transports
>>
>> Then my transports file looks like:
>>
>> domain1.com smtp:192.168.1.5:25
>> domain2.com dbmail-lmtp:127.0.0.1:24
>> domain3.com smtp:mailhost.somewhere.com:25
>> lists.domain1.com mailman:
>>
>>
>> you get the picture.
>>
>> then run postmap hash:/etc/postfix/transports
>>
>> I would imagine that a table in mysql would work as well. The
>> configuration would look something like:
>>
>> transport_maps=mysql:transports.cf
>>
>> /etc/postfix/transports.cf
>>
>> user=dbuser
>> passoword=somepassword
>> hosts=192.168.1.10
>> dbname=<whatever database you're using>
>> select_field=destination
>> where_field=domain
>>
>> then the table would be:
>>
>> create table 'transports' (
>> 'domain' text(120),
>> 'destination' text(120),
>> UNIQUE KEY 'domain' ('domain')
>> ) ENGINE=MyISAM;
>>
>> In fact this is the method that dbmail administrator uses with postfix.
>>
>>
>>> Aaron
>>>
>>> _______________________________________________
>>> DBmail mailing list
>>> [email protected]
>>> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>>>
>>>
>>>
>>>
>>>
>> _______________________________________________
>> DBmail mailing list
>> [email protected]
>> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>>
>>
>
>
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
