get local sendmail to use MX records

[Gerard Meijer]

I really don't understand it at all now.

When I run sendmail in test mode (sendmail -bt) and I do:

3,0 something at domain.com, I get:

canonify           input: something @ domain . com
Canonify2          input: something < @ domain . com >
Canonify2        returns: something < @ domain . com . >
canonify         returns: something < @ domain . com . >
parse              input: something < @ domain . com . >
Parse0             input: something < @ domain . com . >
Parse0           returns: something < @ domain . com . >
ParseLocal         input: something < @ domain . com . >
ParseLocal       returns: something < @ domain . com . >
Parse1             input: something < @ domain . com . >
Parse1           returns: $# local $: something
parse            returns: $# local $: something

So obviously sendmail thinks it should handle the mail. Strange thing is 
that I have 6 domains hosted on this server and I get this outcome by two of 
them. One is the domain I'm talking about and the other one is 
something at machine.domainB.com. something at domainB.com works as it should work 
and goes to the other server.

I emptied my virtusertable and local-host-names files. I really don't know 
why this happens.
----- Original Message ----- 
From: "Greg Barniskis" <nalists at scls.lib.wi.us>
To: "Gerard Meijer" <gmeijer at palmweb.nl>
Cc: <freebsd-questions at freebsd.org>
Sent: Wednesday, February 23, 2005 8:09 PM
Subject: Re: get local sendmail to use MX records


> Gerard Meijer wrote:
>> Hi Greg,
>>
>> I'm absolutely sure that this is not the case anymore. I removed 
>> everything.
> ...
>>> If I followed you correctly, "server B" *formerly* was the appropriate 
>>> end point for mail for "domain.com". If that is true, then on server B, 
>>> the sendmail config probably indicates that mail destined for domain.com 
>>> is delivered locally. Remove that indicator and it should revert to MX 
>>> lookup behavior to find the appropriate handler for the domain. There 
>>> may be multiple places in the sendmail config where domain.com is named 
>>> for different purposes. Hunt them all down and kill them.
>
> Nevertheless... the grep suggested by another poster seems completely 
> appropriate. There are few other explanations than "sendmail config 
> error". You restarted sendmail after the config change, right?
>
> Another test you could try would be to fire up nslookup on server B's 
> command line. If you ask there for the MX record in question, do you 
> actually get the right answer?
>
>
> -- 
> Greg Barniskis, Computer Systems Integrator
> South Central Library System (SCLS)
> Library Interchange Network (LINK)
> <gregb at scls.lib.wi.us>, (608) 266-6348
>
> A: Because it reverses the natural flow of a dialog.
> Q: Why is top posting undesirable when replying?
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"
>
>