17 May 2013 13:58
25 Mar 2013 16:15
[qmailtoaster-devel] Greeting failed, but delivery success
Clement Thomas <clement1289 <at> gmail.com>
2013-03-25 15:15:17 GMT
2013-03-25 15:15:17 GMT
Hi,
We use qmail with ezmlm for mailinglist service
[root <at> xx-yyy ~]# rpm -qa|egrep '(ezmlm|qmail)'
qmail-toaster-1.03-1.3.25
ezmlm-toaster-0.53.324-1.3.3
There was postfix SMTP failure with one of the MX to which qmail tried
mail delivery and got a 4xx reply. Log says ZConnected to , but greeting
failed, server says "All ports busy". Despite this message, the delivery
was success. exact log at
http://pastie.org/private/stwlr6jmvhiljzbed0i3ag All the mail delivery
tried via the above MX is lost, but qmail log reports success with above
ZConnected message. Z means delivery deferral, if i am not wrong.
Regards,
Clement
24 Sep 2012 18:57
[qmailtoaster-devel] dovecot lda discussion
Eric Shubert <ejs <at> shubes.net>
2012-09-24 16:57:14 GMT
2012-09-24 16:57:14 GMT
This thread just popped up on the vpopmail list today. http://www.mail-archive.com/vchkpw <at> inter7.com/msg28208.html We'll be going to use dovecot-lda eventually, perhaps after an initial dovecot implementation, so as not to change too many things at once. Does anyone have any thoughts about this? Just throwing this out here at this point. I don't expect anything to happen with it for several months. -- -- -Eric 'shubes'
10 Aug 2012 06:57
[qmailtoaster-devel] COS 6 Issues
Dan McAllister <qmt <at> it4soho.com>
2012-08-10 04:57:19 GMT
2012-08-10 04:57:19 GMT
Greetings Developers...
As many of you know, I've been running QMT on RHEL/COS 6 for quite some time now... and other than some perl issues on SpamAssassin (and a recent issue with vqadmin), I've always had the greatest of luck building our packages on my COS6 systems. (For brevity sake, I'm only going to refer to it as COS6 from here on in).
I consider myself VERY lucky that this has been the case, and I've helped many a user successfully get QMT installed and running on COS6.
In any case, since the next major rev (1.5) of QMT is on the schedule for SOON, I thought I'd share what I've done already.... This way, the experiences I have had (and obstacles I have overcome) don't have to be re-worked.
There are also a couple of issues that have NOT come up previously, that may NEED to be resolved now.
Dependencies:
The first issue we encountered were the dependencies. I have attached the complete list (133 of them) in a file (deps.txt) here. Along the same lines, the default mail program installed in COS6 is postfix -- a departure from the previous default of sendmail. As a result, any build script now needs to uninstall postfix in addition to (or instead of) sendmail.
Also, as-of the most recent QMT-1.4 release, there are a couple of modifications in the required build order (like control-panel having to come before vqadmin).
PHP & Website Access:
The next issue we found was the reasonably-well-discussed PHP issue (both short tags and global variables must be enabled for control panel, vqadmin, and some parts of squirrelmail to work properly). I believe some, if not all of the vqadmin and squirrelmail issues are dealt with "upstream" -- probably in the QMT 1.4 release -- but I believe control-panel is home-grown, and so someone on our delelopment team will probably need to address that. In the mean time, you can either enable them globally, or use a .htaccess file in the folders that contain the web code.
Build Scripts:
The advent of QMT 1.4, and the bringing up of vqadmin from inter7's 2.3.4 to 2.3.7, we've seen a problem arise that has actually been a problem for several packages for several years -- it's just gone unnoticed (or un-fixed) for all that time.
At issue is the ability of a .configure script (usually created with an automake command sequence) to properly detect the kind of system that it is building on... even COS5 64-bit suffers from this problem on many of our packages. In the past, the build scripts have been able to build anyway -- with a "generic linux" directive (usually seen as "unknown-linux-gnu" or something similar). (This COULD also be a problem on 32-bit linux, but I haven't tested on it -- not much in the way of 32-bit COS6 being installed these days!)
The fix for most of these packages is actually rather simple... when we get the build scripts from upstream, we need to update the included config.sub and config.guess files (the correct versions are included in the rpm package - I believe that is the correct origin, but several copies can be found on most systems). (Package guys, the location for an up-to-date copy of each is /usr/lib/rpm/config.sub and /usr/lib/rpm/config.guess).
One last point -- SEVERAL of our packages fail with these config.sub|guess scripts! The difference vqadmin made was that the other packages built anyway! Of course, not being able to optimize for the local machine, they built in a very generic (and inefficient) way... not that most QMT installations need efficiency that bady!
PHP:
As noted previously, some of our web interfaces (control-panel most notably) will need cleaning up to meet PHP 5.3 guidelines -- especially since backward compatibility to PHP 6 is NOT guaranteed! I won't repeat myself here, other than to say to whomever tackles control-panel: short tags aren't the ONLY issue -- you also have to resolve some global variable issues...
Perl:
The package that relies so very heavily on perl is spamassassin... and I say that because that's the package for which I spent the MOST time resolving dependencies...
... and in some ways I never did resolve all of the deps. In the list of dependencies I've provided, 20 are perl RPMs -- and they then install another 24 "second and third tier" dependencies (for a total of 44 perl packages... SO FAR.
With these 44 perl RPMs installed, spamassassin WILL run, but with some additional perl dependencies not resolved, it may crash if you try to access a missing module.
The perl modules I couldn't find on a "standard" repo were:
Mail::SPF (this is available on repoforge & epel, as well as CPAN)
This adds another 28 perl module dependencies -- and I haven't YET found a way to get them to install cleanly all at once
-- that is, CPAN will partially build, then fail... but if you re-run it, the build is successful
IP::Country (this is available on repoforfe or CPAN, but not epel)
This module has another dependency, but installs cleanly
Net::Ident (also available on repoforge or CPAN, but not epel)
LWP::UserAgent (this is apparently re-named LWP::UserAgent::Determined -- which I found on repoforge)
- The one on CPAN has 32 sub-dependencies, and also will not install cleanly without re-starting CPAN
HTTP::Date (Saved the best for last -- only found this one on CPAN -- neither other repo)
With no repository having ALL of the perl modules SpamAssassin wants to see, I'm of the opinion that we'll have to use CPAN to satisfy some of the deps....
Other ideas??
Package-by-Package:
OK -- here are my first-run observations for each package:
vpopmail-toaster-5.4.33-1.4.0: SRC RPM uses buildprereq, which is deprecated... (usae BuildRequires instead)... probably an upline thing, but I haven't looked into it
control-panel-toaster-0.5-1.4.0: Again, uses buildprereq. Otherwise, it builds & installs cleanly (curious that the buildprereq is for perl, not php -- is that an error???)
vqadmin-toaster-2.3.7-1.4.1: Does not detect 64-bit Linux type, or COS6, build fails as a result... can be fixed by forcing the use of current config.guess and config.sub, at which time it compiles cleanly
ucspi-tcp-toaster-0.88-1.3.9: Builds and installs cleanly (only minor compiler warnings)
libsrs2-toaster-1.0.18-1.3.6: Has some minor compiler warnings with SHA processing (definitely an upline problem), Otherwise builds & installs cleanly
libdomainkeys-toaster-0.68-1.3.6: Builds and installs cleanly
qmail-toaster-1.03-1.3.22: Also uses buildprereq -- plus some minor compiler warnings (which won't likely ever be looked at). Otherwise, it builds & installs cleanly
squirrelmail-toaster-1.4.20-1.3.17: Again, uses buildprereq. Otherwise, it builds & installs cleanly
spamassassin-toaster-3.3.2-1.4.3: As noted previously, perl modules missing (all can be obtained thru CPAN, though not without multiple tries in my current experience)
ripmime-toaster-1.4.0.6-1.3.6: Some minor compiler warnings (which won't likely ever be looked at). Otherwise, it builds & installs cleanly
clamav-toaster-0.97.5-1.4.1: Builds and installs cleanly
simscan-toaster-1.4.0-1.4.0: Some minor compiler warnings (printf declaration issues) Otherwise, it builds & installs cleanly
qmailmrtg-toaster-4.2-1.3.7: Some minor compiler warnings (re-defining exit?) Otherwise, it builds & installs cleanly
ezmlm-toaster-0.53.324-1.3.6: Some minor compiler warnings (re-defining exit?) Otherwise, it builds & installs cleanly
autorespond-toaster-2.0.5-1.4.0: Builds and installs cleanly
qmailadmin-toaster-1.2.16-1.4.0: Some minor compiler warnings (re-defining vars & pkgs) Otherwise, it builds & installs cleanly
courier-authlib-toaster-0.59.2-1.3.10: Builds and installs cleanly
courier-imap-toaster-4.1.2-1.3.10: Again, uses buildprereq. Otherwise, it builds & installs cleanly
maildrop-toaster-2.0.3-1.3.8: Builds and installs cleanly
isoqlog-toaster-2.1-1.3.7: Again, uses buildprereq. Otherwise, it builds & installs cleanly
daemontools-toaster-0.76-1.3.6: Builds and installs cleanly
I hope you guys find this helpful!
Dan McAllister
As many of you know, I've been running QMT on RHEL/COS 6 for quite some time now... and other than some perl issues on SpamAssassin (and a recent issue with vqadmin), I've always had the greatest of luck building our packages on my COS6 systems. (For brevity sake, I'm only going to refer to it as COS6 from here on in).
I consider myself VERY lucky that this has been the case, and I've helped many a user successfully get QMT installed and running on COS6.
In any case, since the next major rev (1.5) of QMT is on the schedule for SOON, I thought I'd share what I've done already.... This way, the experiences I have had (and obstacles I have overcome) don't have to be re-worked.
There are also a couple of issues that have NOT come up previously, that may NEED to be resolved now.
Dependencies:
The first issue we encountered were the dependencies. I have attached the complete list (133 of them) in a file (deps.txt) here. Along the same lines, the default mail program installed in COS6 is postfix -- a departure from the previous default of sendmail. As a result, any build script now needs to uninstall postfix in addition to (or instead of) sendmail.
Also, as-of the most recent QMT-1.4 release, there are a couple of modifications in the required build order (like control-panel having to come before vqadmin).
PHP & Website Access:
The next issue we found was the reasonably-well-discussed PHP issue (both short tags and global variables must be enabled for control panel, vqadmin, and some parts of squirrelmail to work properly). I believe some, if not all of the vqadmin and squirrelmail issues are dealt with "upstream" -- probably in the QMT 1.4 release -- but I believe control-panel is home-grown, and so someone on our delelopment team will probably need to address that. In the mean time, you can either enable them globally, or use a .htaccess file in the folders that contain the web code.
Build Scripts:
The advent of QMT 1.4, and the bringing up of vqadmin from inter7's 2.3.4 to 2.3.7, we've seen a problem arise that has actually been a problem for several packages for several years -- it's just gone unnoticed (or un-fixed) for all that time.
At issue is the ability of a .configure script (usually created with an automake command sequence) to properly detect the kind of system that it is building on... even COS5 64-bit suffers from this problem on many of our packages. In the past, the build scripts have been able to build anyway -- with a "generic linux" directive (usually seen as "unknown-linux-gnu" or something similar). (This COULD also be a problem on 32-bit linux, but I haven't tested on it -- not much in the way of 32-bit COS6 being installed these days!)
The fix for most of these packages is actually rather simple... when we get the build scripts from upstream, we need to update the included config.sub and config.guess files (the correct versions are included in the rpm package - I believe that is the correct origin, but several copies can be found on most systems). (Package guys, the location for an up-to-date copy of each is /usr/lib/rpm/config.sub and /usr/lib/rpm/config.guess).
One last point -- SEVERAL of our packages fail with these config.sub|guess scripts! The difference vqadmin made was that the other packages built anyway! Of course, not being able to optimize for the local machine, they built in a very generic (and inefficient) way... not that most QMT installations need efficiency that bady!

PHP:
As noted previously, some of our web interfaces (control-panel most notably) will need cleaning up to meet PHP 5.3 guidelines -- especially since backward compatibility to PHP 6 is NOT guaranteed! I won't repeat myself here, other than to say to whomever tackles control-panel: short tags aren't the ONLY issue -- you also have to resolve some global variable issues...
Perl:
The package that relies so very heavily on perl is spamassassin... and I say that because that's the package for which I spent the MOST time resolving dependencies...
... and in some ways I never did resolve all of the deps. In the list of dependencies I've provided, 20 are perl RPMs -- and they then install another 24 "second and third tier" dependencies (for a total of 44 perl packages... SO FAR.
With these 44 perl RPMs installed, spamassassin WILL run, but with some additional perl dependencies not resolved, it may crash if you try to access a missing module.
The perl modules I couldn't find on a "standard" repo were:
Mail::SPF (this is available on repoforge & epel, as well as CPAN)
This adds another 28 perl module dependencies -- and I haven't YET found a way to get them to install cleanly all at once
-- that is, CPAN will partially build, then fail... but if you re-run it, the build is successful
IP::Country (this is available on repoforfe or CPAN, but not epel)
This module has another dependency, but installs cleanly
Net::Ident (also available on repoforge or CPAN, but not epel)
LWP::UserAgent (this is apparently re-named LWP::UserAgent::Determined -- which I found on repoforge)
- The one on CPAN has 32 sub-dependencies, and also will not install cleanly without re-starting CPAN
HTTP::Date (Saved the best for last -- only found this one on CPAN -- neither other repo)
With no repository having ALL of the perl modules SpamAssassin wants to see, I'm of the opinion that we'll have to use CPAN to satisfy some of the deps....
Other ideas??
Package-by-Package:
OK -- here are my first-run observations for each package:
vpopmail-toaster-5.4.33-1.4.0: SRC RPM uses buildprereq, which is deprecated... (usae BuildRequires instead)... probably an upline thing, but I haven't looked into it
control-panel-toaster-0.5-1.4.0: Again, uses buildprereq. Otherwise, it builds & installs cleanly (curious that the buildprereq is for perl, not php -- is that an error???)
vqadmin-toaster-2.3.7-1.4.1: Does not detect 64-bit Linux type, or COS6, build fails as a result... can be fixed by forcing the use of current config.guess and config.sub, at which time it compiles cleanly
ucspi-tcp-toaster-0.88-1.3.9: Builds and installs cleanly (only minor compiler warnings)
libsrs2-toaster-1.0.18-1.3.6: Has some minor compiler warnings with SHA processing (definitely an upline problem), Otherwise builds & installs cleanly
libdomainkeys-toaster-0.68-1.3.6: Builds and installs cleanly
qmail-toaster-1.03-1.3.22: Also uses buildprereq -- plus some minor compiler warnings (which won't likely ever be looked at). Otherwise, it builds & installs cleanly
squirrelmail-toaster-1.4.20-1.3.17: Again, uses buildprereq. Otherwise, it builds & installs cleanly
spamassassin-toaster-3.3.2-1.4.3: As noted previously, perl modules missing (all can be obtained thru CPAN, though not without multiple tries in my current experience)
ripmime-toaster-1.4.0.6-1.3.6: Some minor compiler warnings (which won't likely ever be looked at). Otherwise, it builds & installs cleanly
clamav-toaster-0.97.5-1.4.1: Builds and installs cleanly
simscan-toaster-1.4.0-1.4.0: Some minor compiler warnings (printf declaration issues) Otherwise, it builds & installs cleanly
qmailmrtg-toaster-4.2-1.3.7: Some minor compiler warnings (re-defining exit?) Otherwise, it builds & installs cleanly
ezmlm-toaster-0.53.324-1.3.6: Some minor compiler warnings (re-defining exit?) Otherwise, it builds & installs cleanly
autorespond-toaster-2.0.5-1.4.0: Builds and installs cleanly
qmailadmin-toaster-1.2.16-1.4.0: Some minor compiler warnings (re-defining vars & pkgs) Otherwise, it builds & installs cleanly
courier-authlib-toaster-0.59.2-1.3.10: Builds and installs cleanly
courier-imap-toaster-4.1.2-1.3.10: Again, uses buildprereq. Otherwise, it builds & installs cleanly
maildrop-toaster-2.0.3-1.3.8: Builds and installs cleanly
isoqlog-toaster-2.1-1.3.7: Again, uses buildprereq. Otherwise, it builds & installs cleanly
daemontools-toaster-0.76-1.3.6: Builds and installs cleanly
I hope you guys find this helpful!
Dan McAllister
alsa-lib apr apr-util apr-util-ldap aspell atk autoconf avahi-libs bzip2-devel bzip2-libs cairo cloog-ppl compat-gcc-34 compat-gcc-34-c++ cpp cronnie cronnie-anacron crontabs crypto-utils cups-libs curl curl-devel ecj elfutils elfutils-libs expect file fontconfig freetype gcc gcc-c++ gcc-java gd gdb gdbm-devel glibc-devel glibc-headers gmp-devel gnutls gtk2 hicolor-icon-theme httpd httpd-manual httpd-tools jasper-libs java-1.5.0-gcj java_cup jpackage-utils kernel-headers libart_lgpl libcurl libedit libgcj libgcj-devel libgomp libICE libidn-devel libjpeg libpng libSM libstdc++-devel libtasn1 libthai libtiff libtool libtool-ltdl libtool-ltdl-devel libX11 libX11-common libXau libxcb libXcomposite libXcursor libXdamage libXext libXfixes libXft libXi libXinerama libXpm libXrandr libXrender libXtst mailcap make mod_perl mod_ssl mpfr mrtg mysql mysql-devel mysql-libs mysql-server ncurses-devel openssh openssh-clients pango patch pcre pcre-devel perl perl-Archive-Tar perl-BSD-Resource perl-Digest-SHA perl-Digest-SHA1 perl-Encode-Detect perl-Error perl-ExtUtils-MakeMaker perl-Font-AFM perl-HTML-Parser perl-IO-Socket-INET6 perl-IO-Socket-SSL perl-IO-Zlib perl-Mail-DKIM perl-NetAddr-IP perl-Net-DNS perl-Newt perl-TimeDate perl-Time-HiRes php pixman pkgconfig ppl rpm-build sinjdoc tcl unzip webalizer wget xz xz-lzma-compat zip zlib-devel
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-devel-unsubscribe <at> qmailtoaster.com For additional commands, e-mail: qmailtoaster-devel-help <at> qmailtoaster.com
7 Aug 2012 17:21
[qmailtoaster-devel] vqadmin 1.4 BROKEN (?)
Dan McAllister <qmt <at> it4soho.com>
2012-08-07 15:21:34 GMT
2012-08-07 15:21:34 GMT
Greetings QMT developers... I've been off working on other things and just got back to doing some QMT testing this morning... and am finding that vqadmin version 1.4 is broken for 64-bit arch. The error appears in the configure portion of the make, where in spite of being called with a --with cnt5064 flag, the configure call is being made with --host=x86_64-unknown-linux-gnu and --build=x86_64-unknown-linux-gnu flags that are later determined to be unsupported. I have confirmed that the error persists on both 1.4.0 and 1.4.1 I don't know who worked on these... and I haven't checked them against a 32-bit build (is anyone still using 32-bit COS?) or against COS5 yet... but I'm assuming this is a simple error to fix, I just don't know who to look to to get it fixed! Thanks to all Dan McAllister -- -- IT4SOHO, LLC PO Box 507 St. Petersburg, FL 33731-0507 CALL TOLL FREE: 877-IT4SOHO We have support plans for QMail!
6 Aug 2012 19:41
[qmailtoaster-devel] Roadmap update (short term)
Eric Shubert <ejs <at> shubes.net>
2012-08-06 17:41:04 GMT
2012-08-06 17:41:04 GMT
Just an update to keep everyone in the loop here. The 1.4.x versions are upgrades to upstream versions. This phase is essentially complete. Bharath will be making a few more 1.4.x versions that are compatible with the stock php53 and php6 as well. Some packages have a 1.4.x version, and some do not. All packages will have a 1.5.0 version, which will be the first Cos6 compliant version. There will also be an updated QTP package which corresponds with these. I'm beginning work on these this week, and with any luck will have them available before mid-month. In addition to adding cnt_60 sections to the spec files, I'll be removing the oldest cruft for distro versions that are no longer supported. If anyone really needs to go back to that stuff, the older srpms are in the archive. I would have liked to have had that stuff in the initial git repos, but I don't think that value is as great as getting Cos6 support available sooner. I still might grab the older versions when the time comes to populate the github repos. I'll be leaving the current Suse and Mandriva stuff in there, and will also add sections for the latest Fedora releases. There will be no testing done on these before they're released though. Only CentOS 5/6 will be tested and officially supported for the time being. That's all for now. Comment and questions are welcome. Thanks. -- -- -Eric 'shubes'
26 Jul 2012 19:19
[qmailtoaster-devel] QTP Bug for CentOS 6
Dan McAllister <qmt <at> it4soho.com>
2012-07-26 17:19:01 GMT
2012-07-26 17:19:01 GMT
Greetings Developers:
I had occasion today to try to install spamdyke on a FRESH install of CentOS 6 via QTP -- and found that QTP is rejecting my CentOS 6 as unsupported.
However, looking into the scripts themselves, they are supposed to support CentOS & RHEL 6.x (according to notes within the scripts).
Here's what I found:
On line 356 of the qtp-whatami script, version 6 is missing from the case statement...
case $relnum in
4 | 5 )
should read
case $relnum in
4 | 5 | 6 )
NOTE: the check for 6 appears elsewhere, so it appears to have just been an oversight...
Once the extra 4 chars were added, spamdyke installed via QTP just fine...
Dan
-- IT4SOHO, LLC PO Box 507 St. Petersburg, FL 33731-0507 CALL TOLL FREE: 877-IT4SOHO We have support plans for QMail!
I had occasion today to try to install spamdyke on a FRESH install of CentOS 6 via QTP -- and found that QTP is rejecting my CentOS 6 as unsupported.
However, looking into the scripts themselves, they are supposed to support CentOS & RHEL 6.x (according to notes within the scripts).
Here's what I found:
On line 356 of the qtp-whatami script, version 6 is missing from the case statement...
case $relnum in
4 | 5 )
should read
case $relnum in
4 | 5 | 6 )
NOTE: the check for 6 appears elsewhere, so it appears to have just been an oversight...
Once the extra 4 chars were added, spamdyke installed via QTP just fine...
Dan
-- IT4SOHO, LLC PO Box 507 St. Petersburg, FL 33731-0507 CALL TOLL FREE: 877-IT4SOHO We have support plans for QMail!
18 Jul 2012 19:27
[qmailtoaster-devel] clamav 0.97.5 changes
Eric Shubert <ejs <at> shubes.net>
2012-07-18 17:27:11 GMT
2012-07-18 17:27:11 GMT
I hope to have clamav-toaster-0.97.5-1.4.1 available by the first of next week. I intend to make 2 changes in addition to the upstream version update. First, I hope to redo the patch file so that it works with the tighter default fuzz factor that COS6 uses. I prefer doing this rather than adding an option to the patch command. More significantly, I intend to remove the database files from the rpm, and modify the spec file such that on a new install it invokes freshclam in order to obtain the signature database files. This will substantially reduce the size of the rpm, saving a good deal of bandwidth for updates (which has bitten us in the past). If anyone has a problem with this, now's the time to speak up. Thanks. -- -- -Eric 'shubes'
28 Jun 2012 18:24
[qmailtoaster-devel] Clamav 0.97.5 for testing
Bharath Chari <qmailtoaster <at> arachnis.com>
2012-06-28 16:24:31 GMT
2012-06-28 16:24:31 GMT
Hi all, I've uploaded the new clamav 0.97.5 src rpm to my server for TESTING: http://arachnis.com/qmt/clamav/clamav-toaster-0.97.5-1.4.1.src.rpm Please use in production only after Eric promotes it to the mirrors. Eric : No changes made to spec file except for version numbers/packaging information. I've included the main.cvd in this version too. As discussed, at some point we'll stop doing that. Bharath
16 Jun 2012 16:43
[qmailtoaster-devel] Download script with SHA1 verification
Ron Pacheco <ron <at> pacheco.net>
2012-06-16 14:43:33 GMT
2012-06-16 14:43:33 GMT
Devel, Attached is my first shot at a download script that: (1) Makes 10 retry attempts on a file; in the long run probably overkill, but right now with some mirror issues, it should be enough attempts to resolve any problems. (2) Verifies a download against an SHA1 checksum. A checksum fail is simply considered a download fail and the download will be reattempted up to the retry limit. (On a checksum fail, both the srpm and sha1 file are removed before the retry, under the premise that either one could have been corrupt on download.) I tested this extensively on my own servers, but I obviously could not test against the live servers since there are no SHA1 checksum files on the live download mirrors at present. Well, not that I know of. ;) The script assumes the standard convention of the SHA1 file being name file.ext.sha1 for a file named file.ext. Cheers, Ron
#!/bin/sh
# To sha1sum or not to sha1sum
if [ "$1" = "-nosha1" ]; then
USESHA1=no
echo "NOTE: Downloads will NOT be verified with sha1 checksums!"
sleep 3
else
USESHA1=yes
fi
# Verify that sha1sum is available
if [ "$USESHA1" = "yes" ] ; then
which sha1sum >/dev/null 2>&1
if [ $? -ne 0 ]; then
echo "Cannot find sha1sum. Installing sha1sum is highly recommended,"
echo "but you may run this script again with the -nosha1 option."
exit 1
fi
fi
# Got wget?
which wget >/dev/null 2>&1
if [ $? -ne 0 ]; then
echo "Please install wget before proceeding."
exit 1
fi
# Subroutine to download file and verify sha1 checksum
getfile() {
# max retries; 10 seemed reasonable
retries=10
# success flag
finished=no
while [ "$finished" = "no" ]; do
# bail if max retries reached
if [ $retries -eq 0 ]; then
echo "Failed downloading: http://$1/$2"
echo "Please check your connection."
exit 1
else
retries=`expr $retries - 1`
fi
# if we don't have the file already, wget it
if [ ! -f $2 ]; then
wget http://$1/$2
fi
# did we wget the file?
if [ -f $2 ]; then
# are we checking the sha1 sum?
if [ "$USESHA1" = "yes" ]; then
# if we don't have the sha1 checksum file, wget it
if [ ! -f $2.sha1 ]; then
wget http://$1/$2.sha1
fi
# if the sha1 file was retrieved, verify the checksum
if [ -f $2.sha1 ]; then
sha1sum -c $2.sha1
if [ $? -eq 0 ]; then
finished=yes
fi
fi
# if we have both the srpm and sha1 files but the checksum failed,
# then blow them both away for another attempt
if [ -f $2.sha1 -a "$finished" = "no" ]; then
rm -f $2 $2.sha1
fi
else
finished=yes
fi
fi
done
}
QT_RPMLIST="http://www.qmailtoaster.com/info/current.txt"
QT_MIRRORS="mirrors.qmailtoaster.com"
QT_RPMS=`wget -q -O - ${QT_RPMLIST}`
# Make sure we have the list
if [ -z "${QT_RPMS}" ] ; then
echo "Qmail Toaster source RPM list could not be downloaded from"
echo $QT_RPMLIST
echo "Please check your connection and try again."
exit 1
fi
# Download the packages
for SRPM in $QT_RPMS; do
getfile $QT_MIRRORS $SRPM
done
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-devel-unsubscribe <at> qmailtoaster.com For additional commands, e-mail: qmailtoaster-devel-help <at> qmailtoaster.com
23 May 2012 16:58
[qmailtoaster-devel] Linux Today - Mandriva To Use Mageia For Their Business Servers
Eric Shubert <ejs <at> shubes.net>
2012-05-23 14:58:00 GMT
2012-05-23 14:58:00 GMT
Nigel, http://www.linuxtoday.com/infrastructure/mandriva-to-use-mageia-for-their-business-servers.html http://blog.mageia.org/en/2011/06/01/mageia-1/ Perhaps we should be keeping an eye on mageia instead of mandriva? Johannes, Does OBS have support for mageia yet? Any plans that you know of? -- -- -Eric 'shubes'
RSS Feed