'subjectfield' encoding bug

Hello,

We has noticed problem with encoding in field
'subjectfield'.
For example we sent message with subject (next line):
Fwd:
=?windows-1251?b?zu/z4evo6u7i4O3gIO/w7uPw4Ozs4CBIaWdoTG9hZCA
t?= 2007
In SQL select field 'subjectfield' we seen (next line):
?????????>?????????œ???œ ???????????œ?????œ HighLoad -
2007
But if we receive mail via IMAP4 subject is correct (because
subject in message received via IMAP4 get directly from
physical message).
If we set 'binary' encoding for 'subjectfield' subject
correctly stored in database.

We suspect that encoding didn't set at connection time.

We use Linux CentOS 5, DBMail 2.2.5.

P.S. Similar bugs 538, 385, 548.

--
Ilyas.
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Mon, 2007-08-06 at 19:06 +0400, umask wrote:
> Hello,
> 
> We has noticed problem with encoding in field
'subjectfield'.
> For example we sent message with subject (next line):
> Fwd:
=?windows-1251?b?zu/z4evo6u7i4O3gIO/w7uPw4Ozs4CBIaWdoTG9hZCA
t?=
> 2007
> In SQL select field 'subjectfield' we seen (next
line):
> ?????????>?????????°???° ???????????°?????°
HighLoad - 2007

Is your terminal window configured for utf-8?

> But if we receive mail via IMAP4 subject is correct
(because subject
> in message received via IMAP4 get directly from
physical message).

Not always true, it depends on the client.

> If we set 'binary' encoding for 'subjectfield' subject
correctly
> stored in database.
>
> We suspect that encoding didn't set at connection
time.

What is the database_encoding line in your dbmail.conf? Do
you get any
messages about this when DBMail starts up?

> We use Linux CentOS 5, DBMail 2.2.5.

What database and version are you using?

> P.S. Similar bugs 538, 385, 548.

Yep, encoding is kinda hard to get right in every situation
:-(

Aaron

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

06.08.07, 20:27, Aaron Stone <aaronserendipity.cx>:

> On Mon, 2007-08-06 at 19:06 +0400, umask wrote:
> > Hello,
> > 
> > We has noticed problem with encoding in field
'subjectfield'.
> > For example we sent message with subject (next
line):
> > Fwd:
=?windows-1251?b?zu/z4evo6u7i4O3gIO/w7uPw4Ozs4CBIaWdoTG9hZCA
t?=
> > 2007
> > In SQL select field 'subjectfield' we seen (next
line):
> > ?????????>?????????œ???œ ???????????œ?????œ
HighLoad - 2007

> Is your terminal window configured for utf-8?

We used php-script and his display '????...'.

> > But if we receive mail via IMAP4 subject is
correct (because subject
> > in message received via IMAP4 get directly from
physical message).
> Not always true, it depends on the client.

Maybe.

> > If we set 'binary' encoding for 'subjectfield'
subject correctly
> > stored in database.
> >
> > We suspect that encoding didn't set at connection
time.

> What is the database_encoding line in your dbmail.conf?
Do you get any
> messages about this when DBMail starts up?

from dbmail.conf:

encoding             = utf8
default_msg_encoding = utf8

Is correct?

Parameter database_encoding absent in dbmail.conf from
source.

> > We use Linux CentOS 5, DBMail 2.2.5.

> What database and version are you using?

rpm -qa mysql-server
mysql-server-5.0.22-2.1

> > P.S. Similar bugs 538, 385, 548.
> Yep, encoding is kinda hard to get right in every
situation :-(

Yes %(

> Aaron
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

07.08.07, 12:05, umask <umaskyandex.ru>:

> 06.08.07, 20:27, Aaron Stone <aaronserendipity.cx>:
> > On Mon, 2007-08-06 at 19:06 +0400, umask wrote:
> > > Hello,
> > > 
> > > We has noticed problem with encoding in field
'subjectfield'.
> > > For example we sent message with subject
(next line):
> > > Fwd:
=?windows-1251?b?zu/z4evo6u7i4O3gIO/w7uPw4Ozs4CBIaWdoTG9hZCA
t?=
> > > 2007
> > > In SQL select field 'subjectfield' we seen
(next line):
> > > ?????????>?????????œ???œ
???????????œ?????œ HighLoad - 2007
> > Is your terminal window configured for utf-8?

> We used php-script and his display '????...'.

... and php script use UTF8 encoding for connection to mysql
server.

> > > But if we receive mail via IMAP4 subject is
correct (because subject
> > > in message received via IMAP4 get directly
from physical message).
> > Not always true, it depends on the client.
> Maybe.
> > > If we set 'binary' encoding for
'subjectfield' subject correctly
> > > stored in database.
> > >
> > > We suspect that encoding didn't set at
connection time.
> > What is the database_encoding line in your
dbmail.conf? Do you get any
> > messages about this when DBMail starts up?
> from dbmail.conf:
> encoding             = utf8
> default_msg_encoding = utf8
> Is correct?
> Parameter database_encoding absent in dbmail.conf from
source.
> > > We use Linux CentOS 5, DBMail 2.2.5.
> > What database and version are you using?
> rpm -qa mysql-server
> mysql-server-5.0.22-2.1
> > > P.S. Similar bugs 538, 385, 548.
> > Yep, encoding is kinda hard to get right in every
situation :-(
> Yes %(
> > Aaron
> > _______________________________________________
> > DBmail mailing list
> > DBmaildbmail.org
> > htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail