[brlug-general] email question

[Fernando Vilas]

On Friday 28 September 2007 10:48:00 Ronnie Gilkey wrote:
> It's a MUA issue, I've seen it before.  What happens is that some
> clients replace, or what they like to call "encoding", white-space or
> other items with "=<hex value>" (0x20 is hex for a space).  It's a
> really bad "encoding scheme".
>
> Ronnie
>

Yeah, I sort of figured they were the ASCII codes after the =, with the 
exception of the newline, whenever they introduce a line break.  Which could 
be helpful when writing a filter to call from procmail.  I'd prefer to find a 
different way, since my sed/sh skills are somewhat lacking compared to my 
C/C++ skills, but I'll script something if it's the easiest way.  If you've 
seen it before, maybe the script will be useful to others, so I'll share it.


-- 
Thanks,
Fernando Vilas
fvilas at iname.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.brlug.net/pipermail/general_brlug.net/attachments/20070928/b705df24/attachment.bin