At Mon, 4 Jan 2010 20:02:19 -0500, Ed Blackman wrote: > > [1 <multipart/signed (7bit)>] > [1.1 <text/plain; us-ascii (quoted-printable)>] > On Mon, Jan 04, 2010 at 06:45:21PM -0500, David Abrahams wrote: > >When indexing my mail history, I saw various complaints about things > >that "could not be parsed." Some look like this (I kid you not): > > I've experienced this, too. > > The command line for my mairix crontab entry is: > mairix 2>&1 | egrep -v '(could not.*parse|Can.t > (find|process).*boundary|mtime failed)' > > Those are all messages that don't seem to prevent mairix from indexing > the things I want indexed, so I filter them out. A better way to turn > off non-fatal warnings would be appreciated.
I'd prefer to have mairix understand the things it's complaining about so it could legitimately stop complaining. Here are a couple new ones: Header 'text/x-c++hdr; charset=US-ASCII; name="named_pipe.hpp"' in /home/dave/Maildir/.zz_archive.2010.01/cur/1262781433.M285914P91436.boostpro.com,W=18230:2, could not be parsed Header 'text/x-c++hdr; charset=US-ASCII; name="named_pipe_service.hpp"' in /home/dave/Maildir/.zz_archive.2010.01/cur/1262781433.M285914P91436.boostpro.com,W=18230:2, could not be parsed -- 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
