Files could not be expanded: conflict in file postfix.spec

Postfix

Edit Package postfix
http://www.postfix.org/

A fast, secure, and flexible mailer that aims to be an alternative to the widely-used sendmail program.

Refresh
Refresh
Source Files

Sources could not be expanded: conflict in file postfix.spec

Show unmerged sources

Comments 8

Arjen de Korte's avatar

Why do we still bundle /etc/postfix/aliases? As far as I can see, it isn't used by default anyway. Isn't it just confusing to have both /etc/aliases and /etc/postfix/aliases?


Peter Varkoly's avatar

Yes it is confusing, but we do have both traditional conditioned: /etc/aliases is part of netcfg package and will be used by other MTAs too. /etc/postfix/aliases is part of the postfix package and it is there even if it should not be used IMHO :-(


Arjen de Korte's avatar

So why not change that situation? After all, the /etc/postfix/aliases file is just a sample. If it is already provided by the netcfg package, why package it in postfix too. Even when it is technically possible to use both at the same time, it is confusing to do so.


Илья Индиго's avatar

I agree with you! Need replace the /etc/postfix/aliases file with a symlink to ../aliases. That way there would be less confusion and nothing would break.


Christian Wittmer's avatar

Can we please keep stable releases here. If someone prefers to test non-production release then please do so in your home project. Thank you


Arjen de Korte's avatar

Looks pretty stable to me: http://www.postfix.org/announcements/postfix-3.8.0.html


Christian Wittmer's avatar

sorry ... you are right. Only saw that Postfix 3.8 non-production release thing.


Arjen de Korte's avatar

That's probably a bug for the Postfix website. This should probably read Postfix 3.9 non-production release instead, as the non-production releases are based on the current experimental release (which is 3.9 now).

openSUSE Build Service is sponsored by