[Bug 8246] SEO stands for “search engine optimization.”

2024-04-20 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8246

John Hardin  changed:

   What|Removed |Added

   Assignee|dev@spamassassin.apache.org |jhar...@impsec.org
 Status|NEW |RESOLVED
  Component|Building & Packaging|bzspam
 Resolution|--- |INVALID

--- Comment #1 from John Hardin  ---
Spam, deleting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 8246] New: SEO stands for “search engine optimization.”

2024-04-20 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8246

Bug ID: 8246
   Summary: SEO stands for “search engine optimization.”
   Product: Spamassassin
   Version: 4.0.1
  Hardware: PC
OS: Windows 10
Status: NEW
  Severity: normal
  Priority: P2
 Component: Building & Packaging
  Assignee: dev@spamassassin.apache.org
  Reporter: jannatulferdousmokta...@gmail.com
  Target Milestone: Undefined

SEO stands for “search engine optimization.” In simple terms, SEO means the
process of improving your website to increase its visibility in Google,
Microsoft Bing, and other search engines whenever people search for: Products
you sell. Services you provide
https://afazrum4.blogspot.com/;>seo

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 8245] undefined value as an ARRAY reference in DMARC plugin

2024-04-20 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8245

Sidney Markowitz  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Severity|trivial |normal

--- Comment #3 from Sidney Markowitz  ---
This is simpler to reproduce than I expected, and I underestimated the
severity. The log message is just a warning, but the plugin eval fails when it
happens, as evidenced by a test failure.

In a test environment running perl 5.18.4 (or any 5.16 or 5.18), with the
modules for SPF, DKIM, and DMARC installed and with net tests enabled in
t/config.dist (all the requirements to run t/dmarc.t), this bug causes
t/dmarc.t to fail with messages

warn: plugin: eval failed: Can't use an undefined value as an ARRAY reference
at ../blib/lib/Mail/SpamAssassin/Plugin/DMARC.pm line 336

Committed the fix:

trunk % svn ci -m "bug 8245 - fix undefined value error in DMARC in perl 5.16
and 5.18" lib/Mail/SpamAssassin/Plugin/DMARC.pm
Sendinglib/Mail/SpamAssassin/Plugin/DMARC.pm
Transmitting file data .done
Committing transaction...
Committed revision 1917179.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 8245] undefined value as an ARRAY reference in DMARC plugin

2024-04-20 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8245

Sidney Markowitz  changed:

   What|Removed |Added

   Target Milestone|Undefined   |4.0.2
   Severity|normal  |trivial

--- Comment #2 from Sidney Markowitz  ---
More testing of

perl -e 'use strict; my $files; my $foo = sort {$a // 0 <=> $b // 0}
@{$files};'

With perl 5.16.3 and 5.18.4 is outputs

Can't use an undefined value as an ARRAY reference at -e line 1.

With perl 5.20.3 and newer it doesn't output that.

The release notes for 5.20.0 mention a change in the treatment of arguments to
sort that is probably what makes the difference.

The following eliminates the warning in the older versions and doesn't change
the results in newer versions:

perl -e 'use strict; my $files; my $foo = sort {$a // 0 <=> $b // 0} @{$files
// []};'

I'll make that change in DMARC.pm

It is only a warning in the log, not an error, and doesn't effect the results.

-- 
You are receiving this mail because:
You are the assignee for the bug.