Inconsistent spam scores between spam headers and rewritten subject line.
Hi all. I'm running spamassassin 3.3.1 on my openSuse 11.2 box at home. Mail
is collected from multiple ISP mail accounts via fetchmail and delivered to
local IMAP mail folders via procmail. My user account .procmailrc file begins
thus:
LOGFILE=$HOME/pm.log
:0fw: spamassassin.lock
| spamc
:0
* ^Subject.*SPAM\([0-9]{1,3}\.[0-9]\).*
$HOME/Maildir/.Spam//
I'm attempting to filter on the modified subject line (which for some reason
isn't working - that rule never seems to match and spam never gets moved into
the Spam folder, even though I've tested the regex manually). I thought of
filtering on the X-Spam-Status header instead, but when I had a look at a
message that was marked as Spam (according to the subject line) I found
something rather strange...
X-Virus-Flag: no
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
X-Spam-Level: *
X-Spam-Status: No, score=1.5 required=6.5
tests=BAYES_00,IMPOTENCE,NO_RELAYS
autolearn=no version=3.3.1
X-Spam-Virus: No
Received: from localhost by
with SpamAssassin (version 3.3.1);
Mon, 15 Aug 2011 18:58:01 +0930
From: "Adele Key"
To: another.u...@iinet.net.au
Subject: SPAM(10.1)
Date: Mon, 15 Aug 2011 18:12:48 +0900
Message-Id: <165971112.54106003786840@spamdomain.removed>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="--=_4E48E6A1.127A41A2"
X-Length: 7330
X-UID: 83487
X-KMail-Filtered: 61220
Status: R
X-Status: N
X-KMail-EncryptionState:
X-KMail-SignatureState:
X-KMail-MDN-Sent:
Spam detection software, running on the system
, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
postmaster for details.
Content preview: [...]
Content analysis details: (10.1 points, 6.5 required)
pts rule name description
-- --
3.8 KB_DATE_CONTAINS_TAB KB_DATE_CONTAINS_TAB
3.0 IMPOTENCE BODY: Impotence cure
-0.0 BAYES_20 BODY: Bayes spam probability is 5 to 20%
[score: 0.1050]
2.0 KB_FAKED_THE_BAT KB_FAKED_THE_BAT
1.2 RDNS_NONE Delivered to internal network by a host with no
rDNS
I don't get it - the content analysis shows a score of 10.1, the modified
subject line shows 10.1, but the X-Spam-Status header shows 1.5! What have I
messed up in my configuration?
My /etc/mail/spamassassin/local.cf looks like this:
# Add your own customisations to this file. See 'man
Mail::SpamAssassin::Conf'
# for details of what can be tweaked.
#
# do not change the subject
# to change the subject, e.g. use
# rewrite_header Subject SPAM(_SCORE_)
rewrite_header subject SPAM(_SCORE_)
# Set the score required before a mail is considered spam.
# required_score 5.00
# uncomment, if you do not want spamassassin to create a new message
# in case of detecting spam
# report_safe 0
# Enhance the uridnsbl_skip_domain list with some usefull entries
# Do not block the web-sites of Novell and SUSE
ifplugin Mail::SpamAssassin::Plugin::URIDNSBL
uridnsbl_skip_domain suse.de opensuse.org suse.com suse.org
uridnsbl_skip_domain novell.com novell.org novell.ru novell.de novell.hu
novell.co.uk
uridnsbl_skip_domain kernel.org
endif # Mail::SpamAssassin::Plugin::URIDNSBL
# Everything above this line is as per the installed openSuSE default
ok_languages en
#The combination of SpamAssassin + The Bat! as mail client can cause false
positives.
#The reason for the high spam rating is the Reply-To header inserted by
mailman,
#which seems to have more quoting than The Bat! can do.
#If you have such problem activate the next two lines
#header IS_MAILMAN exists:X-Mailman-Version
#score IS_MAILMAN -2
required_score 6.5
whitelist_from
[...]
use_bayes 1
report_header 1
fold_headers 1
report_safe 2
Thanks in advance.
Rodney.
--
==
Rodney Baker
rod...@jeremiah31-10.net
web: www.jeremiah31-10.net
==
Re: Inconsistent spam scores between spam headers and rewritten subject line.
On Tue, 16 Aug 2011 00:48:13 Bowie Bailey wrote:
> On 8/15/2011 10:57 AM, Rodney Baker wrote:
> > Hi all. I'm running spamassassin 3.3.1 on my openSuse 11.2 box at home.
> > Mail is collected from multiple ISP mail accounts via fetchmail and
> > delivered to local IMAP mail folders via procmail. My user account
> > .procmailrc file begins
> >
> > thus:
> >LOGFILE=$HOME/pm.log
> >
> >:0fw: spamassassin.lock
> >:
> >| spamc
> >:
> >:0
> >
> >* ^Subject.*SPAM\([0-9]{1,3}\.[0-9]\).*
> >$HOME/Maildir/.Spam//
> >
> > I'm attempting to filter on the modified subject line (which for some
> > reason isn't working - that rule never seems to match and spam never
> > gets moved into the Spam folder, even though I've tested the regex
> > manually). I thought of filtering on the X-Spam-Status header instead,
> > but when I had a look at a message that was marked as Spam (according to
> > the subject line) I found something rather strange...
> >
> >X-Virus-Flag: no
> >X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
> >
> >
> >
> >X-Spam-Level: *
> >X-Spam-Status: No, score=1.5 required=6.5
> >
> > tests=BAYES_00,IMPOTENCE,NO_RELAYS
> >
> > autolearn=no version=3.3.1
> >
> >X-Spam-Virus: No
> >Received: from localhost by
> >
> > with SpamAssassin (version 3.3.1);
> > Mon, 15 Aug 2011 18:58:01 +0930
> >
> >From: "Adele Key"
> >To: another.u...@iinet.net.au
> >Subject: SPAM(10.1)
> >Date: Mon, 15 Aug 2011 18:12:48 +0900
> >Message-Id: <165971112.54106003786840@spamdomain.removed>
> >MIME-Version: 1.0
> >Content-Type: multipart/mixed;
> >boundary="--=_4E48E6A1.127A41A2"
> >X-Length: 7330
> >X-UID: 83487
> >X-KMail-Filtered: 61220
> >Status: R
> >X-Status: N
> >X-KMail-EncryptionState:
> >X-KMail-SignatureState:
> >
> >X-KMail-MDN-Sent:
> > Spam detection software, running on the system
> > , has
> > identified this incoming email as possible spam. The original message
> > has been attached to this so you can view it (if it isn't spam) or
> > label similar future email. If you have any questions, see
> > postmaster for details.
> >
> >
> > Content preview: [...]
> >
> >
> > Content analysis details: (10.1 points, 6.5 required)
> >
> >pts rule name description
> > --
> >-- 3.8
> >KB_DATE_CONTAINS_TAB KB_DATE_CONTAINS_TAB
> >3.0 IMPOTENCE BODY: Impotence cure
> >-0.0 BAYES_20 BODY: Bayes spam probability is 5 to 20%
> >
> > [score: 0.1050]
> >
> >2.0 KB_FAKED_THE_BAT KB_FAKED_THE_BAT
> >1.2 RDNS_NONE Delivered to internal network by a host
> >with no
> >
> > rDNS
> >
> >
> > I don't get it - the content analysis shows a score of 10.1, the modified
> > subject line shows 10.1, but the X-Spam-Status header shows 1.5! What
> > have I messed up in my configuration?
>
> This message is going through SA twice.
>
> The first time, it is marked as spam and the message is re-written per
> your "report_safe" setting. This generates the analysis shown in the
> body itself.
>
> The second time, the re-written message is scanned by SA. This time,
> all of the incriminating stuff has been hidden by the rewrite, so it is
> not marked as spam. This is the analysis shown in the header.
>
> You need to fix whatever is causing the message to be scanned twice.
OK - that makes sense. Now I'm wondering if there is a global mail config
somewhere that is routing the message through SA, and then my local
.procmailrc is doing it again. Time to go digging...
That then leaves the question as to why my procmail recipe isn't triggering on
the rewritten subject, but that is probably not for this list.
Thanks for the pointer.
Rodney.
--
==
Rodney Baker
rod...@jeremiah31-10.net
web: www.jeremiah31-10.net
==
Re: Inconsistent spam scores between spam headers and rewritten subject line.
On Tue, 16 Aug 2011 01:15:11 Walter Hurry wrote:
> On Mon, 15 Aug 2011 11:18:13 -0400, Bowie Bailey wrote:
> > On 8/15/2011 10:57 AM, Rodney Baker wrote:
>
>
> >>:0
> >>
> >>* ^Subject.*SPAM\([0-9]{1,3}\.[0-9]\).* $HOME/Maildir/.Spam//
>
>
>
> > This message is going through SA twice.
>
> Indeed. And by the way, for what it is worth, my .procmailrc says (inter
> alia)
>
> :0:
> * ^X-Spam-Status: Yes
> # The trailing slashdot means do it as MH
> # instead of MBOX (the default)
> junk/.
>
> # Otherwise it falls through
>
> May I suggest that that's rather simpler than the regex which you are
> using?
>
Of course, and that's what I wanted to do, except that if you have a look at
my X-Spam-Status header it says "No", which is the opposite of what I expect
for a message marked as spam (apparently due, as already suggested, to
spamassassin processing the message twice).
> In addition, should I in the future decide for some reason to change or
> revoke the subject rewriting, I won't need to change .procmailrc.
Of course, if I can just get the message flagged as Spam in the headers, I'll
be able to do the same. ;-)
--
==
Rodney Baker
rod...@jeremiah31-10.net
web: www.jeremiah31-10.net
==
Re: Inconsistent spam scores between spam headers and rewritten subject line.
On Tue, 16 Aug 2011 07:36:05 Karsten Bräckelmann wrote:
> On Tue, 2011-08-16 at 01:07 +0930, Rodney Baker wrote:
> > On Tue, 16 Aug 2011 00:48:13 Bowie Bailey wrote:
> > > >* ^Subject.*SPAM\([0-9]{1,3}\.[0-9]\).*
> > > >$HOME/Maildir/.Spam//
> > > >
> > > > I'm attempting to filter on the modified subject line (which for some
> > > > reason isn't working - that rule never seems to match and spam never
> > > > gets moved into the Spam folder, even though I've tested the regex
> > > > manually). I thought of filtering on the X-Spam-Status header
> > > > instead, but when I had a look at a message that was marked as Spam
> > > > (according to the subject line) I found something rather strange...
>
> Yes, filtering on the SA X-Spam Status or Level headers is the way to
> go. After you found and fixed where SA gets called a second time
> (actually the first time), these won't be harmed and overwritten -- and
> useful for filtering.
>
> Anyway, the secret why the above procmail recipe doesn't work is simply,
> because procmail uses a rather limited sub-set of REs and its own
> flavor. It's not PCRE.
>
> In particular procmail does not understand {x,y} range quantifiers, but
> treats that part as a plain string to match. Which doesn't.
> (Caveat: From memory, not actually looked it up again for verification.)
Ah, thankyou. Despite googling for lots of stuff on procmail I've not been
able to find a definitive reference for what can and can't be used in a
procmail recipe. Maybe I just haven't use the right search terms (or maybe I
just haven't understood what I've read). Anyway, thanks for the clarification.
>
> > > > 3.8 KB_DATE_CONTAINS_TAB KB_DATE_CONTAINS_TAB
> > > > 3.0 IMPOTENCE BODY: Impotence cure
> > > >
> > > >-0.0 BAYES_20 BODY: Bayes spam probability is 5 to
> > > >20%
> > > >
> > > >[score: 0.1050]
> > > >
> > > > 2.0 KB_FAKED_THE_BAT KB_FAKED_THE_BAT
> > > > 1.2 RDNS_NONE Delivered to internal network by a
> > > > host with no
> > > >
> > > >rDNS
>
> Oh, yeah, these do ring quite some bells... ;)
>
> After you fixed your mail processing chain to not have SA chew twice on
> the spam -- you should manually train Bayes, feeding it a lot of hand
> classified spam, and possibly ham. Check your 'sa-learn --dump magic'
> numbers. The Bayes score of 0.1 is way out of line.
Agreed. I do run sa-learn --spam (actually now have it scheduled to run weekly
on a folder into which I drop all the non-classified spam messages) and --ham
(on a folder with messages that were false-positives).
>
> Note though, that a previous site-wide SA filter might use a site-wide
> user, not the one owning the procmail recipe. Thus Bayes scores might
> suddenly change once it's run per user. Check the numbers and
> performance for the user you'll use after fixing the chain issue.
>
> > > You need to fix whatever is causing the message to be scanned twice.
> >
> > OK - that makes sense. Now I'm wondering if there is a global mail config
> > somewhere that is routing the message through SA, and then my local
> > .procmailrc is doing it again. Time to go digging...
>
> Site-wide /etc/procmailrc, SMTP server milter, transport or similar, or
> even something like Amavis in the chain?
There is no /etc/procmailrc, no milter that I'm aware of, running
fetchmail/sendmail/dovecot. This machine doubles as my home mail server/file
server and desktop machine. The only reason I'm running IMAP is so that I can
access the same mail from my laptop or netbook when I need to (and I used to
run squirrelmail to allow access remotely via https webmail, but not any
more).
>
> > That then leaves the question as to why my procmail recipe isn't
> > triggering on the rewritten subject, but that is probably not for this
> > list.
>
> It's sufficiently related. ;) See above.
Thanks again. :-)
--
==
Rodney Baker
rod...@jeremiah31-10.net
web: www.jeremiah31-10.net
==
Re: Inconsistent spam scores between spam headers and rewritten subject line.
On Tue, 16 Aug 2011 05:02:20 John Hardin wrote: > On Tue, 16 Aug 2011, Rodney Baker wrote: > > :0fw: spamassassin.lock > > : > > | spamc > > Just as a test, if you comment that bit out of your personal .procmailrc > does everything work they way you'd expect (i.e. one SA pass, the correct > score in the X- headers)? Yep,that was the first thing that I did. Somehow spamassassin is still checking the messages, even though they're not being piped through spamc via procmail. I'm sure that fetchmail isn't doing it, so that leaves sendmail, dovecot or kmail. So begins the process of elimination (or maybe I just leave it out of procmailrc and be done with it...). Thanks, Rodney. -- ====== Rodney Baker rod...@jeremiah31-10.net web: www.jeremiah31-10.net ==
Re: SELL CVV GOOD ALL COUNTRY,Transfer WU,SHIP LAPTOP( DELL, TOSHIBA,..) IPAD2,IPHONE
On Sat, 9 Jun 2012 16:59:29 Niamh Holding wrote: > Hello best_sellercvv, > > Saturday, June 9, 2012, 7:00:35 AM, you wrote: > > b> Hi every customer > > Oh the irony to see the spamassassin list spammed :) My thoughts exactly... :-) -- ========== Rodney Baker rod...@jeremiah31-10.net web: www.jeremiah31-10.net ==
Compiled rulesets and sa-update
Hi all. I run compiled rulesets on my home mail server (which runs on a Raspberry Pi), which I found necessary to reduce CPU utilisation when it was running on a Raspberry Pi model A (it worked, but it's now on a RasPi 3 which is much better). Do I need to run sa-compile after every sa-update run? Regards, Rodney. -- == Rodney Baker VK5ZTV rodney.ba...@iinet.net.au CCNA #CSCO12880208 ==
Error running sa-update - cannot refresh mirrors file
Hi all, I'm getting the following error when running sa-update on my Raspberry Pi (running spamc/spamd with compiled rulesets); root@mailpi ~ # sa-update --verbose Update available for channel updates.spamassassin.org: 1844624 -> 1844740 http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, FAILED, status: 1792 error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file http: (curl) GET http://sa-update.bitwell.fi/1844740.tar.gz, FAILED, status: 1792 http: (curl) GET http://sa-update.razx.cloud/1844740.tar.gz, success http: (curl) GET http://sa-update.razx.cloud/1844740.tar.gz.sha1, success http: (curl) GET http://sa-update.razx.cloud/1844740.tar.gz.asc, success Update was available, and was downloaded and installed successfully Should I be concerned about the error updating the mirrors file? Thanks in advance, Rodney. -- ====== Rodney Baker VK5ZTV rod...@jeremiah31-10.net CCNA #CSCO12880208 ==
Re: Error running sa-update - cannot refresh mirrors file
On Friday, 26 October 2018 23:46:18 ACDT RW wrote: > On Fri, 26 Oct 2018 22:40:54 +1030 > > Rodney Baker wrote: > > Should I be concerned about the error updating the mirrors file? > > No. sa-update tries to update it after a week so you pick-up new > servers and spread the load, but the old one will probably still be > usable for years. > > The only time it matters is after a SpamAssassin version change when > a new versioned directory is created to hold the rules. Even then you > could just copy over the old MIRRORED.BY file if the server is down. Ok, thanks - that's good to know. Regards, Rodney. -- ========== Rodney Baker rod...@jeremiah31-10.net CCNA #CSCO12880208 ==
Re: Error running sa-update - cannot refresh mirrors file
On Saturday, 27 October 2018 0:14:32 ACDT Kevin A. McGrail wrote: > On 10/26/2018 9:30 AM, Rodney Baker wrote: > > On Friday, 26 October 2018 23:46:18 ACDT RW wrote: > >> On Fri, 26 Oct 2018 22:40:54 +1030 > >> > >> Rodney Baker wrote: > >>> Should I be concerned about the error updating the mirrors file? > >> > >> No. sa-update tries to update it after a week so you pick-up new > >> servers and spread the load, but the old one will probably still be > >> usable for years. > >> > >> The only time it matters is after a SpamAssassin version change when > >> a new versioned directory is created to hold the rules. Even then you > >> could just copy over the old MIRRORED.BY file if the server is down. > > > > Ok, thanks - that's good to know. > > It does concern me that it can't pull the file. I had added an https > redirect which broke a lot of places using a broken version of curl. > > Can you update curl? Is wget available instead and try removing curl? > > Regards, > KAM Hi Kevin. Your reply came to me direct rather than via the mailing list - I suspect my mailer didn't set "Reply-To" correctly when emailing the list. I'll need to fix that. Curl is the latest version available for the Rasbian version running on my box. I'm not thrilled about updating to a newer Raspbian distribution version given that it is so stable as-is. I could try wget instead - does SA require configuration to tell it to use wget instead of curl? If so, where? Thanks Rodney. -- == Rodney Baker rod...@jeremiah31-10.net CCNA #CSCO12880208 ==
Re: Error running sa-update - cannot refresh mirrors file
On 29/10/2018 1:47, RW wrote: On Sun, 28 Oct 2018 21:34:33 +1030 Rodney Baker wrote: On Saturday, 27 October 2018 0:14:32 ACDT Kevin A. McGrail wrote: It does concern me that it can't pull the file. I had added an https redirect which broke a lot of places using a broken version of curl. According to bug 7626 you removed that. I'm not seeing a redirect. Can you update curl? Is wget available instead and try removing curl? Curl is the latest version available for the Rasbian version running on my box. I'm not thrilled about updating to a newer Raspbian distribution version given that it is so stable as-is. I could try wget instead - does SA require configuration to tell it to use wget instead of curl? The easiest thing to do is to temporarily rename curl. Thanks. Did that - it worked with wget instead of curl, successfully downloading the mirrors file and all updates. The last failure with curl was last night. -- ====== Rodney Baker rod...@jeremiah31-10.net CCNA #CSCO12880208 ==
Re: Error running sa-update - cannot refresh mirrors file
On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote:
> On Mon, 29 Oct 2018 09:07:09 -0400
>
> Kevin A. McGrail wrote:
> > On 10/29/2018 8:03 AM, Rodney Baker wrote:
> > > re: renaming curl and using wget
> > >
> > > Thanks. Did that - it worked with wget instead of curl, successfully
> > > downloading the mirrors file and all updates. The last failure with
> > > curl was last night.
>
> Can you try
>
> curl --verbose -L -O --remote-time -g --max-redirs 2 --connect-timeout 30
> --max-time 300 http://spamassassin.apache.org/updates/MIRRORED.BY
> > Then you are likely caught up in the buggy curl we've seen on other
> > distros. Thanks for helping confirm it.
>
> I don't think anything has been confirmed. The problem with curl
> failing on an http uri redirecting to https is no longer relevant, and
> presumably curl has successfully fetched the mirror file since the
> current version of SpamAssassin was installed or there wouldn't be a
> cached copy.
Here's the output from that command:
root@mailpi ~ # curl --verbose -L -O --remote-time -g --max-redirs 2 --
connect-timeout 30 --max-time 300 http://spamassassin.apache.org/updates/
MIRRORED.BY
* Hostname was NOT found in DNS cache
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0*
Trying 40.79.78.1...
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:-- 0*
Connected to spamassassin.apache.org (40.79.78.1) port 80 (#0)
> GET /updates/MIRRORED.BY HTTP/1.1
> User-Agent: curl/7.38.0
> Host: spamassassin.apache.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 31 Oct 2018 12:26:54 GMT
* Server Apache/2.4.18 (Ubuntu) is not blacklisted
< Server: Apache/2.4.18 (Ubuntu)
< Last-Modified: Sat, 27 Oct 2018 16:35:00 GMT
< ETag: "576-579386aca20a2"
< Accept-Ranges: bytes
< Content-Length: 1398
<
{ [data not shown]
100 1398 100 13980 0707 0 0:00:01 0:00:01 --:--:-- 707
* Connection #0 to host spamassassin.apache.org left intact
--
==
Rodney Baker VK5ZTV
rodney.ba...@iinet.net.au
CCNA #CSCO12880208
==
Re: Error running sa-update - cannot refresh mirrors file
On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote:
> On Mon, 29 Oct 2018 09:07:09 -0400
>
> Kevin A. McGrail wrote:
> > On 10/29/2018 8:03 AM, Rodney Baker wrote:
> > > re: renaming curl and using wget
> > >
> > > Thanks. Did that - it worked with wget instead of curl, successfully
> > > downloading the mirrors file and all updates. The last failure with
> > > curl was last night.
>
> Can you try
>
> curl --verbose -L -O --remote-time -g --max-redirs 2 --connect-timeout 30
> --max-time 300 http://spamassassin.apache.org/updates/MIRRORED.BY
> > Then you are likely caught up in the buggy curl we've seen on other
> > distros. Thanks for helping confirm it.
>
> I don't think anything has been confirmed. The problem with curl
> failing on an http uri redirecting to https is no longer relevant, and
> presumably curl has successfully fetched the mirror file since the
> current version of SpamAssassin was installed or there wouldn't be a
> cached copy.
Here's the output from that command:
root@mailpi ~ # curl --verbose -L -O --remote-time -g --max-redirs 2 --
connect-timeout 30 --max-time 300 http://spamassassin.apache.org/updates/
MIRRORED.BY
* Hostname was NOT found in DNS cache
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0*
Trying 40.79.78.1...
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:-- 0*
Connected to spamassassin.apache.org (40.79.78.1) port 80 (#0)
> GET /updates/MIRRORED.BY HTTP/1.1
> User-Agent: curl/7.38.0
> Host: spamassassin.apache.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 31 Oct 2018 12:26:54 GMT
* Server Apache/2.4.18 (Ubuntu) is not blacklisted
< Server: Apache/2.4.18 (Ubuntu)
< Last-Modified: Sat, 27 Oct 2018 16:35:00 GMT
< ETag: "576-579386aca20a2"
< Accept-Ranges: bytes
< Content-Length: 1398
<
{ [data not shown]
100 1398 100 13980 0707 0 0:00:01 0:00:01 --:--:-- 707
* Connection #0 to host spamassassin.apache.org left intact
--
==
Rodney Baker VK5ZTV
rodney.ba...@iinet.net.au
CCNA #CSCO12880208
==
Re: Error running sa-update - cannot refresh mirrors file
On Friday, 2 November 2018 3:45:08 ACDT RW wrote:
> On Wed, 31 Oct 2018 22:59:55 +1030
>
> Rodney Baker wrote:
> > On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote:
> > > curl --verbose -L -O --remote-time -g --max-redirs 2
> > > --connect-timeout 30 --max-time 300
> > > http://spamassassin.apache.org/updates/MIRRORED.BY
> >
> > Here's the output from that command:
> >
> >
> > < HTTP/1.1 200 OK
>
> ...
>
> > { [data not shown]
>
> So curl is working.
Apparently so, at least when run manually. I haven't seen the error repeat for
close to a week now, so whatever the problem was may have been a transient
issue that has now been resolved. I'll keep an eye out and report back if it
happens again.
Regards,
Rodney.
--
==
Rodney Baker
rod...@jeremiah31-10.net
CCNA #CSCO12880208
==
Re: Error running sa-update - cannot refresh mirrors file
On Friday, 2 November 2018 3:45:08 ACDT RW wrote:
> On Wed, 31 Oct 2018 22:59:55 +1030
>
> Rodney Baker wrote:
> > On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote:
> > > curl --verbose -L -O --remote-time -g --max-redirs 2
> > > --connect-timeout 30 --max-time 300
> > > http://spamassassin.apache.org/updates/MIRRORED.BY
> >
> > Here's the output from that command:
> >
> >
> > < HTTP/1.1 200 OK
>
> ...
>
> > { [data not shown]
>
> So curl is working.
So, I got the error reported again. I tried running the curl command suggested
above, and it appeared to complete successfully. I then ran sa-update, and got
the error message.
root@mailpi ~ # curl --verbose -L -O --remote-time -g --max-redirs 2 --
connect-timeout 30 --max-time 300 http://spamassassin.apache.org/updates/
MIRRORED.BY
* Hostname was NOT found in DNS cache
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0* Trying 95.216.24.32...
0 00 00 0 0 0 --:--:-- 0:00:01 --:--:--
0* Connected to spamassassin.apache.org (95.216.24.32) port 80 (#0)
> GET /updates/MIRRORED.BY HTTP/1.1
> User-Agent: curl/7.38.0
> Host: spamassassin.apache.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Tue, 06 Nov 2018 11:36:32 GMT
* Server Apache/2.4.18 (Ubuntu) is not blacklisted
< Server: Apache/2.4.18 (Ubuntu)
< Last-Modified: Sat, 27 Oct 2018 16:35:00 GMT
< ETag: "576-579386aca20a2"
< Accept-Ranges: bytes
< Content-Length: 1398
<
{ [data not shown]
100 1398 100 13980 0615 0 0:00:02 0:00:02 --:--:-- 615
* Connection #0 to host spamassassin.apache.org left intact
root@mailpi ~ # sa-update
error: unable to refresh mirrors file for channel updates.spamassassin.org,
using old file
root@mailpi ~ #
---
This does not appear to be a problem with curl, per se, but rather something
related to sa-update.
--
==
Rodney Baker
rod...@jeremiah31-10.net
CCNA #CSCO12880208
==
