Re: [PATCH] Adequately read mailboxes with s/@/ at / obfuscations
On Tue, May 04, 2010 at 22:55:46 -0500, David Champion wrote: > Adequately read mailboxes with s/@/ at / obfuscations. > > This handles mbox From_ separators and rfc822 address parsing. Ah, nice! Just when I had dug up the "un-at-" script for being able to read some mailing lists archives. Yes, I would like this feature! :-) Moritz
Re: [PATCH] Adequately read mailboxes with s/@/ at / obfuscations
Hi, On Tue, May 04, 2010 at 10:55:46PM -0500, David Champion wrote: > Adequately read mailboxes with s/@/ at / obfuscations. This kind of substitution is not reversible in the general case. Consider for instance this e-mail address: "works at home"@some.dom.ain Address obfuscation/mangling cause much more problems that they solve (if any). The actual problem is the mangling and I don't think mutt should jump through hoops in order to handle them. Cheers, -- Bertrand Yvain http://www.IELO.net/ signature.asc Description: Digital signature
Re: [PATCH] Adequately read mailboxes with s/@/ at / obfuscations
* On 06 May 2010, Bertrand Yvain wrote: > On Tue, May 04, 2010 at 10:55:46PM -0500, David Champion wrote: > > Adequately read mailboxes with s/@/ at / obfuscations. > > This kind of substitution is not reversible in the general case. > Consider for instance this e-mail address: "works at home"@some.dom.ain Of course. That is one of the reasons (digital signature invalidation is another[1]) for only handling rfc822 parsing in headers, and not messing with bodies. If you look at the code or try the patch, you see that it handles your example in exactly the same way as unpatched mutt does. This patch does not disrupt any signature system that relies on rfc822 address headers, because it does not modify the source text of the message. It only changes what is parsed into the in-memory header structure: what you can interact with in mutt. The point is to be able to read a mangled mailbox -- currently mutt fails miserably -- without changing it on disk. > Address obfuscation/mangling cause much more problems that they solve > (if any). The actual problem is the mangling I agree completely, but I can't stop people from mangling. I can undo their damage. > and I don't think mutt > should jump through hoops in order to handle them. I just want to be able to read the mailboxes that manglers have created. -- -D.d...@uchicago.eduIT ServicesUniversity of Chicago
Re: Adequately read mailboxes with s/@/ at / obfuscations
On 06May2010 11:53, David Champion wrote: | * On 06 May 2010, Bertrand Yvain wrote: | > On Tue, May 04, 2010 at 10:55:46PM -0500, David Champion wrote: | > > Adequately read mailboxes with s/@/ at / obfuscations. | > | > This kind of substitution is not reversible in the general case. | > Consider for instance this e-mail address: "works at home"@some.dom.ain | | Of course. [...] | This patch does not disrupt any signature system that relies on rfc822 | address headers, because it does not modify the source text of the | message. It only changes what is parsed into the in-memory header | structure: what you can interact with in mutt. The point is to be able | to read a mangled mailbox -- currently mutt fails miserably -- without | changing it on disk. [...] | > and I don't think mutt | > should jump through hoops in order to handle them. | | I just want to be able to read the mailboxes that manglers have created. Personally, I unmangle mailman archives when I collect them (eg: join list, suck down old archives). Then I file the de-mangled archives into legitimate mutt mail folders. Thus: get-mailman-archive archive-page-url... >mlist.mbox Then "mutt -f mlist.mbox" and save them all into the target folder where I'll be reading this stuff in the future, and where mairix will index it. So mutt (and mairix and any other mail tool) gets clean mail to play with. get-mailman-archive does two demanglings: the un-at- script and also "fix-mail-dates", since these also seem broken in many archives. Scripts here: http://www.cskk.ezoshosting.com/cs/css/bin/get-mailman-archive http://www.cskk.ezoshosting.com/cs/css/bin/un-at- http://www.cskk.ezoshosting.com/cs/css/bin/fix-mail-dates I guess this is a vote for demangling, not teaching mutt to recognise broken data. Cheers, -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ The code was willing, It considered your request, But the chips were weak. - Haiku Error Messages http://www.salonmagazine.com/21st/chal/1998/02/10chal2.html
