Bug Encoding UTF-8

  1. ‹ Older
  2. 5 months ago

    Файл из doogiePim https://yadi.sk/d/UnDrhrFMa3Q5QA

    File from doogiePim https://yadi.sk/d/UnDrhrFMa3Q5QA

  3. Chris

    Nov 28 Developer, Moderator, Beta Tester

    Посмотрите, можете ли вы получить полный источник сообщений из своего источника хостинга. Вам нужно выяснить, где находится источник проблем, а не то, что отображается на конце. Как говорится, «Мусор в мусоре».

    See if you can get the full message source from your hosting source. You need to find out where the problem source is, not what the end display is. As they say "Garbage In. Garbage Out ".

  4. Chris

    Nov 28 Developer, Moderator, Beta Tester

    Пожалуйста, пришлите мне сообщение с вашего хостинга: chris@bitespire.com
    Я могу проверить доставку.

    Please send an email message from your hosting to me: chris@bitespire.com
    I can monitor the delivery.

  5. Chris

    Nov 28 Developer, Moderator, Beta Tester

    I've not received anything from you yet. If you can't send to chris@bitespire.com you can send it to software@bitespire.com
    Ensure you use the same email hosting as the buggy message.

  6. I sent several options from the hosting chris@bitespire.com

  7. Chris

    Nov 28 Developer, Moderator, Beta Tester

    I received three email messages from you. I see they were sent from your hosting provider. There was one with the attachment of an EML file, one with HTML formatting of a table and one plain text style of a forwarded message.

    All messages were received in various email clients; MS Outlook, Thunderbird, Windows Email (yuk!) and doogiePIM version The testing machine is an i7 running Windows Pro 1809 in Russian.

    All messages rendered correctly with no visible signs of "?" anywhere to be seen. I can see they were all encoded as 8bit UTF-8.

    I conclude that your "?" bug is something other than the normal process of Email.

    Are you still receiving those same messages incorrectly? I don't mean old messages from the past but new ones.

  8. -image-

  9. Deleted 5 months ago by Voldemar227
  10. Chris

    Nov 28 Developer, Moderator, Beta Tester

    I'll carry on testing but please tell me:
    Are your connections using POP3 or IMAP?
    Are you using TLS or SSL?

    I'm at a loss here on where the problem is. Two other Russian friends say it's fine. I need to see more fails and find the common theme.

    Back to the drawing board I go...

  11. im use IMAP
    то use TLS or SSL
    All mail clients without TLS or SSL

  12. I collected more information

  13. Chris

    Nov 28 Developer, Moderator, Beta Tester

    Thanks for the information. However, I've just realised that your screenshots use a completely different email message than the ones you sent to me. The ones I received were full of large tables of data.

    Please send me that original email message to chris@bitespire.com from the hosting source. I feel we are close.

  14. Chris

    Nov 28 Developer, Moderator, Beta Tester

    Ah! a Windows Server 2008!

    Is doogiePIM running on the Win2008 machine or the Win10Pro machine?
    Which machine are your other email clients running on?
    Do you have the UTF8 character set installed on your server?

    I really need more information about your setup. If you believe this should be private then send this via email or use the Private Messaging of this forum.

  15. I tested on Windows pro and on server 2008

  16. On two pc problem, I always sent a new letter

  17. I checked the mail template for sending messages, messages are sent to utf-8
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css">
    /* Client-specific Styles */

    #outlook a {padding:0;}
    body{width:100% !important; -webkit-text-size-adjust:100%; -ms-text-size-adjust:100%; margin:0; padding:0;}
    .ExternalClass {width:100%;}
    .ExternalClass p,
    .ExternalClass span,
    .ExternalClass font,
    .ExternalClass td,
    .ExternalClass div {line-height: 100%;}
    #backgroundTable {margin:0; padding:0; width:100% !important; line-height: 100% !important;}

    /* End reset */
    This is commented to avoid Project Quality Control warning

  18. I tried many options:
    I installed fully English in UTF-8 format
    I ran doogiePim on server 2008
    I sent letters in different ways
    But nothing helped

  19. Chris

    Nov 29 Developer, Moderator, Beta Tester

    Today I discovered if you make your account as POP3 then the message is received correctly. On my test machine it did.

    Please try as a POP3 and let me know if that helps. In the meantime, I will work on the IMAP4 version. This is quite an odd rare situation that involves the format of certain email servers.

  20. POP3 does not work, writes not known Protocol

  21. I installed IMAP4 registered the server address pop3.beget.com the letters loaded . . .

  22. Encoding error remained ((((((

  23. I recorded a video, look https://yadi.sk/d/Ff_8It_vDiduyA

  24. Chris

    Nov 30 Developer, Moderator, Beta Tester
    Edited 5 months ago by Chris

    Вы используете порт 143. Это неправильно. Это касается только IMAP.
    Если у вас нет SSL, используйте порт 110 для POP3.
    Я также предлагаю вам установить SSL / TLS и использовать порт POP3 995. Это значит, что ваш почтовый транспорт зашифрован.

    You are using port 143. That is wrong. That is only for IMAP.
    If you don't have SSL then use Port 110 for POP3.
    I would also suggest you install SSL/TLS and use POP3 port 995. This is so your email transport is encrypted.


  25. -image-

  26. Chris

    Nov 30 Developer, Moderator, Beta Tester


  27. Удалось ли найти проблему?
    Did you find the problem?

  28. Chris

    Dec 8 Developer, Moderator, Beta Tester

    @Voldemar227 Удалось ли найти проблему?
    Did you find the problem?

    Проблема заключается в IMAP4 в сочетании с определенной кодировкой символов Unicode на почтовых серверах вашего типа. POP3 в порядке и работает хорошо. Я бы оставался с POP3, пока не перепишу некоторые подпрограммы IMAP4, чтобы приспособить этот тип архитектуры сервера.

    The problem is with the IMAP4 in combination with certain Unicode character encoding on your type of email servers. POP3 is fine and works well. I would stay with POP3 until I rewrite some of the IMAP4 routines to accommodate this type of server architecture.

  29. Edited 5 months ago by Voldemar227

    С POP3 есть проблемы, программа зависает и закрывается....
    Так же есть письма с ошибками кодировки...

    There are problems with POP3, the program hangs and closes. . . .
    There are also letters with encoding errors. . .

    Я приложил скриншот и письмо
    I have attached a screenshot and a letter

  30. Video new bug https://yadi.sk/d/l15AgrzB5RdnQw

  31. Chris

    Dec 11 Developer, Moderator, Beta Tester
    Edited 5 months ago by Chris

    Странная маленькая вещь, но я думаю, что вижу небольшую проблему. Я могу исправить это сегодня и дать патч позже.
    Видео действительно помогло обнаружить ошибку.
    Большое спасибо.

    An odd little thing but I think I see the minor problem. I can fix it today and upload a patch later.
    The video was really helpful in spotting the error.
    Many thanks.

  32. Thanks!

  33. Chris, I managed to catch the message with the wrong encoding in the subject. Now I will register on this resource to your email address chris@bitespire.com. You will receive an information letter, pay attention to the subject of the letter.


  34. Chris

    Dec 11 Developer, Moderator, Beta Tester

    Good catch. This gives me more evidence of the problem. Many thanks.

  35. Chris

    Dec 11 Developer, Moderator, Beta Tester

    FYI: it's charset=Windows-1251
    I'm working on fixing this today.

  36. @Chris FYI: it's charset=Windows-1251

    Yes, in Russian localization for Windows this encoding is often used. You can also meet koi8-r.

  37. @Sergiy Yes, in Russian localization for Windows this encoding is often used. You can also meet koi8-r.

    Yes. This is often

  38. Chris

    Dec 11 Developer, Moderator, Beta Tester
    Edited 5 months ago by Chris

    It will take me a few days or two but I'm working on rewriting improving detection on the following encodings:

    Russian (KOI8-R); CodePage:20878; 'x-koi8-r';
    Russian (KOI8)'; CodePage:20866; 'koi8';
    Russian (ISO)'; CodePage:28595; 'iso-8859-5';
    Russian (Windows)'; CodePage:01251; 'windows-1251';

    This should help the display of said characters.

  39. Hello! How is it going ?

  40. Chris

    Dec 14 Developer, Moderator, Beta Tester

    I'm still working on it.

  41. Hello! How is it going ?

  42. Newer ›

or Sign Up to reply!