Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

Email headers not being ( correctly ) sent to evolution?

 

 

DBMail users RSS feed   Index | Next | Previous | View Threaded


dan at entropy

Feb 3, 2009, 6:20 PM

Post #1 of 11 (1135 views)
Permalink
Email headers not being ( correctly ) sent to evolution?

Just realised I have another issue ...

Email headers aren't properly making it from dbmail ( 2.3.5, post
upgrade from 2.3.3, as per my email from 12 hours back ). If I look at
any email message ( including old email imported from my backup, or
new email received since the new server went online ) from evolution,
I don't get *any* header info rendered in evo's email view. I usually
get 'from' 'to' 'cc' 'subject' and 'date'. If I hit 'CTRL U' to view
the message source for my previous email to the mailing list, here are
the headers I get according to evolution:

Received: from localhost (localhost [127.0.0.1]) by
archeopterix.entropy.homelinux.org (Postfix) with ESMTP id
47B083F46F for
; Wed, 4 Feb 2009 22:04:39 +1100 (EST)
Received: from archeopterix.entropy.homelinux.org ([127.0.0.1
On Tue, 03 Feb 2009 11: 12:17 +0100, Paul J Stevens wrote:
Message-Id:
MIME-Version: 1.0
X-Evolution-Source: imap://dan[at]entropy.homelinux.org/
From:
Date: Wed, 04 Feb 2009 12:06:03
+1100
Subject: No Subject

So something is seriously wrong there. The From: field is empty. The
Subject: field is empty ( and evo is adding 'No Subject' ). I don't
have the full list of smtp servers the email has passed through. And
there's a bit of email body inside the headers ( On Tues .... Paul J
Stevens wrote ... ).

However if I view the same email from Roundcubemail, I at least get
the From: field populated correctly. Unfortunately Roundcubemail
doesn't seem to allow viewing of the complete message source, so I
can't really say whether it's receiving everything or not.

I have tried removing my account from evolution, manually deleting
it's cache folders, and re-creating the account, and get the same
issue.

Sorry guys. I realise I'm using the development branch and can expect
some issues.

Dan


jake at vapourforge

Feb 3, 2009, 7:01 PM

Post #2 of 11 (1093 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

they changed the headers and headercache stuff, did you run the stuff to
migrate and fix that up?

Dan wrote:
>
> Just realised I have another issue ...
>
> Email headers aren't properly making it from dbmail ( 2.3.5, post
> upgrade from 2.3.3, as per my email from 12 hours back ). If I look at
> any email message ( including old email imported from my backup, or
> new email received since the new server went online ) from evolution,
> I don't get *any* header info rendered in evo's email view. I usually
> get 'from' 'to' 'cc' 'subject' and 'date'. If I hit 'CTRL U' to view
> the message source for my previous email to the mailing list, here are
> the headers I get according to evolution:
>
> Received: from localhost (localhost [127.0.0.1]) by
> archeopterix.entropy.homelinux.org (Postfix) with ESMTP id 47B083F46F for
> <dan[at]entropy.homelinux.org>; Wed, 4 Feb 2009 22:04:39 +1100 (EST)
> Received: from archeopterix.entropy.homelinux.org ([127.0.0.1
> On Tue, 03 Feb 2009 11: 12:17 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
> Message-Id: <1233748902l.6666l.80l@(none)>
> MIME-Version: 1.0
> X-Evolution-Source: imap://dan[at]entropy.homelinux.org/
> From:
> Date: Wed, 04 Feb 2009 12:06:03 +1100
> Subject: No Subject
>
> So something is seriously wrong there. The From: field is empty. The
> Subject: field is empty ( and evo is adding 'No Subject' ). I don't
> have the full list of smtp servers the email has passed through. And
> there's a bit of email body inside the headers ( On Tues .... Paul J
> Stevens wrote ... ).
>
> However if I view the same email from Roundcubemail, I at least get
> the From: field populated correctly. Unfortunately Roundcubemail
> doesn't seem to allow viewing of the complete message source, so I
> can't really say whether it's receiving everything or not.
>
> I have tried removing my account from evolution, manually deleting
> it's cache folders, and re-creating the account, and get the same issue.
>
> Sorry guys. I realise I'm using the development branch and can expect
> some issues.
>
> Dan
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail[at]dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>


paul at nfg

Feb 4, 2009, 12:39 AM

Post #3 of 11 (1091 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

Jake Anderson wrote:
> they changed the headers and headercache stuff, did you run the stuff to
> migrate and fix that up?

That was post-2.3.5

Also, if you view the message source you get the raw mimeparts. Those
are never modified by dbmail. Messages are cut-up into binary blobs at
the mime-boundaries, and those are stored as mimeparts. On retrieval
those mimeparts are reconnected into the original message.

In this case I suspect something else is going wrong and evolution tries
to compensate by messing up the message.

2.3.5 and beyond is being actively developed with thunderbird as
reference mailclient, and is also actively being tested on outlook.

Try installing TB to verify the message source. Also, I can't believe
roundcube can't do this. But I had to nuke roundcube here after a
security incident.



>
> Dan wrote:
>>
>> Just realised I have another issue ...
>>
>> Email headers aren't properly making it from dbmail ( 2.3.5, post
>> upgrade from 2.3.3, as per my email from 12 hours back ). If I look at
>> any email message ( including old email imported from my backup, or
>> new email received since the new server went online ) from evolution,
>> I don't get *any* header info rendered in evo's email view. I usually
>> get 'from' 'to' 'cc' 'subject' and 'date'. If I hit 'CTRL U' to view
>> the message source for my previous email to the mailing list, here are
>> the headers I get according to evolution:
>>
>> Received: from localhost (localhost [127.0.0.1]) by
>> archeopterix.entropy.homelinux.org (Postfix) with ESMTP id 47B083F46F
>> for
>> <dan[at]entropy.homelinux.org>; Wed, 4 Feb 2009 22:04:39 +1100 (EST)
>> Received: from archeopterix.entropy.homelinux.org ([127.0.0.1
>> On Tue, 03 Feb 2009 11: 12:17 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
>> Message-Id: <1233748902l.6666l.80l@(none)>
>> MIME-Version: 1.0
>> X-Evolution-Source: imap://dan[at]entropy.homelinux.org/
>> From:
>> Date: Wed, 04 Feb 2009 12:06:03 +1100
>> Subject: No Subject
>>
>> So something is seriously wrong there. The From: field is empty. The
>> Subject: field is empty ( and evo is adding 'No Subject' ). I don't
>> have the full list of smtp servers the email has passed through. And
>> there's a bit of email body inside the headers ( On Tues .... Paul J
>> Stevens wrote ... ).
>>
>> However if I view the same email from Roundcubemail, I at least get
>> the From: field populated correctly. Unfortunately Roundcubemail
>> doesn't seem to allow viewing of the complete message source, so I
>> can't really say whether it's receiving everything or not.
>>
>> I have tried removing my account from evolution, manually deleting
>> it's cache folders, and re-creating the account, and get the same issue.
>>
>> Sorry guys. I realise I'm using the development branch and can expect
>> some issues.
>>
>> Dan
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> DBmail mailing list
>> DBmail[at]dbmail.org
>> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail[at]dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


paul at nfg

Feb 4, 2009, 10:42 AM

Post #4 of 11 (1086 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

Dan,

I just tested evolution on a post 2.3.5 installation. All is peachy
clean for me. And that's on a real eat-my-own-dogfood installation.

Sounds to me like your mysqldump and reload messed things up badly.


Dan wrote:
> Just realised I have another issue ...
>
> Email headers aren't properly making it from dbmail ( 2.3.5, post
> upgrade from 2.3.3, as per my email from 12 hours back ). If I look at
> any email message ( including old email imported from my backup, or new
> email received since the new server went online ) from evolution, I
> don't get *any* header info rendered in evo's email view. I usually get
> 'from' 'to' 'cc' 'subject' and 'date'. If I hit 'CTRL U' to view the
> message source for my previous email to the mailing list, here are the
> headers I get according to evolution:
>
> Received: from localhost (localhost [127.0.0.1]) by
> archeopterix.entropy.homelinux.org (Postfix) with ESMTP id 47B083F46F for
> <dan[at]entropy.homelinux.org>; Wed, 4 Feb 2009 22:04:39 +1100 (EST)
> Received: from archeopterix.entropy.homelinux.org ([127.0.0.1
> On Tue, 03 Feb 2009 11: 12:17 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
> Message-Id: <1233748902l.6666l.80l@(none)>
> MIME-Version: 1.0
> X-Evolution-Source: imap://dan[at]entropy.homelinux.org/
> From:
> Date: Wed, 04 Feb 2009 12:06:03 +1100
> Subject: No Subject
>
> So something is seriously wrong there. The From: field is empty. The
> Subject: field is empty ( and evo is adding 'No Subject' ). I don't have
> the full list of smtp servers the email has passed through. And there's
> a bit of email body inside the headers ( On Tues .... Paul J Stevens
> wrote ... ).
>
> However if I view the same email from Roundcubemail, I at least get the
> From: field populated correctly. Unfortunately Roundcubemail doesn't
> seem to allow viewing of the complete message source, so I can't really
> say whether it's receiving everything or not.
>
> I have tried removing my account from evolution, manually deleting it's
> cache folders, and re-creating the account, and get the same issue.
>
> Sorry guys. I realise I'm using the development branch and can expect
> some issues.
>
> Dan
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail[at]dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


dan at entropy

Feb 4, 2009, 4:20 PM

Post #5 of 11 (1080 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

On Wed, 04 Feb 2009 19:42:29 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:

> I just tested evolution on a post 2.3.5 installation. All is peachy
> clean for me. And that's on a real eat-my-own-dogfood installation.

Hmmm. OK. What upgrades *should* I have done between 2.3.3 and 2.3.5. I
found an upgrade script in the sql/mysql folder for 2.3.5, and ran that. Is
that it?

> Sounds to me like your mysqldump and reload messed things up badly.

That's highly unlikely. I was regularly ( every month ) checking the
integrity of my backups my importing into another database. Also, that
would only explain corruption on old messages, but I've got the same for
incoming messages now.

> 2.3.5 and beyond is being actively developed with thunderbird as
> reference mailclient, and is also actively being tested on outlook.
>
> Try installing TB to verify the message source.

Just did that. Same thing :(

If anyone has any other ideas, I'm more than happy to try. Otherwise I
suppose I'm looking at setting up a new database, and attempting to migrate
whatever mail I can. Sounds messy, time consuming, and will crystalise my
losses in terms of message headers, but I don't have any other ideas ...

Here's what thunderbird sees when I view message source on one of your
messages:

Received: from localhost (localhost [127.0.0.1])
by archeopterix.entropy.homelinux.org (Postfix) with ESMTP id 889488D15
for <dan[at]entropy.homelinux.org>; Thu, 5 Feb 2009 06:39:53 +1100 (EST)
Received: from archeopterix.entropy.homelinux.org ([127.0.0.1]
Jake Anderson wrote:
X-Invalid-Header: > they changed the headers and headercache stuff, did you
run the stuff to
X-Invalid-Header: > migrate and fix that up?
Message-Id: <1233826830l.6666l.1734l@(none)>
MIME-Version: 1.0

That was post-2.3.5

Also, if you view the message source you get the raw mimeparts. Those
are never modified by dbmail. Messages are cut-up into binary blobs at
the mime-boundaries, and those are stored as mimeparts. On retrieval
those mimeparts are reconnected into the original message.

In this case I suspect something else is going wrong and evolution tries
to compensate by messing up the message.

2.3.5 and beyond is being actively developed with thunderbird as
reference mailclient, and is also actively being tested on outlook.

Try installing TB to verify the message source. Also, I can't believe
roundcube can't do this. But I had to nuke roundcube here after a
security incident.

< REST OF MESSAGE SNIPPED >

_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


paul at nfg

Feb 5, 2009, 12:12 AM

Post #6 of 11 (1072 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

Dan,



Dan wrote:
> On Wed, 04 Feb 2009 19:42:29 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
>
>> I just tested evolution on a post 2.3.5 installation. All is peachy
>> clean for me. And that's on a real eat-my-own-dogfood installation.
>
> Hmmm. OK. What upgrades *should* I have done between 2.3.3 and 2.3.5. I
> found an upgrade script in the sql/mysql folder for 2.3.5, and ran that. Is
> that it?

Yes it is.

>> Sounds to me like your mysqldump and reload messed things up badly.
>
> That's highly unlikely. I was regularly ( every month ) checking the
> integrity of my backups my importing into another database. Also, that
> would only explain corruption on old messages, but I've got the same for
> incoming messages now.

Question is whether the data in the store is correct. Try validating the
content of your database.

For old messages, find a message_idnr of interest, and lookup the
physmessage_id. Then run:

SELECT b.messageblk FROM dbmail_messageblks b
JOIN dbmail_physmessage p ON b.physmessage_id=p.id
WHERE b.physmessage_id = <physmessage_id>
ORDER BY b.messageblk_idnr;

This should return the complete raw message.

For newer (post 2.3.2) insertions:

SELECT p.data
FROM dbmail_mimeparts p
JOIN dbmail_partlists l ON p.id = l.part_id
JOIN dbmail_physmessage ph ON ph.id = l.physmessage_id
WHERE l.physmessage_id = <physmessage_id>
ORDER BY l.part_key,l.part_order ASC;

This should return the complete raw message, minus the mimepart boundaries.

You can append a 'LIMIT 1' to both queries to retrieve just the message
headers.



--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


paul at nfg

Feb 5, 2009, 1:28 PM

Post #7 of 11 (1066 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

This could indeed be related to

http://www.dbmail.org/mantis/view.php?id=752

I'd still like the info kindly requested below.


Paul J Stevens wrote:
> Dan,
>
>
>
> Dan wrote:
>> On Wed, 04 Feb 2009 19:42:29 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
>>
>>> I just tested evolution on a post 2.3.5 installation. All is peachy
>>> clean for me. And that's on a real eat-my-own-dogfood installation.
>> Hmmm. OK. What upgrades *should* I have done between 2.3.3 and 2.3.5. I
>> found an upgrade script in the sql/mysql folder for 2.3.5, and ran that. Is
>> that it?
>
> Yes it is.
>
>>> Sounds to me like your mysqldump and reload messed things up badly.
>> That's highly unlikely. I was regularly ( every month ) checking the
>> integrity of my backups my importing into another database. Also, that
>> would only explain corruption on old messages, but I've got the same for
>> incoming messages now.
>
> Question is whether the data in the store is correct. Try validating the
> content of your database.
>
> For old messages, find a message_idnr of interest, and lookup the
> physmessage_id. Then run:
>
> SELECT b.messageblk FROM dbmail_messageblks b
> JOIN dbmail_physmessage p ON b.physmessage_id=p.id
> WHERE b.physmessage_id = <physmessage_id>
> ORDER BY b.messageblk_idnr;
>
> This should return the complete raw message.
>
> For newer (post 2.3.2) insertions:
>
> SELECT p.data
> FROM dbmail_mimeparts p
> JOIN dbmail_partlists l ON p.id = l.part_id
> JOIN dbmail_physmessage ph ON ph.id = l.physmessage_id
> WHERE l.physmessage_id = <physmessage_id>
> ORDER BY l.part_key,l.part_order ASC;
>
> This should return the complete raw message, minus the mimepart boundaries.
>
> You can append a 'LIMIT 1' to both queries to retrieve just the message
> headers.
>
>
>


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


dan at entropy

Feb 5, 2009, 4:20 PM

Post #8 of 11 (1069 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

On Thu, 05 Feb 2009 22:28:20 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:

> I'd still like the info kindly requested below.

Sure. Been sleeping :)

>> For newer (post 2.3.2) insertions:
>>
>> SELECT p.data
>> FROM dbmail_mimeparts p
>> JOIN dbmail_partlists l ON p.id = l.part_id
>> JOIN dbmail_physmessage ph ON ph.id = l.physmessage_id
>> WHERE l.physmessage_id = <physmessage_id>
>> ORDER BY l.part_key,l.part_order ASC;

AHA! AHA! It's all there ( tested both queries you posted ). eg ( older
message ):

---

| Received: from localhost (localhost [127.0.0.1])
by nun.entropy.homelinux.org (Postfix) with ESMTP id 77FA21F9453
for <dan[at]entropy.homelinux.org>; Fri, 29 Feb 2008 09:21:40 +1100
(EST)
Received: from nun.entropy.homelinux.org ([127.0.0.1])
by localhost (entropy.homelinux.org [127.0.0.1]) (amavisd-maia,
port 10024)
with LMTP id 28109-01 for <dan[at]entropy.homelinux.org>;
Fri, 29 Feb 2008 09:21:30 +1100 (EST)
Received: from lists-outbound.sourceforge.net
(lists-outbound.sourceforge.net [66.35.250.225])
by nun.entropy.homelinux.org (Postfix) with ESMTP id 09E9A2DC388
for <dan[at]entropy.homelinux.org>; Fri, 29 Feb 2008 09:21:29 +1100
(EST)
Received: from sc8-sf-list1-new.sourceforge.net
(sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])
by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id
CCCE1120A1;
Thu, 28 Feb 2008 14:22:02 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
helo=mail.sourceforge.net)
by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)
id 1JUr8Z-00021u-Pb for dri-devel[at]lists.sourceforge.net;
Thu, 28 Feb 2008 14:22:00 -0800
Received: from nox.protox.org ([88.191.38.29]) by mail.sourceforge.net
with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id
1JUr8X-0002AJ-VD
for dri-devel[at]lists.sourceforge.net; Thu, 28 Feb 2008 14:21:59
-0800
Received: from randy (ram94-3-82-224-48-207.fbx.proxad.net [82.224.48.207])
(using TLSv1
with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client
certificate requested)
by nox.protox.org (Postfix) with ESMTP id 76532169DF0;
Thu, 28 Feb 2008 23:21:40 +0100 (CET)
Date: Thu, 28 Feb 2008 23:21:43 +0100
From: Jerome Glisse <glisse[at]freedesktop.org>
To: "Jakob Bornecrantz" <wallbraker[at]gmail.com>
Subject: Re: Fwd: kernel modesetting progress report....
Message-Id: <20080228232143.f547eabe.glisse[at]freedesktop.org>
In-Reply-To: <427ca1a20802281012p7e8850aat835eeb9f3977f86b[at]mail.gmail.com>
References: <21d7e9970802272253h1a76ef0fh9d9a991616018b17[at]mail.gmail.com>
<20080228143617.6f187617.glisse[at]freedesktop.org>
<427ca1a20802281008s33d9c3cbk6293903e2aa4ed9f[at]mail.gmail.com>
<427ca1a20802281012p7e8850aat835eeb9f3977f86b[at]mail.gmail.com>
Organization: freedesktop.org
X-Mailer: Sylpheed 2.4.5 (GTK+ 2.12.0; x86_64-pc-linux-gnu)
Cc: dri-devel[at]lists.sf.net, xorg[at]lists.freedesktop.org
X-BeenThere: dri-devel[at]lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <dri-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/dri-devel>,

