mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #411] Show server support (or not) for required or desired standards, extensions and features (diagnostics) #341
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#341
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 (Jun 25, 2020).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/411
Originally assigned to: @jasonmunro on GitHub.
Cypht is designed to work with standard SMTP/IMAP servers, and JMAP:
https://github.com/jasonmunro/cypht/issues/180
And one day, we'll likely add support for Microsoft Exchange:
https://github.com/jasonmunro/cypht/issues/247
And perhaps we'll even add more options to send email:
https://dev.tiki.org/Transaction-Email-Sending-API
Furthermore, we should be in a position to take advantage of evolving standards:
"This document updates RFC 3501 (IMAP4rev1) with persistent identifiers on mailboxes and messages to allow clients to more efficiently reuse cached data when resources have changed location on the server."
Source: https://tools.ietf.org/html/rfc8474
With all these options, there could be some features that work differently depending on server support. Thus, we should add sections which report on features/standards supported by the servers.
As an example, in Tiki Wiki CMS Groupware, we have:
"tiki-check.php is a standalone script for server environment settings diagnostics before installing Tiki, or for an existing Tiki installation. While it was designed for Tiki, and it's bundled in Tiki, it is very useful for any PHP app, as it checks over 100 different things and provides contextual feedback. Started in 2012, this script has been refined over the years and it copes with all kinds of weird edge cases." Source: https://doc.tiki.org/Server-Check
Jason wrote: "If the move extension is not supported, we fall back to copy/delete/expunge. I'm surprised this hasn't come up before. We want to take advantage of any extensions present, but we don't want to rely on them for basic functionality."
Source: https://github.com/jasonmunro/cypht/issues/158#issuecomment-266117404
I hope we can leverage some existing Open Source code.
Thanks!
@marclaporte commented on GitHub (Jul 31, 2022):
An example of why we should do this: https://github.com/jasonmunro/cypht/issues/516