Problem with international characters in the from field in SquirrelMail

[Peter Welzien]

Hi. I'm not sure if the problem I'm having is because of DBMail or
SquirrelMail. I've tried the SquirrelMail mailinglist without getting a
reply.

I'm having problems with international characters in the from field in
the message list in SquirrelMail 1.4.19. Instead of the actual characters
I see eg. =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= (quoted printable?). See
http://welzien.se/misc/squirrelmail.png for an example. For some reason
the characters look good in the subject field.

When I open the email, the from field display correctly though.

The from field in the email header:
From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <xxxxxxxxx@...>

The problem only occurs in the from field in the message list view.

I'm using DBMail 2.2.11_rc3-r1.

I believe that DBMail, mysql and Squirrelmail are all set to UTF8.

What else can I check to try to find the source of the problem?

--
/Peter Welzien


_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[John Fawcett-4]

On 23/10/09 20:03, Peter Welzien wrote:

> Hi. I'm not sure if the problem I'm having is because of DBMail or
> SquirrelMail. I've tried the SquirrelMail mailinglist without getting a
> reply.
>
> I'm having problems with international characters in the from field in
> the message list in SquirrelMail 1.4.19. Instead of the actual characters
> I see eg. =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= (quoted printable?). See
> http://welzien.se/misc/squirrelmail.png for an example. For some reason
> the characters look good in the subject field.
>
> When I open the email, the from field display correctly though.
>
> The from field in the email header:
> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <xxxxxxxxx@...>
>
> The problem only occurs in the from field in the message list view.
>
> I'm using DBMail 2.2.11_rc3-r1.
>
> I believe that DBMail, mysql and Squirrelmail are all set to UTF8.
>
> What else can I check to try to find the source of the problem?
>
>  

Peter
squirrelmail should display quoted printable "from" headers correctly
in the message list display. The header above looks fine, but it does
look a bit different to the one posted at the link. Are they from the
same message?
The position of the quoted-printable part is different and also there
is a " before the text. The " is probably what causes squirrelmail
not to be display the header correctly.
John

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Peter Welzien]

On Sun, 25 Oct 2009 21:09:00 +0100, John Fawcett <john.ml@...> wrote:

> Peter
> squirrelmail should display quoted printable "from" headers correctly
> in the message list display. The header above looks fine, but it does
> look a bit different to the one posted at the link. Are they from the
> same message?

Yes, they are.

> The position of the quoted-printable part is different and also there
> is a " before the text. The " is probably what causes squirrelmail
> not to be display the header correctly.

The " is not present in the raw mail header. I'm not really sure where it
comes from.

--
/Peter Welzien
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[John Fawcett-4]

On 25/10/09 21:36, Peter Welzien wrote:

> On Sun, 25 Oct 2009 21:09:00 +0100, John Fawcett <john.ml@...> wrote:
>
>  
>> The position of the quoted-printable part is different and also there
>> is a " before the text. The " is probably what causes squirrelmail
>> not to be display the header correctly.
>>    
> The " is not present in the raw mail header. I'm not really sure where it
> comes from.
>
>  

just to be sure: where did the info about the raw mail header come
from? e.g. by querying the database directly?
Is it the same value in the header cache table and the message
table?
John
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Peter Welzien]

On Sun, 25 Oct 2009 22:29:01 +0100, John Fawcett <john.ml@...> wrote:

>> The " is not present in the raw mail header. I'm not really sure where
it
>> comes from.

> just to be sure: where did the info about the raw mail header come
> from? e.g. by querying the database directly?

I got it when selecting "View Full Header" in SquirrelMail. It looks like
this:
From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>

> Is it the same value in the header cache table and the message
> table?

The value in dbmail_headervalue is:
"Rikard Åslund Tröger" <dhettneck@...>

dbmail_fromfield is:
fromname: Rikard Åslund Tröger
fromaddr: dhettneck@...

I don't know if I should look in any other tables.

I've noticed though that the from field displays correctly when using
roundcube.

--
/Peter Welzien
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[John Fawcett-4]

On 26/10/09 08:37, Peter Welzien wrote:

> On Sun, 25 Oct 2009 22:29:01 +0100, John Fawcett <john.ml@...> wrote:
>
>  
>>> The " is not present in the raw mail header. I'm not really sure where
>>>      
> it
>  
>>> comes from.
>>>      
>  
>> just to be sure: where did the info about the raw mail header come
>> from? e.g. by querying the database directly?
>>    
> I got it when selecting "View Full Header" in SquirrelMail. It looks like
> this:
> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>
>  
>> Is it the same value in the header cache table and the message
>> table?
>>    
> The value in dbmail_headervalue is:
> "Rikard Åslund Tröger" <dhettneck@...>
>  

