FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Red Hat Linux

 
 
LinkBack Thread Tools
 
Old 08-29-2010, 07:10 AM
John Wong
 
Default 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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:
*** <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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

*******



*



--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 08-30-2010, 04:53 PM
"Allen, Jack"
 
Default Subject: sendmail domain configuration as Message 9

-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:
*** <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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

*******



*



--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 08-30-2010, 08:19 PM
 
Default 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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Date: 08/30/2010 11:59 AM
Subject: RE: Subject: sendmail domain configuration as Message 9
Sent by: redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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









--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 08-30-2010, 08:39 PM
"Allen, Jack"
 
Default Subject: sendmail domain configuration as Message 9

Look at the end.


-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of Greg_Wilson@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Date: 08/30/2010 11:59 AM
Subject: RE: Subject: sendmail domain configuration as Message 9
Sent by: redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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

=========
Thanks for the reply.

I have already tried that and it does not work. When my system connects to the Comcast email server is tells it it's real name and the masqueraded name. Comcast tries to look up the real name which it cannot find and then refuses to relay the email. It returns the email stating it is an invalid domain.

-----
Jack Allen

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 05:46 AM
John Wong
 
Default 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
*

--- On Tue, 8/31/10, redhat-list-request@redhat.com <redhat-list-request@redhat.com> wrote:


From: redhat-list-request@redhat.com <redhat-list-request@redhat.com>
Subject: redhat-list Digest, Vol 78, Issue 27
To: redhat-list@redhat.com
Date: Tuesday, August 31, 2010, 9:00 AM


Send redhat-list mailing list submissions to
*** redhat-list@redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
*** https://www.redhat.com/mailman/listinfo/redhat-list
or, via email, send a message with subject or body 'help' to
*** redhat-list-request@redhat.com

You can reach the person managing the list at
*** redhat-list-owner@redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of redhat-list digest..."


Today's Topics:

***1. RE: Subject: sendmail domain configuration as Message 9
* * * (Allen, Jack)
***2. RE: Subject: sendmail domain configuration as Message 9
* * * (Greg_Wilson@aotx.uscourts.gov)
***3. RE: Subject: sendmail domain configuration as Message 9
* * * (Allen, Jack)
***4. too many nfs error messages (ESGLinux)
***5. Re: too many nfs error messages (Dustin Larmeir)


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

Message: 1
Date: Mon, 30 Aug 2010 12:53:58 -0400
From: "Allen, Jack" <Jack.Allen@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
*** <230ED15F81AFD3409345FFA4E565F0E50D3F16A0@NDHV3000 .na.corp.mckesson.com>
***
Content-Type: text/plain;*** charset="iso-8859-1"

-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:
??? <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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

???????



?


* * *
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



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

Message: 2
Date: Mon, 30 Aug 2010 15:19:32 -0500
From: Greg_Wilson@aotx.uscourts.gov
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
*** <OFDDBC7785.AEB64B49-ON8625778F.006F4DB9-8625778F.006FA72A@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@mckesson.com>
To:* * * ***General Red Hat Linux discussion list <redhat-list@redhat.com>
Date:* * ***08/30/2010 11:59 AM
Subject:* * RE: Subject: sendmail domain configuration as Message 9
Sent by:* * redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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









--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list





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

Message: 3
Date: Mon, 30 Aug 2010 16:39:33 -0400
From: "Allen, Jack" <Jack.Allen@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
*** <230ED15F81AFD3409345FFA4E565F0E50D3F1F70@NDHV3000 .na.corp.mckesson.com>
***
Content-Type: text/plain;*** charset="iso-8859-1"

Look at the end.


-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of Greg_Wilson@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@mckesson.com>
To:* * * ***General Red Hat Linux discussion list <redhat-list@redhat.com>
Date:* * ***08/30/2010 11:59 AM
Subject:* * RE: Subject: sendmail domain configuration as Message 9
Sent by:* * redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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

=========
Thanks for the reply.

I have already tried that and it does not work. When my system connects to the Comcast email server is tells it it's real name and the masqueraded name. Comcast tries to look up the real name which it cannot find and then refuses to relay the email. It returns the email stating it is an invalid domain.

-----
Jack Allen



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

