Bug 1940012

Summary:	JMAP support not enabled in cyrus-imapd 3.2.x
Product:	[Fedora] Fedora	Reporter:	Felix Friedlander <felix>
Component:	cyrus-imapd	Assignee:	Martin Osvald 🛹 <mosvald>
Status:	ASSIGNED ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	amessina, code, j, mosvald, pzhukov, vanmeeuwen+fedora, zdohnal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Felix Friedlander 2021-03-17 12:38:48 UTC

User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0
Build Identifier: 

A major and exciting change in the upgrade from cyrus-imapd 3.0.x to 3.2.x is the addition of JMAP support, an open standard (RFC 8620/8621) modern mail client protocol.

However, this option is not compiled in to the Fedora 34 cyrus packages. (Missing the --enable-jmap flag; all other necessary flags are included.) 

Judging by the current .spec including such features as Xapian support, it appears that the Fedora build seeks to be a full-featured build of Cyrus, and JMAP is not described as an "experimental" or "unsupported" feature, simply one not enabled by default. It does not introduce any additional dependencies, as Xapian is already enabled.

See https://www.cyrusimap.org/imap/developer/jmap.html for more details.

Reproducible: Always

Steps to Reproduce:
Install the cyrus-imapd package.
Actual Results:  
JMAP is not available in the installed cyrus-imapd.

Expected Results:  
JMAP is available in the installed cyrus-imapd.

Comment 1 Jason Tibbitts 2022-02-09 19:48:20 UTC

For the record, I originally had this enabled early in the 3.0 series but disabled it when upstream decided that JMAP wasn't really supposed to be a supported thing at that point in time.  I suppose it just wasn't re-enabled once newer versions had more stable support.   Sadly I'm not really able to be involved with this package much these days.

Comment 2 Ben Cotton 2022-05-12 16:54:02 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.