Re: Cascading qmail servers

From: Barney Wolff (barney_at_databus.com)
Date: 05/29/03

  • Next message: Sreekanth: "RE: gratuitous ARP with em interface." 
    Date: Thu, 29 May 2003 13:24:57 -0400
To: Wes Peters <wes@softweyr.com>

    On Thu, May 29, 2003 at 12:14:34AM -0700, Wes Peters wrote:
    > On Wednesday 28 May 2003 08:00 am, Barney Wolff wrote:
    > > On Wed, May 28, 2003 at 07:45:10AM -0700, Wes Peters wrote:
    > > > > Don't assume that you can't create an alias for each user. When I
    > > > > worked at a very large NY bank, with well over 100,000 employees,
    > > > > /etc/mail/aliases was that big, and sendmail worked just fine.
    > > >
    > > > In sendmail, you can do domain routing with mailertable. I think you
    > > > can do the same in Postfix with relay_domains.
    > >
    > > The question I thought I was answering was how to make the address
    > > <Barney.Wolff@motherofallbanks.com>
    > > route to my actual account,
    > > <Barney.Wolff@dept9876.motherofallbanks.com>.
    > >
    > > If external correspondents use the sub-domains the problem is easier,
    > > but employees in large orgs move around so often it's impractical.
    >
    > It's also impractical to deliver copies of every message to each of the
    > various offices, leaving thousands and thousands of unread messages for
    > the employees that don't work in each office.
    >
    > This is where directory technologies like LDAP come into play, when you
    > have large user bases. I think this has strayed pretty far from the
    > question that was asked, though, which seemed to me to be a 'mail
    > gateway' attached to the internet at the company HQ that would route to
    > ~3 internal mail servers, delivering the correct accounts to each one.
    > Wasn't that the original question?

    You can try a fancy solution with LDAP, yes. Or you can just have an
    /etc/mail/aliases with a line for each employee. All I'm saying is
    that this simpleminded solution actually worked, even for one of the
    largest corps in the world. Of course the alias file was not hand-edited,
    but derived from the HR database, daily. 

    -- 
Barney Wolff         http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Sreekanth: "RE: gratuitous ARP with em interface."

    Relevant Pages

    • Re: too complex for me!
      ... My report query is pulling data from the 'Time', ... 'Employees' and 'Accounts' tables. ... The idea, I guess, is to sum up the LaborHours from each account and show ...
      (microsoft.public.access.reports)
    • Re: echange email
      ... we have an e-mail acount hosted by an isp. ... The acount is a pop 3 account and ... all 4 employees to see the incoming and out going mails ...
      (microsoft.public.windows.server.sbs)
    • Re: Relational model versus object model
      ... That subsystem has a pure data ... With a pure data transfer interface all you need is some shared ... So, we can traverse the list, selecting employees by the joined ... >> Address, Account ID, ...}. ...
      (comp.object)
    • Re: How to secure the Administrator account?
      ... >>Administrator Account: We regularly rename and place strong passwords ... >>company and never to the normal "administrator" of the network. ... > 1) As you pointed out, your employees have to have system authority ...
      (microsoft.public.win2000.security)
    • Re: Computer accounts unused for more than 120 days
      ... the HR department notifies IT when an employee leaves so ... > that we can disable their account. ... > times I have had employees delete what they considered to be unimportant ... > recover any lost data in the event that the user did as I mentioned ...
      (microsoft.public.win2000.active_directory)