mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #605] Maybe we should have 2 forwarding actions, like Nextcloud Mail? #423
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#423
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?
Originally created by @marclaporte on GitHub (Aug 25, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/605
Originally assigned to: @amaninyumu1 on GitHub.
One is forward the whole thing as one attachment, without any modifications. The other is forward by converting to text that I can modify before I send. I usually the later, but I know Jason prefers the former.
Related:
https://github.com/jasonmunro/cypht/pull/558
https://github.com/jasonmunro/cypht/issues/557
@dumblob commented on GitHub (Sep 2, 2022):
This has been discussed before somewhere. I think the problem was which email part to choose (emails nowadays are heavily multipart and heavily nested) and conversions between mime types (this second issue is though solvable by making a plain copy & paste while keeping the mime type and compose in that mime type - in case composition in that mime type is unsupported the user will get empty screen with a message Composition/editing of
image/svg+xmlMIME type not supported. Please switch to another Compose view. whereas switching the compose view would do the smart conversion potentially losing formatting or the whole contents etc.).@dumblob commented on GitHub (Sep 2, 2022):
Related:
https://github.com/jasonmunro/cypht/issues/12
https://github.com/jasonmunro/cypht/issues/382
@amaninyumu1 commented on GitHub (Jun 13, 2024):
https://github.com/cypht-org/cypht/pull/1080

@marclaporte commented on GitHub (Jul 8, 2024):
Work in progress: https://github.com/cypht-org/cypht/pull/1080