looks ok
> dbmail_fromfield is:
> fromname: Rikard Åslund Tröger
> fromaddr: dhettneck@...
>
>  
looks ok
> I don't know if I should look in any other tables.
>
>  
the raw message will be in dbmail_messageblks

> I've noticed though that the from field displays correctly when using
> roundcube.
>
>  
it doesn't sound like a dbmail problem. On the other hand my squirrelmail
1.4.19 doesn't have any issues with displaying quoted printable headers
arriving from dbmail.
But first of all, you need to rule out that there is something wrong with
the message header in input, which I guess not but it's worth checking.
John

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Peter Welzien]

On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:

>> I don't know if I should look in any other tables.

> the raw message will be in dbmail_messageblks

> But first of all, you need to rule out that there is something wrong
with
> the message header in input, which I guess not but it's worth checking.
> John

The from line in the dbmail_messageblks table looks ok to me:
From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>

Does SquirrelMail use any libs for decoding these lines that can cause
these behaviours?

--
/Peter Welzien
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[John Fawcett-4]

On 27/10/09 09:30, Peter Welzien wrote:

> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:
>
>  
> The from line in the dbmail_messageblks table looks ok to me:
> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>
> Does SquirrelMail use any libs for decoding these lines that can cause
> these behaviours?
>
>  

Whenever I saw problems like this it was due to
badly formed input. In this case we're saying that the input looks
ok.
I think that problems on dbmail are almost certainly ruled out
(roundcube displays the info ok) though to verify that 100%
you'd have to execute the imap commands that squirrelmail
uses against the IMAP server and check the output.

So it sounds like the only way to get to the bottom of it is
by debugging squirrelmail.....

Squirrelmail uses functions/mime.php for decoding
quote-printable. There is also functions/i18n.php for char
set decoding.

The problem may not even be in squirrelmail itself but may
be in php or in the webserver php.ini settings (mbstring?).

At this point I'd suggest debugging the php code or getting
help on squirrelmail list.
John

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Peter Welzien]

On Tue, 27 Oct 2009 22:05:51 +0100, John Fawcett <john.ml@...> wrote:
> I think that problems on dbmail are almost certainly ruled out

> At this point I'd suggest debugging the php code or getting
> help on squirrelmail list.

Thank you very much for your help. I'll move on and see if I can get some
help on the squirrelmail list to track down the source of the problem.

--
/Peter Welzien
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Reindl Harald-2]

Sometimes we see this too, but i can not reproduce this

SquirrelMail seems not to be the reason because thunderbird and horde
have also the nearly same problem display a german "Ü". Looks like this
only happens with UTF7/UTF8

Header:      Benachrichtung zum =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus (Fehlgeschlagen)?=
Thunderbird: Benachrichtung zum =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus (Fehlgeschlagen)?=
Horde:       Benachrichtung   zum   +ANw-bermittlungsstatus   (Fehlgeschlagen)
Correct:     Benachrichtung zum Übermittlungsstatus (Fehlgeschlagen)
________________________

This is a bounce-message from a exim-mta over a barracuda-spam-firewall

Received: from barracuda.thelounge.net (barracuda.thelounge.net [10.0.0.20])
        by mail.thelounge.net (Postfix) with ESMTP id 08E47C9
        for <XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>; Tue, 27 Oct 2009 17:02:58 +0100 (CET)
X-ASG-Debug-ID: 1256659288-566918ac0001-ytSoTL
Received: from mx.inode.at (lb01nat30.inode.at [62.99.145.30])
        by barracuda.thelounge.net with ESMTP id GM7ZCSEAwMB3WNYd
        for <XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>; Tue, 27 Oct 2009 17:01:28 +0100 (CET)
X-Barracuda-Envelope-From:
Received: from [217.116.184.234] (port=8698 helo=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)
        by smartmx-09.inode.at with esmtpa (Exim 4.69) id 1N2oUC-0002fR-D3
        for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX; Tue, 27 Oct 2009 17:01:28 +0100
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
To: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Date: Tue, 27 Oct 2009 17:00:18 +0100
X-DSNContext: 335a7efd - 4523 - 00000001 - 80040546
Message-ID: <zC1GcVtUE00000814@XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>
X-ASG-Orig-Subj: Benachrichtung
        zum
        =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus
        (Fehlgeschlagen)?=
Subject: Benachrichtung
        zum
        =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus
        (Fehlgeschlagen)?=
