Skip to content

Conversation

@kambereBr
Copy link
Member

@kambereBr kambereBr commented Oct 24, 2025

  1. Safely convert UTF-8 MIME parts to ISO-8859-1 when possible to prevent Exchange from re-encoding messages.
  2. Properly extract attachment filenames from received messages.
  3. Uncaught Error: Call to undefined method Hm_EWS::supports_dsn() in /cypht/modules/smtp/modules.php:584

@Shadow243 Shadow243 changed the title fix(ews): ews preserve quoted-printable for Latin-1 safe text and fix attachment filenames fix(backend): ews preserve quoted-printable for Latin-1 safe text and fix attachment filenames Oct 24, 2025
@kambereBr kambereBr force-pushed the enh-ews-msg-encoding branch from 14ffe1a to 01f3abd Compare October 27, 2025 00:24
@kambereBr kambereBr marked this pull request as ready for review October 27, 2025 00:32
@kambereBr kambereBr requested a review from kroky October 27, 2025 00:35
* @param string $message The MIME message from Hm_MIME_Msg
* @return string Modified message with ISO-8859-1 where safe
*/
private function use_iso_if_safe($message) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This whole function seems very hacky and low-level. Why do you need to convert a universally available encoding like UTF-8 to something that doesn't even support more than a few hundreds of characters?
If you experience a specific edge case with Exchange, let's discuss what can be done but this conversion certainly looks very suspicious to do on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants