Re: Unexpected filtering of headers
- From: manu <eallaud yahoo fr>
- To: Andreas Schmidt <andy space wh1 tu-dresden de>
- Cc: balsa-list gnome org
- Subject: Re: Unexpected filtering of headers
- Date: Tue, 29 Jun 2004 05:02:13 +0000
On 28.06.2004 06:00:30, Andreas Schmidt wrote:
On 2004.06.28 05:13, manu wrote:
Nope that was perfect! And sorry for the broken patch, it seems that
I was passing around a pointer on a freed string!
Could you please try this one?
Sorry I do not have those fancy mails with several headers to test
it
thoroughly ;-)
OK, this one worked better; the messages with multiple headers got
filtered now. However, some things are still weird. Don't know if it
has anything to do with your patch or whether it's a problem with
something else in HEAD, though.
1) After filtering out those messages with several X-original-to
headers, I made a copy of ~/mail/ so I could run balsa from HEAD and
from unstable alternately with the same stock of mails. There were 28
mails in the Inbox. Unstable would filter all of them, HEAD left them
all there.
First: what do you call unstable and HEAD. For me HEAD is 2.1.x, so it
would be unstable in some sense. And I do have some filtering issues
with it (it "forgets" to filter some mails, I have no idea why for
now).
2) Then, HEAD seemed not to be able to recognize what mails had been
marked as "Read" already. Instead, more or less random, obviously old
messages were marked as "unread". I checked twice with unstable
(which
didn't mark these messages) and HEAD (which always chose to mark the
same messages); but I can't imagine why these messages were always
marked unread.
3) This may be an issue with libgmime2.1. I've updated to 2.1.6-1
this
morning. Attempts to scan mail folders and filter or access mails
resulted in messages like this:
(balsa:32683): gmime-CRITICAL **: file gmime-content-type.c: line 180
(g_mime_content_type_destroy): assertion `mime_type != NULL' failed
This disappears when libgmime2.1 is downgraded to 2.1.5-1.
I think this has been fixed in CVS gmime.
4) In some big mailboxes, HEAD seems to mess up the date displayed in
the tree view. These are headers displayed if the message is
selected:
Subject: Re: Debian Social Contract/Release -> Krise?
Date: 2004.05.03 18:50
From: Sven Hartge <lists ds9 gnuu de>
To: debian-user-german lists debian org
Subject: Re: Debian Social Contract/Release -> Krise?
Date: 2004.05.03 10:37
From: Sven Hartge <lists ds9 gnuu de>
To: debian-user-german lists debian org
Subject: Re: LG-Brenner legt System lahm
Date: 2004.06.01 23:45
From: Sven Hartge <lists ds9 gnuu de>
To: debian-user-german lists debian org
Subject: Re: root-Filesystem remountet ro
Date: 2004.06.24 19:32
From: Sven Hartge <lists ds9 gnuu de>
To: debian-user-german lists debian org
In tree view, for all of these mails "01-01-1970 01:00" is displayed
as received-date. With unstable, the date is shown correctly both in
tree and in message view.
hmm, no idea here, hopefully someone a bit less clueless than me will
hop in the thread ;-)
Bye
Manu
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]