OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Rahul Dhesi (dhesi_at_rahul.net)
Date: Sun Nov 03 2002 - 16:17:16 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Thu, Oct 31, 2002 at 08:08:48AM -0500, Wietse Venema wrote:

    [ on the question of delivering all mail for a domain and its
    subdomains to a mailbox ]

    > > # virtual table
    > > # deliver example.com and all subdomains to joeuser
    > > example.com joeuser
    > > .example.com joeuser
    > >
    > > I tried using this, and I don't think does a table lookup
    > > for .example.com.
    >
    > This is an omission in the design of the transport table. You need
    > the ability to specify the recipient address on the right-hand
    > side. The closest thing I can come up with that can still be
    > implemented reliably would be:
    >
    > some.domain.tld [transport]:[nexthop]:[recipient]

    I might be betraying my ignorance of Postfix's inner working here, but
    couldn't Postfix simply do a lookup for .example.com in the virtual
    table? For domains containing many components separated by dots, this
    could lead to many table look-ups. If this were a problem then a
    configuration variable could be used to limit this:

      # do virtual table look-up for .example.com (has 2 dots) and
      # .xyz.example.com (has 3 dots), but not for
      # .com (has 1 dot) or .abc.xyz.example.com (has 4 dots).
      virtual_subdomain_dot_range = 2 .. 3

    Another possibility is for the magic entry in the virtual table
    to specify what additional lookups are needed for a domain. Then
    after doing a lookup for example.com we know whether we need to
    do a lookup for .example.com, .<subdomain>.example.com, etc.

    Rahul
    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users