Bug 38505 – Make OXSE4UCS work with both Cyrus and Dovecot

Bug 38505 - Make OXSE4UCS work with both Cyrus and Dovecot


Summary:	Make OXSE4UCS work with both Cyrus and Dovecot

Status:	CLOSED DUPLICATE of bug 38463

Product:	UCS
Classification:	Unclassified
Component:	Third party - OXSE4UCS
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Daniel Tröder
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	38470
	Show dependency tree / graph

Reported:	2015-05-11 13:35 CEST by Daniel Tröder
Modified:	2023-03-25 06:48 CET (History)
CC List:	2 users (show)

See Also:	38463
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2015-05-11 13:35:17 CEST

Currently OX has a dependency on univention-mail-cyrus-ox. After a quick glance it seems to be a integration package for OX/Cyrus to enable ham/spam-learning, mailbox rename/creation/shared, quota, sieve.

OX should work with both Cyrus and Dovecot.

Starting by creating a univention-mail-dovecot-ox integration package and a branch of univention-ox with alternative dependencies in component/dovecot.

Comment 1 Daniel Tröder

2015-05-12 11:47:53 CEST

Commit: 60646

univention-ox now has a dependency on "univention-mail-dovecot-ox | univention-mail-cyrus-ox", with those having dependencies on univention-mail-dovecot or univention-mail-cyrus respectively.

OX works with Dovecot IMAP and SIEVE without modifications, but some integration that is in univention-mail-cyrus-ox has yet to be ported, so not marking fixed.

Comment 2 Daniel Tröder

2015-08-25 10:59:54 CEST


*** This bug has been marked as a duplicate of bug 38463 ***