[Bug 6707] PerMsgStatus get_decoded_body_text_array() incorrect documentation

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6707 Henrik Krohns changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 7054] PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7054 --- Comment #3 from Henrik Krohns --- (In reply to RW from comment #2) > It's about caching host A-record look-ups, for plugins to use. > > It not very well put as there doesn't look to be any plugin that uses > get_uri_detail_list and

[Bug 7054] PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7054 RW changed: What|Removed |Added CC||rwmailli...@googlemail.com --- Comment #2

[Bug 7054] PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7054 Henrik Krohns changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 7719] (Can't locate object method "check_uri_host_listed" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1478)

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7719 Steadramon changed: What|Removed |Added CC||paul.st...@gmail.com

[Bug 7719] New: (Can't locate object method "check_uri_host_listed" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1478)

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7719 Bug ID: 7719 Summary: (Can't locate object method "check_uri_host_listed" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1478) P

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Bill Cole changed: What|Removed |Added CC|

[Bug 6707] PerMsgStatus get_decoded_body_text_array() incorrect documentation

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6707 Giovanni Bechis changed: What|Removed |Added CC|

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Kevin A. McGrail changed: What|Removed |Added CC|

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Bill Cole changed: What|Removed |Added CC|

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Bill Cole changed: What|Removed |Added CC|

[Bug 7212] Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 Sidney Markowitz changed: What|Removed |Added CC|

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 Sidney Markowitz changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Mark Martinec changed: What|Removed |Added Resolution|--- |FIXED

Re: [Bug 7404] New: MS::PerMsgStatus::get_content_preview

On Tue, 11 Apr 2017, bugzilla-dae...@issues.apache.org wrote: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Bug ID: 7404 Summary: MS::PerMsgStatus::get_content_preview t/autolearn.t . Unescaped left brace in regex is deprecated here

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 --- Comment #3 from Mark Martinec --- 3.4: Sending PerMsgStatus.pm Committed revision 1791013. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 --- Comment #2 from Mark Martinec --- Created attachment 5441 --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5441=edit Fixes inappropriate regexp (and surrounding logic) -- You are receiving this mail

[Bug 7404] Bad regexp (and logic) in MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Mark Martinec <mark.marti...@ijs.si> changed: What|Removed |Added Summary|MS::PerMsgStatus::get_conte |Bad

[Bug 7404] New: MS::PerMsgStatus::get_content_preview

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7404 Bug ID: 7404 Summary: MS::PerMsgStatus::get_content_preview Product: Spamassassin Version: 3.4.1 Hardware: PC OS: All Status: NEW Severity: normal

[Bug 7212] Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 Kevin A. McGrail kmcgr...@pccc.com changed: What|Removed |Added Resolution|--- |FIXED

[Bug 7212] Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 --- Comment #3 from Kevin A. McGrail kmcgr...@pccc.com --- I'm +1 if you want to apply. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 7212] Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 --- Comment #2 from Mark Martinec mark.marti...@ijs.si --- Created attachment 5309 -- https://bz.apache.org/SpamAssassin/attachment.cgi?id=5309action=edit A more compact alternative A more radical coding approach (attached) reduces the

[Bug 7212] Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added Target Milestone|Undefined |3.4.2 ---

[Bug 7212] New: Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit_with_scores()

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7212 Bug ID: 7212 Summary: Warning of uninitialized value in Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_h it_with_scores() Product: Spamassassin

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 --- Comment #6 from Kevin A. McGrail kmcgr...@pccc.com --- Can this be marked resolved? I'm not clear if the patches are committed or is there a fix needed still? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 --- Comment #3 from Kevin A. McGrail kmcgr...@pccc.com --- (In reply to Mark Martinec from comment #2) Created attachment 5300 [details] proposed patch Is this patch what you mean or is my checking for defined sweeping something

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added Target Milestone|Undefined |3.4.2 -- You

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 --- Comment #4 from Mark Martinec mark.marti...@ijs.si --- trunk: Sending lib/Mail/SpamAssassin/PerMsgStatus.pm Committed revision 1679652. 3.4: Sending lib/Mail/SpamAssassin/PerMsgStatus.pm Committed revision 1679653. -- You are

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added Attachment #5300|0 |1 is

[Bug 7196] New: PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 Bug ID: 7196 Summary: PerMsgStatus Warning Product: Spamassassin Version: 3.4.1 Hardware: PC OS: Windows 7 Status: NEW Severity: normal

[Bug 7195] New: PerMsgStatus Util warnings

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7195 Bug ID: 7195 Summary: PerMsgStatus Util warnings Product: Spamassassin Version: 3.4.1 Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 Kevin A. McGrail kmcgr...@pccc.com changed: What|Removed |Added CC|

[Bug 7196] PerMsgStatus Warning

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7196 --- Comment #2 from Mark Martinec mark.marti...@ijs.si --- Created attachment 5300 -- https://bz.apache.org/SpamAssassin/attachment.cgi?id=5300action=edit proposed patch Is this patch what you mean or is my checking for defined sweeping

Re: Uninitialized value in PerMsgStatus

On 1/15/2015 2:43 PM, Mark Martinec wrote: What is a PR? A bugzilla ticket? Yes, a problem report. Sorry for using terminology from another context. Thanks. I wasn't sure if you meant a press release about the bug but that seemed overkill... If there are other perl critic warnings, they

Re: Uninitialized value in PerMsgStatus

On 1/15/2015 11:09 AM, Mark Martinec wrote: :-) Well I don't want to change the vetting process for a release and xt/60_perlcritic.t has been used for years on the code base. Suggestions what we can do to resolve the issue that also passes that test so we don't have to go down that rabbithole?

Re: Uninitialized value in PerMsgStatus

:-) Well I don't want to change the vetting process for a release and xt/60_perlcritic.t has been used for years on the code base. Suggestions what we can do to resolve the issue that also passes that test so we don't have to go down that rabbithole? There are some other perlcritic warnings

Re: Uninitialized value in PerMsgStatus

There are some other perlcritic warnings about modifying $_ in list functions (in sa-update, spamassassin, spamd). Opening a PR would be warranted. What is a PR? A bugzilla ticket? Yes, a problem report. Sorry for using terminology from another context. If there are other perl critic

Re: Uninitialized value in PerMsgStatus

--On Thursday, January 15, 2015 11:48 AM -0500 Kevin A. McGrail kmcgr...@pccc.com wrote: (in sa-update, spamassassin, spamd). Opening a PR would be warranted. What is a PR? A bugzilla ticket? PR is generally short for problem report. So yes, I'd guess a bugzilla ticket. --Quanah

Re: Uninitialized value in PerMsgStatus

Yep that was done to pass the XT tests for a release. Joe can you look at those returns again? That advice from perlcritic needs to be taken with a large grain of salt. In the past I have been bitten by this several times. It is generally safer to leave 'return undef' unless one carefully

Re: Uninitialized value in PerMsgStatus

On 1/14/2015 3:11 PM, Mark Martinec wrote: Yep that was done to pass the XT tests for a release. Joe can you look at those returns again? That advice from perlcritic needs to be taken with a large grain of salt. In the past I have been bitten by this several times. It is generally safer to

Re: Uninitialized value in PerMsgStatus

Yep that was done to pass the XT tests for a release. Joe can you look at those returns again? That advice from perlcritic needs to be taken with a large grain of salt. In the past I have been bitten by this several times. It is generally safer to leave 'return undef' unless one carefully

Re: Uninitialized value in PerMsgStatus

Yep that was done to pass the XT tests for a release. Joe can you look at those returns again? Regards, KAM On January 14, 2015 1:35:20 PM EST, Mark Martinec mark.martinec...@ijs.si wrote: 2015-01-14 18:06, je Alex Regan napisal Hi, I'm using amavisd-new-2.9.1 and perl-5.18.4 on fedora20

Uninitialized value in PerMsgStatus

Hi, I'm using amavisd-new-2.9.1 and perl-5.18.4 on fedora20 with the svn spamassassin snapshot from today, and receive the following message: Jan 14 11:59:21 mail01 amavis[19431]: (19431-18) _WARN: Use of uninitialized value in concatenation (.) or string at

Re: Uninitialized value in PerMsgStatus

2015-01-14 18:06, je Alex Regan napisal Hi, I'm using amavisd-new-2.9.1 and perl-5.18.4 on fedora20 with the svn spamassassin snapshot from today, and receive the following message: Jan 14 11:59:21 mail01 amavis[19431]: (19431-18) _WARN: Use of uninitialized value in concatenation (.) or

[Bug 7054] PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7054 Philip Prindeville phil...@redfish-solutions.com changed: What|Removed |Added CC|

[Bug 7054] PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7054 Philip Prindeville phil...@redfish-solutions.com changed: What|Removed |Added CC|

[Bug 7054] New: PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list()

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7054 Bug ID: 7054 Summary: PerMsgStatus could simplify plugins by caching A record lookups for get_uri_detail_list() Product: Spamassassin Version: 3.4.0 Hardware: PC

Re: [Bug 6915] PerMsgStatus::get_tag() enhancement and optimization

On 3/6/2013 7:21 PM, bugzilla-dae...@issues.apache.org wrote: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6915 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added

[Bug 6915] PerMsgStatus::get_tag() enhancement and optimization

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6915 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 6915] New: PerMsgStatus::get_tag() enhancement and optimization

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6915 Bug ID: 6915 Summary: PerMsgStatus::get_tag() enhancement and optimization Product: Spamassassin Version: SVN Trunk (Latest Devel Version) Hardware: PC OS: All

