From: tocer.deng@gmail.com (tocer)
Subject: [sup-talk] mismatch in mbox file offset 0
Date: Fri, 5 Dec 2008 10:42:38 +0800 [thread overview]
Message-ID: <d5ea6e840812041842mc5838e1m91f78f88a4d9d063@mail.gmail.com> (raw)
In-Reply-To: <d5ea6e840812041839k11f062b6n5d7f5aa518c82146@mail.gmail.com>
2008/12/3 Nicolas Pouillard <nicolas.pouillard at gmail.com>:
> 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: <yaksavage at gmail.com>\n".
>>
>> Is the very first line of that mbox "Return-Path: <yaksavage at gmail.com>"?
>> 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
>
prev parent reply other threads:[~2008-12-05 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 14:54 tocer
2008-12-02 16:17 ` William Morgan
2008-12-03 3:04 ` tocer
2008-12-03 3:39 ` Christopher Warrington
[not found] ` <1228294025-sup-7941@ausone.inria.fr>
[not found] ` <d5ea6e840812041839k11f062b6n5d7f5aa518c82146@mail.gmail.com>
2008-12-05 2:42 ` tocer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5ea6e840812041842mc5838e1m91f78f88a4d9d063@mail.gmail.com \
--to=tocer.deng@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox