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 thing in my rcpthosts
> is my domain name and 'localhost'.
Okay. In your previous message, it sounded like you were populating it with
domains that you wanted to send mail _to_, which is a common mistake.
> 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 qmail-smtpd to domains not
> listed in rcpthosts, right?
Correct. It can apparently be done with xinetd, but I don't use it.
> > Now that you've written code to do some of this for qmail-smtpd, what would
> > happen if you wanted exactly the same features with qmail-qmtpd, or
> > qmail-pop3d, or fingerd? With djb's modular approach, you don't need to
> > rewrite a single line of code. tcpserver "just works" for all of them.
>
> Well, for the qmail stuff, I you're right: I'd have to patch'em all, use
> tcpserver or patch xinetd to act like tcpserver. But with other servers
> (like fingerd), I'm content to let my firewall and xinet (as is) deal
> with who gets in or out. :-)
If it works for you, great. If you start having problems and need better
control over the concurrency of your daemons (say someone uses your domain
name in a 40-million-spew spam to AOL and Hotmail), consider tcpserver then.
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.
-----------------------------------------------------------------------