[Bug 6915] PerMsgStatus::get_tag() enhancement and optimization

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6915 --- Comment #1 from Mark Martinec mark.marti...@ijs.si --- trunk: Sending lib/Mail/SpamAssassin/Message/Metadata.pm Sending lib/Mail/SpamAssassin/Message.pm Sending lib/Mail/SpamAssassin/PerMsgStatus.pm Sending

[Bug 6915] PerMsgStatus::get_tag() enhancement and optimization

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6915 Mark Martinec mark.marti...@ijs.si changed: What|Removed |Added Target Milestone|Undefined |3.4.0 ---

[Bug 6707] PerMsgStatus get_decoded_body_text_array() incorrect documentation

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6707 Kevin A. McGrail kmcgr...@pccc.com changed: What|Removed |Added CC|

[Bug 6707] New: PerMsgStatus get_decoded_body_text_array() incorrect documentation

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6707 Bug #: 6707 Summary: PerMsgStatus get_decoded_body_text_array() incorrect documentation Product: Spamassassin Version: 3.3 SVN branch Platform: All OS

[Bug 6707] PerMsgStatus get_decoded_body_text_array() incorrect documentation

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6707 --- Comment #1 from Karsten Bräckelmann guent...@rudersport.de 2011-11-26 00:47:09 UTC --- Created attachment 5013 -- https://issues.apache.org/SpamAssassin/attachment.cgi?id=5013 proposed patch POD for PerMsgStatus

