|
|
SA Bugzilla – Full Text Bug Listing |
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | Help
- | New Account
- | Log In
- | Forgot Password
|
|
|
SA Bugzilla – Full Text Bug Listing |
| Summary: | Template TAGS don't allow underscores | ||
|---|---|---|---|
| Product: | Spamassassin | Reporter: | Karsten Bräckelmann <guenther> |
| Component: | Libraries | Assignee: | SpamAssassin Developer Mailing List <dev> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | apache, billcole, kmcgrail, sa |
| Priority: | P5 | ||
| Version: | 3.2.5 | ||
| Target Milestone: | 4.0.0 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Attachments: | Add word boundaries to tag regex | ||
Created attachment 5365 [details]
Add word boundaries to tag regex
Adds word boundaries to the start and end of the tag regex to enable underscores within a template tag.
Checks for a double underscore so that multiple tags can be squashed together without a space/punctuation if desired.
The regex along doesn't even match many of the test cases given in 4793 which avoids issues with that, and the matches it does give will resolve to an unrecognised tag and therefore the default of not changing those as introduced in the fixes would come into effect.
Thanks Kevin. It's a trivial regex and nice you made all the fixes. We'll look at this post Holiday. Allowing underscores inside a tag would be _horrible_ design, given that underscore is the separator. Just looking at any set_tag in SA sources clearly show the spirit of naming is intended to be _JUSTCAPS_. I vote making set_tag to reject anything else than _ALPHANUM(foo)_ for trunk/4.0.0 and clarifying this in documentation. +1 (In reply to Henrik Krohns from comment #3) > Allowing underscores inside a tag would be _horrible_ design, given that > underscore is the separator. Just looking at any set_tag in SA sources > clearly show the spirit of naming is intended to be _JUSTCAPS_. > > I vote making set_tag to reject anything else than _ALPHANUM(foo)_ for > trunk/4.0.0 and clarifying this in documentation. +! Made a note in documentation about alphanumeric format, per previous comments. Committed revision 1898645. |
$pms->set_tag ('TAG_WITH_UNDERSCORE', 'value'); does return the actual value, suggesting the tag indeed has been defined, as per M::SA::PerMsgStatus set_tag() documentation, since the returned value is not undef. Using a a template with underscores however, is not expanded to the value, but used literally. add_header all Foo _TAG_WITH_UNDERSCORES_ results in the following header in the mail. X-Spam-Foo: _TAG_WITH_UNDERSCORES_ $pms->{tag_data}->{TAG_WITH_UNDERSCORES} does hold the correct 'value'. And the winner is... Somewhere between _process_header(), _replace_tags() and _get_tag(), it seems. After quite a long hunt, I believe I finally got the little bugger. PerMsgStatus _replace_tags(), who came up with *that* wonderful line of code? $text =~ s{(_(\w+?)(?:\((.*?)\))?_)}{ The fact that RE is not anchored, but the $2 match is not greedy, results in the RE missing TAG_WITH_UNDERSCORE. Did not test this, though, because... Any fix, if any, needs to carefully consider bug 4793.