X-Barracuda-Connect: lb01nat30.inode.at[62.99.145.30]
X-Barracuda-Start-Time: 1256659288
X-Barracuda-URL: http://barracuda.thelounge.net:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at thelounge.net
X-Barracuda-Spam-Score: 2.88
X-Barracuda-Spam-Status: No, SCORE=2.88 using global scores of TAG_LEVEL=3.5

________________________

A test with ISO-8859-1 shows all fine

Header:      =?ISO-8859-1?Q?Umlaut-Test_=FC=F6=E4?=
Thunderbird: Umlaut-Test üöä
Horde:       Umlaut-Test üöä
Correct:     Umlaut-Test üöä

Am 27.10.2009 09:30, schrieb Peter Welzien:

> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:
>
>>> I don't know if I should look in any other tables.
>
>> the raw message will be in dbmail_messageblks
>
>> But first of all, you need to rule out that there is something wrong
> with
>> the message header in input, which I guess not but it's worth checking.
>> John
>
> The from line in the dbmail_messageblks table looks ok to me:
> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>
> Does SquirrelMail use any libs for decoding these lines that can cause
> these behaviours?
>

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[John Fawcett-4]

On 28/10/09 14:54, Reindl Harald wrote:

> Sometimes we see this too, but i can not reproduce this
>
> SquirrelMail seems not to be the reason because thunderbird and horde
> have also the nearly same problem display a german "Ü". Looks like this
> only happens with UTF7/UTF8
>
> Header:      Benachrichtung zum =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus (Fehlgeschlagen)?=
> Thunderbird: Benachrichtung zum =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus (Fehlgeschlagen)?=
> Horde:       Benachrichtung   zum   +ANw-bermittlungsstatus   (Fehlgeschlagen)
> Correct:     Benachrichtung zum Übermittlungsstatus (Fehlgeschlagen)
> ________________________
>
>  

Harald
Looks like a different problem. I don't think that header follows any RFC.
John

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Peter Welzien]

On Tue, 27 Oct 2009 22:05:51 +0100, John Fawcett <john.ml@...> wrote:
> I think that problems on dbmail are almost certainly ruled out
> (roundcube displays the info ok) though to verify that 100%
> you'd have to execute the imap commands that squirrelmail
> uses against the IMAP server and check the output.

The message header looks like this:
From: =?iso-8859-1?B?UmlrYXJkIMVzbHVuZCBUcvZnZXI=?=
<dhettneck@...>

But FETCH 1:* (FLAGS BODY[HEADER.FIELDS (FROM)]) returns:
From: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?=
<dhettneck@...>

Why's that? Does dbmail modify the headers at insertion?

--
/Peter Welzien
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Daniel Urstöger]

Hi Peter,

I hope someone of the dev team can clear this up, I just remember this vaguely from developing my webmail client:

quoting the wikipedia article about MIME:

"encoding can be either "Q" denoting Q-encoding that is similar to the quoted-printable encoding, or "B" denoting base64 encoding."
(section: Encoded-Word)

The B obviously stands for base64 encoding, the q in the fetch retrieved header is Q-encoded.
So the header was for some reason changed from base64 to Q-encoded.

greetings,
Daniel

Am 15.11.2009 um 18:31 schrieb Peter Welzien:

> On Tue, 27 Oct 2009 22:05:51 +0100, John Fawcett <john.ml@...> wrote:
>> I think that problems on dbmail are almost certainly ruled out
>> (roundcube displays the info ok) though to verify that 100%
>> you'd have to execute the imap commands that squirrelmail
>> uses against the IMAP server and check the output.
>
> The message header looks like this:
> From: =?iso-8859-1?B?UmlrYXJkIMVzbHVuZCBUcvZnZXI=?=
> <dhettneck@...>
>
> But FETCH 1:* (FLAGS BODY[HEADER.FIELDS (FROM)]) returns:
> From: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?=
> <dhettneck@...>
>
> Why's that? Does dbmail modify the headers at insertion?
>
> --
> /Peter Welzien
> _______________________________________________
> DBmail mailing list
> DBmail@...
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Tomas Kuliavas]

John Fawcett-4 wrote:

On 27/10/09 09:30, Peter Welzien wrote:
> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <[e-mail]> wrote:
>
>  
> The from line in the dbmail_messageblks table looks ok to me:
> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <[e-mail]>
>
> Does SquirrelMail use any libs for decoding these lines that can cause
> these behaviours?
>
>  
Whenever I saw problems like this it was due to
badly formed input. In this case we're saying that the input looks
ok.
I think that problems on dbmail are almost certainly ruled out
(roundcube displays the info ok) though to verify that 100%
you'd have to execute the imap commands that squirrelmail
uses against the IMAP server and check the output.

