From mboxrd@z Thu Jan 1 00:00:00 1970 From: tocer.deng@gmail.com (tocer) Date: Fri, 5 Dec 2008 10:42:38 +0800 Subject: [sup-talk] mismatch in mbox file offset 0 In-Reply-To: References: <49354C2B.502@gmail.com> <1228234512-sup-3309@entry> <20805870.post@talk.nabble.com> <1228294025-sup-7941@ausone.inria.fr> Message-ID: 2008/12/3 Nicolas Pouillard : > Excerpts from tocer's message of Wed Dec 03 04:04:25 +0100 2008: >> >> > Scanning mbox:/home/dm/mail/vim... >> > problem getting messages from mbox:/home/dm/mail/vim: mismatch in mbox >> > file >> > offset 0: "Return-Path: \n". >> >> Is the very first line of that mbox "Return-Path: "? >> If so, that's not a valid mbox. >> >> >> >> No, it's a valid mbox, refer http://en.wikipedia.org/wiki/Return_path >> >> it works if I relace return_path with "from ". I'll try to define a rule to >> do replacement >> in procmailrc. But it would be good idea to dealing correctly it in sup :) > > I think you make the confusion between the email field "From:" and the mbox > email separator "From ". "Return-Path:" is also an email field, so I think > your email is not properly wrapped to be in an mbox. No, I don't. Now I solve it by adding the following lines into .procmailrc's header :0 fhw | formail -I "From " -a "From " I think it's helpful if someone use procmail as MTA >> And it seems that sup-sync can't run while sup is running. It means that I >> can't open >> sup in whole day because I need sup-sync run when I get new mail if I use >> some mbox >> as source > > Yes there is a lock on the index to avoid data-corruption. > > -- > Nicolas Pouillard aka Ertai >