>-----Original Message-----
>From: Douglas Kirkland [mailto:[EMAIL PROTECTED]
>Sent: Tue 12/23/2003 8:34 PM
>To: [EMAIL PROTECTED]
>Cc:
>Subject: Re: [SAtalk] SpamAssassin only working on 127.0.0.1 & not on
external mail
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>>On Tuesday 23 December 2003 19:00, Wendel, Jesse wrote:
>>
>> Stuff originating on my local box is scanned. Stuff origniating externally
>>is not scanned. In both cases, the IP that spamassassin uses to scan from is
>>127.0.0.1.
>>
>> And as I showed on ps -aux | grep spam, on both systems, the -A was missing.
>> Yet one is working and the other never has.
>
>
>What versions are you running for spamd and spamassassin module? Are they the
>same.
On both test and production, the answer is as follows:
[EMAIL PROTECTED] i386]# rpm -q spamassassin-tools
spamassassin-tools-2.61-1
[EMAIL PROTECTED] i386]# rpm -q perl-Mail-SpamAssassin
perl-Mail-SpamAssassin-2.61-1
[EMAIL PROTECTED] i386]# rpm -q spamassassin
spamassassin-2.61-1
[EMAIL PROTECTED] i386]#
>Also check out the -i option.
>
> -i ipaddress, --listen-ip=ipaddress, --ip-address=ipad-
> dress
> Tells spamd to listen on the specified IP address
> [defaults to 127.0.0.1]. Use 0.0.0.0 to listen on all
> interfaces.
>
Um, I guess I could Doug. But my question is, why would it be necessary?
I just went to the production system. I compared the file which starts up
spamd when the server boots, which is: /etc/rc.d/init/d/spamassassin
I grabbed it and ran a DIFF against the same file on the test system. They're
identical on both systems, which is what the ps I showed you in an earlier email was
showing.
Here is the key section from the file:
# Source spamd configuration.
if [ -f /etc/sysconfig/spamassassin ] ; then
. /etc/sysconfig/spamassassin
else
SPAMDOPTIONS="-d -c -a -m5 -H"
fi
[ -f /usr/bin/spamd -o -f /usr/local/bin/spamd ] || exit 0
I can't figure out what the -o is from the documentation, and I think the -a
is the wrong case. Otherwise, everything makes sense.
What doesn't make sense, is why in Production, mail from external systems is
scaned by spamd on 127.0.0.1 (which I'm now clear is the interface it should be
scanned on, so there's no need to open that up wider), and in Test, mail from external
systems is not scaned by spamd.
Anyone have any more ideas?
Jesse
áŠÄë^™¨¥ŠË)¢{(ç[ÈL.)îÅ;¢¸š–À^r‰žjw±¥êíŠrÈ5Eè®;¬¶ÈZ®—§Ê«²H¥–Ä‚{©~ŠÈËç{±Nëh®&¥°·š®w¯z¼†)à~º&¶›jÈl…ée¶‹2±§fŠp¥‰É'£m¶ŸÿiÛ(±ÙÜoÚv'uÛ–Z ‰Ý÷ïZ)rXœ‘*Z™«,jË"žÖ’f¢–)à–+-J–¦j˲ȵ©d–+-²Ê.Ç¢¸ ëa¶Úlÿùb²Û,¢êÜyú+éÞùb²Û?–+-ŠwèþÊZ™«,jË"žÖ
