On Tue, Jul 25, 2000 at 02:12:17PM +0100, Daniel Cave wrote:
! 1. If someone tries to relay an email from an IP address (ISP dialup) which
! is not listed in /etc/tcp.smtp, and who's domainname happens to be listed in
! rcpthosts, desined for a recipient 'somewhere' on the internet,  am I right
! in thinking that this connection/request to relay will be blocked by
! tcpserver?

If RELAYCLIENT is not set when qmail-smtpd is invoked, then they can't
relay.

!            How do I allow this to happen, if I dont know the IP address of
! the user wishing to relay??

Put rules of the form =.foo.bar, if the domain name you wish to allow
relay is foo.bar. Then any client whose IP address reverse-resolves
to *.foo.bar can relay.

=.foo.bar:allow,RELAYCLIENT=""

!                             This in essence is the same as [EMAIL PROTECTED]
! sending an email to [EMAIL PROTECTED], isnt it??

Not sure I understood you here, sorry.

! 2. What is the significance of using qmail-qmqpd over the above method.
! Which is better.??

QMQP (628/tcp) is really only used for ``null-client'' setups. You were
referring to dialup users, so I must presume you are referring to tools
in the serialmail package, in which case SMTP and QMTP are the options.

QMTP (209/tcp) is similar to SMTP, but more efficient. Set it up if you
have dialup users using qmail. qmail-qmtpd has as much relay protection
as qmail-smtpd.

        ---Chris K.
-- 
 Chris, the Young One |_ but what's a dropped message between friends? 
  Auckland, New Zealand |_ this is UDP, not TCP after all ;) ---John H. 
http://cloud9.hedgee.com/ |_ Robinson, IV  
 PGP: 0xCCC6114E/0x706A6AAD |_ 

Reply via email to