Re: sa-update errors
Am 31.08.2016 um 18:22 schrieb John Hardin: On Wed, 31 Aug 2016, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: > We've had errors the past 2 nights for all of the uridnsbl_skip_domain > rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com I just confirmed that those lines are not in the latest update (1758345, 8/30). Your 8/31 update should not have generated lint errors should is the correct word! TODAY with the 9/01 update the lint-warnings are gone and that's what i meant with "i doubt that the process is working proper" when the change itself was done days ago while every day "sa-update" pulled sucessful 23-Aug-2016 11:46:53: SpamAssassin: Update processed successfully 24-Aug-2016 00:49:42: SpamAssassin: No update available 25-Aug-2016 00:01:12: SpamAssassin: Update processed successfully 26-Aug-2016 00:27:58: SpamAssassin: Update processed successfully 27-Aug-2016 01:15:48: SpamAssassin: Update processed successfully 28-Aug-2016 00:43:06: SpamAssassin: Update processed successfully 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully 01-Sep-2016 00:35:01: SpamAssassin: Update processed successfully
Re: sa-update errors
On 2016-08-31 14:19, Groach wrote: On 31/08/2016 10:32, Axb wrote: I get no errors with spamassassin --lint Nor me. All ok. it possible already fixed ? :=) (ioT humor)
Re: sa-update errors
On Wed, 31 Aug 2016, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: > We've had errors the past 2 nights for all of the uridnsbl_skip_domain > rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zkb.ch Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zugerkb.ch I just confirmed that those lines are not in the latest update (1758345, 8/30). Your 8/31 update should not have generated lint errors. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- People seem to have this obsession with objects and tools as being dangerous in and of themselves, as though a weapon will act of its own accord to cause harm. A weapon is just a force multiplier. It's *humans* that are (or are not) dangerous. --- 253 days since the first successful real return to launch site (SpaceX)
Re: sa-update errors
On 31/08/2016 10:32, Axb wrote: I get no errors with spamassassin --lint Nor me. All ok.
Re: sa-update errors
Am 31.08.2016 um 13:18 schrieb Martin Gregorie: On Wed, 2016-08-31 at 12:25 +0200, Axb wrote: Blame it on the boogie Another data point: I haven't seen this problem. I've just searched my Considering that it doesn't seem to hit everybody, I wonder if it could be software related, i.e. connected with specific Perl package versions. I'm running Fedora 23, fully patched as of last Thursday Fedora 24 x86_64 fully patched perl-5.22.2-362.fc24.x86_64 seems to also make visible errors on other places or make already known more visible like undefined vars in case of invalid uribl dns-calls and so on
Re: sa-update errors
On Wed, 2016-08-31 at 12:25 +0200, Axb wrote: > > Blame it on the boogie > Another data point: I haven't seen this problem. I've just searched my Considering that it doesn't seem to hit everybody, I wonder if it could be software related, i.e. connected with specific Perl package versions. I'm running Fedora 23, fully patched as of last Thursday. Martin
Re: sa-update errors
On 08/31/2016 12:03 PM, li...@rhsoft.net wrote: Am 31.08.2016 um 11:56 schrieb Axb: On 08/31/2016 11:41 AM, li...@rhsoft.net wrote: however, what annoys me more is that "uridnsbl_skip_domain entries have not yet been removed" and obviosuly nobody knows why - what if there would be a issue leading to fatal errors for everybody running "sa-update" and nobody has a clue how to get the fix out and when I don't have a satisfying answer. But maybe someobody else does. what annoys me is that there's a bunch of uridnsbl_skip_domain entries in 25_uribl.cf and nobody complains they are not making problems as also my "/etc/mail/spamassassin/local-06-uridnsbl-skip-domain.cf" without "ifplugin" containing a large list don't make any issue when some show up in 72_active.cf some systems cough over them and I cannot reproduce it. Seems these are not setups from source and something is getting in the way. All I can think of is that the missing "ifplugin" caused this. I'll probably never know if the plugin would be the problem i guess URIBL would not work at all, also see about the 06-uridnsbl-skip-domain.cf above - so the "72_active.cf" issue must be some other problem however, if it is removed and that removal don't appear on setups which did successful "sa-update" calls is *a big problem* because it indicates the "sa-update" process is out of control somewhere All I can say: Don't blame it on the sunshine Don't blame it on the moonlight Don't blame it on the good times Blame it on the boogie *a big problem* is not having a roof over your head, go to sleep hungry, be ill or someone around you is suffering... sa-update is a nice to have... end & off
Re: sa-update errors
Am 31.08.2016 um 11:56 schrieb Axb: On 08/31/2016 11:41 AM, li...@rhsoft.net wrote: however, what annoys me more is that "uridnsbl_skip_domain entries have not yet been removed" and obviosuly nobody knows why - what if there would be a issue leading to fatal errors for everybody running "sa-update" and nobody has a clue how to get the fix out and when I don't have a satisfying answer. But maybe someobody else does. what annoys me is that there's a bunch of uridnsbl_skip_domain entries in 25_uribl.cf and nobody complains they are not making problems as also my "/etc/mail/spamassassin/local-06-uridnsbl-skip-domain.cf" without "ifplugin" containing a large list don't make any issue when some show up in 72_active.cf some systems cough over them and I cannot reproduce it. Seems these are not setups from source and something is getting in the way. All I can think of is that the missing "ifplugin" caused this. I'll probably never know if the plugin would be the problem i guess URIBL would not work at all, also see about the 06-uridnsbl-skip-domain.cf above - so the "72_active.cf" issue must be some other problem however, if it is removed and that removal don't appear on setups which did successful "sa-update" calls is *a big problem* because it indicates the "sa-update" process is out of control somewhere
Re: sa-update errors
On 08/31/2016 11:41 AM, li...@rhsoft.net wrote: Am 31.08.2016 um 11:32 schrieb Axb: On 08/31/2016 11:25 AM, li...@rhsoft.net wrote: Am 31.08.2016 um 11:15 schrieb Axb: On 08/31/2016 10:57 AM, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Just did a manual sa-update -D while the uridnsbl_skip_domain entries have not yet been removed from 72_active.cf I get no "failed to parse line" msgs you get them with "spamassassin --lint" and not due the update - IHMO the subject of this thread is just wrong I get no errors with spamassassin --lint or spamassassin --lint -D :-( however, what annoys me more is that "uridnsbl_skip_domain entries have not yet been removed" and obviosuly nobody knows why - what if there would be a issue leading to fatal errors for everybody running "sa-update" and nobody has a clue how to get the fix out and when I don't have a satisfying answer. But maybe someobody else does. what annoys me is that there's a bunch of uridnsbl_skip_domain entries in 25_uribl.cf and nobody complains when some show up in 72_active.cf some systems cough over them and I cannot reproduce it. Seems these are not setups from source and something is getting in the way. All I can think of is that the missing "ifplugin" caused this. I'll probably never know.
Re: sa-update errors
Am 31.08.2016 um 11:32 schrieb Axb: On 08/31/2016 11:25 AM, li...@rhsoft.net wrote: Am 31.08.2016 um 11:15 schrieb Axb: On 08/31/2016 10:57 AM, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Just did a manual sa-update -D while the uridnsbl_skip_domain entries have not yet been removed from 72_active.cf I get no "failed to parse line" msgs you get them with "spamassassin --lint" and not due the update - IHMO the subject of this thread is just wrong I get no errors with spamassassin --lint or spamassassin --lint -D :-( however, what annoys me more is that "uridnsbl_skip_domain entries have not yet been removed" and obviosuly nobody knows why - what if there would be a issue leading to fatal errors for everybody running "sa-update" and nobody has a clue how to get the fix out and when
Re: sa-update errors
On 08/31/2016 11:25 AM, li...@rhsoft.net wrote: Am 31.08.2016 um 11:15 schrieb Axb: On 08/31/2016 10:57 AM, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zkb.ch Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zugerkb.ch Just did a manual sa-update -D while the uridnsbl_skip_domain entries have not yet been removed from 72_active.cf I get no "failed to parse line" msgs you get them with "spamassassin --lint" and not due the update - IHMO the subject of this thread is just wrong I get no errors with spamassassin --lint or spamassassin --lint -D
Re: sa-update errors
Am 31.08.2016 um 11:15 schrieb Axb: On 08/31/2016 10:57 AM, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zkb.ch Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zugerkb.ch Just did a manual sa-update -D while the uridnsbl_skip_domain entries have not yet been removed from 72_active.cf I get no "failed to parse line" msgs you get them with "spamassassin --lint" and not due the update - IHMO the subject of this thread is just wrong
Re: sa-update errors
On 08/31/2016 10:57 AM, li...@rhsoft.net wrote: Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zkb.ch Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zugerkb.ch Just did a manual sa-update -D while the uridnsbl_skip_domain entries have not yet been removed from 72_active.cf I get no "failed to parse line" msgs
Re: sa-update errors
Am 30.08.2016 um 22:03 schrieb John Hardin: On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck i doubt that the process is working proper or why are the errors after two successful sa-update runs still here? 29-Aug-2016 00:44:41: SpamAssassin: Update processed successfully 30-Aug-2016 01:58:40: SpamAssassin: Update processed successfully 31-Aug-2016 00:49:44: SpamAssassin: Update processed successfully Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zenithbank.com Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zkb.ch Aug 31 10:56:16.871 [28612] warn: config: failed to parse line, skipping, in "/var/lib/spamassassin/3.004001/updates_spamassassin_org/72_active.cf": uridnsbl_skip_domain zugerkb.ch
Re: sa-update errors
On Tue, 30 Aug 2016, Joseph Brennan wrote: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? It's been fixed, waiting for a new update to be generated by masscheck. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- It is criminal to teach a man not to defend himself when he is the constant victim of brutal attacks. -- Malcolm X (1964) --- 252 days since the first successful real return to launch site (SpaceX)
Re: sa-update errors
Am 30.08.2016 um 21:56 schrieb Joseph Brennan: We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? no since there where yesterday at least two treads about this topic, the first by me and AFAIR it should have been fixed last night but wasn't which indicates some problem in the update process when even emergency changes are not pushed relieable (besides they would not be pushed when the mass-check did not have enough samples, but in that case sa-update would not have done anything at all)
sa-update errors
We've had errors the past 2 nights for all of the uridnsbl_skip_domain rules. It's just us? Redhat 2.6.32-504.3.3.el6.x86_64 > spamassassin -V SpamAssassin version 3.4.0 running on Perl version 5.10.1 I'm inserting blank lines for clarity, in case my email client starts wrapping: config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain 1stnationalbank.com config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain 365online.com config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain 53.com config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain abl.com.pk config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain accessbankplc.com ... config: failed to parse line, skipping, in "/tmp/.spamassassin17852Aeax7dtmp/72_active.cf": uridnsbl_skip_domain zugerkb.ch channel: lint check of update failed, channel failed Joseph Brennan Columbia University Information Technology
sa-update errors
I get errors like this when I run sa-update from cron /usr/local/bin/setlock -n /tmp/cronlock.4051759.53932 sh -c $'/home/skipmorrow/bin/sa-update --gpgkey 6C6191E3 --channel sought.rules.yerp.org' gpg: WARNING: unsafe ownership on homedir `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys' gpg: failed to create temporary file `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/.#lk0x5d7320.ps11651.23686': Permission denied gpg: keyblock resource`/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/secring.gpg': general error gpg: failed to create temporary file `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/.#lk0x5d7320.ps11651.23686': Permission denied gpg: keyblock resource `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/pubring.gpg': general error gpg: no writable keyring found: eof gpg: error reading `/home/skipmorrow/share/spamassassin/sa-update-pubkey.txt': general error gpg: import from `/home/skipmorrow/share/spamassassin/sa-update-pubkey.txt' failed: general error But when I run it from a login shell, it doesn't show those errors. So I wrote a cript to verify that the cron job is running as the correct user by putting in whoami, and indeed it is running as skipmorrow skipmor...@ps11651:~$ ls etc/mail/spamassassin/sa-update-keys/ -la total 28 drwx-- 2 skipmorrow pg652 4096 Jul 20 00:00 . drwxr-xr-x 3 skipmorrow pg652 4096 Jul 17 13:29 .. -rw--- 1 skipmorrow pg652 5123 Jul 17 14:29 pubring.gpg -rw--- 1 skipmorrow pg652 4505 Jul 17 13:32 pubring.gpg~ -rw--- 1 skipmorrow pg6520 Jul 17 13:29 secring.gpg -rw--- 1 skipmorrow pg652 1200 Jul 17 13:29 trustdb.gpg skipmor...@ps11651:~$ ls .gnupg/ -la total 24 drwx-- 2 skipmorrow pg652 4096 Jul 10 13:27 . drwxr-x--x 30 skipmorrow pg652 4096 Jul 20 03:48 .. -rw--- 1 skipmorrow pg652 4128 Jul 10 13:27 pubring.gpg -rw--- 1 skipmorrow pg652 3039 Jul 10 13:27 pubring.gpg~ -rw--- 1 skipmorrow pg6520 Jul 10 13:27 secring.gpg -rw--- 1 skipmorrow pg652 1200 Jul 10 13:27 trustdb.gpg should sa-update be looking for keys in ~/.gnupg? Or is it working correctly? What environment variable does sa-learn and gnupg look for that would be present in my login shell but not be present when running in a cron environment? -- View this message in context: http://www.nabble.com/sa-update-errors-tp24569115p24569115.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: sa-update errors
MrGibbage wrote: I get errors like this when I run sa-update from cron /usr/local/bin/setlock -n /tmp/cronlock.4051759.53932 sh -c $'/home/skipmorrow/bin/sa-update --gpgkey 6C6191E3 --channel sought.rules.yerp.org' gpg: WARNING: unsafe ownership on homedir `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys' gpg: failed to create temporary file `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/.#lk0x5d7320.ps11651.23686': Permission denied gpg: keyblock resource`/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/secring.gpg': general error gpg: failed to create temporary file `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/.#lk0x5d7320.ps11651.23686': Permission denied gpg: keyblock resource `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/pubring.gpg': general error gpg: no writable keyring found: eof gpg: error reading `/home/skipmorrow/share/spamassassin/sa-update-pubkey.txt': general error gpg: import from `/home/skipmorrow/share/spamassassin/sa-update-pubkey.txt' failed: general error But when I run it from a login shell, it doesn't show those errors. So I wrote a cript to verify that the cron job is running as the correct user by putting in whoami, and indeed it is running as skipmorrow skipmor...@ps11651:~$ ls etc/mail/spamassassin/sa-update-keys/ -la total 28 drwx-- 2 skipmorrow pg652 4096 Jul 20 00:00 . drwxr-xr-x 3 skipmorrow pg652 4096 Jul 17 13:29 .. -rw--- 1 skipmorrow pg652 5123 Jul 17 14:29 pubring.gpg -rw--- 1 skipmorrow pg652 4505 Jul 17 13:32 pubring.gpg~ -rw--- 1 skipmorrow pg6520 Jul 17 13:29 secring.gpg -rw--- 1 skipmorrow pg652 1200 Jul 17 13:29 trustdb.gpg skipmor...@ps11651:~$ ls .gnupg/ -la total 24 drwx-- 2 skipmorrow pg652 4096 Jul 10 13:27 . drwxr-x--x 30 skipmorrow pg652 4096 Jul 20 03:48 .. -rw--- 1 skipmorrow pg652 4128 Jul 10 13:27 pubring.gpg -rw--- 1 skipmorrow pg652 3039 Jul 10 13:27 pubring.gpg~ -rw--- 1 skipmorrow pg6520 Jul 10 13:27 secring.gpg -rw--- 1 skipmorrow pg652 1200 Jul 10 13:27 trustdb.gpg should sa-update be looking for keys in ~/.gnupg? No, it should not be looking in .gnupg. That would be the location for keys you use. The keys used by sa-update are application specific, so why would you want them on the keyring you use for email? Or is it working correctly? Well, it's not working correctly, as you're having errors :) What environment variable does sa-learn and gnupg look for that would be present in my login shell but not be present when running in a cron environment? I don't think it's missing an enviornment variable. Are you sure the cronjob is running with an effective userid of skipmorrow? This message: gpg: failed to create temporary file `/home/skipmorrow/etc/mail/spamassassin/sa-update-keys/.#lk0x5d7320.ps11651.23686': Permission denied Strongly suggests you've got a permissions issue, where the cronjob is running as a user that can't create files in /home/skipmorrow/etc/mail/spamassassin/sa-update-keys/ . Since skipmorrow has rwx, that suggests the cronjob is running as some other userid (probably cron or some other system account).
Re: sa-update errors
Thanks, Matt. I call my sa-update in a script from cron. I don't think I have a permissions problem, but I agree, that is what it looks like. Perhaps this will shed a little light. skipmor...@ps11651:~$ id uid=15203(skipmorrow) gid=588771(pg652) groups=588771(pg652) skipmor...@ps11651:~$ whoami skipmorrow skipmor...@ps11651:~$ crontab -l ###--- BEGIN DREAMHOST BLOCK ###--- Changes made to this part of the file WILL be destroyed! # sa-update JM_SOUGHT MAILTO=s...@pelorus.org @hourly /usr/local/bin/setlock -n /tmp/cronlock.4061564.53932 sh -c $'/home/skipmorrow/update_sa_rules.sh' ###--- You can make changes below the next line and they will be preserved! ###--- END DREAMHOST BLOCK skipmor...@ps11651:~$ tail sa_update.log Mon Jul 20 07:00:04 PDT 2009 Who Am I: skipmorrow id: uid=15203(skipmorrow) gid=588771(pg652) groups=588771(pg652) skipmor...@ps11651:~$ cat update_sa_rules.sh #!/bin/bash echo `date`/home/skipmorrow/sa_update.log echo Who Am I: `whoami`/home/skipmorrow/sa_update.log echo id: `id`/home/skipmorrow/sa_update.log echo /home/skipmorrow/sa_update.log /home/skipmorrow/bin/sa-update -D --gpgkey 6C6191E3 --channel sought.rules.yerp.org --gpghomedir /home/skipmorrow/etc/mail/spamassassin/sa-update-keys I just recently added the gpghomedir, but that didn't make a difference at all to the error messages, and I wouldn't have expected it to make a difference, since sa-update is finding that directory on its own anyway. I would be most appreciative of any other ideas that you may have. Skip -- View this message in context: http://www.nabble.com/sa-update-errors-tp24569115p24570739.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: sa-update errors
On 18/02/2008 7:29 AM, Arthur Dent wrote: Gentle Bump... I thought that the approved place to alter scores was in /etc/mail/spamassassin/local.cf so I have not gone rooting around trying to give these rules scores which surely they should have by default? What exactly do you mean. The two halfs of the sentence make no sense when combined. OK Sorry - My lack of understanding of exactly what the error(s) means meant that I made a poor stab at explaining it. The error message says: score undef for rule which I take to mean that there is to score assigned to this particular rule. Is that correct? So my question was - if that's what it means - Why is there no score for these rules? I have not tinkered with anything (that I know of). I have never seen this error before. And I guess, because I was searching for a solution, should I be assigning scores manually?... Are these new rules? Obsolete rules? Altered rules? Why the sudden error? I can't remember right now what exactly you have to break to cause these errors. Does your channel file sare-sa-update-channels.txt, include the channel updates.spamassassin.org? Yup... Have you recently attempted an upgrade of SpamAssassin? Nope... Daryl Or have I misunderstood something? Thanks... Mark Any suggestions gratefully received! Thanks Mark On Thu, Feb 14, 2008 at 02:27:40PM -, Arthur Dent wrote: Hello all, I run a bog-standard out-of-the-box (Fedora 8) SA (v.3.2.4) installation. Every night I run: sa-update --channelfile /etc/mail/spamassassin/sare-sa-update-channels.txt --gpgkey 856AA88A /sbin/service spamassassin restart as a cron job. Never been a problem before. But this morning I find this in my root email: rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at
Re: sa-update errors
On Fri, Feb 29, 2008 at 09:40:24AM -, Arthur Dent wrote: On 18/02/2008 7:29 AM, Arthur Dent wrote: Gentle Bump... I thought that the approved place to alter scores was in /etc/mail/spamassassin/local.cf so I have not gone rooting around trying to give these rules scores which surely they should have by default? What exactly do you mean. The two halfs of the sentence make no sense when combined. OK Sorry - My lack of understanding of exactly what the error(s) means meant that I made a poor stab at explaining it. The error message says: score undef for rule which I take to mean that there is to score assigned to this particular rule. Is that correct? ^^ that there is *no* score assigned... (sorry!) So my question was - if that's what it means - Why is there no score for these rules? I have not tinkered with anything (that I know of). I have never seen this error before. And I guess, because I was searching for a solution, should I be assigning scores manually?... Are these new rules? Obsolete rules? Altered rules? Why the sudden error? I can't remember right now what exactly you have to break to cause these errors. Does your channel file sare-sa-update-channels.txt, include the channel updates.spamassassin.org? Yup... Have you recently attempted an upgrade of SpamAssassin? Nope... Daryl Or have I misunderstood something? Thanks... Mark Any suggestions gratefully received! Thanks Mark On Thu, Feb 14, 2008 at 02:27:40PM -, Arthur Dent wrote: Hello all, I run a bog-standard out-of-the-box (Fedora 8) SA (v.3.2.4) installation. Every night I run: sa-update --channelfile /etc/mail/spamassassin/sare-sa-update-channels.txt --gpgkey 856AA88A /sbin/service spamassassin restart as a cron job. Never been a problem before. But this morning I find this in my root email: rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at
sa-update errors
, near } 1 (Missing operator before 1?) rules: failed to run header tests, skipping some: syntax error at (eval 105) line 6, at EOF Global symbol $plugin requires explicit package name at (eval 105) line 7. syntax error at (eval 105) line 11, near ; } Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Number found where operator expected at (eval 106) line 10, near } 1 (Missing operator before 1?) rules: failed to run header tests, skipping some: syntax error at (eval 106) line 6, at EOF Global symbol $plugin requires explicit package name at (eval 106) line 7. syntax error at (eval 106) line 11, near ; } Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Number found where operator expected at (eval 107) line 10, near } 1 (Missing operator before 1?) rules: failed to run header tests, skipping some: syntax error at (eval 107) line 6, at EOF Global symbol $plugin requires explicit package name at (eval 107) line 7. syntax error at (eval 107) line 11, near ; } Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm line 2669. Number found where operator expected at (eval 108) line 10, near } 1 (Missing operator before 1?) rules: failed to run header tests, skipping some: syntax error at (eval 108) line 6, at EOF Global symbol $plugin requires explicit package name at (eval 108) line 7. syntax error at (eval 108) line 11, near ; } -- View this message in context: http://www.nabble.com/sa-update-errors-tp15746399p15746399.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: sa-update errors
On 18/02/2008 7:29 AM, Arthur Dent wrote: Gentle Bump... I thought that the approved place to alter scores was in /etc/mail/spamassassin/local.cf so I have not gone rooting around trying to give these rules scores which surely they should have by default? What exactly do you mean. The two halfs of the sentence make no sense when combined. Are these new rules? Obsolete rules? Altered rules? Why the sudden error? I can't remember right now what exactly you have to break to cause these errors. Does your channel file sare-sa-update-channels.txt, include the channel updates.spamassassin.org? Have you recently attempted an upgrade of SpamAssassin? Daryl Or have I misunderstood something? Thanks... Mark On Thu, Feb 14, 2008 at 02:27:40PM -, Arthur Dent wrote: Hello all, I run a bog-standard out-of-the-box (Fedora 8) SA (v.3.2.4) installation. Every night I run: sa-update --channelfile /etc/mail/spamassassin/sare-sa-update-channels.txt --gpgkey 856AA88A /sbin/service spamassassin restart as a cron job. Never been a problem before. But this morning I find this in my root email: rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at
Re: sa-update errors
Gentle Bump... I thought that the approved place to alter scores was in /etc/mail/spamassassin/local.cf so I have not gone rooting around trying to give these rules scores which surely they should have by default? Are these new rules? Obsolete rules? Altered rules? Why the sudden error? Or have I misunderstood something? Thanks... Mark On Thu, Feb 14, 2008 at 02:27:40PM -, Arthur Dent wrote: Hello all, I run a bog-standard out-of-the-box (Fedora 8) SA (v.3.2.4) installation. Every night I run: sa-update --channelfile /etc/mail/spamassassin/sare-sa-update-channels.txt --gpgkey 856AA88A /sbin/service spamassassin restart as a cron job. Never been a problem before. But this morning I find this in my root email: rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in
sa-update errors
Hello all, I run a bog-standard out-of-the-box (Fedora 8) SA (v.3.2.4) installation. Every night I run: sa-update --channelfile /etc/mail/spamassassin/sare-sa-update-channels.txt --gpgkey 856AA88A /sbin/service spamassassin restart as a cron job. Never been a problem before. But this morning I find this in my root email: rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'NO_RECEIVED' in '' 'NO_RECEIVED' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'MISSING_SUBJECT' in '' 'MISSING_SUBJECT' at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2140. rules: score undef for rule 'EMPTY_MESSAGE' in '' 'EMPTY_MESSAGE' at
Re: sa-update errors out with no mirror data available for channel updates.spamassassin.org
From: Daryl C. W. O'Shea [EMAIL PROTECTED]
ahattarki wrote:
[4724] dbg: http: GET request,
http://spamassassin.apache.org/updates/MIRRORED.BY
[4724] dbg: http: request failed, retrying: 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error)
Any ideas what could be causing this ?
Firewalled tcp/80?
Put in a delay for each file you test and fetch.
Otherwise you trigger prolexic's DoS detector.
I had to do that with my GetRules.sh script.
{^_^}
Re: sa-update errors out with no mirror data available for channel updates.spamassassin.org
jdow wrote: From: Daryl C. W. O'Shea [EMAIL PROTECTED] ahattarki wrote: [4724] dbg: http: GET request, http://spamassassin.apache.org/updates/MIRRORED.BY [4724] dbg: http: request failed, retrying: 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error) Any ideas what could be causing this ? Firewalled tcp/80? Put in a delay for each file you test and fetch. Otherwise you trigger prolexic's DoS detector. Prolexic has nothing to do with apache.org. Daryl
sa-update errors out with no mirror data available for channel updates.spamassassin.org
We are currently running - SpamAssassin for Win32 v3.1.7.0
downloaded sa-update sa-update v3.1.7.0
After running D:\SpamAssassinsa-update.exe --nogpg
I get the following error -
http: request failed: 500 Can't connect to spamassassin.apache.org:80
(connect:
Unknown error): 500 Can't connect to spamassassin.apache.org:80 (connect:
Unknow
n error)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
Running with -D gives me the following stack -
D:\SpamAssassinsa-update.exe --nogpg -D
[4724] dbg: logger: adding facilities: all
[4724] dbg: logger: logging level is DBG
[4724] dbg: generic: SpamAssassin version 3.1.7
[4724] dbg: config: score set 0 chosen.
[4724] dbg: util: defining getpwuid() wrapper using 'unknown' as username
[4724] dbg: message: MIME PARSER START
[4724] dbg: message: main message type: text/plain
[4724] dbg: message: parsing normal part
[4724] dbg: message: added part, type: text/plain
[4724] dbg: message: MIME PARSER END
[4724] dbg: dns: is Net::DNS::Resolver available? yes
[4724] dbg: dns: Net::DNS version: 0.59
[4724] dbg: generic: sa-update version svn454083
[4724] dbg: generic: using update directory: ./share/3.001007
[4724] dbg: diag: perl platform: 5.008006 MSWin32
[4724] dbg: diag: module installed: Digest::SHA1, version 2.10
[4724] dbg: diag: module installed: DB_File, version 1.810
[4724] dbg: diag: module installed: HTML::Parser, version 3.54
[4724] dbg: diag: module installed: MIME::Base64, version 3.05
[4724] dbg: diag: module installed: Net::DNS, version 0.59
[4724] dbg: diag: module installed: Net::SMTP, version 2.29
[4724] dbg: diag: module installed: Mail::SPF::Query, version 1.997
[4724] dbg: diag: module installed: IP::Country::Fast, version 309.002
[4724] dbg: diag: module installed: Razor2::Client::Agent, version 2.82
[4724] dbg: diag: module not installed: Net::Ident ('require' failed)
[4724] dbg: diag: module installed: IO::Socket::INET6, version 2.51
[4724] dbg: diag: module installed: IO::Socket::SSL, version 0.96
[4724] dbg: diag: module installed: Time::HiRes, version 1.65
[4724] dbg: diag: module installed: DBI, version 1.47
[4724] dbg: diag: module installed: Getopt::Long, version 2.34
[4724] dbg: diag: module installed: LWP::UserAgent, version 2.033
[4724] dbg: diag: module installed: HTTP::Date, version 1.46
[4724] dbg: diag: module installed: Archive::Tar, version 1.29
[4724] dbg: diag: module installed: IO::Zlib, version 1.04
[4724] dbg: channel: attempting channel updates.spamassassin.org
[4724] dbg: channel: update directory
share\3.001007\updates_spamassassin_org
[4724] dbg: channel: channel cf file
share\3.001007\updates_spamassassin_org.cf
[4724] dbg: channel: channel pre file
share\3.001007\updates_spamassassin_org.pr
e
[4724] dbg: dns: 7.1.3.updates.spamassassin.org = 507739, parsed as 507739
[4724] dbg: channel: no MIRRORED.BY file available
[4724] dbg: http: GET request,
http://spamassassin.apache.org/updates/MIRRORED.BY
[4724] dbg: http: request failed, retrying: 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error)
[4724] dbg: http: GET request,
http://spamassassin.apache.org/updates/MIRRORED.BY
[4724] dbg: http: request failed, retrying: 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error)
[4724] dbg: http: GET request,
http://spamassassin.apache.org/updates/MIRRORED.BY
[4724] dbg: http: request failed, retrying: 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to
spamassassin.apache.org:80 (connect: Unknown error)
http: request failed: 500 Can't connect to spamassassin.apache.org:80
(connect:Unknown error): 500 Can't connect to spamassassin.apache.org:80
(connect: Unknown error)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
[4724] dbg: diag: updates complete, exiting with code 4
Any ideas what could be causing this ?
Thanks,
Anjali
--
View this message in context:
http://www.nabble.com/sa-update-errors-out-with-no-mirror-data-available-for-channel-updates.spamassassin.org-tf3997492.html#a11353096
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: sa-update errors out with no mirror data available for channel updates.spamassassin.org
ahattarki wrote: [4724] dbg: http: GET request, http://spamassassin.apache.org/updates/MIRRORED.BY [4724] dbg: http: request failed, retrying: 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error) Any ideas what could be causing this ? Firewalled tcp/80?
Re: sa-update errors out with no mirror data available for channel updates.spamassassin.org
On Thu, Jun 28, 2007 at 05:18:50PM -0700, ahattarki wrote: [4724] dbg: http: GET request, http://spamassassin.apache.org/updates/MIRRORED.BY [4724] dbg: http: request failed, retrying: 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error): 500 Can't connect to spamassassin.apache.org:80 (connect: Unknown error) Any ideas what could be causing this ? Hrm. Either the apache site had issues, although it's odd you'd get a 500 which is Internal Server Error for a request for a static text file. Or perhaps you either are trying to go through a proxy, or need to go through a proxy? If you request that file in a browser, does it work? It's working fine for me right now fwiw. -- Randomly Selected Tagline: In a few minutes a computer can make a mistake so great that it would have taken many men many months to equal it. - Unknown pgpEvykk4uSpe.pgp Description: PGP signature
sa-update errors with 3.1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - From this morning's log from three of our MX servers running SA 3.1.7. Does the channel for 3.1.7 have the wrong rules? config: configuration file /tmp/.spamassassin8654JTlidztmp/20_advance_fee.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_body_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_compensate.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_dnsbl_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_drugs.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_fake_helo_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_head_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_html_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_meta_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_net_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_phrases.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_porn.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_uri_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/23_bayes.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/72_active.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: warning: score set for non-existent rule
Re: sa-update errors with 3.1.7
Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. By the way this is _totally_ harmless -- since the lint check failed, sa-update didn't make any change to the existing ruleset. --j. Steven Stern writes: - From this morning's log from three of our MX servers running SA 3.1.7. Does the channel for 3.1.7 have the wrong rules? config: configuration file /tmp/.spamassassin8654JTlidztmp/20_advance_fee.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_body_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_compensate.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_dnsbl_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_drugs.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_fake_helo_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_head_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_html_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_meta_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_net_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_phrases.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_porn.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_uri_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/23_bayes.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/72_active.cf requires version 3.002000 of SpamAssassin, but this is code
Re: sa-update errors with 3.1.7
On Mon, Jan 01, 2007 at 07:11:03PM +, Justin Mason wrote: Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. Um. No, I didn't. In fact, I upgraded my machines right after pushing the upgrade. Doing a little digging, it appears that a 3.2.0 update got pushed out with the same number and overwrote the 3.1 update. Speciically: $ head -1 /var/lib/spamassassin/3.001007/updates_spamassassin_org.cf # UPDATE version 491519 Looking at the updates dir: -r--r--r-- 1 updatesd other 118681 Jan 1 08:50 491519.tar.gz -r--r--r-- 1 updatesd other823 Jan 1 08:50 491519.tar.gz.asc -r--r--r-- 1 updatesd other 84 Jan 1 08:50 491519.tar.gz.sha1 Untarring that file does show a 3.2 update tree. Note the time on the file is 0850 GMT (0350 EST) on 1/1, and I pushed the update around 2030 EST on 12/31. So ... Bug in JM's code, not checking if there's already an update with that rev number? :P (looks like run_part2, lines 142-144 btw) -- Randomly Selected Tagline: I have a switch in my apartment that doesn't do anything. Every once in a while I turn it on and off. On and off. On and off. One day I got a call from a woman in France who said Cut it out! -- Steven Wright pgpKfUxW8wGyo.pgp Description: PGP signature
Re: sa-update errors with 3.1.7
On Tue, 2 Jan 2007 02:16:56 -0500, Theo Van Dinter [EMAIL PROTECTED] wrote: On Mon, Jan 01, 2007 at 07:11:03PM +, Justin Mason wrote: Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. Um. No, I didn't. In fact, I upgraded my machines right after pushing the upgrade. Doing a little digging, it appears that a 3.2.0 update got pushed out with the same number and overwrote the 3.1 update. Speciically: $ head -1 /var/lib/spamassassin/3.001007/updates_spamassassin_org.cf # UPDATE version 491519 Looking at the updates dir: -r--r--r-- 1 updatesd other 118681 Jan 1 08:50 491519.tar.gz -r--r--r-- 1 updatesd other823 Jan 1 08:50 491519.tar.gz.asc -r--r--r-- 1 updatesd other 84 Jan 1 08:50 491519.tar.gz.sha1 Untarring that file does show a 3.2 update tree. Note the time on the file is 0850 GMT (0350 EST) on 1/1, and I pushed the update around 2030 EST on 12/31. So ... Bug in JM's code, not checking if there's already an update with that rev number? :P (looks like run_part2, lines 142-144 btw) It went in clean on all servers when I ran it this morning. I guess you fixed whatever the issue was? Kind regards Nigel
Re: sa-update errors with 3.1.7
On Tue, Jan 02, 2007 at 07:21:02AM +, Nigel Frankcom wrote: It went in clean on all servers when I ran it this morning. I guess you fixed whatever the issue was? I believe the order of what happened was: - I pushed the update on the evening of 12/31 - In the morning of 1/1, the automatic 3.2 update process pushed out an update with the same revision number, overwriting the 3.1 file - JM pushed out a new 3.1 update package So it's working now, but there was a time where the 3.1 channel pointed at a 3.2 file. Needless to say, the automatic update script needs at least a if [ -f ... ] snippet to avoid overwriting existing files. -- Randomly Selected Tagline: A CAT scan should take less time than a PET scan. For a CAT scan, they're only looking for one thing, whereas a PET scan could result in a lot of things. - Carl Princi, 2002/07/19 pgpJOrb0YrRZJ.pgp Description: PGP signature
