Slack 11.0 postfix from SlackBuilds - problem
in [Slackware]
|
Prev: slack 13.0 DVD Burning
Next: Menu editing in KDE 4.2
From: Rich Grise on 8 Dec 2009 14:08 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... 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 <alan(a)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
From: Henrik Carlqvist on 9 Dec 2009 02:40 Rich Grise <richgrise(a)example.net> wrote: > 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 <alan(a)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(a)localhost postmaster(a)localhost
From: Rich Grise on 9 Dec 2009 11:00 On Wed, 09 Dec 2009 08:40:20 +0100, Henrik Carlqvist wrote: > Rich Grise <richgrise(a)example.net> wrote: >> 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 <alan(a)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. > 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. Thanks! Rich
From: Loki Harfagr on 9 Dec 2009 12:53 Wed, 09 Dec 2009 08:00:57 -0800, Rich Grise did cat : > On Wed, 09 Dec 2009 08:40:20 +0100, Henrik Carlqvist wrote: >> Rich Grise <richgrise(a)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 ;->
From: Rich Grise on 9 Dec 2009 15:02
On Wed, 09 Dec 2009 17:53:15 +0000, Loki Harfagr wrote: > Wed, 09 Dec 2009 08:00:57 -0800, Rich Grise did cat�: > >> On Wed, 09 Dec 2009 08:40:20 +0100, Henrik Carlqvist wrote: >>> Rich Grise <richgrise(a)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 > ;-> 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 |