Bug 787646

Thanks for a bug report. Evolution-mapi tries to recognize code-page for the message, but it seems like it failed for some reason. An other option is that the message is missing a unicode version of the message body, in which case the server returns non-unicode version of it, where most Russian letters are passed to evolution-mapi like this.

I can provide a test package, which will show what properties are stored with the message. That may help to identify the issue. (I'm afraid that the message was received either as TNEF, or only as compressed RTF, whose parser is not available in evo-mapi. The TNEF has a plugin in evolution, the compressed RTF not.)

Created attachment 559643 [details]
yet another problem mail

Well, I'm waiting your test package.

A small clarification, the bug occur after n response on normal letter.

Created attachment 559846 [details]
pre bug letter

Thanks for the update. Is it a response (aka reply) from you to the sender, or vice versa? I mean, is the message broken when you reply to the sender, thus he/she sees it as garbage, or the other side receives it correctly, but when replies back then it's broken on your side?

Here [1] is a test package. You can install it with something like
  $ rpm -Uvh package-name
and if anything will go wrong then you can revert back to the standard package:
  $ yum downgrade evolution-mapi

Just run evolution from console like this:
  $ evolution &>log.txt
and the evolution-mapi code will dump each message it downloads to the file (it'll be rather long list of MAPI properties with their values).

The only issue is that messages are downloaded only once, when you open message which is already in a cache then it is not downloaded again. Thus look at
  ~/.local/share/evolution/mail/<mapi-account-id>/folders/...
where is stored mail cache of your MAPI account. The three dots '...' are meant as a folder structure similar to that shown in a folder tree in a mailer view. For me it's like
  ~/.local/share/evolution/mail/<mapi-account-id>/folders/Mailbox - Milan Crha/Inbox/cache/XX/<message-id>
for messages in my MAPI Inbox. Finding the offending message to delete, can be tricky. Maybe try by date.

When you delete the message from the cache, and start evolution afterwards, then selecting the message may write debug information into the log. Feel free to send the log only to me, to avoid sharing it in public, because it contains basically anything related to message itself. Only make sure you'll write bug number into the subject, otherwise I may overlook it in my "maybe-spam" folder. Thanks in advance.

[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=3768152

(In reply to comment #6)
> Thanks for the update. Is it a response (aka reply) from you to the sender, or
> vice versa? I mean, is the message broken when you reply to the sender, thus
> he/she sees it as garbage, or the other side receives it correctly, but when
> replies back then it's broken on your side?

This is message which I received, as reply on my letter. After, I go to machine with Windows and reply to the sender. Next I go to machine with Linux and saw my sended letter correctly. After I again receive answer, I see again symbols '?' instead letters.

> [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=3768152

Status of task [1] is closed and binary packages is not provided, what is wrong?

(In reply to comment #7)
> > [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=3768152
> 
> Status of task [1] is closed and binary packages is not provided, what is
> wrong?

Works for me if I click on the 64bit build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3768153

or 32bit build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3768154

Then at the bottom are rpm packages, like usual. I'm not logged in koji, thus I hope this is available publicly.

I send logs to you.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.