This is cut-and-pasted from https://bugzilla.redhat.com/show_bug.cgi?id=437652 Description of problem: Recently (in the last month or so), linkedin.com has started sending very long From fields. As a result, pick fails with messages like this: pick: field name "From notif+qSVakQSqixxnIDNMC-T3Lx04p25VW39JQgVTHbM4Vv0ir0xnV-CG_gSQxxjCdsSEs56P_1MmEv5E0PNMxxjQFo(_at_)bounce(_dot_)linkedin(_dot_)com Mon Mar " exceeds 127 bytes pick: format error in message 169 Here's the start of the message: From notif+qSVakQSqixxnIDNMC-T3Lx04p25VW39JQgVTHbM4Vv0ir0xnV-CG_gSQxxjCdsSEs56P_1MmEv5E0PNMxxjQFo(_at_)bounce(_dot_)linkedin(_dot_)com Mon Mar 3 02:03:01 2008 Return-Path: <notif+qSVakQSqixxnIDNMC-T3Lx04p25VW39JQgVTHbM4Vv0ir0xnV-CG_gSQxxjCdsSEs56P_1MmEv5E0PNMxxjQFo(_at_)bounce(_dot_)linkedin(_dot_)com> ... Version-Release number of selected component (if applicable): nmh-1.2-20070115cvs.4.fc8 How reproducible: Always Steps to Reproduce: 1. generate a message with a too-long From line 2. scan +inbox 3. Actual Results: See description for error message. Expected Results: No error message, successful scan. Additional info: I have a patch and will attach it subsequently. Patches attached. -John Heidemann
nmh-namesz.patch
Description: Binary data
nmh-namesz-spec.patch
Description: Binary data
_______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org http://lists.nongnu.org/mailman/listinfo/nmh-workers
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [Nmh-workers] content-transfer-encoding: base64, Valdis . Kletnieks |
---|---|
Next by Date: | Re: [Nmh-workers] problem with long field names, Josh Bressers |
Previous by Thread: | [Nmh-workers] content-transfer-encoding: base64, Anders Eriksson |
Next by Thread: | Re: [Nmh-workers] problem with long field names, Josh Bressers |
Indexes: | [Date] [Thread] [Top] [All Lists] |