mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 21:15:56 +03:00
[PR #944] [MERGED] [FIX] Stalwart: fix jmap 0.7.0 msg_header keys(message-id,message_id) #1166
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#1166
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/cypht-org/cypht/pull/944
Author: @Shadow243
Created: 4/11/2024
Status: ✅ Merged
Merged: 4/18/2024
Merged by: @kroky
Base:
master← Head:jmap-stalwart-new-release-check📝 Commits (1)
4b1226d[FIX] Stalwart: fix jmap 0.7.0 msg_header keys(message-id,message_id)📊 Changes
1 file changed (+7 additions, -2 deletions)
View changed files
📝
modules/smtp/modules.php(+7 -2)📄 Description
Pull Request Description
Title: Update Draft Saving Functionality for Stalwart 0.7.0 Compatibility
Description:
Issue:
In Stalwart release 0.5.0, the message ID field was consistently labeled as "message-id" in the response data when saving drafts. However, with the release of Stalwart 0.7.0, there has been a change where the message ID field is now labeled as "message_id". This inconsistency has caused issues when attempting to save drafts as our codebase was expecting the previous format.
Solution:
To ensure compatibility with Stalwart 0.7.0 and future versions, this pull request updates the draft saving functionality to handle both "message-id" and "message_id" fields in the response data. The code now checks for the existence of both keys and compares their values accordingly. This change allows our application to seamlessly handle drafts saved using both versions of Stalwart.
Changes Made:
This pull request aims to resolve the compatibility issue with Stalwart 0.7.0 and improve the robustness of our draft saving feature for future releases.
Related Issue: https://github.com/cypht-org/cypht/issues/931
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.