Bug 21337 - postfix won't send mail after mga5 to mga6 upgrade
Summary: postfix won't send mail after mga5 to mga6 upgrade
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Daniel Lucio
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 07:01 CEST by Remco Rijnders
Modified: 2020-08-05 14:40 CEST (History)
2 users (show)

See Also:
Source RPM: postfix-3.1.6-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Remco Rijnders 2017-07-24 07:01:36 CEST
After upgrading from Mageia 5 to Mageia 6, postfix won't send any mails. In the log file I see errors similar to:

Jul 24 06:55:21 silvertown postfix/qmgr[8722]: A1123611C6: from=<remco@webconquest.com>, size=2815, nrcpt=1 (queue active)
Jul 24 06:55:21 silvertown postfix/smtp[8724]: A1123611C6: local data error while talking to broadstreet.webconquest.com[178.62.201.32]
Jul 24 06:55:21 silvertown postfix/smtp[8724]: A1123611C6: to=<remco@webconquest.com>, relay=broadstreet.webconquest.com[2a03:b0c0:2:d0::58:1001]:25, delay=2003, delays=2003/0.04/0.05/0, dsn=4.3.0, status=deferred (local data error while talking to broadstreet.webconquest.com[2a03:b0c0:2:d0::58:1001])

/var/log/mail/errors.log is filled with errors like:

Jul 24 06:52:21 silvertown postfix/smtp[8662]: error: unsupported dictionary type: pcre
Jul 24 06:52:21 silvertown postfix/smtp[8663]: error: unsupported dictionary type: pcre
Jul 24 06:55:21 silvertown postfix/smtp[8724]: error: unsupported dictionary type: pcre

This despite package postfix-pcre being installed.

Receiving mails on the server still works as expected. Mail user clients show no errors, so postfix does accept mails for delivery, it just completely fails to send them to the destination mail servers.
Comment 1 Remco Rijnders 2017-07-24 07:31:46 CEST
Having investigated this further, I could fix it by:

1) cp /etc/postfix/dynamicmaps.cf.rpmnew /etc/postfix/dynamicmaps.cf
2) Copy select values from /etc/postfix/main.cf.rpmnew to /etc/postfix/main.cf
3) urpme postfix-pcre
4) urpmi postfix-pcre
5) postfix stop
6) postfix start

I am not sure if steps 3 and 4 are necessary, but a postfix reload at that point did not result in a working configuration for me.
Rémi Verschelde 2017-07-24 14:52:34 CEST

Assignee: bugsquad => luis.daniel.lucio

Comment 2 Robert Thompson 2017-07-25 07:55:55 CEST
I saw a very similar problem, except on incoming emails. Instead of receiving incoming emails, each incoming email generated an error message delivered to the intended recipient of the email with a subject like:

Postfix SMTP server: errors from mail-ua0-f179.google.com[209.85.217.179]

The body of the message contains:

Out: 451 4.3.0 Error: queue file write error

my main.cf contains the line:

mime_header_checks=pcre:/etc/postfix/header_checks.pcre

Checking the pcre file with postmap gave the following:

# postmap -q test pcre:./header_checks.pcre 
postmap: warning: unsupported dictionary type: pcre (/usr/lib64/postfix/dict_pcre.so: No such file or directory)
postmap: fatal: unsupported dictionary type: pcre

There is also a similar message in /var/log/mail/warnings.log.

However, postconf -m does report that pcre is supported.

Initially I created a symbolic link from /usr/lib64/postfix-pcre.so to /usr/lib64/postfix/dict_pcre.so  and this solved the problem (I got this from googling the error message and found this workaround on a debian forum - I know different distro, but the workaround works anyway!)

I came here to report the problem and found this bug. I followed the steps in comment #1 (after removing my symbolic link) and can confirm the workaround in comment #1 also solved the problem.

As I've never knowingly modified dynamicmaps.cf, I don't see why the new file installed as .rpmnew, but whatever...

CC: (none) => rob

Comment 3 David Walser 2017-07-30 21:17:09 CEST
dynamicmaps.cf is modified by %post scriplets from postfix module subpackages to list which ones are installed, IIRC.
Comment 4 Aurelien Oudelet 2020-08-05 14:40:19 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


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