[Bug 5948] New: uninitialized value within @pristine_headers PerMsgStatus. pm line 832

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5948 Summary: uninitialized value within @pristine_headers PerMsgStatus.pm line 832 Product: Spamassassin Version: 3.2.5 Platform: Other OS/Version: All

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 4497] reorganise PerMsgStatus code

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4497 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-07-12 15:26 --- I think this may be fixed in svn trunk. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the

[Bug 4973] get_tag and set_tag APIs missing from PerMsgStatus pod

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4973 --- Additional Comments From [EMAIL PROTECTED] 2006-07-06 12:17 --- Created an attachment (id=3569) -- (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3569action=view) Trivial patch to fix the POD I did submit an

[Bug 4973] get_tag and set_tag APIs missing from PerMsgStatus pod

||FIXED Summary|get_tag and set_tag APIs|get_tag and set_tag APIs |missing from PerMsgStatus |missing from PerMsgStatus |pod |pod Target Milestone|Undefined |3.1.4

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-26 00:55 --- I'm not completely clear about how often, or under what exact circumstances and config, you're seeing this but you're probably seeing bug 4179. The last

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-24 18:36 --- My suspicion is that spamd is not clearing the config completely between users when allow_user_rules is set, and the rules, but not the scores, are surviving

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 13:29 --- Stock RPM built from the tarball. No special plugins. A couple of custom system rules for the float obfuscation spam but they have scores. What's the Perl

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 14:20 --- if (!defined $score) { warn HELP undef score; } that's what you're after. curious! --- You are receiving this mail because: --- You are the

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 18:40 --- Ok, here's a clue. In /etc/mail/spamassassin/locals.cf I have allow_user_rules 1. In my userprefs I have this rule: header__MIME_VERSION

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 18:44 --- Correction, the original test case works, just not when I test as root. Testing as a mortal other than me elicits the bug. --- You are receiving this

