MHonArc - Bugs: bug #20142, strip backslash in rfc822 From:...
You are not allowed to post comments on this tracker with your current authentication level.
bug #20142: strip backslash in rfc822 From: field
Submitter: | Jeff Breidenbach <jab> | ||
Submitted: | Sun 10 Jun 2007 07:19:01 PM UTC | ||
Category: | Resource Variables | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | Incorrect Behavior |
Status: | Fixed | Privacy: | Public |
Assigned to: | None | Open/Closed: | Closed |
Operating System: | Linux | Perl Version: | v5.8.4 |
Component Version: | 2.6.16 | Fixed Release: | 2.6.17 |
Jump to the original submission
Sun 02 Jan 2011 08:44:23 AM UTC, comment #11: |
Earl Hood <ehood> |
Sun 02 Jan 2011 12:07:30 AM UTC, comment #10: I should also mention the Tamil problem went away by itself (I think it turned out to be a weird browser bug or something like that) |
Jeff Breidenbach <jab> |
Sun 02 Jan 2011 12:04:35 AM UTC, comment #9: I've added about 500 examples of From fields containing backslashes - all this data is within the last two weeks. Since by necessity this field contains email addresses, I recommend deleting the dataset when finished. It is very easy to regenerate.
|
Jeff Breidenbach <jab> |
Fri 31 Dec 2010 09:10:27 PM UTC, comment #8: It's been too long since I last looked at this problem.
|
Earl Hood <ehood> |
Mon 04 May 2009 03:30:03 AM UTC, comment #7: I posted a response to your Tamil problem awhile back
|
Earl Hood <ehood> |
Mon 04 May 2009 03:24:39 AM UTC, comment #6: Note to self: check if this patch is a possible cause of the $SUBJECT$ $SUSBJECTNA$ weirdness with Tamil.
|
Jeff Breidenbach <jab> |
Wed 10 Oct 2007 04:35:31 AM UTC, comment #5: --- /var/tmp/mhutil.pl 2007-10-09 20:30:36.000000000 -0700
|
Jeff Breidenbach <jab> |
Wed 08 Aug 2007 05:32:36 AM UTC, comment #4: I've placed a sample of raw messages at the following location. It is encrypted to the mhonarc signing key and is representative of production traffic. Maybe the size is a little bit of overkill for this particular problem, but the dataset might be useful for other
|
Jeff Breidenbach <jab> |
Sat 04 Aug 2007 06:51:55 PM UTC, comment #3: Do you have any original messages that illustrate
|
Earl Hood <ehood> |
Mon 30 Jul 2007 02:41:47 AM UTC, comment #2: This is super useful, and really comes into play for us on $FROMNAME$.
|
Jeff Breidenbach <jab> |
Tue 26 Jun 2007 11:37:19 PM UTC, comment #1: RFC 822 does support the use of '\' to escape characters.
|
Earl Hood <ehood> |
Sun 10 Jun 2007 07:19:01 PM UTC, original submission:
It is not uncommon to have an escaped character in the From: field of an email header. I've noticed this mainly with parentheses and quotation marks, e.g. \( \) \". Out of the last 75000 mails, approximately one in 500 have this characteristic. Mhonarc leaves the backslash in and produces messages that look a little funnny. Especially when one person posts a lot to a list, and each time his or her name is littered with extra backslashes in the index pages.
|
Jeff Breidenbach <jab> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-01-09 | ehood | Open/Closed | Open | Closed | |
2011-01-09 | ehood | Status | Ready For Test | Fixed | |
Fixed Release | 2.6.17 | ||||
2011-01-02 | ehood | Status | Need Info | Ready For Test | |
2011-01-02 | ehood | Attached File | #22335 | Removed | |
2011-01-02 | jab | Attached File | - | Added data.gz, #22335 | |
2010-12-31 | ehood | Status | None | Need Info |
Powered by Savane 3.13-aa77.
Corresponding source code
Tokenize module does not translate quoted pairs
("\" CHAR) when tokenizing. For now, it will stay that way,
so mhonarc::extract_email_name() modified to unquote chars in
quoted-string and comment token data, if used as the
email name.
Also, while examining tokenizer code, noticed bug in parsing
comments: quoted "\(" or "\)" not taken into account, which
could lead to improper tokenization. This has been fixed.