<mailto:dri-devel-request[at]lists.sourceforge.net?subject=unsubscribe>
List-Archive:
<http://sourceforge.net/mailarchive/forum.php?forum_name=dri-devel>
List-Post: <mailto:dri-devel[at]lists.sourceforge.net>
List-Help: <mailto:dri-devel-request[at]lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/dri-devel>,
<mailto:dri-devel-request[at]lists.sourceforge.net?subject=subscribe>
Sender: dri-devel-bounces[at]lists.sourceforge.net
Errors-To: dri-devel-bounces[at]lists.sourceforge.net
X-Virus-Scanned: Maia Mailguard 1.0.2a
Return-Path: dri-devel-bounces[at]lists.sourceforge.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

---

So it looks like the data is good ( cool ). I'm happy to do what I can with
more diagnosis, but unfortunately I'm not yet very handy with C ( learning,
but like I say ... not very handy yet ). I'm good with SQL though, if
that's going to help ...

Dan

_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


dan at entropy

Feb 8, 2009, 6:20 PM

Post #9 of 11 (1037 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

I've done some more testing:

- backing up DB, dropping, recreating fresh schema, recreating
accounts

- rebuilding libzdb without optimization

- upgrading gmime to gmime-2.2.23

- rolling back to 2.3.3 ( dropped / recreated DB & accounts )

