Loading ...
Sorry, an error occurred while loading the content.
 

Re: virtual file

Expand Messages
  • admin2
    ... okay this is not really Addressing the issue. the domains/hostnames are not specific to mailman and are already in the main.cf mydestination and
    Message 1 of 4 , May 30, 2009
      Wietse Venema wrote:
      > Victor Duchovni:
      >> On Fri, May 29, 2009 at 04:45:34PM -0700, admin2 wrote:
      >>
      >>> I have a question about changing the default behavior of postfix. As
      >>> current configuration stands I need to add a mailman maillist hosted by
      >>> virtual hosts/domains I need to add the to list entries to the /var/lib/
      >>> mailman/data/aliases file and also the /etc/postfix/virtual file
      >
      > You could eliminate the intermediate virtual-alias step and list
      > the mailman domains in "mydestination", and the mailman aliases
      > file in "alias_maps"
      >
      > mydestination = $myhostname localhost.$mydomain lists.$mydomain
      > alias_maps = hash:/var/lib/mailman/data/aliases
      >
      > But this has the minor drawback that UNIX system accounts can
      > receive mail as user@lists.$mydomain.



      okay this is not really Addressing the issue. the domains/hostnames are
      not specific to mailman and are already in the main.cf mydestination and
      alias_maps configurations.


      >
      >>> Is there any way to get postfix to deliver mail to a virutal domain/hosted
      >>> email, such as a mailman maillist, if it is found in the /var/lib/
      >>> mailman/data/aliases file but does not appear in the /etc/postfix/virtual
      >>> file?
      >
      > If I'm not mistake, the mailman aliases file does not specify the
      > email domain, so the email domain would need to be specified in
      > some other way.
      >
      > If Postfix implemented automatic discovery via the file system,
      > the directory tree could look like this:
      >
      > Use local(8)-style alias (not username) lookup for lists.example.com:
      >
      > /etc/postfix/domains/lists.example.com/class -> local
      > /etc/postfix/domains/lists.example.com/aliases.db
      >
      > Use virtual alias expansion for another.example.com:
      >
      > /etc/postfix/domains/another.example.com/class -> virtual_alias
      > /etc/postfix/domains/another.example.com/aliases.db
      >
      > /etc/postfix/domains/athird.example.com/class -> virtual_alias
      > /etc/postfix/domains/athird.example.com/aliases.mysql
      >
      > Use local(8)-style username and alias lookup for myname.example.com,
      > example.com and localhost.example.com:
      >
      > /etc/postfix/domains/myname.example.com/class -> local
      > /etc/postfix/domains/myname.example.com/users -> passwd
      > /etc/postfix/domains/myname.example.com/aliases -> aliases.db, aliases.ldap
      > /etc/postfix/domains/myname.example.com/aliases.db
      > /etc/postfix/domains/myname.example.com/aliases.ldap
      >
      > /etc/postfix/domains/localhost.example.com -> myname.example.com
      > /etc/postfix/domains/example.com -> myname.example.com
      >
      > Relay mail for the following:
      >
      > /etc/postfix/domains/one.example.org/class -> relay
      > /etc/postfix/domains/one.example.org/recipients.db
      >
      > /etc/postfix/domains/two.example.org/class -> relay
      > /etc/postfix/domains/two.example.org/recipients.db
      >
      > I suppose that all this could be hidden under a sufficiently powerful
      > lookup table API: to find out the address class of localhost.example.com,
      > search the tree for each address class for the named domain; to
      > look up an alias for localhost.example.com, discover and search
      > the aliases.* files under domains/localhost.example.com.


      okay thanks



      >
      > Wietse
    Your message has been successfully submitted and would be delivered to recipients shortly.