Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1745321

Summary: Move postfix-pcre, postfix-cdb, postfix-sqlite to AppStream repository
Product: Red Hat Enterprise Linux 8 Reporter: Morten Stevens <ms>
Component: postfixAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Patrik Moško <pmosko>
Severity: medium Docs Contact: Mariya Pershina <mpershin>
Priority: unspecified    
Version: 8.0CC: apmukher, bugzilla-redhat-com, bwalton, john, jskarvad, jwboyer, lmanasko, mhoward, mpershin, pawel.bien, pmosko, psklenar, swardle, tcrider, thozza
Target Milestone: rcFlags: apmukher: needinfo-
pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: postfix-3.3.1-10.el8 Doc Type: Bug Fix
Doc Text:
.PCRE, CDB, and SQLite can now be used with Postfix In RHEL 8, the `postfix` package has been split into multiple subpackages, each subpackage providing a plug-in for a specific database. Previously, RPM packages containing the `postfix-pcre`, `postfix-cdb`, and `postfix-sqlite` plug-ins were not distributed. Consequently, databases with these plug-ins could not be used with Postfix. This update adds RPM packages containing the PCRE, CDB, and SQLite plug-ins to the AppStream repository. As a result, these plug-ins can be used after the appropriate RPM package is installed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:47:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Morten Stevens 2019-08-25 11:49:05 UTC
Description of problem:

Postfix does not support PCRE on RHEL8.

Version-Release number of selected component (if applicable):

postfix-3.3.1-8.el8.x86_64


Steps to Reproduce:
1. postconf -m

Actual results:

# postconf -m
btree
cidr
environ
fail
hash
inline
internal
memcache
nis
pipemap
proxy
randmap
regexp
socketmap
static
tcp
texthash
unionmap
unix


Expected results:

PCRE support

Comment 6 bugzilla-redhat-com 2019-11-05 21:49:05 UTC
Somehow, this does not look like a model solution, but it seems to work. I my case, I downloaded latest fedora 29 versions of
- libicu
- postfix
- postfix-pcre
- postfix-ldap
and installed with

  yum localinstall *.rpm

Then I added to /etc/yum.conf

  exclude=libicu,postfix*

to avoid any update conflicts. Hope this get's fixed fast. Thanks

Comment 20 bwalton 2020-04-20 12:49:32 UTC
I see there is a knowledge base article now linked to this bug report.  When I click on it, I get access denied.  Is that intentional?

Comment 22 errata-xmlrpc 2020-04-28 16:47:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1816