ban_list: addresses which begin with caret ("^")
Bug #1074542 reported by
/dev/rob0
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNU Mailman |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
This is very minor, but probably deserves a note in the documentation. In the ban_list (and probably other places) a regular expression requires the leading end anchor "^". Thus one without that as first character would be interpreted as an email address. With the "^", the entry will be read as a regular expression.
How would you handle an email address where the localpart begins with "^"? Granted, this is a very rare thing, but it is possible. Escape it with backslash? It could be done as a regular expression also, but that fact might be worth noting. Thanks.
FYI, I discussed this with Terri in IRC, and she suggested filing a bug.
Revision history for this message
| Mark Sapiro (msapiro) wrote | #1 |
| Changed in mailman: | |
| importance: | Undecided → Low |
| status: | New → Won't Fix |
To post a comment you must log in.
Assuming there actually is such an address, it could be represented as you suggest with a regexp that would match only the literal address. E.g. if the address were "^<email address hidden>", the regexp would be "^\^some\
Escaping the leading ^ with a backslash wouldn't work without changes to Mailman. Non-regexp matches on addresses are done by simple string comparison which would treat the backslash as any other character.
I'm not convinced that this is a valid bug, but I'm marking it "Won't Fix" so it can serve as documentation of how to deal with such an address.