Re: (now unsigned) how not to match a sub-subdomain

Marc Risse: > Am 23.03.21 um 15:10 schrieb Wietse Venema: > > Marc Risse: > >> Hello everyone, > >> > >> will ".domain.com" match "b...@sub2.sub1.domain.com" or only > >> "b...@sub1.domain.com" in transport maps? > > With an indexed table (for example, hash: or btree:), .domain.com > > will not

Re: (now unsigned) how not to match a sub-subdomain

Am 23.03.21 um 15:10 schrieb Wietse Venema: Marc Risse: Hello everyone, will ".domain.com" match "b...@sub2.sub1.domain.com" or only "b...@sub1.domain.com" in transport maps? With an indexed table (for example, hash: or btree:), .domain.com will not match any email address, and it will match

Re: (now unsigned) how not to match a sub-subdomain

Marc Risse: > Hello everyone, > > will ".domain.com" match "b...@sub2.sub1.domain.com" or only > "b...@sub1.domain.com" in transport maps? With an indexed table (for example, hash: or btree:), .domain.com will not match any email address, and it will match every subdomain. If you want finer

(now unsigned) how not to match a sub-subdomain

Hello everyone, will ".domain.com" match "b...@sub2.sub1.domain.com" or only "b...@sub1.domain.com" in transport maps? "parent_domain_matches_subdomains" is not set and I don't want it to match all subdomains on all levels. Best Marc