Re: Relay IP address ranges - NEWBIE
Thanks for your help - all of you. Based on your advice, I nixed xinetd and tcpserver is happy as a clam - so it is reading its config files and forwarding is working. If/when I need ssh, I'll set that up with tcpserver.
Relay IP address ranges - NEWBIE
Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. In other words, I'm lost - help?
Re: Relay IP address ranges - NEWBIE
On Fri, Jun 15, 2001 at 12:43:24PM -0500, Stephen Froehlich wrote: Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. In other words, I'm lost - help? You mentioned both xinetd and ucspi-tcp, which one are you using?? Try: $ ps axw | tcpserver If you get an output post it, if not check the xinetd FAQ. Jörgen
Re: Relay IP address ranges - NEWBIE
Stephen Froehlich [EMAIL PROTECTED] wrote: Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and daemontools installed, which is far superior in any case. Then go to lifewithqmail.org and set up tcpserver/tcprules controls to allow relaying. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Relay IP address ranges - NEWBIE
OK, so both xinetd and tcpserver are running. I get the feeling that I should pull xinetd out of the startup scripts. How will this effect apache and other services (most epically bind)? I assume the two don't coexist well? (A logical push-me-pull-you?) I have two instances of tcp server, both called with the command: /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smptd xinetd is also running (one process). The other services can go; (I'd like the ability to run a web server in a pinch, however, the Mac can actually take care of that on an emergency basis (which is all I want locally).), however I need DNS on the mail box for the internal (NAT) DNS configuration. - Original Message - From: Charles Cazabon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 2:04 PM Subject: Re: Relay IP address ranges - NEWBIE Stephen Froehlich [EMAIL PROTECTED] wrote: Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and daemontools installed, which is far superior in any case. Then go to lifewithqmail.org and set up tcpserver/tcprules controls to allow relaying. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Relay IP address ranges - NEWBIE
Technology Strategic Planning, Inc. wrote: OK, so both xinetd and tcpserver are running. I get the feeling that I should pull xinetd out of the startup scripts. How will this effect apache and other services (most epically bind)? I assume the two don't coexist well? (A logical push-me-pull-you?) I have two instances of tcp server, both called with the command: /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smptd xinetd is also running (one process). The other services can go; (I'd like the ability to run a web server in a pinch, however, the Mac can actually take care of that on an emergency basis (which is all I want locally).), however I need DNS on the mail box for the internal (NAT) DNS configuration. Just remove any e-mail related protocols from xinetd's conf files and send it a reload signal (SIGUSR1 if I remember correctly from my darker experiences with it). -- Nick (Keith) Fish Network Engineer Triton Technologies, Inc.
Re: Relay IP address ranges - NEWBIE
For Apache and Bind do not care, they are stand alone servers, if you have an FTP, Telnet, or other service you have 2 options: disable it (safest), make a run script and run it from tcpsefver. Nazghul Microsoft is not the answer, its the question. And the answer is no. www.badran.co.uk - Original Message - From: Technology Strategic Planning, Inc. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 3:24 PM Subject: Re: Relay IP address ranges - NEWBIE OK, so both xinetd and tcpserver are running. I get the feeling that I should pull xinetd out of the startup scripts. How will this effect apache and other services (most epically bind)? I assume the two don't coexist well? (A logical push-me-pull-you?) I have two instances of tcp server, both called with the command: /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smptd xinetd is also running (one process). The other services can go; (I'd like the ability to run a web server in a pinch, however, the Mac can actually take care of that on an emergency basis (which is all I want locally).), however I need DNS on the mail box for the internal (NAT) DNS configuration. - Original Message - From: Charles Cazabon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 2:04 PM Subject: Re: Relay IP address ranges - NEWBIE Stephen Froehlich [EMAIL PROTECTED] wrote: Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and daemontools installed, which is far superior in any case. Then go to lifewithqmail.org and set up tcpserver/tcprules controls to allow relaying. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Relay IP address ranges - NEWBIE
On Fri, Jun 15, 2001 at 03:24:05PM -0500, Technology Strategic Planning, Inc. wrote: OK, so both xinetd and tcpserver are running. I get the feeling that I should pull xinetd out of the startup scripts. How will this effect apache and other services (most epically bind)? I assume the two don't coexist well? (A logical push-me-pull-you?) They can coexist but not bind to the same port. I have two instances of tcp server, both called with the command: /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smptd Two identical instances of tcpserver?? one them changing PID all the time?? There's most probably a problem with your start scripts and something (svscan?) tries to start it twice. If you want to control relay check /etc/tcp.smtp and the documentation for tcprules[1]. xinetd is also running (one process). It's fine unless it doesn't try to bind to the same ports as tcpserver. Jörgen [1] http://cr.yp.to/ucspi-tcp/tcprules.html