Message: 4
Date: Tue, 31 Aug 2010 09:07:38 +0200
From: ESGLinux <esggrupos@gmail.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: too many nfs error messages
Message-ID:
*** <AANLkTiniqUk6atcw-78FVaM_SkC2GeqRrgML77RtAvxa@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I have a nfs server that I use to store my backups and in the client machine
I get a lot of messages like these:

Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding,
still trying
Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding,
still trying
Aug 31 09:03:48 SERVER kernel: nfs: server 192.168.1.111 not responding,
still trying
Aug 31 09:03:51 SERVER kernel: nfs: server 192.168.1.111 OK

I have mounted the export this way:

192.168.1.111:/nas/NASDisk-00002/share on /backup type nfs
(rw,noatime,noacl,rsize=8192,wsize=8192,hard,timeo =10,intr,addr=192.168.1.111)

which can be the problem? Is there any problem with de mount options?

I have tried with the soft option but with this option the server gives the
error and the backup process stops. (which is worse)

any idea?

Thank in advance

ESG


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

Message: 5
Date: Tue, 31 Aug 2010 07:02:28 -0500
From: Dustin Larmeir <dustin@larmeir.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: Re: too many nfs error messages
Message-ID:
*** <AANLkTikiK6YpdGLuZPv=aGrKeUHXxBtP-uOkpWjJpTbG@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

ESG,

That message simply implies that the client is unable to reach the NFS
server for some reason. This could be because of a network issue or a issue
on the NFS server side. What do the logs show on the server side? Also, it
may be useful to check this in realtime when the issue occurs from both the
client and the server to get a better assessment of the issue. - Dustin

On Tue, Aug 31, 2010 at 2:07 AM, ESGLinux <esggrupos@gmail.com> wrote:

> Hi all,
>
> I have a nfs server that I use to store my backups and in the client
> machine
> I get a lot of messages like these:
>
> Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding,
> still trying
> Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding,
> still trying
> Aug 31 09:03:48 SERVER kernel: nfs: server 192.168.1.111 not responding,
> still trying
> Aug 31 09:03:51 SERVER kernel: nfs: server 192.168.1.111 OK
>
> I have mounted the export this way:
>
> 192.168.1.111:/nas/NASDisk-00002/share on /backup type nfs
>
> (rw,noatime,noacl,rsize=8192,wsize=8192,hard,timeo =10,intr,addr=192.168.1.111)
>
> which can be the problem? Is there any problem with de mount options?
>
> I have tried with the soft option but with this option the server gives the
> error and the backup process stops. (which is worse)
>
> any idea?
>
> Thank in advance
>
> ESG
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>


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

__
redhat-list mailing list
Unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

End of redhat-list Digest, Vol 78, Issue 27
*******************************************




--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 02:56 PM
"Allen, Jack"
 
Default Subject: sendmail domain configuration as Message 9

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@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of John Wong
Sent: Wednesday, September 01, 2010 1:47 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
*** <230ED15F81AFD3409345FFA4E565F0E50D3F16A0@NDHV3000 .na.corp.mckesson.com>
***
Content-Type: text/plain;*** charset="iso-8859-1"

-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:
??? <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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@aotx.uscourts.gov
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: RE: Subject: sendmail domain configuration as Message 9
Message-ID:
*** <OFDDBC7785.AEB64B49-ON8625778F.006F4DB9-8625778F.006FA72A@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@mckesson.com>
To:* * * ***General Red Hat Linux discussion list <redhat-list@redhat.com>
Date:* * ***08/30/2010 11:59 AM
Subject:* * RE: Subject: sendmail domain configuration as Message 9
Sent by:* * redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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@mckesson.com>
To: General Red Hat Linux discussion list <redhat-list@redhat.com>
Subject: sendmail domain configuration
Message-ID:

<230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@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@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of Greg_Wilson@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@mckesson.com>
To:* * * ***General Red Hat Linux discussion list <redhat-list@redhat.com>
Date:* * ***08/30/2010 11:59 AM
Subject:* * RE: Subject: sendmail domain configuration as Message 9
Sent by:* * redhat-list-bounces@redhat.com



-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com
] On Behalf Of John Wong
Sent: Sunday, August 29, 2010 3:11 AM
To: redhat-list@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

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 05:11 PM
 
