[100438] in RedHat Linux List
Re: MX secondary, dns and sendmail - what's wrong?
daemon@ATHENA.MIT.EDU (Aaron Holtz)
Fri Nov 20 14:27:42 1998
Date: Fri, 20 Nov 1998 14:25:22 -0500 (EST)
From: Aaron Holtz <aholtz@bright.net>
To: Drew Mouton <drew@etool.com>
cc: Red Hat List <redhat-list@redhat.com>
In-Reply-To: <B0000007301@redwood.etool.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Drew,
There are a few avenues of approach. If you want a machine to be
able to relay certain domains and not others, see using the /etc/access
file. You can put an entry in there like:
domain.com RELAY
This will allow relaying for this domain. However, as long as the
anti-relay rulesets are turned on, you'll deny relay to other domains.
You can also look at using /etc/mailertable. The mailertable will show
how to route mail for a particular domain:
domain.com smtp:10mx.host.net
Remember, when sendmail fires up, it probes all local interfaces to see
who it is know as. So if you have virtual IP's running on a box, sendmail
will think it is supposed to accept mail for that domain. You can get
around this using the mailertables as above, or use the following in
/etc/sendmail.cf:
O DontProbeInterfaces
Restart sendmail and it won't look for those IP's. Not sure if I've
offered any help, but let me know if I can expand further.
--------------------------------------------------------------------------
Aaron Holtz
ComNet Inc.
Manager, Unix Systems Administration
Email: aholtz@bright.net
"I'd give my right arm to be ambidextrous."
--------------------------------------------------------------------------
On Fri, 20 Nov 1998, Drew Mouton wrote:
>Lemme see if I can fill in some blanks, and maybe that'll spark an idea.
>
>it appears that around 11/20/98 11:28 AM, Godfrey Nix said:
>
>>Yeah, I fully sympathise. I was messed about by a previous supplier myself.
>>
>>If you have many sub-domains, not just a single domain, then you will
>>be using a file called sendmail.cw
>
>[snip]
>>> Two probs: in the cases where I have a user "Drew" on both serverA AND
>>> serverB, I'm getting some mail delivered locally on serverB (when it
>>> should be forwarded to serverA). Other messages seem to be getting lost
>>> altogether.
>>>
>>> Secondly, some of our domains are being refused altogether by serverB,
>>> when they should be forwarded to serverA for local delivery.
>
>Right - but let me clarify. Rem that I have two sendmail servers (A and
>B), with dns like this (expanded to show relation of other domains I'm
>hosting):
>
>mydomain.com IN MX 10 serverA.mydomain.com;
>mydomain.com IN MX 20 serverB.mydomain.com;
>yourdomain.com IN MX 10 serverA.mydomain.com;
>yourdomain.com IN MX 20 serverB.mydomain.com;
>
>If I take out all the references to serverB, then everything works fine -
>which indicates that my sendmail.cw is set up correctly for serverA...and
>sendmail.cw for serverB should only have an entry for
>serverB.mydomain.com, because it's only allowed to accept mail for itself
>(right?).
>
>Both serverA and serverB have a pretty simple alias setup - in other
>words, very few. I don't think aliasing is the problem because I've
>checked pretty closely.
>
>My guess is that I have two problems - one that causes some mail to be
>handled locally on serverB, and another problem that's causing serverB to
>bounce domains that we handle, rather than simply relaying to serverA for
>local delivery.
>
>Let me start here: can somebody confirm how you setup sendmail to relay
>some domains (the domains we host), but to refuse to relay others?
>
>
>Thx,
>
>Drew
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
