Bug 6836

Summary:	SASL socket hardlinks not created for postfix
Product:	Mageia	Reporter:	François Andriot <albator78>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	fundawang, guillomovitch, javier_diaz, mageia, stormi-mageia
Version:	2	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	cyrus-sasl-2.1.23-19.mga2	CVE:
Status comment:

Description François Andriot 2012-07-20 17:22:21 CEST

Description of problem:
Hello, I'm using Postfix with SASL authentication enabled; so that SMTP clients (e.g. thunderbird) users have to enter login/password to send mails. It was working well in Mageia 1.

In order for Postfix to access the SASL server, the old SASL startup script (/etc/rc.d/init.d/saslauthd) creates hardlinks to the SASL socket (/var/lib/sasl2/mux) inside the postfix chroot directory (/var/spool/postfix/var/run/saslauthd/mux).

Alas, this old SYSV startup script is no more used now with Systemd.
See: /lib/systemd/system/saslauthd.service
The SASL server daemon is started directly, there is no "pre-startup actions", so there is no more hardlink creation for postfix.

Without access to the SASL socket, postfix cannot process SASL authentication.


As a workaroung, I have to restart the SASL daemon without using systemd, with the following command:
SYSTEMCTL_SKIP_REDIRECT=1 /etc/rc.d/init.d/saslauthd restart




Version-Release number of selected component (if applicable):
cyrus-sasl-2.1.23-19.mga2

How reproducible:
Steps to Reproduce:
1. Install postfix and cyrus-sasl.
2. Configure Postfix to use SASL authentication.
3. Restart postfix and SASL daemon
4. Use your favorite MUA to send a mail through the MTA: the authentication always fail.
5. Restart SASL daemon using SYSTEMCTL_SKIP_REDIRECT=1
6. Try to send the mail again from the MUA: authentication now works, the mail is processed normally.

Comment 1 Manuel Hiebel 2012-07-21 02:35:45 CEST

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

CC: (none) => fundawang, guillomovitch

Javier Díaz 2012-07-29 21:50:29 CEST

CC: (none) => javier_diaz

Samuel Verschelde 2013-08-29 15:16:13 CEST

Keywords: (none) => Triaged
CC: (none) => stormi

David Walser 2013-08-30 23:37:36 CEST

CC: (none) => mageia

Comment 2 Manuel Hiebel 2013-10-22 12:11:12 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 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.

-- 
The Mageia Bugsquad

Comment 3 Manuel Hiebel 2013-11-23 16:14:32 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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