I am using the out-of-the-box configuration of qmail 1.0.3.
Here is an excerpt from my syslog:
Jul 11 13:43:10 noif qmail: 963348190.748782 new msg 2654625
Jul 11 13:43:10 noif qmail: 963348190.748946 info msg 2654625: bytes 1426
from <> qp 17024 uid 7774
Jul 11 13:43:10 noif qmail: 963348190.760341 starting delivery 9163: msg
2654625 to remote [EMAIL PROTECTED]
Jul 11 13:43:10 noif qmail: 963348190.760460 status: local 0/10 remote 1/20
Jul 11 13:43:31 noif qmail: 963348211.448284 delivery 9163: success:
216.102.143.2_accepted_message./Remote_host_said:_250_OK/
Jul 11 13:43:31 noif qmail: 963348211.448695 end msg 2654625
I would have thought that this message should have failed since it is not
in my rcpthosts, or listed in my tcp.smtp.cbd file, and therefore not
considered local.
Here is my tcp.smtp:
192.168.2.:allow,RELAYCLIENT""
:allow
My rcpthosts contains the all of my domains. The locals file contains all
of the local domains that I want delivered to.
Maybe I am asking the question in the wrong manner.
Thanks for the help.
At 11:59 AM 7/18/00 -0700, you wrote:
>Quoting Robert Spraggs ([EMAIL PROTECTED]):
> > I have been successful stopping relaying to outside hosts using tcpserver,
> > but any message starting with a <> Message ID can be delivered to an
>
>Do you mean anything with a null return path? qmail doesn't give a
>whit what's in the message-id, nor does it relay to anywhere just
>because the return path is null. Only connections that have
>RELAYCLIENT set or to recipients in rcpthosts are accepted for relay.
>If this is really the behavior you see, you need to provide
>information on your qmail setup--any patches, addons, etc that you
>have applied or using that may cause this sort of behavior. The
>results of qmail-showctl and the IP address of the server in question
>would be nice, too, so others can test it. Results of your relay
>tests (telnet to port 25, for example) may be helpful.
>
>To be sure, I've never seen such behavior by stock qmail, so something
>is rotten in Denmark. :)
>
>Aaron
