Bug 80335 - regexp matches when it shouldn't
regexp matches when it shouldn't
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
7.3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-24 12:29 EST by Ben LaHaise
Modified: 2016-11-24 10:20 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-24 12:49:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
mail message with a Subject: that the regexp matches (1.84 KB, application/octet-stream)
2002-12-24 12:36 EST, Ben LaHaise
no flags Details

  None (edit)
Description Ben LaHaise 2002-12-24 12:29:00 EST
procmail and grep have a problem filtering out several spam rules on my mail
server.  A simple testcase is as follows:

echo "ÉÏÍø¼æÖ°£¬ÔÂ׬ÍòÔª£¡£¡" | LANG=en_US grep [a-zA-Z] >/dev/null && echo failed

For an english speaker, none of those characters are part of the alphabet, and
the behaviour of the regexp is completely bogus.  At the very least, this must
work in procmail somehow, as it is otherwise impossible to correctly guess how
to write regexps that actually work.
Comment 1 Ben LaHaise 2002-12-24 12:36:50 EST
Created attachment 88890 [details]
mail message with a Subject: that the regexp matches
Comment 2 Ben LaHaise 2002-12-24 12:49:56 EST
Okay, I'm an idiot.  Must drink coffee before filing bugs.  The shell was
expanding my regexp... sigh


Note You need to log in before you can comment on or make changes to this bug.