On Sat, 9 Nov 2013 08:54:40 +0530 tejas sarade <tejas.a.sar...@gmail.com> wrote:
> If lookup fails Postfix will use default transport. Sure but this is only _one_ "hard-coded" transport and not one I can dynamically change like in the tcp_table lookup. So it looks like as if the logic tries to minimize the lookup queries and expect all tables which are more than a "key"=>"value" mapping knows with _one_ query if it is responsible or not. That means I can't use static hash tables for domains if I want to have a tcp table which gives me a default value if _no other hash based_ table has a domain hit. Correct me if I'm wrong. Simon > On Nov 9, 2013 7:49 AM, "Simon Effenberg" <sa...@schuldeigen.de> wrote: > > > > > > > > > > wie...@porcupine.org schrieb: > > >transport_maps are searched in the order as specified in main.cf. > > >If it's not found in regexp:/etc/postfix/transport.exp, then > > >the tcp map is queried. > > > > > > Wietse > > > > So this means that I cannot distinguish between x...@yyy.com and > > yyy.comlookups in the tcp table because I will only be queried with > > x...@yyy.com and yo the tcp table has to know all domains as well if it > > should be a last resort to all unknown domains in the transport file, right? > > > > Simon > > -- > > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail > > gesendet. > > --
