Thanks, Steve, hopefully that will work. Short of using a smarthost, which I can do, how do other people configure mailservers so that they deliver internal mail internally and can relay to external MTA's also? I know most mail servers are not so anal about reverse lookups, so my setup will generally work, but I want to have it perfect if possible.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Cowles, Steve Sent: Wednesday, February 05, 2003 6:16 PM To: '[EMAIL PROTECTED]' Subject: RE: Mail is refused due to domain > -----Original Message----- > From: Chris Mason > Sent: Wednesday, February 05, 2003 3:42 PM > Subject: RE: Mail is refused due to domain > > > Of course it can't talk to the nameserver, it's a > non-existant domain behind a firewall. > > The question is, why does it want to? Why doesn't the mail > server present itself as a company.ocm as that's the masquerade? > > Masquerading an e-mail envelope vs. the EHLO negotiation between the MTA's are two different things. Sendmail (like most mta's) is going to make a call to the resolver libs to determine the FQDN (canonical domain name) of the host its running on at startup. It's this name that is used during the EHLO negotiation with the remote MTA. IF the masq'd canonical domain name is not resolvable by the external MTA's resolver libs, then (if configured) the remote MTA could reject your e-mail. With the above in mind, try adding the following to your sendmail.mc file. Change mail.mydomain.com to a resolvable FQDN. i.e. a FQDN that resolves from an external source. define(`confDOMAIN_NAME', `mail.mydomain.com')dnl Steve Cowles -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