[Bug 4906] New: Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 Summary: Uninitialized $score in PerMsgStatus::_handle_hit Product: Spamassassin Version: 3.1.1 Platform: Other OS/Version: other Status: NEW Severity: normal

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-22 23:06 --- Created an attachment (id=3519) -- (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3519action=view) Sample spam for triggering the error message

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-22 23:13 --- This is one of those can't ever happen (without something crazy going on) issues. But it looks like this is probably the same as bug 4699. Can you try

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 00:54 --- No joy. I applied the patch to Timeout.pm and spamd and restarted the daemon and still get the same error messages. --- You are receiving this mail

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-23 01:41 --- (In reply to comment #3) No joy. I applied the patch to Timeout.pm and spamd and restarted the daemon and still get the same error messages. hrm. can

[Bug 4497] reorganise PerMsgStatus code

http://bugzilla.spamassassin.org/show_bug.cgi?id=4497 --- Additional Comments From [EMAIL PROTECTED] 2005-10-17 16:36 --- Mail::SpamAssassin::Message::Node will need a ptr to {main} for bug 4636, so there's little point for a separate Mail::SpamAssassin::Message:Rendered. ---

[Bug 4497] reorganise PerMsgStatus code

http://bugzilla.spamassassin.org/show_bug.cgi?id=4497 --- Additional Comments From [EMAIL PROTECTED] 2005-10-17 16:54 --- Subject: Re: reorganise PerMsgStatus code On Mon, Oct 17, 2005 at 04:36:06PM -0700, [EMAIL PROTECTED] wrote: Mail::SpamAssassin::Message::Node will need a ptr

[Bug 4497] reorganise PerMsgStatus code

http://bugzilla.spamassassin.org/show_bug.cgi?id=4497 --- Additional Comments From [EMAIL PROTECTED] 2005-10-17 16:59 --- There is a work-in-progress patch attached to bug 4636. It would be better to discuss the issue in that bug. --- You are receiving this mail because:

Re: PerMsgStatus

a) what the heck are priorities, who sets them, and do they really have any justifiable purpose? Ie: can they just quietly vanish into the night with nobody being any the wiser? They order the rules -- or more correctly, sets of rules. Most rules are priority 500 (iirc), but some need

Re: PerMsgStatus

-- that *should* be implemented as some kind of general mechanism, instead of being keyed off the rule type, because doing it by rule type means that there'll be no way for plugins to support similar models for future unforeseen rule types without changes to PerMsgStatus and/or Conf. Also, AWL was previously

Re: PerMsgStatus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loren Wilton writes: I just spent 45 minutes or so staring at the PerMsgStatus code and figuring out a bit more about how it works. Baroque! Still, there is the basis of a concept underlying the implementation, and it doesn't *look* like

Re: PerMsgStatus

[Lots of stuff snipped] You know, it'd be nice if Daniel, or anyone else, checked in my optimised PMS.pm [*] in as a branch. That way it can be worked on easily by multiple people. An optimisation branch would mean you can continue with the current release work, while others work on

Re: [Bug 4497] New: reorganise PerMsgStatus code

Loren Wilton [EMAIL PROTECTED] writes: Is there a way that [user rules] could be saved in a more-compiled state when used with spamd and similar? Maybe name the rules with the username as part of the procedure name, and just add them to the namespace the first time encountered? Beyond the

Re: [Bug 4497] New: reorganise PerMsgStatus code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Quinlan writes: Loren Wilton [EMAIL PROTECTED] writes: Is there a way that [user rules] could be saved in a more-compiled state when used with spamd and similar? Maybe name the rules with the username as part of the procedure name,

Re: [Bug 4497] New: reorganise PerMsgStatus code

Justin Mason [EMAIL PROTECTED] writes: I don't get it -- how does that help? Basically, user rule would always run last. Something like: for (@priorities) { standard prorities loop } if ($allow_user_rules $defined_rules{$user}) { do_xxx_tests($user, ...); # $user is the priority

[Bug 4497] New: reorganise PerMsgStatus code

http://bugzilla.spamassassin.org/show_bug.cgi?id=4497 Summary: reorganise PerMsgStatus code Product: Spamassassin Version: SVN Trunk (Latest Devel Version) Platform: Other OS/Version: other Status: NEW Severity: enhancement

Re: [Bug 4497] New: reorganise PerMsgStatus code