It does not rule out dbmail. SquirrelMail displays same headers correctly on other servers.

Message has
From: =?utf-8?B?UmlrYXJkIMOFc2x1bmQgVHLDtmdlcg==?= <[e-mail]>

SquirrelMail issues
"UID FETCH some-message-ids (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type)"

DBMail 2.2.9 returns
from: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= <[e-mail]>

Your smart quoted printable encoder eats trailing double quote in display-name. It becomes part of encoded word and display-name is no longer atom or quoted-string. It is safer to encode everything and not to keep first word unencoded like your code does. Check string. If you notice that something in it must be encoded, encode whole string.

If you fixed it between 2.2.9 and 2.2.13, then package provided by Gentoo is broken and should be updated.

--
Tomas

[Paul J Stevens]

Peter Welzien wrote:

> On Tue, 27 Oct 2009 22:05:51 +0100, John Fawcett <john.ml@...> wrote:
>> I think that problems on dbmail are almost certainly ruled out
>> (roundcube displays the info ok) though to verify that 100%
>> you'd have to execute the imap commands that squirrelmail
>> uses against the IMAP server and check the output.
>
> The message header looks like this:
> From: =?iso-8859-1?B?UmlrYXJkIMVzbHVuZCBUcvZnZXI=?=
> <dhettneck@...>
>
> But FETCH 1:* (FLAGS BODY[HEADER.FIELDS (FROM)]) returns:
> From: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?=
> <dhettneck@...>
>
> Why's that? Does dbmail modify the headers at insertion?

The original message headers themselves left intact.

With a FETCH BODY[<bodypart>] type query the result will be a valid
representation of the requested parts of the message object. Messages
are internally represented by a GMimeMessage object. In this case
headers are requested, so headers are returned through the gmime
interfaces for doing so. Gmime has translated the original message into
it's utf8 internal format, and returns them here in what it considers
the best utf7 encoded form.

I don't think a IMAP compliant server MUST or even SHOULD return the
requested header values in the same encoding as the original message,
but please correct me if I'm wrong.





--
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Paul J Stevens]

Been doing some tests with this on both the 2.2 and 2.3 codebases.

looks like this is indeed a bug on the 2.2 branch where dbmail tries
very hard to work around bugs in older gmime versions. This may
occasionally lead to problems - like in this case.

in 2.3 (git-HEAD) we're on gmime-2.4, and all the workarounds for older
gmime versions have been removed. There this bug does not occur.



Tomas Kuliavas wrote:

>
> John Fawcett-4 wrote:
>> On 27/10/09 09:30, Peter Welzien wrote:
>>> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:
>>>
>>>  
>>> The from line in the dbmail_messageblks table looks ok to me:
>>> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>>>
>>> Does SquirrelMail use any libs for decoding these lines that can cause
>>> these behaviours?
>>>
>>>  
>> Whenever I saw problems like this it was due to
>> badly formed input. In this case we're saying that the input looks
>> ok.
>> I think that problems on dbmail are almost certainly ruled out
>> (roundcube displays the info ok) though to verify that 100%
>> you'd have to execute the imap commands that squirrelmail
>> uses against the IMAP server and check the output.
>>
>
> It does not rule out dbmail. SquirrelMail displays same headers correctly on
> other servers.
>
> Message has
> From: =?utf-8?B?UmlrYXJkIMOFc2x1bmQgVHLDtmdlcg==?= <test@...>
>
> SquirrelMail issues
> "UID FETCH some-message-ids (FLAGS UID RFC822.SIZE INTERNALDATE
> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
> Priority Content-Type)"
>
> DBMail 2.2.9 returns
> from: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= <test@...>
>
> Your smart quoted printable encoder eats trailing double quote in
> display-name. It becomes part of encoded word and display-name is no longer
> atom or quoted-string. It is safer to encode everything and not to keep
> first word unencoded like your code does. Check string. If you notice that
> something in it must be encoded, encode whole string.
>
> If you fixed it between 2.2.9 and 2.2.13, then package provided by Gentoo is
> broken and should be updated.
>

--
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Paul J Stevens]

the proposed solution is to follow the git-head code:

declare a dependency on gmime >= 2.2.10.
trust gmime.
drop support for broken encoded headers.



Paul J Stevens wrote:

