* [sup-talk] Crash after sending a message
@ 2009-06-11 10:48 Fabio Riga
2009-06-11 11:39 ` Fabio Riga
0 siblings, 1 reply; 12+ messages in thread
From: Fabio Riga @ 2009-06-11 10:48 UTC (permalink / raw)
Hi all,
First of all, Sup is a great peace of software because it's a superior and
simplified Mutt, it's fast, it isn't web-based (I hate web-based
client...) and... Well, great job!
I started using 0.7, with no problems at all, excepting those crappy
character on screen... Since upgrading to 0.8 my screen looks very nice,
but when I send a message, Sup crashes badly. It seems a problem
with Ferret failing indexing my Sent box (attached exception-log). After
a sup-sync, there are no Sent messages in index. Maybe it's a problem
with locale (it) as sup-sync -a sup://sent gives me a lot of lines like:
[Thu Jun 11 12:32:36 +0200 2009] found invalid date in potential mbox
split line, not splitting: "From usul at aruba.it gio giu 11 11:45:37 +0200
2009\n"
Scanned 14, added 0, updated 14 messages from sup://sent.
_My sent messages are much more then 14!_
Anyway, messages are sent before the crash.. like this one!
Ideas?
Thanks,
Fabio
--
Fabio Riga
348 4458014 - fabio at comunicattiva.it
ComunicAttiva S.a.s. di Silvana D'Agata & C.
via Campestre,189 - Sesto San Giovanni (MI) - Italia
tel. 02 97373202 - fax 02 97373474
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090611/fc505855/attachment.txt>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-11 10:48 [sup-talk] Crash after sending a message Fabio Riga
@ 2009-06-11 11:39 ` Fabio Riga
2009-06-15 16:53 ` William Morgan
0 siblings, 1 reply; 12+ messages in thread
From: Fabio Riga @ 2009-06-11 11:39 UTC (permalink / raw)
Excerpts from Fabio Riga's message of Thu Jun 11 12:48:59 +0200 2009:
> a sup-sync, there are no Sent messages in index. Maybe it's a problem
> with locale (it) as sup-sync -a sup://sent gives me a lot of lines like:
>
> [Thu Jun 11 12:32:36 +0200 2009] found invalid date in potential mbox
> split line, not splitting: "From usul at aruba.it Thu Jun 11 11:45:37 +0200
> 2009\n"
> Scanned 14, added 0, updated 14 messages from sup://sent.
>
Hello again,
I translated with a script names of days and months in ~/.sup/sent.mbox,
then made a sup-sync -a sup://sent.mbox and run
$ LANG=C sup
All is fine, I just need to remember to launch sup this way. Maybe it
needs some work on localization?
Cheers,
Fabio
--
Fabio Riga
348 4458014 - fabio at comunicattiva.it
ComunicAttiva S.a.s. di Silvana D'Agata & C.
via Campestre,189 - Sesto San Giovanni (MI) - Italia
tel. 02 97373202 - fax 02 97373474
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-11 11:39 ` Fabio Riga
@ 2009-06-15 16:53 ` William Morgan
2009-06-15 19:11 ` Guillaume Quintard
2009-06-18 9:00 ` Fabio Riga
0 siblings, 2 replies; 12+ messages in thread
From: William Morgan @ 2009-06-15 16:53 UTC (permalink / raw)
Reformatted excerpts from Fabio Riga's message of 2009-06-11:
> All is fine, I just need to remember to launch sup this way. Maybe it
> needs some work on localization?
Sorry about that. The problem is that Sup was writing an invalid
sent.mbox file in certain locales, including yours, and then dying when
it couldn't parse its own file. If you update to the latest git, this
should be fixed for new messages, and you shouldn't need the LANG=C
hack.
Please let me know if you have any more problems.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-15 16:53 ` William Morgan
@ 2009-06-15 19:11 ` Guillaume Quintard
2009-06-15 19:17 ` William Morgan
2009-06-18 9:00 ` Fabio Riga
1 sibling, 1 reply; 12+ messages in thread
From: Guillaume Quintard @ 2009-06-15 19:11 UTC (permalink / raw)
Excerpts from William Morgan's message of Mon Jun 15 18:53:47 +0200 2009:
> Please let me know if you have any more problems.
Still have it here, arg., with next.
There is a sense of tragic in the fact that I know that after sending
that mail to get help, sup will inevitably crash :-)
--
Guillaume
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-15 19:11 ` Guillaume Quintard
@ 2009-06-15 19:17 ` William Morgan
2009-06-15 21:30 ` Guillaume Quintard
0 siblings, 1 reply; 12+ messages in thread
From: William Morgan @ 2009-06-15 19:17 UTC (permalink / raw)
Reformatted excerpts from Guillaume Quintard's message of 2009-06-15:
> Still have it here, arg., with next.
You probably still have broken lines in your sent.mbox. This fix only
works for new messages, so you'll have to edit sent.mbox by hand. Look
for "From " lines that have a localized timestamp in them, and change
them to something that Time.parse can parse. It's probably possible to
write a script to do this if you have a large number of htem.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-15 19:17 ` William Morgan
@ 2009-06-15 21:30 ` Guillaume Quintard
2009-06-16 2:18 ` William Morgan
0 siblings, 1 reply; 12+ messages in thread
From: Guillaume Quintard @ 2009-06-15 21:30 UTC (permalink / raw)
Excerpts from William Morgan's message of Mon Jun 15 21:17:20 +0200 2009:
> You probably still have broken lines in your sent.mbox. This fix only
> works for new messages, so you'll have to edit sent.mbox by hand. Look
> for "From " lines that have a localized timestamp in them, and change
> them to something that Time.parse can parse. It's probably possible to
> write a script to do this if you have a large number of htem.
I think I said "save them in the mbox" to sup-config, and I still get
that behaviour, so what? Do I dig in the 3.2Go .mbox (please, not that one),
do I change to "save in sup://sent"? BTW, I renamed my sent.mbox, just
in case.
If I really have to go into the huge mbox, what should I look for
exactly, I didn't quite get what the parser failed on.
Regards
--
Guillaume
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-15 21:30 ` Guillaume Quintard
@ 2009-06-16 2:18 ` William Morgan
2009-06-16 8:06 ` Guillaume Quintard
0 siblings, 1 reply; 12+ messages in thread
From: William Morgan @ 2009-06-16 2:18 UTC (permalink / raw)
Reformatted excerpts from Guillaume Quintard's message of 2009-06-15:
> I think I said "save them in the mbox" to sup-config, and I still get
> that behaviour, so what? Do I dig in the 3.2Go .mbox (please, not that
> one), do I change to "save in sup://sent"? BTW, I renamed my
> sent.mbox, just in case.
If you're seeing that error, you should edit the "From " lines in your
sent.mbox file (which is presumably not the 3.2g one).
You'll see something like:
From guillaume.quintard at gmail.com <date>
And a couple recent messages (i.e. at the bottom of the file) will have
a <date> that's been localized to your locale. That's what has to
change.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-16 2:18 ` William Morgan
@ 2009-06-16 8:06 ` Guillaume Quintard
2009-06-16 11:20 ` Ben Walton
0 siblings, 1 reply; 12+ messages in thread
From: Guillaume Quintard @ 2009-06-16 8:06 UTC (permalink / raw)
Excerpts from William Morgan's message of Tue Jun 16 04:18:05 +0200 2009:
> If you're seeing that error, you should edit the "From " lines in your
> sent.mbox file (which is presumably not the 3.2g one).
>
> You'll see something like:
> From guillaume.quintard at gmail.com <date>
>
> And a couple recent messages (i.e. at the bottom of the file) will have
> a <date> that's been localized to your locale. That's what has to
> change.
So, I grep'ed "save them in the mbox" from the big mbox, and from
sent.mbox, logically, I should have found 2 occurences, one in my mail,
one in yours, but found only one :-(.
I re-ran sup-config, told it to save in "sent", and that seems better.
But I still don't know where the few messages sent during that time are.
Plus, I sent a mail to one of my alternate addresses, and it popped up
in the mailbox, without the "Sent" label, is that expected?
--
Guillaume
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-16 8:06 ` Guillaume Quintard
@ 2009-06-16 11:20 ` Ben Walton
2009-06-16 11:52 ` Guillaume Quintard
0 siblings, 1 reply; 12+ messages in thread
From: Ben Walton @ 2009-06-16 11:20 UTC (permalink / raw)
Excerpts from Guillaume Quintard's message of Tue Jun 16 04:06:48 -0400 2009:
Hi Guillaume,
> I re-ran sup-config, told it to save in "sent", and that seems better.
> But I still don't know where the few messages sent during that time are.
> Plus, I sent a mail to one of my alternate addresses, and it popped up
> in the mailbox, without the "Sent" label, is that expected?
The patch that allows for using any (most) sources as the outbox
changed the way the sent label gets applied. When the message is
polled, the label 'sent' is applied iff the source of the message
matches the source uri in config.yaml. The default sent source
(outbox) is sup://sent, which translates to $SUB_BASE/sent.mbox
(normally ~/.sup/sent).
The other small behaviour change that this introduced was that
depending on poll intervals, sent messages may not be immediately
added to the index, but instead are picked up on the next run...I see
this with my Maildir outbox. The source used as the outbox is logged
at startup, although if you've restarted sup, that log is lost to you
now...
HTH
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090616/b648e879/attachment.bin>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-16 11:20 ` Ben Walton
@ 2009-06-16 11:52 ` Guillaume Quintard
2009-06-16 16:34 ` Ben Walton
0 siblings, 1 reply; 12+ messages in thread
From: Guillaume Quintard @ 2009-06-16 11:52 UTC (permalink / raw)
Excerpts from Ben Walton's message of Tue Jun 16 13:20:41 +0200 2009:
> The patch that allows for using any (most) sources as the outbox
> changed the way the sent label gets applied. When the message is
> polled, the label 'sent' is applied iff the source of the message
> matches the source uri in config.yaml. The default sent source
> (outbox) is sup://sent, which translates to $SUB_BASE/sent.mbox
> (normally ~/.sup/sent).
Well, it seems it's not the case, sent messages pop up in the mailbox
without the sent label, last message got this:
"From guillaume.quintard at gmail.com Tue Jun 16 13:47:26 +0200 2009"
as a first line, and it's my main address, yet no label.
Am I misunderstanding something?
--
Guillaume
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-16 11:52 ` Guillaume Quintard
@ 2009-06-16 16:34 ` Ben Walton
0 siblings, 0 replies; 12+ messages in thread
From: Ben Walton @ 2009-06-16 16:34 UTC (permalink / raw)
Excerpts from Guillaume Quintard's message of Tue Jun 16 07:52:35 -0400 2009:
> Well, it seems it's not the case, sent messages pop up in the mailbox
> without the sent label, last message got this:
> "From guillaume.quintard at gmail.com Tue Jun 16 13:47:26 +0200 2009"
> as a first line, and it's my main address, yet no label.
The sent label is filtered from the inbox view. Try searching for
sent mail with the search term: label:sent
> Am I misunderstanding something?
Maybe, but I may be misunderstanding too...
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090616/61ef63d0/attachment.bin>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [sup-talk] Crash after sending a message
2009-06-15 16:53 ` William Morgan
2009-06-15 19:11 ` Guillaume Quintard
@ 2009-06-18 9:00 ` Fabio Riga
1 sibling, 0 replies; 12+ messages in thread
From: Fabio Riga @ 2009-06-18 9:00 UTC (permalink / raw)
Excerpts from William Morgan's message of lun giu 15 18:53:47 +0200 2009:
> Sorry about that. The problem is that Sup was writing an invalid
> sent.mbox file in certain locales, including yours, and then dying when
> it couldn't parse its own file. If you update to the latest git, this
> should be fixed for new messages, and you shouldn't need the LANG=C
> hack.
>
> Please let me know if you have any more problems.
It seems ok with sup-git. I'd rather prefer to use a "stable" branch
instead of bleeding-edge, I don't feel like a developer...
Thank you,
Fabio
--
Fabio Riga
348 4458014 - fabio at comunicattiva.it
ComunicAttiva S.a.s. di Silvana D'Agata & C.
via Campestre,189 - Sesto San Giovanni (MI) - Italia
tel. 02 97373202 - fax 02 97373474
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2009-06-18 9:00 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-06-11 10:48 [sup-talk] Crash after sending a message Fabio Riga
2009-06-11 11:39 ` Fabio Riga
2009-06-15 16:53 ` William Morgan
2009-06-15 19:11 ` Guillaume Quintard
2009-06-15 19:17 ` William Morgan
2009-06-15 21:30 ` Guillaume Quintard
2009-06-16 2:18 ` William Morgan
2009-06-16 8:06 ` Guillaume Quintard
2009-06-16 11:20 ` Ben Walton
2009-06-16 11:52 ` Guillaume Quintard
2009-06-16 16:34 ` Ben Walton
2009-06-18 9:00 ` Fabio Riga
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox