* bug#23040: Resolved [not found] ` <8737q7kquz.fsf@thinkpad.rath.org> @ 2017-01-26 22:55 ` Lars Ingebrigtsen 2017-01-27 17:56 ` Nikolaus Rath 0 siblings, 1 reply; 3+ messages in thread From: Lars Ingebrigtsen @ 2017-01-26 22:55 UTC (permalink / raw) To: Nikolaus Rath; +Cc: 23040 Nikolaus Rath <Nikolaus@rath.org> writes: > The problem here is that recently some spam has started to come with > extremely long "References" headers, and that the regular expression > used in one of my scoring rules is sub-optimal when applied to such long > strings. > > In particular, the leading dot in "<.+@[a-z0-9]+\\.rath\\.org>" first > matches the entire reference header, and then emacs presumably has to > backtrack character by character (or something like that). > > Fixing the rule by restricting the match to one message id fixes the > problem: "<[^<>@]+@[a-z0-9]+\\.rath\\.org>" Could you submit a patch for this problem? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#23040: Resolved 2017-01-26 22:55 ` bug#23040: Resolved Lars Ingebrigtsen @ 2017-01-27 17:56 ` Nikolaus Rath 2017-01-27 19:09 ` Lars Ingebrigtsen 0 siblings, 1 reply; 3+ messages in thread From: Nikolaus Rath @ 2017-01-27 17:56 UTC (permalink / raw) To: Lars Ingebrigtsen; +Cc: 23040 On Jan 26 2017, Lars Ingebrigtsen <larsi@gnus.org> wrote: > Nikolaus Rath <Nikolaus@rath.org> writes: > >> The problem here is that recently some spam has started to come with >> extremely long "References" headers, and that the regular expression >> used in one of my scoring rules is sub-optimal when applied to such long >> strings. >> >> In particular, the leading dot in "<.+@[a-z0-9]+\\.rath\\.org>" first >> matches the entire reference header, and then emacs presumably has to >> backtrack character by character (or something like that). >> >> Fixing the rule by restricting the match to one message id fixes the >> problem: "<[^<>@]+@[a-z0-9]+\\.rath\\.org>" > > Could you submit a patch for this problem? If I understand the issue correctly, then it is caused by a sub-optimal regular expression in my local configuration that triggers problems in Emacs' regular expression engine. I think the former can't be patched in Gnus, and the latter is definitely beyond my area of expertise, sorry. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#23040: Resolved 2017-01-27 17:56 ` Nikolaus Rath @ 2017-01-27 19:09 ` Lars Ingebrigtsen 0 siblings, 0 replies; 3+ messages in thread From: Lars Ingebrigtsen @ 2017-01-27 19:09 UTC (permalink / raw) To: Nikolaus Rath; +Cc: 23040 Nikolaus Rath <Nikolaus@rath.org> writes: > If I understand the issue correctly, then it is caused by a sub-optimal > regular expression in my local configuration that triggers problems in > Emacs' regular expression engine. I think the former can't be patched in > Gnus, and the latter is definitely beyond my area of expertise, sorry. OK; closing. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-01-27 19:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <87lh5hp1oi.fsf@thinkpad.rath.org>
[not found] ` <8737q7kquz.fsf@thinkpad.rath.org>
2017-01-26 22:55 ` bug#23040: Resolved Lars Ingebrigtsen
2017-01-27 17:56 ` Nikolaus Rath
2017-01-27 19:09 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).