Re your message below.

I have now deinstalled gmime gmime-26-2.6.16 and dropped down to
gmime-26-2.6.10 as per your recommendation.


I have then recompiled/installed dbmail 3.1.4 and noticed no change
(roundcube still failed to open a message it could open in dbmail 3.1.3).
By failed to open I mean no message text or attachments was shown.


I then deinstalled dbmail 3.1.4 and went down to dbmail 3.1.3 and again
roundcube could open the message.

 

For my own amusement I have realised I can take the source of the message
and use dbmail-deliver to insert it into a user's account. I took the source
from my test case message from a clean source which did not have anything to
do with my dbmail installation. 

 

Also note that this test case message entered my dbmail system for the first
time when it was running dbmail 3.1.4 with gmime-26-2.6.16.

 

So I installed dbmail 3.1.4 again and hand delivered the message roundcube
couldn't open into the mailbox and the result was Roundcube COULD open this
hand delivered message but Outlook still showed it corrupted (and in an
identical manner).

 

So all I have shown is a) on my system changing gmime version has not made a
difference for either 3.1.3 or 3.1.4 b) 3.1.3 and 3.1.4 are currently both
resulting in corrupt messages for me in Outlook.

 

p.s. for interests sake here is the example damaged message, you can see
Outlook seems to be presenting the HTML part:

 

IN OUTLOOK

"

Hi Daniel,<=span>

 

Thank you your for you= email, I have now updated the staff list for CWA
accordingly. I have emai=ed our accounts department with regards to the
additional costs and will c=me back to you as soon as possible.

"

 

IN GMAIL (text part)

Content-Type: text/plain; charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable

 

Hi Daniel,

 

Thank you your for your email, I have now updated the staff list for CWA ac=

cordingly. I have emailed our accounts department with regards to the addit=

ional costs and will come back to you as soon as possible.

 

IN GMAIL (text text/html)

<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Daniel,<o:p></o:p><=

/span></p>

<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=

n></p>

<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you your for you=

r email, I have now updated the staff list for CWA accordingly. I have emai=

led our accounts department with regards to the additional costs and will c=

ome back to you as soon as possible.<o:p></o:p></span></p>

 

 

 

 

 

Am 02.09.2013 18:53, schrieb "Daniel Schütze" <[email protected]>":

> I have quickly downgraded back to 3.1.3 from 3.1.4 because there were 

> messages which would now not even display in

> roundcube mail which had been working "fine" with 3.1.3 (displayed ok in 

> Roundcube, not in Outlook).  Messages with

> 3.1.4 are still heavily corrupted in Outlook for me.

 

this is really new in 3.1.4 and can be reproduced?

"messages" for me sounds like more than one?!

 

*wow* i am running load-tests on the final 3.1.4 this time

but after all the tests and fixes for border-cases I did

not explain that 3.1.4 could have a single problem more

than 3.1.3 - dmaned i never in my life spent more

time and energy in testing any software even to my

physical broders :-(

 

originally i planned to upgrade tomrrow but now i am unsure

are there people who can test oulook with all sorts of messages?

 

> I have sent some message source to Paul as shown in 3.1.4 (just now)
because 

> I don't feel happy posting messages on

> the general listing.

 

is in doubt also my primary way to go because this way i can submit

messages which are not critical but also not for public

 

> We were using gmime-24-2.4.32 for dbmail 3.0.2

 

2.6.9 until now did a good job for 3.0.x

2.6.12 broke it horrible

 

> Unfortunately the dbmail 3.1.3 port on FreeBSD required gmime 26 which was


> therefore built (gmime-26-2.6.16) and

> everything on our system has gotten a lot worse since 3.1.3 was installed.

> 

> Is there actually anything I can run to see if gmime is at fault here?

 

build preferable 2.6.10 in /usr/local and link dbmail aginst this version

2.6.10 is the version Paul is using on Ubuntu, well i have no idea

if this is a unpatched-upstream tarball

 

after force downgrade to 3.0.x and saw gmime 2.6.12 *horrible* break dbmail

at the moment hardly a smile will hit my face because i am missing the

feeling "if you do this it works" and Paul has *really* spent a lot of

energy in 3.1.x proven by unbelieveable 450 off-list mails between him

and me since 2013/07/25 counted in my archive yesterday

 

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to