On Thu, 28 Jun 2001, Charles Cazabon wrote:
>Err -- this is the whole problem. If you're running inetd, I can get your
xinetd != inetd. Have you tested and seen that this is still a problem?
>system to shut off the POP3 service for ten minutes simply by initiating five
>or ten connections in a
Thorkild Stray <[EMAIL PROTECTED]> wrote:
>
> >The reason you won't find much advice on inetd/xinetd configurations here is
> >because use of inetd and xinetd are deprecated. tcpserver is simpler, more
> >reliable, more flexible, and more efficient.
>
> One thing that xinetd apparantly gives yo
On Thu, 28 Jun 2001, Charles Cazabon wrote:
>Kenneth <[EMAIL PROTECTED]> wrote:
>The reason you won't find much advice on inetd/xinetd configurations here is
>because use of inetd and xinetd are deprecated. tcpserver is simpler, more
>reliable, more flexible, and more efficient.
One thing that
Kenneth <[EMAIL PROTECTED]> wrote:
> I missed the original disucssion but I never saw a config file posted to
> the archive so here's one.
The reason you won't find much advice on inetd/xinetd configurations here is
because use of inetd and xinetd are deprecated. tcpserver is simpler, more
reli
At 10:05 AM 6/5/01, Charles Cazabon wrote:
>David Means <[EMAIL PROTECTED]> wrote:
>
> > If it's empty, then I'm a relayer, which is a no-no. Without
> tcpserver, I
> > can't (or haven't figured out how with Xinetd) to populate the
> required env
> > vars, hence my clients can't send email via
David Means <[EMAIL PROTECTED]> wrote:
>
> Charles Cazabon wrote:
> >
> > You're misunderstanding the purpose of rcpthosts. It's only supposed to
> > contain the domains for which you act as either a primary or backup mail
> > exchanger.
>
> I don't think I'm misunderstanding it. The only thi
Charles Cazabon wrote:
{ snip }
>
> > That way, I can have only my domain in rcpthosts, but allow my other clients
> > access.
>
> You're misunderstanding the purpose of rcpthosts. It's only supposed to
> contain the domains for which you act as either a primary or backup mail
> exchanger.
It's also in tcp-env
Scott Schwartz wrote:
>
> > tcpserver does much more than this; in particular, the ability to arbitrarily
> > set environment variables on a per-IP or per-hostname basis is particularly
> > valuable in controlling certain aspects of qmail's behaviour.
>
> Historical note:
David Means <[EMAIL PROTECTED]> wrote:
>
> I believe your points are valid. But I'm just stuborn, I suppose :)
Perhaps. More importantly, you're re-inventing the wheel, possibly with bugs.
> So stuborn as a matter of fact, that I patched qmail-smptd this weekend
> to read a new control file w
> tcpserver does much more than this; in particular, the ability to arbitrarily
> set environment variables on a per-IP or per-hostname basis is particularly
> valuable in controlling certain aspects of qmail's behaviour.
Historical note: that functionality used to be available in
a separate pro
Charles:
I believe your points are valid. But I'm just stuborn, I suppose :)
So stuborn as a matter of fact, that I patched qmail-smptd this weekend
to read a new control file which I called ipaddrallowed. In which I can
put things like 192.168. or a full IP addr. If the source address of
the
Hello,
I discussed XINETD on my web page intensively. Look at:
http://www.fehcom.de/qmail_en.html
cheers.
eh.
At 16:58 2.6.2001 -0300, Eduardo Gargiulo wrote:
>Hi all.
>
>I had installed qmail and it's running ok.
>All the examples says to add a line in /etc/inetd.conf to run
>qmail-smtpd, but
Su 04 Jun 2001 08:22:59 -0600, Charles Cazabon ha scritto:
> David Means <[EMAIL PROTECTED]> wrote:
>
> > Charles Cazabon wrote:
> > >
> > > Eduardo Gargiulo <[EMAIL PROTECTED]> wrote:
> > > >
> > > > I had installed qmail and it's running ok. All the examples
says to add
> > > > a line in /etc/
Charles Cazabon <[EMAIL PROTECTED]> writes:
> tcpserver does much more than this;
One additional thing: It doesn't have to run as root when the service
doesn't require it.
Regards, Frank
David Means <[EMAIL PROTECTED]> wrote:
> Charles Cazabon wrote:
> >
> > Eduardo Gargiulo <[EMAIL PROTECTED]> wrote:
> > >
> > > I had installed qmail and it's running ok. All the examples says to add
> > > a line in /etc/inetd.conf to run qmail-smtpd, but I don't know how to
> > > configure it i
I personally don't care to run tcpserver, although I've run it in the
past, and it worked well at that time. tcpserver is nothing but a
wrapper to enable one to 1) log connections, and 2) keep unallowed hosts
out. Xinetd does that for me. Why would any one want to run two
servers that can do th
Eduardo:
xinetd.conf is something new. I have seen it in RH 7.1. You will notice that
it includes a statement that looks something like this:
"includedir /etc/xinetd.d"
If you open the directory "xinetd.x", you will find several files. Each file
represent an entry in the old "inetd.conf
Eduardo Gargiulo <[EMAIL PROTECTED]> wrote:
>
> I had installed qmail and it's running ok. All the examples says to add a
> line in /etc/inetd.conf to run qmail-smtpd, but I don't know how to
> configure it in xinetd. Where can I find an xinetd example and what is
> tcp-env for?
Running qmail
Eduardo Gargiulo wrote:
>
> Hi all.
>
> I had installed qmail and it's running ok.
> All the examples says to add a line in /etc/inetd.conf to run
> qmail-smtpd, but I don't know how to configure it in xinetd.
> Where can I find an xinetd example and what is tcp-env for?
>
> --xgnu powered by v
Why not use tcpserver?
My experience with xinetd has been terrible.
By the way, try to set RELAYCLIENT="".
> -Original Message-
> From: John Evans [mailto:[EMAIL PROTECTED]]
> Sent: jueves, 12 de abril de 2001 20:28
> To: [EMAIL PROTECTED]
> Subject: xinetd, tcpwrappers and qmail
>
>
>
I will suggest tcpserver since it is the "proper" and recommend way of
running qmail, and probably 95% of your support on this list will come with
tcpserver related answers.
The reason you were getting 30+ second responses is due to DNS not setup or
resolving properly. You can get around it by a
John Evans <[EMAIL PROTECTED]> wrote:
>I am missing something in my settings, but I just can't find what it is.
What you're missing is that you should be using tcpserver.
>I tried using tcpserver and that worked for allowing selective relaying, but
>connections to any port from systems other th
quot; <[EMAIL PROTECTED]>
Sent: Thursday, December 28, 2000 12:37 PM
Subject: RE: Xinetd & Qmail & New Problem!
> Jeff,
>
> I think you'll need to post your logs and startup files for the list
members
> to be able to help you.
>
> cheers,
>
> Andrew.
Hello,
This set up used to work with qmail and RH7.0. It uses vpopmail so if
you have a standard qmail instalation you'll have to change vchkpw to use
checkpassword.
Each service is in one file inside /etc/xinet.d. Read xinet man pages to
allow and deny connections, set a maximun number
On Fri, Oct 06, 2000 at 10:27:42AM +0200,
Martin Jespersen <[EMAIL PROTECTED]> wrote:
> The problem with tcpserver is that it doesn't use libwrap and this is
> absolutely nescessry since i have automated hosts.allow and hosts.deny
> generation by programs that i haven't written and are not a goo
The problem with tcpserver is that it doesn't use libwrap and this is
absolutely nescessry since i have automated hosts.allow and hosts.deny
generation by programs that i haven't written and are not a good enough
coder to rewrite so they will support tcp-rules.
also tcpserver (for me) is really a
Hi,
actually, I did the opposit (xinetd --> tcpserver).
At 23:33 5.10.2000 +0200, Martin Jespersen wrote:
>Hi all
>
>I have just switched from tcpserver to xinetd for simpler management since
i need to be able to use
>the libwrap method of handeling access (/etc/hosts.(allow|deny))
>
- Well, wi
Hi,
check my Qmail Web-page: http://www.fehcom.de/qmail_en.html
xinetd is maintained by synack: http://synack.net
Works fine anyway.
cheers.
eh.
At 18:02 5.9.2000 +0200, [EMAIL PROTECTED] wrote:
>
>Hello,
>
> I have been trying to set up qmail and xinetd. No prob
>lem th the
>smtp p
Most of the people on the list either choose two methods:
1. The lazy method, use inetd. Works fine, and most systems are already
setup for inetd.
2. The good method. Use tcpserver. tcpserver, also written by DJB is fast,
stable, and can be secured much like inetd, but with more functionality.
On Tue, 9 Mar 1999, Czeh Istvan wrote:
> Hi!
>
> I'm running qmail-smtpd from xinetd, and now I need to allow SMTP relay for
> the localhost.
>
> I've read FAQ 5.4, and I configured xinetd like this:
>
> service smtp
> {
> socket_type = stream
> protocol= tcp
> wait=
30 matches
Mail list logo