Nothing has fixed my problems. Emails seem to be getting into the
database with their headers intact ( as evidenced by queries that Paul
posted in reply to me ). But they don't come back out well at all. In
particular, I'm getting:

- headers truncated

- bits of email body inside headers

- headers missing completely

Does anyone have any other ideas about what might be up? I assumed
going back to 2.3.3 would fix things, but instead behaves the same way
on my system. So I assume the problem lies elsewhere? What other libs
are involved? Already rebuild glib and gmime. Anything else?
Dan


paul at nfg

Feb 9, 2009, 12:01 AM

Post #10 of 11 (1029 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

Dan wrote:
>
> I've done some more testing:
>
> - backing up DB, dropping, recreating fresh schema, recreating
> accounts
>
> - rebuilding libzdb without optimization
>
> - upgrading gmime to gmime-2.2.23

There is your problem. Your problem may very well be related to bug
#752. Try gmime-2.2.11 as present in debian/etch and ubuntu/hardy.

Only yesterday did I update the code to fix some problems with gmime >=
2.2.22.





>
> - rolling back to 2.3.3 ( dropped / recreated DB & accounts )
>
> Nothing has fixed my problems. Emails seem to be getting into the
> database with their headers intact ( as evidenced by queries that Paul
> posted in reply to me ). But they don't come back out well at all. In
> particular, I'm getting:
>
> - headers truncated
>
> - bits of email body inside headers
>
> - headers missing completely
>
> Does anyone have any other ideas about what might be up? I assumed
> going back to 2.3.3 would fix things, but instead behaves the same way
> on my system. So I assume the problem lies elsewhere? What other libs
> are involved? Already rebuild glib and gmime. Anything else?
> Dan
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail[at]dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail


