Bug 80335 - regexp matches when it shouldn't
Summary: regexp matches when it shouldn't
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: All Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-12-24 17:29 UTC by Ben LaHaise
Modified: 2016-11-24 15:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-24 17:49:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
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 17:36 UTC, Ben LaHaise
no flags Details

Description Ben LaHaise 2002-12-24 17:29:00 UTC
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 17:36:50 UTC
Created attachment 88890 [details]
mail message with a Subject: that the regexp matches

Comment 2 Ben LaHaise 2002-12-24 17:49:56 UTC
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.