You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Peter <pe...@yahoo.ca> on 2006/01/11 22:54:10 UTC
rules_du_jour/curl suddenly broken?
A couple of hours ago I started seeing errors regarding RDJ:
exec: curl -w %{http_code} --compressed -O -R -s -S -z
/var/amavisd/etc/mail/spamassassin/RulesDuJour/rules_du_jour
http://sandgnat.com/rdj/rules_du_jour 2>&1
curl_output: curl: (7) Failed to connect to 208.42.148.125: No route to
host
000
Performing preliminary lint (sanity check; does the CURRENT config lint?).
I am running OpenBSD 3.8 on this server for a month now with no such
errors. Any ideas? My internet connection is fine. It is something to
do with curl perhaps?
--
Peter
__________________________________________________________
Find your next car at http://autos.yahoo.ca
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by jdow <jd...@earthlink.net>.
From: "Matt Kettler" <mk...@evi-inc.com>
> jdow wrote:
>> From: "Matt Kettler" <mk...@evi-inc.com>
>>
>>> Peter wrote:
>>> > False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
>>>
>>>> Strange I never got these errors before. Does it only use curl when it
>>>> detects (how?) an update is required?
>>>>
>>>
>>> Nope.. it always needs to go out over port 80. The "check for update"
>>> is done
>>> using HTTP "If-Modified-Since" requests.
>>
>>
>> To be clearer, I use wget with ftp here. It would also work with http.
>
> Erm.. That confuses me Joanne..
>
> Yes, wget supports FTP, but none of the rule mirrors, such as rulesemporium, has
> FTP access. So how is that relevant here?
I used to use ftp. It seems these days I do indeed use http via wget.
I was working on a stale memory there. Now that you mention it I remember
having to switch GetRules.sh over to http. When I first built it ftp
worked, I believe.
> AFAIK pretty much the *only* way to get rule updates with RDJ is to use HTTP,
> which is on port 80.
>
> I can only speak conclusively about antidrug (which nobody using SA 3.0.0 or
> higher should use), but I'll tell you for sure that there is no way to update
> antidrug over FTP. HTTP only.
{^_^}
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Matt Kettler <mk...@evi-inc.com>.
jdow wrote:
> From: "Matt Kettler" <mk...@evi-inc.com>
>
>> Peter wrote:
>> > False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
>>
>>> Strange I never got these errors before. Does it only use curl when it
>>> detects (how?) an update is required?
>>>
>>
>> Nope.. it always needs to go out over port 80. The "check for update"
>> is done
>> using HTTP "If-Modified-Since" requests.
>
>
> To be clearer, I use wget with ftp here. It would also work with http.
Erm.. That confuses me Joanne..
Yes, wget supports FTP, but none of the rule mirrors, such as rulesemporium, has
FTP access. So how is that relevant here?
AFAIK pretty much the *only* way to get rule updates with RDJ is to use HTTP,
which is on port 80.
I can only speak conclusively about antidrug (which nobody using SA 3.0.0 or
higher should use), but I'll tell you for sure that there is no way to update
antidrug over FTP. HTTP only.
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by jdow <jd...@earthlink.net>.
From: "Matt Kettler" <mk...@evi-inc.com>
> Peter wrote:
> > False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
>> Strange I never got these errors before. Does it only use curl when it
>> detects (how?) an update is required?
>>
>
> Nope.. it always needs to go out over port 80. The "check for update" is done
> using HTTP "If-Modified-Since" requests.
To be clearer, I use wget with ftp here. It would also work with http.
{^_^}
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Mark Martinec <Ma...@ijs.si>.
Peter,
> TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
> /etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line 1,
> <GEN6> line 1706.
Search the amavisd-new web page for 'swash_fetch'.
It is consequence of Perl bugs when handling UTF-8 characters.
What version of Perl and what version of amavisd-new is that?
If using Perl 5.8.0 in UTF-8 environment, you are asking
for touble. Later versions of amavisd-new may be able to
work around some of these Perl problems.
Mark
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Peter <pe...@yahoo.ca>.
--- Matt Kettler <mk...@evi-inc.com> wrote:
> Peter wrote:
> > False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
> > Strange I never got these errors before. Does it only use curl when
> it
> > detects (how?) an update is required?
> >
>
> Nope.. it always needs to go out over port 80. The "check for update" is
> done
> using HTTP "If-Modified-Since" requests.
Let's try that again...
Looks like I had two problems simultaneously. The update issue was not
causing the error it seems. The real problem I'm encountering appears to
concern a particular SARE rule. I am running amavisd-new with SA and this
is what I'm getting in my logs:
TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
/etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line 1,
<GEN6> line 1706.
This started happening today at 14:00 hrs EST. It's always the same rule
listed in the error (70_sare_specific.cf).
Blllllllllllpppp....
Ok, it looks like all these errors are due to a resend of the same stupid
piece of red hot spam. That SARE rule seems to be barfing from it. I
enclose it for those interested.
--
Peter
__________________________________________________________
Find your next car at http://autos.yahoo.ca
Re: Re[2]: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Peter <pe...@yahoo.ca>.
--- Robert Menschel <Ro...@Menschel.net> wrote:
> Hello Peter,
>
> Wednesday, January 11, 2006, 7:31:39 PM, you wrote:
>
> P> Looks like I had two problems simultaneously. The update issue was
> not
> P> causing the error it seems. The real problem I'm encountering
> appears to
> P> concern a particular SARE rule. I am running amavisd-new with SA and
> this
> P> is what I'm getting in my logs:
>
> P> TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
> P> /etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ,
> line 1,
> P> <GEN6> line 1706.
>
> P> Ok, it looks like all these errors are due to a resend of the same
> stupid
> P> piece of red hot spam. That SARE rule seems to be barfing from it.
> I
> P> enclose it for those interested.
>
> Peter, I ran your spam through my SA with that file/rule, and had no
> problem. My test ran on Windows XP, Cygwin, SpamAssassin version
> 3.1.0, running on Perl version 5.8.5.
>
> Can you use the command
> > spamassassin -D <redhotspam.txt >redhot.out 2>redhot.err
> and see if the problem hits there? If so, send me a copy of the two
> output files?
>
> I can't see how such a short and sweet rule could cause this problem.
> Can use some help.
>
> Also, maybe you can download a fresh copy of the specific.cf rules
> file, and see if maybe the copy you're running with has been corrupted
> some how?
I scanned it per your suggestion and I did not find anything wrong in the
output. I guess that places the blame on amavisd-new. It doesn't know
how to handle the output this rule provides???
--
Peter
__________________________________________________________
Find your next car at http://autos.yahoo.ca
Re[2]: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Robert Menschel <Ro...@Menschel.net>.
Hello Peter,
Wednesday, January 11, 2006, 7:31:39 PM, you wrote:
P> Looks like I had two problems simultaneously. The update issue was not
P> causing the error it seems. The real problem I'm encountering appears to
P> concern a particular SARE rule. I am running amavisd-new with SA and this
P> is what I'm getting in my logs:
P> TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
P> /etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line 1,
P> <GEN6> line 1706.
P> Ok, it looks like all these errors are due to a resend of the same stupid
P> piece of red hot spam. That SARE rule seems to be barfing from it. I
P> enclose it for those interested.
Peter, I ran your spam through my SA with that file/rule, and had no
problem. My test ran on Windows XP, Cygwin, SpamAssassin version
3.1.0, running on Perl version 5.8.5.
Can you use the command
> spamassassin -D <redhotspam.txt >redhot.out 2>redhot.err
and see if the problem hits there? If so, send me a copy of the two
output files?
I can't see how such a short and sweet rule could cause this problem.
Can use some help.
Also, maybe you can download a fresh copy of the specific.cf rules
file, and see if maybe the copy you're running with has been corrupted
some how?
Bob Menschel
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Peter <pe...@yahoo.ca>.
--- Matt Kettler <mk...@evi-inc.com> wrote:
> Peter wrote:
> > False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
> > Strange I never got these errors before. Does it only use curl when
> it
> > detects (how?) an update is required?
> >
>
> Nope.. it always needs to go out over port 80. The "check for update" is
> done
> using HTTP "If-Modified-Since" requests.
Looks like I had two problems simultaneously. The update issue was not
causing the error it seems. The real problem I'm encountering appears to
concern a particular SARE rule. I am running amavisd-new with SA and this
is what I'm getting in my logs:
TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
/etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line 1,
<GEN6> line 1706.
This started happening today at 14:00 hrs EST. It's always the same rule
listed in the error (70_sare_specific.cf).
Blllllllllllpppp....
Ok, it looks like all these errors are due to a resend of the same stupid
piece of red hot spam. That SARE rule seems to be barfing from it. I
enclose it for those interested.
--
Peter
__________________________________________________________
Find your next car at http://autos.yahoo.ca
Re: [SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Matt Kettler <mk...@evi-inc.com>.
Peter wrote:
> False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
> Strange I never got these errors before. Does it only use curl when it
> detects (how?) an update is required?
>
Nope.. it always needs to go out over port 80. The "check for update" is done
using HTTP "If-Modified-Since" requests.
[SOLVED] Re: rules_du_jour/curl suddenly broken?
Posted by Peter <pe...@yahoo.ca>.
--- Peter <pe...@yahoo.ca> wrote:
> A couple of hours ago I started seeing errors regarding RDJ:
>
> exec: curl -w %{http_code} --compressed -O -R -s -S -z
> /var/amavisd/etc/mail/spamassassin/RulesDuJour/rules_du_jour
> http://sandgnat.com/rdj/rules_du_jour 2>&1
> curl_output: curl: (7) Failed to connect to 208.42.148.125: No route to
> host
> 000
> Performing preliminary lint (sanity check; does the CURRENT config
> lint?).
>
> I am running OpenBSD 3.8 on this server for a month now with no such
> errors. Any ideas? My internet connection is fine. It is something to
> do with curl perhaps?
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when it
detects (how?) an update is required?
--
Peter
__________________________________________________________
Find your next car at http://autos.yahoo.ca