Michael Bryan writes:
> Sam wrote:
> >
> > Michael Bryan writes:
> >
> > > <[EMAIL PROTECTED]>:
> > > 208.15.106.2 does not like recipient.
> > > Remote host said: 553 sorry, that domain isn't in my list of allowed
> > > rcpthosts (#5.7.1)
> > > Giving up on 208.15.106.2.
> > >
> > > All the tcp stuff is correct. And, I can actually send mail to virtual
> > > addresses from that machine (via pine, or Web-Based Programs)
> > >
> > > So where do I look? rcpthosts,virtualdomains,locals all look good.
> >
> > You look into the manual page for qmail-smtpd, which explains how
> > qmail-smtpd uses rcpthosts, and how it uses the RELAYCLIENT environment
> > variable. Together with the knowledge of what your IP addresses are, this
> > information is sufficient to be able to set up controlled relaying in your
> > domain.
> >
> > --
> > Sam
>
> What I'm saying is that I've looked and looked and looked and can't see
> why it's not working. I've got Qmail running fine on other machines on
> different networks with virtual domains and correct relaying.
>
> What are things that I can check? I'd be happy to paste the contents of
> certain files.
You check:
A) The set of IP addresses that you're sending the mail from.
B) The contents of control/rcpthosts.
C) The mechanism by which you're setting the contents of the RELAYCLIENT
environment variable, whether it's accomplished via tcpserver, a shell
script, or by some other means.
Those are the only three factors which affect whether an arbitrary
recipient is accepted by qmail-smtpd. In each case, you declare not only
what you THINK each item of information should be, but also provide some
kind of an independent confirmation -- that you're verifying the contents
of control/rcpthosts on the right machine; by running a trace to yourself
to verify your actual IP address; by temporarily implementing some
debugging code that accurately logs the contents of the environment just
prior to qmail-smtpd being invoked, etc...
--
Sam
