Forwarded emails do not include full original message content

[LeeLinkoff]

When forwarding an email in the Proton Mail iOS app, the To field is not populated with the original sender's email address. The user must manually enter the recipient address, which defeats the purpose of the forward action and breaks expected email client behavior.
Steps to Reproduce

Open any email in the Proton Mail iOS app
Tap the forward option
Observe the To field in the compose window

• Expected Behavior: The To field should be pre-populated with the original sender's email address.
• Actual Behavior: The To field is empty. The user must manually type the recipient address.
• Impact: This affects the ability to forward emails for documentation, dispute resolution, and record-keeping purposes where forwarding to a specific external address is required quickly and accurately.
• Environment:

  Device: iPhone 14
  iOS version: 26.4.1
  Proton Mail app version: 7.9.1 (1) - 0.164.16

[jjoanna2-debug]

This appears to be expected email-client behavior, not a Proton Mail bug.

When using standard email workflows:

• Reply pre-populates the recipient with the original sender.
• Reply All includes the relevant existing participants.
• Forward leaves the To field empty because the user chooses the new recipient.

Apple Mail behaves the same way, and this is the normal behavior across email clients. A forward action should not automatically address the message back to the original sender. That would be confusing and could easily cause users to send forwarded content back to the wrong person.

There is also a mismatch between the issue title and the body. The title says “Forwarded emails do not include full original message content,” but the body describes the To field being empty. Those are two different issues.

If the actual problem is missing forwarded content, the issue should be retitled and updated with examples showing what content is missing. If the concern is only that the To field is empty when forwarding, then this looks like expected behavior and should probably be closed rather than treated as a bug.