Hi, I have a user who is on a VPS account running Webmin as a control panel on Linux 2.4.20-021stab022.4.777-smp Red Hat Enterprise Linux AS release 3 (Taroon Update 1).
He runs sendmail and wanted to use DNSBL, so I put the line:
FEATURE(`dnsbl',`sbl.spamhaus.org')dnl
in sendmail.mc, ran make, and I see that it's been added to sendmail.cf
It seems to work from sendmail test mode (I tested beforehand, and it did not work):
# sendmail -bt
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
Enter <ruleset> <address>
> .D{client_addr}192.203.178.107
> Basic_check_relay <>
Basic_check_rela input: < >
Basic_check_rela returns: $# error $@ 5 . 7 . 1 $: "550 Rejected: " 192 . 203 . 178 . 107 " listed at sbl.spamhaus.org"
> /quit
But when I send a test to
nelson-sbl-test@crynwr.com
(per www . spamhaus.org/sbl/howtouse.html),
it says the block is not working. It shows the SMTP conversation:
220 domain.com ESMTP Sendmail 8.12.10/8.12.10; Mon, 15 Nov 2004 12:11:20-0800
helo sbl.crynwr.com
250 domain.com Hello sbl.crynwr.com [192.203.178.107], pleased to meet you
mail from:<>
250 2.1.0 <>... Sender ok
rcpt to:<root@domain.com>
250 2.1.5 <root@domain.com>... Recipient ok
[snip]
[It goes on to give the body of the message and show that the mail server accepts it. It also sent another message which said uh-oh, your sbl block is not working.]
On another machine that works (qmail + DNSBL), the test message stops right after the "rcpt to:" line and says:
451 www . spamhaus.org/SBL/sbl.lasso?query=SBL230
Terminating conversation
So, it works from test mode, but fails the nelson-sbl-test. And the logs don't show any hits either (he gets a lot of spam to his mail accounts, it's been a couple nights, so if it was working, surely he would've gotten some hits).
At first, I thought it wasn't reading the same cf file, but there is only one on the machine, so I assume it is. I don't know of any way of checking.
The only things I can think of that might be relevant: sendmail on his machine seems to be controlled by xinetd, i.e., it's not constantly running, but when mail comes in, a new sendmail process is spawned by xinetd. We've restarted xinetd, in fact, rebooted just to be sure, and it still doesn't make a difference.
My gut tells me it's somehow xinetd related, but really, I'm at a loss.
Thanks for any suggestions.