dan at entropy

Feb 10, 2009, 6:20 AM

Post #11 of 11 (1009 views)
Permalink
Re: Email headers not being ( correctly ) sent to evolution? [In reply to]

On Mon, 09 Feb 2009 09:01:11 +0100, Paul J Stevens <paul[at]nfg.nl> wrote:
> There is your problem. Your problem may very well be related to bug
> #752. Try gmime-2.2.11 as present in debian/etch and ubuntu/hardy.
>
> Only yesterday did I update the code to fix some problems with gmime >=
> 2.2.22.

OK. I've downgraded to gmime-2.2.11. Also rebuilt dbmail after this. Still
no change :(

Dan

>
>
>
>
>>
>> - rolling back to 2.3.3 ( dropped / recreated DB & accounts )
>>
>> Nothing has fixed my problems. Emails seem to be getting into the
>> database with their headers intact ( as evidenced by queries that Paul
>> posted in reply to me ). But they don't come back out well at all. In
>> particular, I'm getting:
>>
>> - headers truncated
>>
>> - bits of email body inside headers
>>
>> - headers missing completely
>>
>> Does anyone have any other ideas about what might be up? I assumed
>> going back to 2.3.3 would fix things, but instead behaves the same way
>> on my system. So I assume the problem lies elsewhere? What other libs
>> are involved? Already rebuild glib and gmime. Anything else?
>> Dan
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> DBmail mailing list
>> DBmail[at]dbmail.org
>> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>
>
>

_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.