Re: What happened to SOUGHT rules' server?
On 2010/03/16 5:03 PM, Karsten Bräckelmann wrote: How is this messing you up? This should not affect any of your other channels. The only effect is that the sought rules don't get updated. I'm not sure how everyone else is doing it, but my script checks for updates using --channelfile, then runs sa-compile if sa-update returns 0. If a channel fails, sa-update returns something other than 0. Sure, my old rules are intact and the server continues to run normally, but I'm not getting the benefit of updates in other channels. This sounds like an improvement to sa-compile would be beneficial, so as to distinguish 'some updates available' from 'none' and 'all ok, updated'. Please open a feature request. s/compile/update/# :) In order to properly open a feature request, I'd like to get a better idea where you're going with this. It seems to me that a new exit code from sa-update would be more appropriate than running sa-compile every time just in case. Maybe I misunderstand? Yup, seems that is it. There are only all-or-nothing exit codes (0 and 4 respectively) in this scenario. It looks like the SOUGHT server is having issues again, so Bug 6380 is again relevant. Does anyone know the status of the SOUGHT server or if any work has been done on the bug? https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6380 -- /Jason smime.p7s Description: S/MIME Cryptographic Signature
Re: What happened to SOUGHT rules' server?
On Thu, 2010-10-14 at 12:30 -0400, Jason Bertoch wrote:
On 2010/03/16 5:03 PM, Karsten Bräckelmann wrote:
In order to properly open a feature request, I'd like to get a better
idea where you're going with this. It seems to me that a new exit code
from sa-update would be more appropriate than running sa-compile every
time just in case. Maybe I misunderstand?
Yup, seems that is it. There are only all-or-nothing exit codes (0 and 4
respectively) in this scenario.
It looks like the SOUGHT server is having issues again, so Bug 6380 is
again relevant. Does anyone know the status of the SOUGHT server or if
*Had* have issues today, for about 10 hours +/- 2 according to my logs.
Granted, you sent this shortly before the issue has been resolved. ;)
I can confirm there have been issues with a missing update tarball, the
server appeared to be responsive all the while. I also can confirm
operation is back to normal since a couple hours ago.
any work has been done on the bug?
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6380
According to the bug, quite obviously, no one has been working on it.
Until your patch just today. Thanks!
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: What happened to SOUGHT rules' server?
On 10/14/2010 5:30 PM, Karsten Bräckelmann wrote: any work has been done on the bug? https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6380 According to the bug, quite obviously, no one has been working on it. Until your patch just today. Thanks! Yes, I decided this was a logic issue and probably required little knowledge of perl, in which I have none. In the end, the change was trivial, to me at least. We'll see what the real devs think, though. /Jason
Re: What happened to SOUGHT rules' server?
On Monday 15 March 2010, Daryl C. W. O'Shea wrote: On 15/03/2010 11:07 PM, j wrote: I've been having the same problem from several locations/ISPs, since mid-Saturday. 500 Can't connect to yerp.org:80 (connect: timeout) Dave Anyone figure this out? I have received the same yerp.org down errors and it's screwing up my SA royally. I guess this is what we get when we rely on external sources to help us at no charge.. :( Just so I understand your use case, so we can improve sa-update... how is it that a failing channel is royally screwing up your SA? Thanks! Daryl FWIW, my weekly sa-update from yerp.org also failed. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) I consider the day misspent that I am not either charged with a crime, or arrested for one. -- Ratsy Tourbillon
Re: What happened to SOUGHT rules' server?
j wrote: I've been having the same problem from several locations/ISPs, since mid-Saturday. 500 Can't connect to yerp.org:80 (connect: timeout) Dave Anyone figure this out? I have received the same yerp.org down errors and it's screwing up my SA royally. I guess this is what we get when we rely on external sources to help us at no charge.. :( It appears to be having intermittent problems. It has only failed 2 out of the last 7 times I've checked it. How is this messing you up? This should not affect any of your other channels. The only effect is that the sought rules don't get updated. -- Bowie
Re: What happened to SOUGHT rules' server?
On 2010/03/16 9:30 AM, Bowie Bailey wrote: How is this messing you up? This should not affect any of your other channels. The only effect is that the sought rules don't get updated. I'm not sure how everyone else is doing it, but my script checks for updates using --channelfile, then runs sa-compile if sa-update returns 0. If a channel fails, sa-update returns something other than 0. Sure, my old rules are intact and the server continues to run normally, but I'm not getting the benefit of updates in other channels. Perhaps I should replace --channelfile with a loop instead, though it seems to me that caused other problems. -- /Jason smime.p7s Description: S/MIME Cryptographic Signature
Re: What happened to SOUGHT rules' server?
On Tuesday 16 March 2010 19:37:02 Jason Bertoch wrote: On 2010/03/16 9:30 AM, Bowie Bailey wrote: How is this messing you up? This should not affect any of your other channels. The only effect is that the sought rules don't get updated. I'm not sure how everyone else is doing it, but my script checks for updates using --channelfile, then runs sa-compile if sa-update returns 0. If a channel fails, sa-update returns something other than 0. Sure, my old rules are intact and the server continues to run normally, but I'm not getting the benefit of updates in other channels. This sounds like an improvement to sa-compile would be beneficial, so as to distinguish 'some updates available' from 'none' and 'all ok, updated'. Please open a feature request. Mark
Re: What happened to SOUGHT rules' server?
On 2010/03/16 2:44 PM, Mark Martinec wrote: On Tuesday 16 March 2010 19:37:02 Jason Bertoch wrote: On 2010/03/16 9:30 AM, Bowie Bailey wrote: How is this messing you up? This should not affect any of your other channels. The only effect is that the sought rules don't get updated. I'm not sure how everyone else is doing it, but my script checks for updates using --channelfile, then runs sa-compile if sa-update returns 0. If a channel fails, sa-update returns something other than 0. Sure, my old rules are intact and the server continues to run normally, but I'm not getting the benefit of updates in other channels. This sounds like an improvement to sa-compile would be beneficial, so as to distinguish 'some updates available' from 'none' and 'all ok, updated'. Please open a feature request. Mark, In order to properly open a feature request, I'd like to get a better idea where you're going with this. It seems to me that a new exit code from sa-update would be more appropriate than running sa-compile every time just in case. Maybe I misunderstand? /Jason smime.p7s Description: S/MIME Cryptographic Signature
Re: What happened to SOUGHT rules' server?
Jason, In order to properly open a feature request, I'd like to get a better idea where you're going with this. It seems to me that a new exit code from sa-update would be more appropriate than running sa-compile every time just in case. Maybe I misunderstand? Yes, that's what I had in mind. Or a short and concise message written to stdout or stderr when a verbose option (-v) is used. One or the other or both, so as to make shell scripting easier for cases like you came across. I didn't consider it thoroughly, so this is just a suggestion that came up first to my head. Mark
Re: What happened to SOUGHT rules' server?
How is this messing you up? This should not affect any of your other
channels. The only effect is that the sought rules don't get updated.
I'm not sure how everyone else is doing it, but my script checks for
updates using --channelfile, then runs sa-compile if sa-update returns
0. If a channel fails, sa-update returns something other than 0. Sure,
my old rules are intact and the server continues to run normally, but
I'm not getting the benefit of updates in other channels.
This sounds like an improvement to sa-compile would be beneficial,
so as to distinguish 'some updates available' from 'none' and
'all ok, updated'. Please open a feature request.
s/compile/update/# :)
In order to properly open a feature request, I'd like to get a better
idea where you're going with this. It seems to me that a new exit code
from sa-update would be more appropriate than running sa-compile every
time just in case. Maybe I misunderstand?
Yup, seems that is it. There are only all-or-nothing exit codes (0 and 4
respectively) in this scenario.
However, not even close to royally screwing update, as per some
earlier comment.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: What happened to SOUGHT rules' server?
I've been having the same problem from several locations/ISPs, since mid-Saturday. 500 Can't connect to yerp.org:80 (connect: timeout) Dave Anyone figure this out? I have received the same yerp.org down errors and it's screwing up my SA royally. I guess this is what we get when we rely on external sources to help us at no charge.. :(
Re: What happened to SOUGHT rules' server?
On 15/03/2010 11:07 PM, j wrote: I've been having the same problem from several locations/ISPs, since mid-Saturday. 500 Can't connect to yerp.org:80 (connect: timeout) Dave Anyone figure this out? I have received the same yerp.org down errors and it's screwing up my SA royally. I guess this is what we get when we rely on external sources to help us at no charge.. :( Just so I understand your use case, so we can improve sa-update... how is it that a failing channel is royally screwing up your SA? Thanks! Daryl
What happened to SOUGHT rules' server?
It seems that the yerp.org www server is irresponsive. To my knowledge, that server was hosting the sought.rules.yerp.org update channel. Anybody knows if it is a transient problem or if that channel moved elsewhere? Regards, Giampaolo
Re: What happened to SOUGHT rules' server?
Giampaolo Tomassoni a écrit : It seems that the yerp.org www server is irresponsive. To my knowledge, that server was hosting the sought.rules.yerp.org update channel. Anybody knows if it is a transient problem or if that channel moved elsewhere? it was working yesterday. most probably a transient problem.
Re: What happened to SOUGHT rules' server?
On Sun, Mar 14, 2010 at 3:13 AM, Giampaolo Tomassoni g.tomass...@libero.it wrote: It seems that the yerp.org www server is irresponsive. To my knowledge, that server was hosting the sought.rules.yerp.org update channel. Anybody knows if it is a transient problem or if that channel moved elsewhere? Regards, Giampaolo I've been having the same problem from several locations/ISPs, since mid-Saturday. 500 Can't connect to yerp.org:80 (connect: timeout) Dave
