Subject: sendmail domain configuration as Message 9

Wed Sep 1 14:56:53 UTC 2010

John:
	Yes I tried that. The problem is when my system connects to the ISP mail server it send the hostname. Even if the host name is simple the system domain is added and that is what the ISP mail server uses to validate.

-----
Jack Allen

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of John Wong
Sent: Wednesday, September 01, 2010 1:47 AM
To: redhat-list at redhat.com
Subject: RE: Subject: sendmail domain configuration as Message 9

Allen,

You said you have tried various masquerade but have you tried masqyerade as suggested by Greg?

MASQUERADE_AS(`my_domain.net')dnl

Just curious.

jw

Message: 1
Date: Mon, 30 Aug 2010 12:53:58 -0400
From: "Allen, Jack" <Jack.Allen at mckesson.com>
To: General Red Hat Linux discussion list <redhat-list at redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
    <230ED15F81AFD3409345FFA4E565F0E50D3F16A0 at NDHV3000.na.corp.mckesson.com>

Content-Type: text/plain;    charset="iso-8859-1"

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list at redhat.com
Cc: j w
Subject: Re: Subject: sendmail domain configuration as Message 9

Hi Allen,
?
I believe you need to ask your ISP to add a DNS MX record for system.house.network.
?
Why don't you just change house.network to one of your registered domain? The reason it work is because BigDaddy.com created DNS MX records for those domains.
?
Hope it will help.
?
jw

------------------------------

Message: 9
Date: Thu, 26 Aug 2010 19:01:16 -0400
From: "Allen, Jack" <Jack.Allen at mckesson.com>
To: General Red Hat Linux discussion list <redhat-list at redhat.com>
Subject: sendmail domain configuration
Message-ID:
??? <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1 at NDHV3000.na.corp.mckesson.com>
??? 
Content-Type: text/plain;??? charset="us-ascii"

Hello:

? ? ? ? I need to know exactly what options need to be specified in
sendmail.mc to generate the proper sendmail.cf file so the domain name
my ISP sees is valid.

? ? ? ? Here is some information why this is needed. I have 2 Windows PC
and 1 Linux systems and several Home Automation, NAS, Media systems on a
home network. I have named running on the Linux system for a local
fictional domain called "house.network". I know network is longer than
the normal 3 character .com, .net, ..., but it works with no problems as
far as name lookup and what have you. I also chose the longer name so
there would be no conflict with a real domain name out in the real world
and thing on my local network would not get routed to it. I have some of
the special systems send email to the Linux system which then has
aliases to send certain emails to my ISP email and/or my work email.
This is where the problem starts.

? ? ? ? If the Linux host name is set to system. house.network, then
when it connects to the ISP I get error 550 Invalid sender domain. This
is because the domain cannot be looked up by the ISP and I can
understand why. If I set the Linux host name to system.my_domain.net it
works like it should. I registered 2 real domain names (my_domain.com
and my_domain.net) with BigDaddy.com partly for this. But when the Linux
host name is not in the same domain as the other systems on my local
network it cause some other problem.

? ? ? ? If I add the option in sendmail.mc to generate a sendmail.cf
file with Djmy_domain.net and have the Linux host name set to
system.house.network the ISP complains with basically the same 550
error. Looking at the returned email some of the header information
looks like:

Reporting-MTA: dns; my_domain.net

Received-From-MTA: DNS; system.house.network

Which indicates to me the value of the host name is what my ISP sees
that it tries to validate. I have looked at and tried various
configurations for masquerading, but have the same problem. It seems to
rewrite certain header entries that basically the user's client software
look at to display from and to and what have you, but does not change
the Received-From-MTA entry.

? ? ? ? So I hope someone has some good suggestions to help me resolve
this problem.

-----

Jack Allen
============

Thanks for the reply, but my ISP is NOT going to add anything to their DNS for my system. I am just one hundreds of thousands that get a dynamic IP address from them. The point of my question is to find suggestions on how to configure sendmail to work with an ISP that is not going to change anything, but validates the systems that connects to them to relay email. This is done to eliminate SPAMER.

-----
Jack Allen

Message: 2
Date: Mon, 30 Aug 2010 15:19:32 -0500
From: Greg_Wilson at aotx.uscourts.gov
To: General Red Hat Linux discussion list <redhat-list at redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
    <OFDDBC7785.AEB64B49-ON8625778F.006F4DB9-8625778F.006FA72A at uscmail.uscourts.gov>

Content-Type: text/plain; charset=ISO-8859-1

MASQUERADE_AS(`my_domain.net')dnl

Greg Wilson
Information Technology Specialist
Systems Deployment and Support Division

From:       "Allen, Jack" <Jack.Allen at mckesson.com>
To:         General Red Hat Linux discussion list <redhat-list at redhat.com>
Date:       08/30/2010 11:59 AM
Subject:    RE: Subject: sendmail domain configuration as Message 9
Sent by:    redhat-list-bounces at redhat.com

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list at redhat.com
Cc: j w
Subject: Re: Subject: sendmail domain configuration as Message 9

Hi Allen,

I believe you need to ask your ISP to add a DNS MX record for
system.house.network.

Why don't you just change house.network to one of your registered domain?
The reason it work is because BigDaddy.com created DNS MX records for those
domains.

Hope it will help.

jw

------------------------------

Message: 9
Date: Thu, 26 Aug 2010 19:01:16 -0400
From: "Allen, Jack" <Jack.Allen at mckesson.com>
To: General Red Hat Linux discussion list <redhat-list at redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1 at NDHV3000.na.corp.mckesson.com>

Content-Type: text/plain;??? charset="us-ascii"

Hello:

? ? ? ? I need to know exactly what options need to be specified in
sendmail.mc to generate the proper sendmail.cf file so the domain name
my ISP sees is valid.

? ? ? ? Here is some information why this is needed. I have 2 Windows PC
and 1 Linux systems and several Home Automation, NAS, Media systems on a
home network. I have named running on the Linux system for a local
fictional domain called "house.network". I know network is longer than
the normal 3 character .com, .net, ..., but it works with no problems as
far as name lookup and what have you. I also chose the longer name so
there would be no conflict with a real domain name out in the real world
and thing on my local network would not get routed to it. I have some of
the special systems send email to the Linux system which then has
aliases to send certain emails to my ISP email and/or my work email.
This is where the problem starts.

? ? ? ? If the Linux host name is set to system. house.network, then
when it connects to the ISP I get error 550 Invalid sender domain. This
is because the domain cannot be looked up by the ISP and I can
understand why. If I set the Linux host name to system.my_domain.net it
works like it should. I registered 2 real domain names (my_domain.com
and my_domain.net) with BigDaddy.com partly for this. But when the Linux
host name is not in the same domain as the other systems on my local
network it cause some other problem.

? ? ? ? If I add the option in sendmail.mc to generate a sendmail.cf
file with Djmy_domain.net and have the Linux host name set to
system.house.network the ISP complains with basically the same 550
error. Looking at the returned email some of the header information
looks like:

Reporting-MTA: dns; my_domain.net

Received-From-MTA: DNS; system.house.network

Which indicates to me the value of the host name is what my ISP sees
that it tries to validate. I have looked at and tried various
configurations for masquerading, but have the same problem. It seems to
rewrite certain header entries that basically the user's client software
look at to display from and to and what have you, but does not change
the Received-From-MTA entry.

? ? ? ? So I hope someone has some good suggestions to help me resolve
this problem.

-----

Jack Allen
============

Thanks for the reply, but my ISP is NOT going to add anything to their DNS
for my system. I am just one hundreds of thousands that get a dynamic IP
address from them. The point of my question is to find suggestions on how
to configure sendmail to work with an ISP that is not going to change
anything, but validates the systems that connects to them to relay email.
This is done to eliminate SPAMER.

-----
Jack Allen

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of Greg_Wilson at aotx.uscourts.gov
Sent: Monday, August 30, 2010 4:20 PM
To: General Red Hat Linux discussion list
Subject: RE: Subject: sendmail domain configuration as Message 9

MASQUERADE_AS(`my_domain.net')dnl

Greg Wilson
Information Technology Specialist
Systems Deployment and Support Division

From:       "Allen, Jack" <Jack.Allen at mckesson.com>
To:         General Red Hat Linux discussion list <redhat-list at redhat.com>
Date:       08/30/2010 11:59 AM
Subject:    RE: Subject: sendmail domain configuration as Message 9
Sent by:    redhat-list-bounces at redhat.com

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list at redhat.com
Cc: j w
Subject: Re: Subject: sendmail domain configuration as Message 9

Hi Allen,

I believe you need to ask your ISP to add a DNS MX record for
system.house.network.

Why don't you just change house.network to one of your registered domain?
The reason it work is because BigDaddy.com created DNS MX records for those
domains.

Hope it will help.

jw