1 Topic by luxor.pad (edited by luxor.pad 2020-03-25 17:25:20)

  • luxor.pad
  • Member
  • Offline
  • Registered: 2020-03-25
  • Posts: 2

Topic: inbox message format

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Deployed with iRedMail Easy or the downloadable installer? don't know
- Linux/BSD distribution name and version: Linux version 3.10.0-957.21.3.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) )
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? no

====
Hi! Please help me!
Problem:
one message from external domain on HTML format.
We use outlook 2016.
Open letter - format HTML.
Open letter in account who in "copy to" - message format is Plain text.

try open from web "roundcube" - main address HTML and "copy to" - "plain text".

We start from problem with images on letters - some recive "cid", and on roundcube web interface too.
And don't matter, address are "main" or "copy to".

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,094

Re: inbox message format

Looks like a MUA issue and not iRedMail server side.

3 Reply by luxor.pad (edited by luxor.pad 2020-05-15 14:24:21)

  • luxor.pad
  • Member
  • Offline
  • Registered: 2020-03-25
  • Posts: 2

Re: inbox message format

ZhangHuangbin wrote:

Looks like a MUA issue and not iRedMail server side.

this help?

message info from main reciver:

Received: from Sxxxxx.local ([1xxxxxx]) by xxxmex
([1xxxxxxxx]) with mapi id 14.03.0487.000; Fri, 15 May 2020 09:00:15
+0300
Content-Type: multipart/mixed;
    boundary="_000_82E54958377AC5409E7B88BF62165AFC022AE3D6DAs02mex_"
From: =?utf-8?xxxxxxxxxxx?= <xxx@xx>
To: "'xxxxxx'" <xxxxxxxxx>
CC: =?utf-8?xxxx?=
    <xxxxxx>
Subject: =?utf-8?B?0L/RgNC+0LLQtdGA0LrQsCDQvtGC0L/RgNCw0LLQu9C10L3QuNC5?=
Thread-Topic: =?utf-8?B?0L/RgNC+0LLQtdGA0LrQsCDQvtGC0L/RgNCw0LLQu9C10L3QuNC5?=
Thread-Index: AdYqfhnni00KuJQORXqFKyh4yOyhuQ==
Date: Fri, 15 May 2020 06:00:14 +0000
Message-ID: <82E54958377AC5409E7B88BF62165AFC022AE3D6DA@xxx>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <82E54958377AC5409E7B88BF62165AFC022AE3D6DA@xxx>
x-originating-ip: [xxxxxx]
MIME-Version: 1.0

this message info from CC

Return-Path: <xxxxx>
Delivered-To: xxxxxx
Received: from xxxxx (localhost [127.0.0.1])
    by xxxx (Postfix) with ESMTP id 8DD564993CC5
    for <xxxxx>; Fri, 15 May 2020 09:00:33 +0300 (MSK)
X-Virus-Scanned: amavisd-new at xxxxx
Received: from xxxxxx ([127.0.0.1])
    by xxxx (xxxxx [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id dzLpj098Eo0h for <xxxxxxx>;
    Fri, 15 May 2020 09:00:33 +0300 (MSK)
Received: from mail.kraneks.ru (xxxx [87.255.229.153])
    by xxxxxx (Postfix) with ESMTPS id A0C4949901C9
    for <xxxxx>; Fri, 15 May 2020 09:00:32 +0300 (MSK)
Received: from xxxxx (unknown [xxxx])
    (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
    (No client certificate requested)
    by xxxx (Postfix) with ESMTPS id 80FBB6601D8
    for <xxxxxx>; Fri, 15 May 2020 09:03:54 +0300 (MSK)
Received: from xxxxl ([xxxx0]) by sxxxxx
([xxx]) with mapi id 14.03.0487.000; Fri, 15 May 2020 09:00:15
+0300
From: =?utf-8?xxxx?= <xxxxx>
To: "'xxx'" <xxxx>
CC: =?utf-8?Bxxx?=
    <xx@xxxx>
Subject: =?utf-8?B?0L/RgNC+0LLQtdGA0LrQsCDQvtGC0L/RgNCw0LLQu9C10L3QuNC5?=
Thread-Topic: =?utf-8?B?0L/RgNC+0LLQtdGA0LrQsCDQvtGC0L/RgNCw0LLQu9C10L3QuNC5?=
Thread-Index: AdYqfhnni00KuJQORXqFKyh4yOyhuQ==
Date: Fri, 15 May 2020 06:00:14 +0000
Message-ID: <82E54958377AC5409E7B88BF62165AFC022AE3D6DA@xxxxx>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [xxxx9]
Content-Type: multipart/related;
    boundary="_004_82E54958377AC5409E7B88BF62165AFC022AE3D6DAs02mex_";
    type="multipart/alternative"
MIME-Version: 1.0

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,094

Re: inbox message format

This is a MUA issue. Composing and encoding messages are done by MUA, rendering received (encoded) message is also done by MUA.

iRedMail server just transfers the messages.