You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we are having problems with chinese / hongkong mails and I'm wondering what the charset attribute in the DataPartInfo.php is used for. The problem is the following: We are receiving a mail with two parts, one of them is that:
`
--00000000000035bb5705ae7bcde0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
The charset is set to UTF-8 and the DataPartInfo.php recognizes that correctly. But in the method convertEncodingAfterFetch this charset isn't used anymore. Instead the method decodeMimeStr uses imap_mime_header_decode, which extracts the element and returns default as charset. But with barbushin/php-imap#513 I can override the "default", which I need to do since some of the chinese mails need to be converted. Thus the previous correct string is converted and is now corrupted. So why is the charset parameter of the DataPartInfo not used for encoding the message part? Or am I missing something?
Best regards
Felix
The text was updated successfully, but these errors were encountered:
Hi,
we are having problems with chinese / hongkong mails and I'm wondering what the charset attribute in the DataPartInfo.php is used for. The problem is the following: We are receiving a mail with two parts, one of them is that:
`
--00000000000035bb5705ae7bcde0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
5L2g5aW977yM5pyJ5pu05aSa6Zec5pa86Jaq6YWs6LOH5paZ5ZeO77yfDQoNCuOAjEhPIE1hcmt1
cyA8bWFya3VzaG8xMDMwQGdtYWlsLmNvbT7jgI3lnKggMjAyMOW5tDnmnIgz5pelIOmAseWbm++8
jDIxOjI4IOWvq+mBk++8mg0KDQo+IOS9oOWlve+8jOaIkeacg+eboeW/q+Whq+WlveS4puS4lOaK
iuihqOagvOS6pOWbnu+8jOS9huaIkeacieWAi+WVj+mhjOaYr+iWqumFrOWmguS9leioiOeul++8
nw0KPg0KPiBDbG91ZHdvcmtlcnMgQWdlbnRzIEhLIDxqb2JzLmhrQGNsb3Vkd29ya2Vycy5jb21w
YW55PiDmlrwgMjAyMOW5tDnmnIgz5pelIOmAseWbmw0KPiDkuIvljYg2OjQ45a+r6YGT77yaDQo+
DQo+Pg0KPj4NCj4+DQo+Pg0KPj4g5oKo5aW977yM5YaN5qyh5oSf6Kyd5oKo5bCH6KaB5rGC55qE
5paH5Lu26YCA6YKE57Wm5oiR5YCR44CCDQo+Pg0KPj4NCj4+DQo+Pg0KPj4g5L2G5piv77yM55Sx
5pa857y65bCR5YW25Lit55qE5paH5qqU77yM6KuL5YaN5qyh55m86YCB6YCZ5Lqb5paH5qqU77yM
5Lul5L6/5oiR5YCR6IO95aSg5b+r6YCf6JmV55CG5oKo55qE55Sz6KuL77yM5Lim5biM5pyb5oKo
5pys6YCx6IO95aSg5Yqg5YWl44CCDQo+Pg0KPj4NCj4+DQo+Pg0KPj4g6Yyv6Kqk5oiW5pyq6YCB
55qE5paH5Lu277yaDQo+Pg0KPj4NCj4+DQo+Pg0KPj4NCj4+DQo+PiAxLlNlbGYgQmlsbGluZyBB
Z3JlZW1lbnQNCj4+DQo+Pg0KPj4NCj4+DQo+PiAyLkNsb3Vkd29ya2VycyBDb250cmFjdA0KPj4N
Cj4+IDMgQXV0byBQYXkgSW5mbw0KPj4NCj4+DQo+PiBQUzsg5q+U6LW36YqA6KGM5oiR5pu05o6o
6JamcGF5cGFs77yM5Zug54K65omL57qM6LK75pyD5pu05YiS566X44CCDQo+Pg0KPj4NCj4+DQo+
Pg0KPj4g6KuL6YCA5Zue5LiK6Z2i5YiX5Ye655qE5paH5Lu2LCDpnZ7luLjph43opoHnmoTmmK/v
vIzpgJnkupvoq4vlhJjlv6vmrbjpgoTntabmiJHlgJHjgIINCj4+DQo+Pg0KPj4NCj4+DQo+Pg0K
Pj4NCj4+DQo+Pg0KPj4NCj4+IOisneisneaCqOeahOWQiOS9nOOAgg0KPj4NCj4+DQo+Pg0KPj4N
Cj4+DQo+Pg0KPj4NCj4+DQo+Pg0KPj4gKkNMT1VEV09SS0VSUyBDT01QQU5ZKg0KPj4NCj4+DQo+
Pg0KPj4NCj4+ICpSZWNydWl0aW5nIE9mZmljZSoNCj4+DQo+Pg0KPj4NCj4+DQo+PiBGb246ICs0
NCAoMCkgMjA4MDgwNjU3MQ0KPj4NCj4+DQo+Pg0KPj4NCj4+IDEyOCBDYW5ub24gV29ya3Nob3Bz
IENhbm5vbiBEcml2ZQ0KPj4NCj4+DQo+Pg0KPj4NCj4+IEUxNCA0QVMgTG9uZG9uDQo+Pg0KPj4N
Cj4+DQo+Pg0KPj4gd3d3LmNsb3Vkd29ya2Vycy5jb21wYW55DQo+Pg0KPj4NCj4+DQo+Pg0KPg0K
Pg0K
`
The charset is set to UTF-8 and the DataPartInfo.php recognizes that correctly. But in the method convertEncodingAfterFetch this charset isn't used anymore. Instead the method decodeMimeStr uses imap_mime_header_decode, which extracts the element and returns default as charset. But with barbushin/php-imap#513 I can override the "default", which I need to do since some of the chinese mails need to be converted. Thus the previous correct string is converted and is now corrupted. So why is the charset parameter of the DataPartInfo not used for encoding the message part? Or am I missing something?
Best regards
Felix
The text was updated successfully, but these errors were encountered: