When indexing my mail history, I saw various complaints about things that "could not be parsed." Some look like this (I kid you not):
' in /home/dave/Maildir/.zz_archive.2007.12/cur/1197763800.85556FMIc25369.boost-consulting.com:2,S could not be parsed Others are more legible, for example: Header 'text/plain; charset=""' in /home/dave/Maildir/.zz_archive.2008.04/cur/1207769548.P98977Q0M318028.boost-consulting.com:2,Sb could not be parsed Header 'multipart/report; report-type=delivery-status boundary="-------=_6EA978CF.6052361B"' in /home/dave/Maildir/.zz_archive.2008.04/cur/1207835495.P16385Q0M795970.boost-consulting.com:2,Sb could not be parsed Header 'multipart/alternative; boundary="mUlTiPaRtBoUnDaRy_MailInBlack"; ' in /home/dave/Maildir/.zz_archive.2008.04/cur/1207840036.P17565Q0M59056.boost-consulting.com:2,Sb could not be parsed Giving up on message /home/dave/Maildir/.zz_archive.2009.06/cur/1244069561.M250971P39261.boost-consulting.com,W=20556:2, with bad header Skipping /home/dave/Maildir/.zz_archive.2009.06/cur/1244069561.M250971P39261.boost-consulting.com,W=20556:2, (could not parse message) Are these mairix bugs? Would you like examples of the messages causing these complaints? -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com BoostPro Computing http://www.boostpro.com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mairix-users mailing list Mairix-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mairix-users
