[bug #20142] strip backslash in rfc822 From: field

2011-01-09 Thread Earl Hood
Update of bug #20142 (project mhonarc): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #20142] strip backslash in rfc822 From: field

2011-01-09 Thread Earl Hood
Update of bug #20142 (project mhonarc): Status: Ready For Test => Fixed Fixed Release: => 2.6.17 ___ Reply to this item at:

[bug #20142] strip backslash in rfc822 From: field

2011-01-02 Thread Earl Hood
Update of bug #20142 (project mhonarc): Status: Need Info => Ready For Test ___ Follow-up Comment #11: Tokenize module does not translate quoted pairs ("" CHAR) when tokenizing. For now, it will s

[bug #20142] strip backslash in rfc822 From: field

2011-01-01 Thread Jeff Breidenbach
Follow-up Comment #10, bug #20142 (project mhonarc): 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) ___ Reply to this item at:

[bug #20142] strip backslash in rfc822 From: field

2011-01-01 Thread Jeff Breidenbach
Follow-up Comment #9, bug #20142 (project mhonarc): 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 regenera

[bug #20142] strip backslash in rfc822 From: field

2011-01-01 Thread Jeff Breidenbach
Additional Item Attachment, bug #20142 (project mhonarc): File name: data.gzSize:5 KB ___ Reply to this item at: ___ Messag

[bug #20142] strip backslash in rfc822 From: field

2010-12-31 Thread Earl Hood
Update of bug #20142 (project mhonarc): Status:None => Need Info ___ Follow-up Comment #8: It's been too long since I last looked at this problem. Jeff, do you mind providing a sample da

[bug #20142] strip backslash in rfc822 From: field

2009-05-03 Thread Earl Hood
Follow-up Comment #7, bug #20142 (project mhonarc): I posted a response to your Tamil problem awhile back to the user's list: http://www.mhonarc.org/archive/cgi-bin/mesg.cgi?a=mhonarc-users&i=200903230354.n2N3sQD3008778%40gator.earlhood.com Wrt to the Tamil problem, I could not verify the proble

[bug #20142] strip backslash in rfc822 From: field

2009-05-03 Thread Jeff Breidenbach
Follow-up Comment #6, bug #20142 (project mhonarc): Note to self: check if this patch is a possible cause of the $SUBJECT$ $SUSBJECTNA$ weirdness with Tamil. http://www.mail-archive.com/mhonarc-us...@mhonarc.org/msg01387.html ___ Reply t

Re: [bug #20142] strip backslash in rfc822 From: field

2007-10-09 Thread Jeff Breidenbach
Ah, now I understand. This is the right patch. # diff -u /var/tmp/mhutil.pl /usr/share/mhonarc/mhutil.pl --- /var/tmp/mhutil.pl 2007-10-09 20:30:36.0 -0700 +++ /usr/share/mhonarc/mhutil.pl2007-10-09 22:05:59.0 -0700 @@ -177,6 +177,7 @@ - Hide quoted text - next if

Re: [bug #20142] strip backslash in rfc822 From: field

2007-10-09 Thread Jeff Breidenbach
Here's an unmangled copy of the patch. I think this works, but the \" part acts a little weird during testing. (E.g. if I run -editidx I can fix an index page, but I can't seem to break it again if I change the code back) -Jeff # diff -u /var/tmp/mhutil.pl /usr/share/mhonarc/mhutil.pl --- /var/t

[bug #20142] strip backslash in rfc822 From: field

2007-10-09 Thread Jeff Breidenbach
Follow-up Comment #5, bug #20142 (project mhonarc): --- /var/tmp/mhutil.pl 2007-10-09 20:30:36.0 -0700 +++ /usr/share/mhonarc/mhutil.pl2007-10-09 21:32:05.0 -0700 @@ -176,7 +176,8 @@ foreach $tok (@tokens) { next if $skip; if ($tok =~ /^"/) { # Quo

[bug #20142] strip backslash in rfc822 From: field

2007-08-07 Thread Jeff Breidenbach
Follow-up Comment #4, bug #20142 (project mhonarc): 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

[bug #20142] strip backslash in rfc822 From: field

2007-08-04 Thread Earl Hood
Follow-up Comment #3, bug #20142 (project mhonarc): Do you have any original messages that illustrate the problem? I want to make sure thay any work I do will address the cases you are encountering. Thanks. ___ Reply to this item at:

[bug #20142] strip backslash in rfc822 From: field

2007-07-29 Thread Jeff Breidenbach
Follow-up Comment #2, bug #20142 (project mhonarc): This is super useful, and really comes into play for us on $FROMNAME$. Everything else can essentially stay the same. In particular, $SUBJECT$ will quite often have unescaped backslashes, for example, a message talking about Windows software m

[bug #20142] strip backslash in rfc822 From: field

2007-06-26 Thread Earl Hood
Follow-up Comment #1, bug #20142 (project mhonarc): RFC 822 does support the use of '\' to escape characters. I'll need to do some testing to see if the RFC-822 parser has a bug or if it is mhonarc. Mhonarc historically has tried to do some short-cuts in some cases to avoid full rfc-822 parsing

[bug #20142] strip backslash in rfc822 From: field

2007-06-10 Thread Jeff Breidenbach
URL: Summary: strip backslash in rfc822 From: field Project: MHonArc Submitted by: jab Submitted on: Sunday 06/10/2007 at 19:19 Category: Resource Variables Severit