Default Subject: sendmail domain configuration as Message 9

Allen, Jack wrote:
> 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.

Are you supposed to be getting a hostname from the ISP?

mark

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 05:38 PM
"Allen, Jack"
 
Default Subject: sendmail domain configuration as Message 9

Allen, Jack wrote:
> 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.

Are you supposed to be getting a hostname from the ISP?

mark

=========

No, my ISP does not provide a hostname.

Maybe I did not explain the problem clearly. I have a cable
modem connected to a router. The ISP provides an IP Address to the
router via DHCP. That would be on the WAN side of the router. On the LAN
side of the router I am using 10.11.12.X for my systems. The router is
10.11.12.254 and my Linux system is 10.11.12.1 and the PCs are
10.11.12.2 and 10.11.12.3 and the home automation device is 10.11.12.4
and TIVO is 10.11.12.5. I have DNS (named) running on my Linux system
with the domain name of my_domain.network. The Linux system is setup to
relay email to the ISP. When the Linux system connects to the ISP mail
servers it tells it the connection is from linux.my_domain.network which
is validated and determined not to be a valid domain, which it is not. I
want the ISP mail server to see the connection form linux.my_domain.net
which is a valid registered domain. But using masquerading is not doing
that.

I have looked at the sendmail source and when it first starts it
get the hostname and assigns the value to $k. There does not seem to be
anything that changes that value when doing masquerading and the value
of $k is what is sent to the ISP mail server as the domain.

-----
Jack Allen

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 05:51 PM
 
Default Subject: sendmail domain configuration as Message 9

Allen, Jack wrote:
<snip>
> No, my ISP does not provide a hostname.
>
> Maybe I did not explain the problem clearly. I have a cable
> modem connected to a router. The ISP provides an IP Address to the
> router via DHCP. That would be on the WAN side of the router. On the LAN
> side of the router I am using 10.11.12.X for my systems. The router is
> 10.11.12.254 and my Linux system is 10.11.12.1 and the PCs are
> 10.11.12.2 and 10.11.12.3 and the home automation device is 10.11.12.4
> and TIVO is 10.11.12.5. I have DNS (named) running on my Linux system
> with the domain name of my_domain.network. The Linux system is setup to
> relay email to the ISP. When the Linux system connects to the ISP mail
> servers it tells it the connection is from linux.my_domain.network which
> is validated and determined not to be a valid domain, which it is not. I
> want the ISP mail server to see the connection form linux.my_domain.net
> which is a valid registered domain. But using masquerading is not doing
> that.

Hmmm, is it complaining about the domain, or about the server's fully
qualified name, and complaining the server's unknown?
<snip>
mark

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 
Old 09-01-2010, 06:17 PM
"Allen, Jack"
 
Default Subject: sendmail domain configuration as Message 9

Allen, Jack wrote:
<snip>
> No, my ISP does not provide a hostname.
>
> Maybe I did not explain the problem clearly. I have a cable
> modem connected to a router. The ISP provides an IP Address to the
> router via DHCP. That would be on the WAN side of the router. On the
LAN
> side of the router I am using 10.11.12.X for my systems. The router is
> 10.11.12.254 and my Linux system is 10.11.12.1 and the PCs are
> 10.11.12.2 and 10.11.12.3 and the home automation device is 10.11.12.4
> and TIVO is 10.11.12.5. I have DNS (named) running on my Linux system
> with the domain name of my_domain.network. The Linux system is setup
to
> relay email to the ISP. When the Linux system connects to the ISP mail
> servers it tells it the connection is from linux.my_domain.network
which
> is validated and determined not to be a valid domain, which it is not.
I
> want the ISP mail server to see the connection form
linux.my_domain.net
> which is a valid registered domain. But using masquerading is not
doing
> that.

Hmmm, is it complaining about the domain, or about the server's fully
qualified name, and complaining the server's unknown?
<snip>
mark

=====
It is complaining about the domain name, see my original post. It shows
what that masquerading stated one domain, but the sendmail also send the
real domain of the system based on the host name and this is what the
ISP mail server validates.

-----
Jack Allen

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
 

Thread Tools




All times are GMT. The time now is 02:45 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org