Bill Shupp wrote the following on 04/04/2008 02:31 PM:
On Apr 4, 2008, at 2:18 PM, Michael McCallister wrote:

Greetings,

Sorry to bug the list, but I cannot figure this out. I really like the idea of surbl support on the smtp level before it hits SA (i.e. wipe out junk before it hits SA). However, I can't seem to get it to work. I am running the latest toaster and I can see all the SURBL additions to qmail-smtpd.c. I have exported SURBL=1 in /var/qmail/supervise/qmail-smtpd/run and /home/vpopmail/etc/tcp.smtp

In my tests, I send an email with a URL I know is in multi.surbl.org (only the URL in the body) while having "tcpdump port 53" fired up - there are no lookups on multi.surbl.org and the email gets through. When I enable the URIBL tests in SA, I see the lookups so I know that DNS is working.

SURBL checking might be skipped if RELAYCLIENT is set, I don't recall. Try an smtp connection where you don't use SMTP-AUTH or come from an IP that has RELAYCLIENT set.

Regards,

Bill
Thanks Bill,

I was not using SMTP-AUTH.  I just tried from my gmail account (using
the same test URL) to eliminate anything I may have on my servers.  Here
is the output from smtpd/current:

@4000000047f6a0860122003c tcpserver: pid 31447 from 64.233.182.187
@4000000047f6a0860122d714 tcpserver: ok 31447 0:206.83.209.9:25
:64.233.182.187::27591
@4000000047f6a08627acd664 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
<nf-out-0910.google.com:unknown:64.233.182.187> rcpt <> : sender accepted
@4000000047f6a08638f419dc CHKUSER accepted any rcpt: from
<[EMAIL PROTECTED]::> remote
<nf-out-0910.google.com:unknown:64.233.182.187> rcpt
<[EMAIL PROTECTED]> : accepted any recipient for this domain
@4000000047f6a0892c7f1ef4 simscan:[31447]:PASSTHRU
(23.10/6.00):2.6041s:[SPAM] testing
surbl:64.233.182.187:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
@4000000047f6a0a80828ef94 tcpserver: end 31447 status 0
@4000000047f6a0a80828fb4c tcpserver: status: 0/500

contacthosting.com is essentially a test domain I use for this sort of
thing.  When I connect via SMTP-AUTH, I see "client allowed to relay" in
smtpd/current - furthermore, when I try to relay without authentication,
I am denied relay (5.7.1 sorry, that domain isn't in my list of allowed
rctphosts (chkuser)) so I am pretty sure the whole SMTP-AUTH thing is
solidly in place.

Michael


Reply via email to