eric

what would be a better option

download the source rpms from and recompile
http://mirror5.qmailtoaster.com/


OR

directly download and install from here
http://mirror5.qmailtoaster.com/current/CentOS/6/x86_64/
the packages here seems to be more updated


rajesh



On 09/05/2014 09:24 AM, [email protected] wrote:
> eric
>
> thanks for your reply
>
> i have been using qmail on a 32 bit centos 5 for the past over 6 years
> and it was a super smooth install and absolutely stable  .... always
> used to work.
>
> further since each package was separate it gave me the freedom to
> customize. example i used to modify chkuser and prevent it from checking
> for formatting and mx records and also the messages error messages.
>
> is there some way to download the individual rpm packages for centos 6
> 64 bit version which i can recompile and install in a manner similar to
> the packages for centos 5 ?
>

Sure. The source rpms are in the repo. Just use your web browser to find
and download them.

>
> other than the above -- in reply to your questions
> during qmail installation -- i did not get any specific error other than
> what i have given below ie
> Non-fatal POSTIN scriptlet failure in rpm package
>  > clamav-0.98.4-2.qt.el6.x86_64
>  > warning: %post(clamav-0.98.4-2.qt.el6.x86_64) scriptlet failed, exit
>  > status 1

I'll have a look into that when I get a chance. I didn't get that error,
I promise you. That was an upgrade though, not a fresh install. I can
hopefully spot the error just by looking at it, now that I know there's
one there.

> thank you for you help as always ...

Certainly!

--
-Eric 'shubes'

>
> ----- Original Message -----
> From: Eric Shubert [mailto:[email protected]]
> To: [email protected]
> Sent: Thu, 04 Sep 2014 06:34:24 -0700
> Subject: [qmailtoaster] Re: install qmailtoaster on centos 6.5 64 bit
> version
>
> On 09/02/2014 12:29 AM, [email protected] wrote:
>  > eric
>  >
>  > thanks for the info.
>  >
>  > packages downloaded correctly but during the installation i got the
>  > following errors related to clam and spamassassin
>  >
>  > in /var/qmail/supervise the folder clamd and spamd are not created.
>  >
>
> Clamav no longer runs under supervise, so it shouldn't be trying to
> create those. spamd is in the process of being moved out from under
> supervise.
>
>  >
>  > Installing : clamav 0.98.4-2.qt.el6.x86_64
>  >                  11/53
>  >
>  > Non-fatal POSTIN scriptlet failure in rpm package
>  > clamav-0.98.4-2.qt.el6.x86_64
>  > warning: %post(clamav-0.98.4-2.qt.el6.x86_64) scriptlet failed, exit
>  > status 1
>  >
>  > Installing : spamassassin-3.3.2-2.qt.el6.x86_64
>  >                  44/53
>  > Non-fatal POSTIN scriptlet failure in rpm package
>  > spamassassin-3.3.2-2.qt.el6.x86_64
>  > warning: %post(spamassassin-3.3.2-2.qt.el6.x86_64) scriptlet failed,
>  > exit status 1
>
> I'll look into these. Can you identify exactly what's failing in the
> scriplet for me? Whatever's running in %post should by and large be
> moved into an independent script (if it hasn't already been).
>
>  >
>  > also another point is that my server was in datacenter and i was
>  > carrying out a remote install via ssh and the firewall locked me out.
>  > my existing firewall settings were over written.
>
> Yeah, you know, I had those lines commented out myself, and I decided to
> put them back in when I redid the install process. Bad decision. They're
> more touble than they're worth. I should just cut a new release w/out
> them while I work on doing it right. I'll see about making that a
> priority. Shouldn't take a whole lot of effort with the new build
> process. (So long as there aren't other changes in there which can't be
> released yet for some reason).
>
>
> Thanks!
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to