https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7108

            Bug ID: 7108
           Summary: sa_update fails: config: invalid regexp for rule
                    __PDS_FROM_2_EMAILS
           Product: Spamassassin
           Version: 3.4.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Rules
          Assignee: [email protected]
          Reporter: [email protected]

New rule for __PDS_FROM_2_EMAILS breaks sa-update run as of 11/26/2014

========== sa-update cron run ==========
/etc/cron.daily/zzz-sa-update.cron:

Update available for channel updates.spamassassin.org: 1641165 -> 1641542
http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, success
http: (curl) GET http://www.sa-update.pccc.com/1641542.tar.gz, success
http: (curl) GET http://www.sa-update.pccc.com/1641542.tar.gz.sha1, success
http: (curl) GET http://www.sa-update.pccc.com/1641542.tar.gz.asc, success
config: invalid regexp for rule __PDS_FROM_2_EMAILS:
/^\W+([\w+.-]+\@[\w.-]+\.\w\w++)(?:[^\n\w<]{0,80})?<(?!\1)[^\n\s]*\@/i: Nested
quantifiers in regex; marked by <-- HERE in
m/(?i)^\W+([\w+.-]+\@[\w.-]+\.\w\w++ <-- HERE
)(?:[^\n\w<]{0,80})?<(?!\1)[^\n\s]*\@/

channel: lint check of update failed, channel failed
Update failed, exiting with code 4
Spamassassin rules update completed.
Spamassassin restarted.
========== sa-update cron run ==========

{443}root:gateway:~craig/work/dev/spam/saupdate> grep __PDS_FROM_2_EMAILS *.cf
72_active.cf:meta    PDS_FROM_2_EMAILS       __PDS_FROM_2_EMAILS && !__VIA_ML
&& !__VIA_RESIGNER
72_active.cf:header  __PDS_FROM_2_EMAILS     From =~
/^\W+([\w+.-]+\@[\w.-]+\.\w\w++)(?:[^\n\w<]{0,80})?<(?!\1)[^\n\s]*\@/i

Spamassassin 3.4.0, perl 5.8.8, CentOS 5.x (up to date)
{445}root:gateway:~craig/work/dev/spam/saupdate> uname -a
Linux gateway.myittybitty.com 2.6.18-398.el5 #1 SMP Tue Sep 16 20:50:52 EDT
2014 x86_64 x86_64 x86_64 GNU/Linux

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

Reply via email to