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 Puryear Information Technology, LLC Baton Rouge, LA * 225-706-8414 http://www.puryear-it.com Visit http://www.puryear-it.com/pubs/ebooks/ to download your free copies of: "Best Practices for Managing Linux and UNIX Servers" "Spam Fighting and Email Security in the 21st Century" Dustin Puryear wrote: > That's for EVERY email? Weird. If memory serves, that's a MIME parsing > issue, but I could be wrong. Ronnie? > > -- > Puryear Information Technology, LLC > Baton Rouge, LA * 225-706-8414 > http://www.puryear-it.com > > Author, "Best Practices for Managing Linux and UNIX Servers" > http://www.puryear-it.com/pubs/linux-unix-best-practices > > Identity Management, LDAP, and Linux Integration > > > Fernando Vilas wrote: > >> Back to technical topics... Whenever I pull my LSU email via POP, with >> fetchmail, or on PAWS, it has an = inserted before every newline, and >> randomly, =20 or 3D scattered in the email. Is there a setting that I >> should >> be looking at to fix this, or should I just add a sed filter to >> my .procmailrc on my home server? >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> General mailing list >> General at brlug.net >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> > > _______________________________________________ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.brlug.net/pipermail/general_brlug.net/attachments/20070928/02712a69/attachment.html