I know user rules aren't real popular with the sa dev community, however that attitude isn't universally shared by sa users. Therefore may I suggest: Would it be possible when reorganizing things to come up with some semi-persistant storage for compiled user rules, so that they don't have to be

[Bug 4411] $permsgstatus-get_uri_list too aggressive?

http://bugzilla.spamassassin.org/show_bug.cgi?id=4411 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 4411] New: $permsgstatus-get_uri_list too aggressive?

http://bugzilla.spamassassin.org/show_bug.cgi?id=4411 Summary: $permsgstatus-get_uri_list too aggressive? Product: Spamassassin Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: enhancement

[Bug 4411] $permsgstatus-get_uri_list too aggressive?

http://bugzilla.spamassassin.org/show_bug.cgi?id=4411 --- Additional Comments From [EMAIL PROTECTED] 2005-06-20 12:51 --- Subject: Re: New: $permsgstatus-get_uri_list too aggressive? On Mon, Jun 20, 2005 at 12:43:28PM -0700, [EMAIL PROTECTED] wrote: that a URI of http://username

[Bug 4218] PerMsgStatus $status-finish() not getting registered

, there was a bug. Basically, a temporary PerMsgStatus object is created *very* early on -- in lib/Mail/SpamAssassin/Message/Metadata/Received -- before the plugin was loaded, resulting in the 'per_msg_finish' callbacks being cached without the plugin's method in the list. fix was to get that object created

[Bug 4218] PerMsgStatus $status-finish() not getting registered

http://bugzilla.spamassassin.org/show_bug.cgi?id=4218 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 3885] Undefined subroutine Mail::SpamAssassin::PerMsgStatus::is_razor2_available

http://bugzilla.spamassassin.org/show_bug.cgi?id=3885 --- Additional Comments From [EMAIL PROTECTED] 2005-03-30 06:42 --- Subject: Re: Undefined subroutine Mail::SpamAssassin::PerMsgStatus::is_razor2_available [EMAIL PROTECTED] writes: http://bugzilla.spamassassin.org

[Bug 3885] Undefined subroutine Mail::SpamAssassin::PerMsgStatus::is_razor2_available

http://bugzilla.spamassassin.org/show_bug.cgi?id=3885 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 4218] New: PerMsgStatus $status-finish() not getting registered

http://bugzilla.spamassassin.org/show_bug.cgi?id=4218 Summary: PerMsgStatus $status-finish() not getting registered Product: Spamassassin Version: 3.0.2 Platform: All OS/Version: Linux Status: NEW Severity: minor

speedup for PerMsgStatus

OK, here's a trick I was thinking about. Currently we have these massive hashtable refs: $pms-{conf}-{rbl_evals} {head_tests} {body_tests} {scoreset}-[0,1,2,3] {tflags} Each of those is keyed by

Re: speedup for PerMsgStatus

[EMAIL PROTECTED] (Justin Mason) writes: Array lookups are quite a bit faster than hash lookups. +1 -- Daniel Quinlan ApacheCon! 13-17 November (3 SpamAssassin http://www.pathname.com/~quinlan/ http://www.apachecon.com/ sessions more)

Re: speedup for PerMsgStatus

so I'm thinking that we should replace parts of this with arrays, using integer indexes, instead of hashes with string indexes. Array lookups are quite a bit faster than hash lookups. I have no idea how painful linked lists are in Perl (or if they even exist). But if you are essentially

Re: speedup for PerMsgStatus

I have no idea how painful linked lists are in Perl (or if they even exist). Why are you commenting then??? Because they are very useful, as I pointed out. They don't exist as a native data structure. Arrays are fast, painless, and dynamically sized. They don't exist as a native data

Re: speedup for PerMsgStatus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loren Wilton writes: I have no idea how painful linked lists are in Perl (or if they even exist). Why are you commenting then??? Because they are very useful, as I pointed out. They don't exist as a native data structure. Arrays are

Re: speedup for PerMsgStatus

That is an unreasonablly nasty retort. Original Message: - From: Daniel Quinlan [EMAIL PROTECTED] Date: 27 Sep 2004 22:53:38 -0700 To: [EMAIL PROTECTED], dev@spamassassin.apache.org Subject: Re: speedup for PerMsgStatus Loren Wilton [EMAIL PROTECTED] writes: I have no idea how