> Been doing some tests with this on both the 2.2 and 2.3 codebases.
>
> looks like this is indeed a bug on the 2.2 branch where dbmail tries
> very hard to work around bugs in older gmime versions. This may
> occasionally lead to problems - like in this case.
>
> in 2.3 (git-HEAD) we're on gmime-2.4, and all the workarounds for older
> gmime versions have been removed. There this bug does not occur.
>
>
>
> Tomas Kuliavas wrote:
>> John Fawcett-4 wrote:
>>> On 27/10/09 09:30, Peter Welzien wrote:
>>>> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:
>>>>
>>>>  
>>>> The from line in the dbmail_messageblks table looks ok to me:
>>>> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>>>>
>>>> Does SquirrelMail use any libs for decoding these lines that can cause
>>>> these behaviours?
>>>>
>>>>  
>>> Whenever I saw problems like this it was due to
>>> badly formed input. In this case we're saying that the input looks
>>> ok.
>>> I think that problems on dbmail are almost certainly ruled out
>>> (roundcube displays the info ok) though to verify that 100%
>>> you'd have to execute the imap commands that squirrelmail
>>> uses against the IMAP server and check the output.
>>>
>> It does not rule out dbmail. SquirrelMail displays same headers correctly on
>> other servers.
>>
>> Message has
>> From: =?utf-8?B?UmlrYXJkIMOFc2x1bmQgVHLDtmdlcg==?= <test@...>
>>
>> SquirrelMail issues
>> "UID FETCH some-message-ids (FLAGS UID RFC822.SIZE INTERNALDATE
>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
>> Priority Content-Type)"
>>
>> DBMail 2.2.9 returns
>> from: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= <test@...>
>>
>> Your smart quoted printable encoder eats trailing double quote in
>> display-name. It becomes part of encoded word and display-name is no longer
>> atom or quoted-string. It is safer to encode everything and not to keep
>> first word unencoded like your code does. Check string. If you notice that
>> something in it must be encoded, encode whole string.
>>
>> If you fixed it between 2.2.9 and 2.2.13, then package provided by Gentoo is
>> broken and should be updated.
>>
>
>

--
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Paul J Stevens]

Paul J Stevens wrote:
> the proposed solution is to follow the git-head code:
>
> declare a dependency on gmime >= 2.2.10.
> trust gmime.
> drop support for broken encoded headers.

this has now been pushed to the dbmail_2_2 git branch.

>
>
>
> Paul J Stevens wrote:
>> Been doing some tests with this on both the 2.2 and 2.3 codebases.
>>
>> looks like this is indeed a bug on the 2.2 branch where dbmail tries
>> very hard to work around bugs in older gmime versions. This may
>> occasionally lead to problems - like in this case.
>>
>> in 2.3 (git-HEAD) we're on gmime-2.4, and all the workarounds for older
>> gmime versions have been removed. There this bug does not occur.
>>
>>
>>
>> Tomas Kuliavas wrote:
>>> John Fawcett-4 wrote:
>>>> On 27/10/09 09:30, Peter Welzien wrote:
>>>>> On Mon, 26 Oct 2009 21:24:13 +0100, John Fawcett <john.ml@...> wrote:
>>>>>
>>>>>  
>>>>> The from line in the dbmail_messageblks table looks ok to me:
>>>>> From: =?iso-8859-1?Q?Rikard_=C5slund_Tr=F6ger?= <dhettneck@...>
>>>>>
>>>>> Does SquirrelMail use any libs for decoding these lines that can cause
>>>>> these behaviours?
>>>>>
>>>>>  
>>>> Whenever I saw problems like this it was due to
>>>> badly formed input. In this case we're saying that the input looks
>>>> ok.
>>>> I think that problems on dbmail are almost certainly ruled out
>>>> (roundcube displays the info ok) though to verify that 100%
>>>> you'd have to execute the imap commands that squirrelmail
>>>> uses against the IMAP server and check the output.
>>>>
>>> It does not rule out dbmail. SquirrelMail displays same headers correctly on
>>> other servers.
>>>
>>> Message has
>>> From: =?utf-8?B?UmlrYXJkIMOFc2x1bmQgVHLDtmdlcg==?= <test@...>
>>>
>>> SquirrelMail issues
>>> "UID FETCH some-message-ids (FLAGS UID RFC822.SIZE INTERNALDATE
>>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance
>>> Priority Content-Type)"
>>>
>>> DBMail 2.2.9 returns
>>> from: "Rikard =?iso-8859-1?q?=C5slund_Tr=F6ger=22?= <test@...>
>>>
>>> Your smart quoted printable encoder eats trailing double quote in
>>> display-name. It becomes part of encoded word and display-name is no longer
>>> atom or quoted-string. It is safer to encode everything and not to keep
>>> first word unencoded like your code does. Check string. If you notice that
>>> something in it must be encoded, encode whole string.
>>>
>>> If you fixed it between 2.2.9 and 2.2.13, then package provided by Gentoo is
>>> broken and should be updated.
>>>
>>
>
>

--
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail