Re: Postfix stable release 3.0.0
Am 09.02.2015 um 21:51 schrieb li...@rhsoft.net:
Am 09.02.2015 um 21:46 schrieb Wietse Venema:
li...@rhsoft.net:
well, meta_directory=%{postfix_daemon_dir} at build leads in
/usr/libexec/postfix/postfix-files instead /etc/postfix/postfix-files
but postfix refuses to start like below
cp /usr/libexec/postfix/postfix-files /etc/postfix/postfix-files
Please do a proper install without copying files by hand
*i do*
that was only to demonstrate that it still seeks it in /etc
the problem is that built-in "meta_directory" defaults to /etc/postfix
[root@testserver:~]$ postconf -d meta_directory
meta_directory = /etc/postfix
ok, add -DDEF_META_DIR to CCARGS changes the default
issue solved, postfix 3.0 is running perfectly - thanks!
CCARGS="-fPIC -DNO_NIS -DNO_NISPLUS -DNO_EAI -DNO_LMDB -DNO_CDB
-DNO_LDAP -DNO_PGSQL -DNO_SQLITE -DHAS_PCRE -I%{_includedir}/pcre
-DHAS_MYSQL -I%{_includedir}/mysql -DUSE_TLS -DUSE_SASL_AUTH
-DUSE_CYRUS_SASL -I%{_includedir}/sasl
-DDEF_CONFIG_DIR=\\\"%{postfix_config_dir}\\\"
-DDEF_META_DIR=\\\"%{postfix_daemon_dir}\\\""
[root@testserver:~]$ postconf -d meta_directory
meta_directory = /usr/libexec/postfix
Re: Postfix stable release 3.0.0
li...@rhsoft.net:
> Am 09.02.2015 um 21:46 schrieb Wietse Venema:
> > li...@rhsoft.net:
> >> well, meta_directory=%{postfix_daemon_dir} at build leads in
> >> /usr/libexec/postfix/postfix-files instead /etc/postfix/postfix-files
> >> but postfix refuses to start like below
> >>
> >> cp /usr/libexec/postfix/postfix-files /etc/postfix/postfix-files
> >
> > Please do a proper install without copying files by hand
>
> *i do*
>
> that was only to demonstrate that it still seeks it in /etc
> the problem is that built-in "meta_directory" defaults to /etc/postfix
meta_directory (default: see 'postconf -d' output)
...
For backwards compatibility with Postfix versions 2.6..2.11, specify
"meta_directory = $daemon_directory" in main.cf before installing or
upgrading Postfix, or specify "meta_directory = /path/name" on the
"make makefiles", "make install" or "make upgrade" command line.
So, you do it in main.cf *before* installation or at install time:
$ make makefiles meta_directory=/path/name ...
# make install meta_directory=/path/name ...
# make upgrade meta_directory=/path/name ...
If these do not work, let me know. If your build script is borked,
then you will have to fix it.
Wietse
Re: Postfix stable release 3.0.0
Am 09.02.2015 um 21:46 schrieb Wietse Venema:
li...@rhsoft.net:
well, meta_directory=%{postfix_daemon_dir} at build leads in
/usr/libexec/postfix/postfix-files instead /etc/postfix/postfix-files
but postfix refuses to start like below
cp /usr/libexec/postfix/postfix-files /etc/postfix/postfix-files
Please do a proper install without copying files by hand
*i do*
that was only to demonstrate that it still seeks it in /etc
the problem is that built-in "meta_directory" defaults to /etc/postfix
[root@testserver:~]$ postconf -d meta_directory
meta_directory = /etc/postfix
hence for now "mv %{buildroot}%{postfix_daemon_dir}/postfix-files
%{buildroot}%{_sysconfdir}/%{name}/postfix-files" after "sh postfix-install"
__
%build
CCARGS="-fPIC -DNO_NIS -DNO_NISPLUS -DNO_EAI -DNO_LMDB -DNO_CDB
-DNO_LDAP -DNO_PGSQL -DNO_SQLITE -DHAS_PCRE -I%{_includedir}/pcre
-DHAS_MYSQL -I%{_includedir}/mysql -DUSE_TLS -DUSE_SASL_AUTH
-DUSE_CYRUS_SASL -I%{_includedir}/sasl
-DDEF_CONFIG_DIR=\\\"%{postfix_config_dir}\\\""
AUXLIBS="-lpcre -L%{_libdir}/mysql -lmysqlclient -lm -L%{_libdir}/sasl2
-lsasl2 -lssl -lcrypto -pie -Wl,-z,now -Wl,-z,relro,-z,noexecstack"
%{__make} %{?_smp_mflags} -f Makefile.init makefiles shared=no
CCARGS="${CCARGS}" AUXLIBS="${AUXLIBS}" DEBUG="" OPT="%{optflags}
-Wno-comment -fno-strict-aliasing"
%{__make} %{?_smp_mflags} CCARGS="${CCARGS}" AUXLIBS="${AUXLIBS}"
DEBUG="" OPT="%{optflags} -Wno-comment -fno-strict-aliasing"
%install
sh postfix-install -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
meta_directory=%{postfix_daemon_dir}
daemon_directory=%{postfix_daemon_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1
install -c auxiliary/rmail/rmail %{buildroot}%{_bindir}/rmail
for i in active bounce corrupt defer deferred flush incoming private
saved maildrop public pid saved trace; do
mkdir -p %{buildroot}%{postfix_queue_dir}/$i
done
mkdir -p %{buildroot}%{_sysconfdir}/pam.d %{buildroot}%{postfix_doc_dir}
%{buildroot}%{postfix_doc_dir}/examples{,/chroot-setup}
install -m 644 %{SOURCE2} %{buildroot}%{_sysconfdir}/pam.d/smtp.%{name}
cp -pr examples/{qmail-local,smtpd-policy}
%{buildroot}%{postfix_doc_dir}/examples
cp -p examples/chroot-setup/LINUX2
%{buildroot}%{postfix_doc_dir}/examples/chroot-setup
rm -f %{buildroot}%{postfix_config_dir}/{TLS_,}LICENSE
%{buildroot}%{_sysconfdir}/%{name}/bounce.cf.default
%{buildroot}%{_sysconfdir}/%{name}/main.cf.default
mv %{buildroot}%{postfix_daemon_dir}/postfix-files
%{buildroot}%{_sysconfdir}/%{name}/postfix-files
find %{buildroot}%{postfix_doc_dir} -type f | xargs chmod 644
find %{buildroot}%{postfix_doc_dir} -type d | xargs chmod 755
Re: Postfix stable release 3.0.0
li...@rhsoft.net:
> well, meta_directory=%{postfix_daemon_dir} at build leads in
> /usr/libexec/postfix/postfix-files instead /etc/postfix/postfix-files
> but postfix refuses to start like below
>
> cp /usr/libexec/postfix/postfix-files /etc/postfix/postfix-files
Please do a proper install without copying files by hand.
Wietse
Re: Postfix stable release 3.0.0
Am 09.02.2015 um 20:32 schrieb Viktor Dukhovni:
On Mon, Feb 09, 2015 at 08:22:12PM +0100, li...@rhsoft.net wrote:
I don't set meta_directory to
/etc in my builds. Indeed none of the meta_directory files are
intended to be "configuration" files that are hand-edited. They
should only be modified as a side-effect of package installation
or removal. This includes dynamicmaps.cf{,.d}, which list installed
dictionary plugins.
well, looks like $meta_directory defaults to /etc, at least *that* is where
they ended in my rpmbuild just change the tarball
Yes, perhaps as a concession to compatibility with Debian, but feel
free to use a more suitable location
well, meta_directory=%{postfix_daemon_dir} at build leads in
/usr/libexec/postfix/postfix-files instead /etc/postfix/postfix-files
but postfix refuses to start like below
cp /usr/libexec/postfix/postfix-files /etc/postfix/postfix-files
and all is fine - so it seems to expect that file somehow below /etc/postfix
Feb 9 21:31:57 testserver postfix/postfix-script[3378]: waiting for the
Postfix mail system to terminate
Feb 9 21:31:59 testserver postfix/postfix-script[3404]: fatal: unable
to create missing queue directories
Feb 9 21:31:59 testserver postfix/postfix-script[3405]: fatal: Postfix
integrity check failed!
Feb 9 21:32:00 testserver postfix/postfix-script[3426]: fatal: unable
to create missing queue directories
Feb 9 21:32:00 testserver postfix/postfix-script[3427]: fatal: Postfix
integrity check failed!
Feb 9 21:32:01 testserver postfix/postfix-script[3448]: fatal: unable
to create missing queue directories
Feb 9 21:32:01 testserver postfix/postfix-script[3449]: fatal: Postfix
integrity check failed!
Feb 9 21:32:02 testserver postfix/postfix-script[3473]: fatal: unable
to create missing queue directories
Feb 9 21:32:02 testserver postfix/postfix-script[3474]: fatal: Postfix
integrity check failed!
Feb 9 21:32:04 testserver postfix/postfix-script[3495]: fatal: unable
to create missing queue directories
Feb 9 21:32:04 testserver postfix/postfix-script[3496]: fatal: Postfix
integrity check failed!
Re: Postfix stable release 3.0.0
On Mon, Feb 09, 2015 at 08:22:12PM +0100, li...@rhsoft.net wrote:
> >I don't set meta_directory to
> >/etc in my builds. Indeed none of the meta_directory files are
> >intended to be "configuration" files that are hand-edited. They
> >should only be modified as a side-effect of package installation
> >or removal. This includes dynamicmaps.cf{,.d}, which list installed
> >dictionary plugins.
>
> well, looks like $meta_directory defaults to /etc, at least *that* is where
> they ended in my rpmbuild just change the tarball
Yes, perhaps as a concession to compatibility with Debian, but feel
free to use a more suitable location.
--
Viktor.
Re: Postfix stable release 3.0.0
Am 09.02.2015 um 20:13 schrieb Viktor Dukhovni:
On Mon, Feb 09, 2015 at 07:47:50PM +0100, li...@rhsoft.net wrote:
one question:
why are "postfix-files", "main.cf.proto" and "master.cf.proto" below /etc
since they are not intended to get modified by the admin and hence belongs
somewhere below /usr?
They are not in "/etc":
$ egrep '(master|main|dynamicmaps)\.cf|postfix-files' conf/postfix-files
| egrep -v '^#' | sort
$config_directory/main.cf.default:f:root:-:644:1
$config_directory/main.cf:f:root:-:644:p
$config_directory/master.cf:f:root:-:644:p
$daemon_directory/main.cf:f:root:-:644:o
$daemon_directory/master.cf:f:root:-:644:o
$meta_directory/dynamicmaps.cf.d:d:root:-:755
$meta_directory/dynamicmaps.cf:f:root:-:644
$meta_directory/main.cf.proto:f:root:-:644
$meta_directory/master.cf.proto:f:root:-:644
$meta_directory/postfix-files.d:d:root:-:755
$meta_directory/postfix-files:f:root:-:644
Rather they are in $meta_directory. I don't set meta_directory to
/etc in my builds. Indeed none of the meta_directory files are
intended to be "configuration" files that are hand-edited. They
should only be modified as a side-effect of package installation
are removal. This includes dynamicmaps.cf{,.d}, which list installed
dictionary plugins.
well, looks like $meta_directory defaults to /etc, at least *that* is
where they ended in my rpmbuild just change the tarball
[harry@srv-rhsoft:~]$ postconf -d | grep meta
meta_directory = /etc/postfix
http://www.postfix.org/postconf.5.html#meta_directory
For backwards compatibility with Postfix versions 2.6..2.11, specify
"meta_directory = $daemon_directory" in main.cf before installing or
upgrading Postfix, or specify "meta_directory = /path/name" on the "make
makefiles", "make install" or "make upgrade" command line
IMHO that should default to $daemon_directory
%build
CCARGS="-fPIC -DNO_NIS -DNO_NISPLUS -DNO_EAI -DNO_LMDB -DNO_CDB
-DNO_LDAP -DNO_PGSQL -DNO_SQLITE -DHAS_PCRE -I%{_includedir}/pcre
-DHAS_MYSQL -I%{_includedir}/mysql -DUSE_TLS -DUSE_SASL_AUTH
-DUSE_CYRUS_SASL -I%{_includedir}/sasl
-DDEF_CONFIG_DIR=\\\"%{postfix_config_dir}\\\""
AUXLIBS="-lpcre -L%{_libdir}/mysql -lmysqlclient -lm -L%{_libdir}/sasl2
-lsasl2 -lssl -lcrypto -pie -Wl,-z,now -Wl,-z,relro,-z,noexecstack"
%{__make} %{?_smp_mflags} -f Makefile.init makefiles shared=no
CCARGS="${CCARGS}" AUXLIBS="${AUXLIBS}" DEBUG="" OPT="%{optflags}
-Wno-comment -fno-strict-aliasing"
%{__make} %{?_smp_mflags} CCARGS="${CCARGS}" AUXLIBS="${AUXLIBS}"
DEBUG="" OPT="%{optflags} -Wno-comment -fno-strict-aliasing"
%install
sh postfix-install -non-interactive install_root=%{buildroot}
config_directory=%{postfix_config_dir}
daemon_directory=%{postfix_daemon_dir}
command_directory=%{postfix_command_dir}
queue_directory=%{postfix_queue_dir} data_directory=%{postfix_data_dir}
sendmail_path=%{postfix_command_dir}/sendmail
newaliases_path=%{_bindir}/newaliases mailq_path=%{_bindir}/mailq
mail_owner=%{postfix_user} setgid_group=%{maildrop_group}
manpage_directory=%{_mandir} sample_directory=%{postfix_sample_dir}
readme_directory=%{postfix_readme_dir} || exit 1
install -c auxiliary/rmail/rmail %{buildroot}%{_bindir}/rmail
If there is a complaint here to be made, it is that perhaps
main.cf.default is largely obsolete (duplicates "postconf -d"),
and is perhaps no longer needed in $config_directory
agreed
Re: Postfix stable release 3.0.0
On Mon, Feb 09, 2015 at 07:47:50PM +0100, li...@rhsoft.net wrote:
> one question:
>
> why are "postfix-files", "main.cf.proto" and "master.cf.proto" below /etc
> since they are not intended to get modified by the admin and hence belongs
> somewhere below /usr?
They are not in "/etc":
$ egrep '(master|main|dynamicmaps)\.cf|postfix-files' conf/postfix-files |
egrep -v '^#' | sort
$config_directory/main.cf.default:f:root:-:644:1
$config_directory/main.cf:f:root:-:644:p
$config_directory/master.cf:f:root:-:644:p
$daemon_directory/main.cf:f:root:-:644:o
$daemon_directory/master.cf:f:root:-:644:o
$meta_directory/dynamicmaps.cf.d:d:root:-:755
$meta_directory/dynamicmaps.cf:f:root:-:644
$meta_directory/main.cf.proto:f:root:-:644
$meta_directory/master.cf.proto:f:root:-:644
$meta_directory/postfix-files.d:d:root:-:755
$meta_directory/postfix-files:f:root:-:644
Rather they are in $meta_directory. I don't set meta_directory to
/etc in my builds. Indeed none of the meta_directory files are
intended to be "configuration" files that are hand-edited. They
should only be modified as a side-effect of package installation
are removal. This includes dynamicmaps.cf{,.d}, which list installed
dictionary plugins.
If there is a complaint here to be made, it is that perhaps
main.cf.default is largely obsolete (duplicates "postconf -d"),
and is perhaps no longer needed in $config_directory.
--
Viktor.
Re: Postfix stable release 3.0.0
Am 08.02.2015 um 23:29 schrieb Wietse Venema: [An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.0.0.html] Postfix stable release 3.0.0 is available. This release ends support for Postfix 2.8 thanks - especially for the header_checks BCC feature! one question: why are "postfix-files", "main.cf.proto" and "master.cf.proto" below /etc since they are not intended to get modified by the admin and hence belongs somewhere below /usr? files below /etc are typically packaged as %config(noreplace) which would be definitly wrong in that case
Re: Postfix stable release 3.0.0
> Am 08.02.2015 um 23:29 schrieb Wietse Venema : > > [An on-line version of this announcement will be available at > http://www.postfix.org/announcements/postfix-3.0.0.html] > > Postfix stable release 3.0.0 is available. This release ends support > for Postfix 2.8. Thanks very much for this great release! I really enjoyed all the snapshots since mid last year. Especially the per milter and per policy service stuff is really great (and of course all other improvements as well). I really love this release. Christian -- Bachelor of Science Informatik Erlenwiese 14, 36304 Alsfeld T: +49 6631 78823400, F: +49 6631 78823409, M: +49 171 9905345 USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com signature.asc Description: Message signed with OpenPGP using GPGMail
