On Sat, 2006-06-24 at 07:55, Steve Campbell wrote: > I configured sendmail using mostly domains as the criteria for everything. As > you both know, there are quite a few different ways of setting up sendmail to > recognize who is local, what should be relayed, how to define the path for the > relay to the next server, etc. So in my case, if email comes in to the primary > MX for a domain, it knows by the domain name, that it should use the local > delivery to the mailbox. If mail arrives on the backup MX, it knows it should > relay it, and where to relay it, because of the domain the mail is addressed > to.
If the user turnover isn't huge or you can script it, there is yet another approach that might work. On the secondary, use virtusertable with entries like: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] @domain1 error:nouser No such user here That gives basically the same effect as using the access file with a default deny, but is more flexible if you want to forward some mail to different locations. > These servers are pretty hefty, and are rarely down. My load problems are > mostly > due to the buildup sendmail process of non-deliverable mail, not delivery of > real mail. I wonder if you really have some other problem, like internal machines sending viruses or spam. If you just shut down your secondary so the primary doesn't have to generate undeliverable bounces for unknown users most of this should go away. There really isn't that much value in having a second MX anyway if you aren't down a lot. The sending mailers will queue and retry anyway. -- Les Mikesell [EMAIL PROTECTED] _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
