Slack 11.0 postfix from SlackBuilds - problem
Rich Grise
told me bare-metal reinstall. I emailed Alan Hicks and asked if I should
know anything, and he said what to back up, then use his SlackBuild
scripts, and he said, "The SlackBuild scripts at the above web site
should make this almost trivial. "
Well, somehow in the last two hours, I've managed to create the
package postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it,
I get:
"Installing package postfix-2.4.1-i486-1_SBo...
PACKAGE DESCRIPTION:
postfix: What is Postfix? It is Wietse Venema's mailer that started life as an
postfix: alternative to the widely-used Sendmail program.
postfix:
postfix: Postfix attempts to be fast, easy to administer, and secure, while at
postfix: the same time being sendmail compatible enough to not upset existing
postfix: users. Thus, the outside has a sendmail-ish flavor, but the inside is
postfix: completely different.
postfix:
postfix: Packaging script written by Alan Hicks <al...@lizella.net>
postfix: and the SlackBuilds.org Team http://www.slackbuilds.org
postfix:
Executing install script for postfix-2.4.1-i486-1_SBo...
chown: missing operand after `postfix'
Try `chown --help' for more information."
I've chowned my whole postfix dir tree to root:root; what am I missing
_NOW_?
Thanks,
Rich
Henrik Carlqvist
> When my system got compromised, I asked how to fix it, and everybody
> told me bare-metal reinstall.
No, not everybody. At least trryhend and I suggested that you should _not_
try to reinstall to a status which could easily be compromised again.
Instead we both suggested that you should have a separate small bullet
proof firewall and place any servers safely behind that firewall.
> I emailed Alan Hicks and asked if I should know anything, and he said
It probably feels safe to have direct contact to someone as knowledgdable
as Alan.
> Well, somehow in the last two hours, I've managed to create the package
> postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it, I get:
I hope that you are not trying to put a mailserver on your firewall box
again? It would be safer to have a mailserver on a separate box in a DMZ.
> postfix: Packaging script written by Alan Hicks <al...@lizella.net>
That name seems familiar :-)
> Executing install script for postfix-2.4.1-i486-1_SBo... chown: missing
> operand after `postfix' Try `chown --help' for more information."
Ouch, something seems broken in that package.
> I've chowned my whole postfix dir tree to root:root; what am I missing
> _NOW_?
As you have direct contact with Alan you could ask him what is broken in
the package. He probably knows best about that package and if there is any
bug in the script he should be the one to know so he can fix it.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
Rich Grise
I get a "page not found" error - I'll have to ask Alan if there's a
proper tarball out there - the postfix website offers 2.4.13; the
slackbuild for Slack 11.0 says v2.4.1; I'll have to ask Alan if that will
work with the current slackbuild scripts, or maybe to fix that page at
slackbuilds.
Thanks!
Rich
Loki Harfagr
> On Wed, 09 Dec 2009 08:40:20 +0100, Henrik Carlqvist wrote:
>> Rich Grise <rich...@example.net> wrote:
>>> When my system got compromised, I asked how to fix it, and everybody
>>> told me bare-metal reinstall.
...
>> Ouch, something seems broken in that package.
>>
>>> I've chowned my whole postfix dir tree to root:root; what am I missing
>>> _NOW_?
>>
>> As you have direct contact with Alan you could ask him what is broken
>> in the package. He probably knows best about that package and if there
>> is any bug in the script he should be the one to know so he can fix it.
>>
> Yeah. I went to the slackbuild site again, to download the tarball, and
> I get a "page not found" error - I'll have to ask Alan if there's a
> proper tarball out there - the postfix website offers 2.4.13; the
> slackbuild for Slack 11.0 says v2.4.1; I'll have to ask Alan if that
> will work with the current slackbuild scripts, or maybe to fix that page
> at slackbuilds.
On another angle you also may consider to use sendmail which has the
special(*) advantage to cost no sweat in finding the package in Slackware ;-)
(*) it also has other non-special advantages but that's another trollalley ;->
Rich Grise
For one thing, from what I hear, sendmail is a nightmare to configure, and
for another, the company alreay paid Alan Hicks almost $1000.00 to set up
postfix, dovecot, and spamassassin.
Thanks,
Rich
+Alan Hicks+
Hash: SHA1
On 2009-12-08, Rich Grise <rich...@example.net> wrote:
> When my system got compromised, I asked how to fix it, and everybody
> told me bare-metal reinstall. I emailed Alan Hicks and asked if I should
> know anything, and he said what to back up, then use his SlackBuild
> scripts, and he said, "The SlackBuild scripts at the above web site
> should make this almost trivial. "
>
> Well, somehow in the last two hours, I've managed to create the
> package postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it,
> I get:
>
> "Installing package postfix-2.4.1-i486-1_SBo...
<snip>
> Executing install script for postfix-2.4.1-i486-1_SBo...
> chown: missing operand after `postfix'
> Try `chown --help' for more information."
>
> I've chowned my whole postfix dir tree to root:root; what am I missing
> _NOW_?
The fact that your whole postfix dir tree should not be root:root after
installing. Several files and directories installed by postfix need
special user and/or group permissions for security purposes. postfix is
fairly unique in that the Makefile does not set permissions on the
different files and directories before the package is created. Rather
there is a special argument to the postfix binary that handles this.
The doinst.sh script attempts to resolve this for you. Apparently that
has not worked in this case.
Did you create the postfix user and postdrop group as stated in the
build script? Did you by chance already have an existing /etc/postfix
directory when you installed this package? Either of those could
possibly result in this error if they were not done properly.
You can attempt to repair this problem after installation by running
the following command as root:
# postfix set-permissions
This should resolve the permissions problems, assuming of course that
the user and group are properly setup, and that the configuration files
in /etc/postfix are correct.
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkshhYQACgkQNj1TaGS9H5JyMwCaA/ptaTaEXkW7/e9U+WDZRa6k
6lwAn1jIlvwUzLmVfVZwCdaBNaabxjL2
=JD/K
-----END PGP SIGNATURE-----
Rich Grise
Whew! ;-)
Rich
Rich Grise
Cheers!
Rich