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@xxxxxxxxxx <redhat-list-request@xxxxxxxxxx> wrote: From: redhat-list-request@xxxxxxxxxx <redhat-list-request@xxxxxxxxxx> Subject: redhat-list Digest, Vol 78, Issue 27 To: redhat-list@xxxxxxxxxx Date: Tuesday, August 31, 2010, 9:00 AM Send redhat-list mailing list submissions to redhat-list@xxxxxxxxxx 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@xxxxxxxxxx You can reach the person managing the list at redhat-list-owner@xxxxxxxxxx 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@xxxxxxxxxxxxxxxxx) 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: RE: Subject: sendmail domain configuration as Message 9 Message-ID: <230ED15F81AFD3409345FFA4E565F0E50D3F16A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of John Wong Sent: Sunday, August 29, 2010 3:11 AM To: redhat-list@xxxxxxxxxx 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: sendmail domain configuration Message-ID: ??? <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> ??? 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@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ------------------------------ Message: 2 Date: Mon, 30 Aug 2010 15:19:32 -0500 From: Greg_Wilson@xxxxxxxxxxxxxxxxx To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: RE: Subject: sendmail domain configuration as Message 9 Message-ID: <OFDDBC7785.AEB64B49-ON8625778F.006F4DB9-8625778F.006FA72A@xxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Date: 08/30/2010 11:59 AM Subject: RE: Subject: sendmail domain configuration as Message 9 Sent by: redhat-list-bounces@xxxxxxxxxx -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx ] On Behalf Of John Wong Sent: Sunday, August 29, 2010 3:11 AM To: redhat-list@xxxxxxxxxx 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: sendmail domain configuration Message-ID: <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: RE: Subject: sendmail domain configuration as Message 9 Message-ID: <230ED15F81AFD3409345FFA4E565F0E50D3F1F70@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Look at the end. -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Greg_Wilson@xxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Date: 08/30/2010 11:59 AM Subject: RE: Subject: sendmail domain configuration as Message 9 Sent by: redhat-list-bounces@xxxxxxxxxx -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx ] On Behalf Of John Wong Sent: Sunday, August 29, 2010 3:11 AM To: redhat-list@xxxxxxxxxx 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@xxxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: sendmail domain configuration Message-ID: <230ED15F81AFD3409345FFA4E565F0E50D2B4FB1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: too many nfs error messages Message-ID: <AANLkTiniqUk6atcw-78FVaM_SkC2GeqRrgML77RtAvxa@xxxxxxxxxxxxxx> 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@xxxxxxxxxxx> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx> Subject: Re: too many nfs error messages Message-ID: <AANLkTikiK6YpdGLuZPv=aGrKeUHXxBtP-uOkpWjJpTbG@xxxxxxxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > ------------------------------ __ redhat-list mailing list Unsubscribe mailto:redhat-list-request@xxxxxxxxxx?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@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
