Skip to Content.
Sympa Menu

en - Re: [sympa-users] problems with soap interface (probably all utf8 related)

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: IKEDA Soji <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: Re: [sympa-users] problems with soap interface (probably all utf8 related)
  • Date: Mon, 9 Dec 2013 18:45:36 +0900

Sorry Goltz, you are right.

However, I suppose patch to mail.pm is not required.
Instead, list names should also be encoded at beginning of
sympasoap::subscribe() etc. Though they contain only ASCII,
they have utf8 flags set!

If you send complete patch, I'd like to check it and apply.

Regards,

--- Soji

2013/12/04 17:33、IKEDA Soji <address@concealed> のメッセージ:

> Goltz and all,
>
> On Tue, 19 Nov 2013 13:23:45 +0000
> "Goltz, Immo [Extern]" <address@concealed> wrote:
>
>> Hello sympa users,
>>
>> i am evaluating sympa with the intention to replace a lyris listmanger
>> installation.
>> So far so good, but when it comes to soap, which is mandatory for our
>> environment, sympa fails.
>>
>> That the provided functions are limited is not the point, i found some
>> patches to enhance this. But using soap, web gui (and mail) leads to
>> encoding problems. An broken welcome mails. I hope someone can point me
>> into the right direction how to fix this.
>>
>> Base system is CentOS 6.4 / 64 bit. soap::lite, mime:: and other packages
>> via cpan, all other perl from centos or epel/rpmforge. MySQl as DB.
>> sympa is version 6.1.17
>>
>> Creation of a list with UTF8 characters inside subject and info
>> * Using Web-GUI
>> -> correctly encoded in DB and in the 2 files (config, info)
>> -> correct view in Web-GUI
>> -> incorrect subject view in soap
>> * Using soap
>> -> correctly encoded in DB
>> -> wrong (and different) encoding in the 2 files (config: Ä becomes C4,
>> info: Ä becomes EFBFBD)
>> -> incorrect view in Web-GUI
>> -> correct subject view in soap
>
> I guess Encode::decode*() and Encode::encode*() in the codes for
> soap may not be neccessary at all. As it simply reads byte-string
> data and output byte-strings, there seems no oppotunity of
> conversion between internal Unicode.
>
> How about removing all of these functions?
> # I did so in current trunk of SVN repository.
>
>> Adding a user with uf8 comment_subscriber to a list
>> * Using Web-GUI
>> -> (add user first, then edit user) correctly encoded in DB
>> -> correct view in Web-GUI
>> -> welcome mail correctly encoded
>> * Using soap
>> -> correctly encoded in DB
>> -> correct view in Web-GUI
>> -> welcome mail incorrectly encoded (and body repeated 3 times if list
>> info contains cyrillic text)
>
> This fact seems to support my guess above: anywhere in the code
> for soap will call Encode::decode() (or Encode::decode_utf8())
> in surplus. WWSympa may not do it.
>
>
>> I had a look at different sourcesup entries and did fiddly with
>> sympasoap.pm. But i couldnt fully solve these errors.
>> Most disturbing, the problem of the broken welcome mail. This happens in
>> mail.pm, in sub reformat_message.
>> It has something to do with MIME::Parser here: $msg =
>> $parser->parse_data($message);
>> But as far as i could debug, the function is called with identical values
>> from soap and from web. So why is ist broken via soap?
>> (with perl-MIME-tools-5.427-4.el6.noarch and MIME-tools-5.504 from cpan)
>
>
> Regards,
>
>
> --- Soji
>
>
>> Any help is appreciated
>> Thank you in advance
>>
>> Immo Goltz
>
>
>
>
> --
> 株式会社 コンバージョン セキュリティ&OSSソリューション部 池田荘児
> 〒231-0004 神奈川県横浜市中区元浜町3-21-2 ヘリオス関内ビル7F
> e-mail address@concealed TEL 045-640-3550
> http://www.conversion.co.jp/




Archive powered by MHonArc 2.6.19+.

Top of Page