Re: Fwd: Re: [qmailtoaster] centos 6

[Andrew Swartz]

I had the issue.

I merely fixed it rather than fully investigating it.

I had some accounts where, after the backup/restore, the passwords
worked fine.  Yet other where the passwords failed.  When I looked at
the database, the ones where the passwords failed had a long cleartext
password which was chopped off at 16 characters.  All the accounts with
short passwords worked fine.  I looked at the database schema, and saw
that the cleartext password field is 16 characters.  So I tried
authenticating with the shortened version of the password, and I
~believe~ that it worked.  However, I figured that there was now a
discrepancy between the cleartext and the hash, so I reset the passwords
for all the affected accounts.

In retrospect, I wish I had investigated further; however, I was in the
mode of fixing the problem as rapidly as possible.  I apologize for not
digging further so that I could pass the info along to others.

I do not remember if I visually compared the hashes.  I probably did,
and they were probably the same.  That is probably why I got worried
about a cleartext versus hash discrepancy.

This much I can say with 100% confidence:
The accounts with passwords >16 characters would not authenticate after
the backup/restore procedure.  Resetting those passwords fixed the problem.


-Andy



On 10/2/2018 2:49 PM, Tony White wrote:
> Hi Eric,
>   Sorry, I made it sound like you had the issue. I know it was not you.
> 
> best wishes
>   Tony White
> 
> On 03/10/18 07:50, Eric Broch wrote:
> 
>> Okay,
>>
>> It seems odd, to me at least, that using the mysql/mariadb commands
>> 'mysqldump' to backup the vpopmail database and to restore it again
>> with 'mysql -u xxx -pyyy vpopmail < db' yields a corrupt database. How
>> is this possible? Certainly a backup/restore doesn't rehash passwords
>> using the clear text field. It should simply restore exactly what's
>> backed up. Is this thinking erroneous???
>>
>> Eric
>>
>>
>> On 10/2/2018 12:09 PM, Dan McAllister - QMT DNS wrote:
>>> I hear ya Andrew! I have a very large QMT that hosts hundreds of
>>> domains. One of those tenants knows that this is a QMT install, and
>>> wanted to have access to the vqadmin program -- which WOULD have
>>> given them visibility to other domains' passwords -- but I deny
>>> access to that tool to anyone (I don't even use it)... they CAN use
>>> the admin role with the standard qmailadmin interface, because that
>>> is limited to one domain at a time.
>>>
>>> I have a list of "superadmins" for that system that have access to
>>> the user passwords through the shell "vuserinfo" command -- and you
>>> have to be elevated (root) to run that, so anyone breaking in
>>> (hacking) the website (apache user), or qmail (qmail, qmaill, or
>>> qmailq users) or even vpopmail (vpopmail user) will NOT be able to
>>> run that command.
>>>
>>> I also CHANGE the default passwords for the MySQL database... so if
>>> you CAN break in, you CANNOT just query the database (because the
>>> vpopmail password is well known).
>>>
>>> So that's been my way to deal with it... your mileage may vary 😊
>>>
>>> Dan
>>>
>>>
>>> -Original Message-
>>> From: Andrew Swartz 
>>> Sent: Tuesday, October 2, 2018 11:24 AM
>>> To: qmailtoaster-list@qmailtoaster.com
>>> Subject: Re: Fwd: Re: [qmailtoaster] centos 6
>>>
>>> Dan,
>>>
>>> Excellent explanation. Thank you.
>>>
>>> It explains something which I did not report in my email:  I solved this
>>> by trying only the first 16 characters of the long passwords, and sure
>>> enough they validated.  I did not put enough thought into it to realize
>>> that the hashes had been regenerated from the shortened passwords.
>>>
>>> This explanation implies that the problem is that the restore script
>>> generates new hashes from the [stored] cleartext passwords.  Seems like
>>> an easy fix would be to just backup/restore the hashes instead of
>>> generating new hashes.
>>>
>>> QUESTIONS:
>>> 1. What is the format of the stored hash?  Looks like concatenation of
>>> two [atypical] base64 fields.
>>>
>>> 2. How difficult would it be to remove the cleartext passwords from
>>> vpopmail?  I see the logic of storing the "hint".  But it means that for
>>> systems with multiple admins, all of the admins can view (and therefore
>>> use) most users' passwords.  That is problematic e

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

No problem, Tony. I understood.

I know that corruption can happen, which is an inevitable result of the 
software world, but using the standard MySQL/MariaDB tools doesn't 
(generally) invite it, IMHO. That is, an encrypted password (a text, 
CHAR, field) will remain the same, barring aforementioned corruption, 
across databases and their fields on migration.



On 10/2/2018 4:49 PM, Tony White wrote:

Hi Eric,
  Sorry, I made it sound like you had the issue. I know it was not you.

best wishes
   Tony White

On 03/10/18 07:50, Eric Broch wrote:

Okay,

It seems odd, to me at least, that using the mysql/mariadb commands 
'mysqldump' to backup the vpopmail database and to restore it again 
with 'mysql -u xxx -pyyy vpopmail < db' yields a corrupt database. 
How is this possible? Certainly a backup/restore doesn't rehash 
passwords using the clear text field. It should simply restore 
exactly what's backed up. Is this thinking erroneous???


Eric


On 10/2/2018 12:09 PM, Dan McAllister - QMT DNS wrote:
I hear ya Andrew! I have a very large QMT that hosts hundreds of 
domains. One of those tenants knows that this is a QMT install, and 
wanted to have access to the vqadmin program -- which WOULD have 
given them visibility to other domains' passwords -- but I deny 
access to that tool to anyone (I don't even use it)... they CAN use 
the admin role with the standard qmailadmin interface, because that 
is limited to one domain at a time.


I have a list of "superadmins" for that system that have access to 
the user passwords through the shell "vuserinfo" command -- and you 
have to be elevated (root) to run that, so anyone breaking in 
(hacking) the website (apache user), or qmail (qmail, qmaill, or 
qmailq users) or even vpopmail (vpopmail user) will NOT be able to 
run that command.


I also CHANGE the default passwords for the MySQL database... so if 
you CAN break in, you CANNOT just query the database (because the 
vpopmail password is well known).


So that's been my way to deal with it... your mileage may vary 😊

Dan


-Original Message-
From: Andrew Swartz 
Sent: Tuesday, October 2, 2018 11:24 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved 
this

by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords. Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that 
for

systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext 
passwords?


-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:
I know I'm "Johnny-come-lately" on this topic, but I can explain 
the results you're seeing and have seen the same myself:


The QMT vpopmail default setup saves the hashed password, as well 
as the first 16-characters of the clear-text password, in the MySQL 
database. That has already been established. What you probably 
don't know (or didn't think of) is how those fields are used!


Consider the following:
  - First, the length of the hashing algorithm is a fixed length. 
Different hashes, different lengths (for example: MD5 hashes are 
always 32 characters, SHA1 hashes have 40 characters, sha512 hashes 
128, and so on...)
  - Second, ONLY the hashed password is used for validation. There 
is no NEED for the cleartext password in the database, it's there 
simply because the MySQL database was considered somewhat secure, 
and the original developers of the QMT realized that about 40% of 
user problems are caused by NOT KNOWING THEIR PASSWORDS, and being 
able to GIVE them their existing password was generally easier than 
resetting it (and hearing complaints that, although you "fixed" 
their desktop mail, now their phone's weren't getting email!)
  - Finally, the original designers 

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Hi Eric,
  Sorry, I made it sound like you had the issue. I know it was not you.

best wishes
  Tony White

On 03/10/18 07:50, Eric Broch wrote:


Okay,

It seems odd, to me at least, that using the mysql/mariadb commands 'mysqldump' to backup the vpopmail database and to 
restore it again with 'mysql -u xxx -pyyy vpopmail < db' yields a corrupt database. How is this possible? Certainly a 
backup/restore doesn't rehash passwords using the clear text field. It should simply restore exactly what's backed up. Is 
this thinking erroneous???


Eric


On 10/2/2018 12:09 PM, Dan McAllister - QMT DNS wrote:
I hear ya Andrew! I have a very large QMT that hosts hundreds of domains. One of those tenants knows that this is a QMT 
install, and wanted to have access to the vqadmin program -- which WOULD have given them visibility to other domains' 
passwords -- but I deny access to that tool to anyone (I don't even use it)... they CAN use the admin role with the 
standard qmailadmin interface, because that is limited to one domain at a time.


I have a list of "superadmins" for that system that have access to the user passwords through the shell "vuserinfo" 
command -- and you have to be elevated (root) to run that, so anyone breaking in (hacking) the website (apache user), or 
qmail (qmail, qmaill, or qmailq users) or even vpopmail (vpopmail user) will NOT be able to run that command.


I also CHANGE the default passwords for the MySQL database... so if you CAN break in, you CANNOT just query the database 
(because the vpopmail password is well known).


So that's been my way to deal with it... your mileage may vary 😊

Dan


-Original Message-
From: Andrew Swartz 
Sent: Tuesday, October 2, 2018 11:24 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved this
by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords. Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that for
systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext passwords?

-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:

I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
you're seeing and have seen the same myself:

The QMT vpopmail default setup saves the hashed password, as well as the first 16-characters of the clear-text 
password, in the MySQL database. That has already been established. What you probably don't know (or didn't think of) 
is how those fields are used!


Consider the following:
  - First, the length of the hashing algorithm is a fixed length. Different hashes, different lengths (for example: MD5 
hashes are always 32 characters, SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
  - Second, ONLY the hashed password is used for validation. There is no NEED for the cleartext password in the 
database, it's there simply because the MySQL database was considered somewhat secure, and the original developers of 
the QMT realized that about 40% of user problems are caused by NOT KNOWING THEIR PASSWORDS, and being able to GIVE them 
their existing password was generally easier than resetting it (and hearing complaints that, although you "fixed" their 
desktop mail, now their phone's weren't getting email!)
  - Finally, the original designers of QMT assumed people would use long passwords -- it was suggested in the original 
documentation. Thus, saving only the first 16 characters of the password in cleartext meant you were only REALLY saving 
a "password hint" vs. the entire password.


So - when you enter a 75 character password (only slightly absurd these days), and if we assume a sha1 password hash, 
then the "set password" function hashes your 75

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Hi Eric,
  Having just done this for my migration from COS 5 to 6 I have not come across 
this problem.
I have just verified a few accounts using vuserinfo and comparing the results 
between the old server
and new and they are identical.
  Is it possible you had old_passwords set on the old server and not on the new?

best wishes
  Tony White

On 03/10/18 07:50, Eric Broch wrote:


Okay,

It seems odd, to me at least, that using the mysql/mariadb commands 'mysqldump' to backup the vpopmail database and to 
restore it again with 'mysql -u xxx -pyyy vpopmail < db' yields a corrupt database. How is this possible? Certainly a 
backup/restore doesn't rehash passwords using the clear text field. It should simply restore exactly what's backed up. Is 
this thinking erroneous???


Eric


On 10/2/2018 12:09 PM, Dan McAllister - QMT DNS wrote:
I hear ya Andrew! I have a very large QMT that hosts hundreds of domains. One of those tenants knows that this is a QMT 
install, and wanted to have access to the vqadmin program -- which WOULD have given them visibility to other domains' 
passwords -- but I deny access to that tool to anyone (I don't even use it)... they CAN use the admin role with the 
standard qmailadmin interface, because that is limited to one domain at a time.


I have a list of "superadmins" for that system that have access to the user passwords through the shell "vuserinfo" 
command -- and you have to be elevated (root) to run that, so anyone breaking in (hacking) the website (apache user), or 
qmail (qmail, qmaill, or qmailq users) or even vpopmail (vpopmail user) will NOT be able to run that command.


I also CHANGE the default passwords for the MySQL database... so if you CAN break in, you CANNOT just query the database 
(because the vpopmail password is well known).


So that's been my way to deal with it... your mileage may vary 😊

Dan


-Original Message-
From: Andrew Swartz 
Sent: Tuesday, October 2, 2018 11:24 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved this
by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords. Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that for
systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext passwords?

-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:

I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
you're seeing and have seen the same myself:

The QMT vpopmail default setup saves the hashed password, as well as the first 16-characters of the clear-text 
password, in the MySQL database. That has already been established. What you probably don't know (or didn't think of) 
is how those fields are used!


Consider the following:
  - First, the length of the hashing algorithm is a fixed length. Different hashes, different lengths (for example: MD5 
hashes are always 32 characters, SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
  - Second, ONLY the hashed password is used for validation. There is no NEED for the cleartext password in the 
database, it's there simply because the MySQL database was considered somewhat secure, and the original developers of 
the QMT realized that about 40% of user problems are caused by NOT KNOWING THEIR PASSWORDS, and being able to GIVE them 
their existing password was generally easier than resetting it (and hearing complaints that, although you "fixed" their 
desktop mail, now their phone's weren't getting email!)
  - Finally, the original designers of QMT assumed people would use long passwords -- it was suggested in the original 
documentation. Thus, saving only the first 16 characters of the password in cleartext meant you were only REALL

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

Okay,

It seems odd, to me at least, that using the mysql/mariadb commands 
'mysqldump' to backup the vpopmail database and to restore it again with 
'mysql -u xxx -pyyy vpopmail < db' yields a corrupt database. How is 
this possible? Certainly a backup/restore doesn't rehash passwords using 
the clear text field. It should simply restore exactly what's backed up. 
Is this thinking erroneous???


Eric


On 10/2/2018 12:09 PM, Dan McAllister - QMT DNS wrote:

I hear ya Andrew! I have a very large QMT that hosts hundreds of domains. One 
of those tenants knows that this is a QMT install, and wanted to have access to 
the vqadmin program -- which WOULD have given them visibility to other domains' 
passwords -- but I deny access to that tool to anyone (I don't even use it)... 
they CAN use the admin role with the standard qmailadmin interface, because 
that is limited to one domain at a time.

I have a list of "superadmins" for that system that have access to the user passwords 
through the shell "vuserinfo" command -- and you have to be elevated (root) to run that, 
so anyone breaking in (hacking) the website (apache user), or qmail (qmail, qmaill, or qmailq 
users) or even vpopmail (vpopmail user) will NOT be able to run that command.

I also CHANGE the default passwords for the MySQL database... so if you CAN 
break in, you CANNOT just query the database (because the vpopmail password is 
well known).

So that's been my way to deal with it... your mileage may vary 😊

Dan


-Original Message-
From: Andrew Swartz 
Sent: Tuesday, October 2, 2018 11:24 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved this
by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords.  Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that for
systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext passwords?

-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:

I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
you're seeing and have seen the same myself:

The QMT vpopmail default setup saves the hashed password, as well as the first 
16-characters of the clear-text password, in the MySQL database. That has 
already been established. What you probably don't know (or didn't think of) is 
how those fields are used!

Consider the following:
  - First, the length of the hashing algorithm is a fixed length. Different 
hashes, different lengths (for example: MD5 hashes are always 32 characters, 
SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
  - Second, ONLY the hashed password is used for validation. There is no NEED for the 
cleartext password in the database, it's there simply because the MySQL database was 
considered somewhat secure, and the original developers of the QMT realized that about 
40% of user problems are caused by NOT KNOWING THEIR PASSWORDS, and being able to GIVE 
them their existing password was generally easier than resetting it (and hearing 
complaints that, although you "fixed" their desktop mail, now their phone's 
weren't getting email!)
  - Finally, the original designers of QMT assumed people would use long passwords -- it 
was suggested in the original documentation. Thus, saving only the first 16 characters of 
the password in cleartext meant you were only REALLY saving a "password hint" 
vs. the entire password.

So - when you enter a 75 character password (only slightly absurd these days), and if we assume a 
sha1 password hash, then the "set password" function hashes your 75 characters into a 
40-character SHA1 hash and saves it into the database field that stores up to (magically) 40 
characters. (FWIW: when you 

RE: Fwd: Re: [qmailtoaster] centos 6

[Dan McAllister - QMT DNS]

I hear ya Andrew! I have a very large QMT that hosts hundreds of domains. One 
of those tenants knows that this is a QMT install, and wanted to have access to 
the vqadmin program -- which WOULD have given them visibility to other domains' 
passwords -- but I deny access to that tool to anyone (I don't even use it)... 
they CAN use the admin role with the standard qmailadmin interface, because 
that is limited to one domain at a time.

I have a list of "superadmins" for that system that have access to the user 
passwords through the shell "vuserinfo" command -- and you have to be elevated 
(root) to run that, so anyone breaking in (hacking) the website (apache user), 
or qmail (qmail, qmaill, or qmailq users) or even vpopmail (vpopmail user) will 
NOT be able to run that command.

I also CHANGE the default passwords for the MySQL database... so if you CAN 
break in, you CANNOT just query the database (because the vpopmail password is 
well known).

So that's been my way to deal with it... your mileage may vary 😊

Dan


-Original Message-
From: Andrew Swartz  
Sent: Tuesday, October 2, 2018 11:24 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved this
by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords.  Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that for
systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext passwords?

-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:
> I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
> you're seeing and have seen the same myself:
> 
> The QMT vpopmail default setup saves the hashed password, as well as the 
> first 16-characters of the clear-text password, in the MySQL database. That 
> has already been established. What you probably don't know (or didn't think 
> of) is how those fields are used!
> 
> Consider the following:
>  - First, the length of the hashing algorithm is a fixed length. Different 
> hashes, different lengths (for example: MD5 hashes are always 32 characters, 
> SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
>  - Second, ONLY the hashed password is used for validation. There is no NEED 
> for the cleartext password in the database, it's there simply because the 
> MySQL database was considered somewhat secure, and the original developers of 
> the QMT realized that about 40% of user problems are caused by NOT KNOWING 
> THEIR PASSWORDS, and being able to GIVE them their existing password was 
> generally easier than resetting it (and hearing complaints that, although you 
> "fixed" their desktop mail, now their phone's weren't getting email!)
>  - Finally, the original designers of QMT assumed people would use long 
> passwords -- it was suggested in the original documentation. Thus, saving 
> only the first 16 characters of the password in cleartext meant you were only 
> REALLY saving a "password hint" vs. the entire password.
> 
> So - when you enter a 75 character password (only slightly absurd these 
> days), and if we assume a sha1 password hash, then the "set password" 
> function hashes your 75 characters into a 40-character SHA1 hash and saves it 
> into the database field that stores up to (magically) 40 characters. (FWIW: 
> when you enter your 2-character password of "ok", the sha1 algorithm ALSO 
> generates a 40 character output!). After is stores the hashed password, it 
> ALSO stores the first 16 characters of the cleartext password -- because 
> that's the length of the field in the database.
> 
> When you try to authenticate, the passwo

Re: Fwd: Re: [qmailtoaster] centos 6

[Andrew Swartz]

Dan,

Excellent explanation. Thank you.

It explains something which I did not report in my email:  I solved this
by trying only the first 16 characters of the long passwords, and sure
enough they validated.  I did not put enough thought into it to realize
that the hashes had been regenerated from the shortened passwords.

This explanation implies that the problem is that the restore script
generates new hashes from the [stored] cleartext passwords.  Seems like
an easy fix would be to just backup/restore the hashes instead of
generating new hashes.

QUESTIONS:
1. What is the format of the stored hash?  Looks like concatenation of
two [atypical] base64 fields.

2. How difficult would it be to remove the cleartext passwords from
vpopmail?  I see the logic of storing the "hint".  But it means that for
systems with multiple admins, all of the admins can view (and therefore
use) most users' passwords.  That is problematic even without
considering the foreign intruder risk.

My security concern for QMT has always been that I've never trusted the
qmail accessories as much as qmail itself.  I remain fairly confident
that an intruder will not enter via port 25 (i.e. through qmail).  But
running the web server (for webmail) markedly increases the risk.

QUESTION: could a webserver SQL-injection retrieve the cleartext passwords?

-Andy



On 10/2/2018 5:02 AM, Dan McAllister - QMT DNS wrote:
> I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
> you're seeing and have seen the same myself:
> 
> The QMT vpopmail default setup saves the hashed password, as well as the 
> first 16-characters of the clear-text password, in the MySQL database. That 
> has already been established. What you probably don't know (or didn't think 
> of) is how those fields are used!
> 
> Consider the following:
>  - First, the length of the hashing algorithm is a fixed length. Different 
> hashes, different lengths (for example: MD5 hashes are always 32 characters, 
> SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
>  - Second, ONLY the hashed password is used for validation. There is no NEED 
> for the cleartext password in the database, it's there simply because the 
> MySQL database was considered somewhat secure, and the original developers of 
> the QMT realized that about 40% of user problems are caused by NOT KNOWING 
> THEIR PASSWORDS, and being able to GIVE them their existing password was 
> generally easier than resetting it (and hearing complaints that, although you 
> "fixed" their desktop mail, now their phone's weren't getting email!)
>  - Finally, the original designers of QMT assumed people would use long 
> passwords -- it was suggested in the original documentation. Thus, saving 
> only the first 16 characters of the password in cleartext meant you were only 
> REALLY saving a "password hint" vs. the entire password.
> 
> So - when you enter a 75 character password (only slightly absurd these 
> days), and if we assume a sha1 password hash, then the "set password" 
> function hashes your 75 characters into a 40-character SHA1 hash and saves it 
> into the database field that stores up to (magically) 40 characters. (FWIW: 
> when you enter your 2-character password of "ok", the sha1 algorithm ALSO 
> generates a 40 character output!). After is stores the hashed password, it 
> ALSO stores the first 16 characters of the cleartext password -- because 
> that's the length of the field in the database.
> 
> When you try to authenticate, the password you provided is re-hashed 
> (regardless of its length -- although usually those fields have 64, 72, or 
> 128 character field limits - depending on the web-page designer/programmer), 
> and those 40 characters (the output of the sha1 hash) are compared to your 
> stored hash... there is no query of the cleartext password.
> 
> Unfortunately, when you attempt to restore your passwords using just the 
> stored cleartext passwords, you will find (not surprisingly) that passwords 
> that were longer than the 16 chars generate a totally different hash result! 
> (Interesting side-note: you could have told your users that their passwords 
> were unchanged, but that they had to stop after the 16th character -- and it 
> would have worked!)
> 
> I hope this explains a few things!!
> 
> Dan
> 
> 
> IT4SOHO, LLC
> 33 4th St N; STE 211
> St. Petersburg, FL 33701
> +1-877-IT4SOHO
> +1-877-484-7646
> For service requests, direct your email to serv...@it4soho.com
> 
> 
> 
> -Original Message-
> From: Eric Broch  
> Sent: Friday, September 28, 2018 1:35 AM
> To: qmailtoaster-list@qmailtoaster.com
> Subject: Re: Fwd: Re: [qmailtoaster] centos 

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

Thanks, Dan.


On 10/2/2018 7:02 AM, Dan McAllister - QMT DNS wrote:

I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
you're seeing and have seen the same myself:

The QMT vpopmail default setup saves the hashed password, as well as the first 
16-characters of the clear-text password, in the MySQL database. That has 
already been established. What you probably don't know (or didn't think of) is 
how those fields are used!

Consider the following:
  - First, the length of the hashing algorithm is a fixed length. Different 
hashes, different lengths (for example: MD5 hashes are always 32 characters, 
SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
  - Second, ONLY the hashed password is used for validation. There is no NEED for the 
cleartext password in the database, it's there simply because the MySQL database was 
considered somewhat secure, and the original developers of the QMT realized that about 
40% of user problems are caused by NOT KNOWING THEIR PASSWORDS, and being able to GIVE 
them their existing password was generally easier than resetting it (and hearing 
complaints that, although you "fixed" their desktop mail, now their phone's 
weren't getting email!)
  - Finally, the original designers of QMT assumed people would use long passwords -- it 
was suggested in the original documentation. Thus, saving only the first 16 characters of 
the password in cleartext meant you were only REALLY saving a "password hint" 
vs. the entire password.

So - when you enter a 75 character password (only slightly absurd these days), and if we assume a 
sha1 password hash, then the "set password" function hashes your 75 characters into a 
40-character SHA1 hash and saves it into the database field that stores up to (magically) 40 
characters. (FWIW: when you enter your 2-character password of "ok", the sha1 algorithm 
ALSO generates a 40 character output!). After is stores the hashed password, it ALSO stores the 
first 16 characters of the cleartext password -- because that's the length of the field in the 
database.

When you try to authenticate, the password you provided is re-hashed 
(regardless of its length -- although usually those fields have 64, 72, or 128 
character field limits - depending on the web-page designer/programmer), and 
those 40 characters (the output of the sha1 hash) are compared to your stored 
hash... there is no query of the cleartext password.

Unfortunately, when you attempt to restore your passwords using just the stored 
cleartext passwords, you will find (not surprisingly) that passwords that were 
longer than the 16 chars generate a totally different hash result! (Interesting 
side-note: you could have told your users that their passwords were unchanged, 
but that they had to stop after the 16th character -- and it would have worked!)

I hope this explains a few things!!

Dan


IT4SOHO, LLC
33 4th St N; STE 211
St. Petersburg, FL 33701
+1-877-IT4SOHO
+1-877-484-7646
For service requests, direct your email to serv...@it4soho.com



-Original Message-
From: Eric Broch 
Sent: Friday, September 28, 2018 1:35 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Thanks, Andy. Plain text password have been a part of qt for as long as I've 
been using it. I understand you're concern. I'm not sure about the password 
length issue, I don't remember ever changing (patching) vpopmail like that, but 
I'll look into it.


On 9/27/2018 11:28 PM, Andrew Swartz wrote:

I recently did the backup/restore and I have one hiccup to report.

A few of the account passwords did not work after backup from centos5
and restore to centos7.

Took some time to troubleshoot, but I poked around in the vpopmail
database and figured it out.  It was due to the vpopmail database
schema, which stores a 16 character password AND its hash.  It allowed
[and worked with] passwords longer than 16 characters (I'm unsure how).
But after the backup/restore, all passwords longer than 16 characters
failed.  Problem was fixed by resetting all of these passwords to new
ones with the proper length.  Luckily there were not many like this.
But for a large system, this could be a major pain.

This seems like a bug.  If the max password length is 16 characters,
then the set-password webpage should reject passwords that are too long.

Also, I'm not sure why it stores a plaintext password in addition to
its hash.  The modern standard is to store only the hash.  This is
potentially a major security problem.

-Andy


On 9/27/2018 8:57 PM, Tony White wrote:

Eric,
I now have a working v6 COS qmt, thank you for you help an patience.
Now the backup and restore...

best wishes
Tony White

On 28/09/18 14:43, Eric Broch wrote:


changed now


On 9/27/2018 10:41 PM, Tony White wrote:

Eric,
Yes I did run that command.

RE: Fwd: Re: [qmailtoaster] centos 6

[Dan McAllister - QMT DNS]

I know I'm "Johnny-come-lately" on this topic, but I can explain the results 
you're seeing and have seen the same myself:

The QMT vpopmail default setup saves the hashed password, as well as the first 
16-characters of the clear-text password, in the MySQL database. That has 
already been established. What you probably don't know (or didn't think of) is 
how those fields are used!

Consider the following:
 - First, the length of the hashing algorithm is a fixed length. Different 
hashes, different lengths (for example: MD5 hashes are always 32 characters, 
SHA1 hashes have 40 characters, sha512 hashes 128, and so on...)
 - Second, ONLY the hashed password is used for validation. There is no NEED 
for the cleartext password in the database, it's there simply because the MySQL 
database was considered somewhat secure, and the original developers of the QMT 
realized that about 40% of user problems are caused by NOT KNOWING THEIR 
PASSWORDS, and being able to GIVE them their existing password was generally 
easier than resetting it (and hearing complaints that, although you "fixed" 
their desktop mail, now their phone's weren't getting email!)
 - Finally, the original designers of QMT assumed people would use long 
passwords -- it was suggested in the original documentation. Thus, saving only 
the first 16 characters of the password in cleartext meant you were only REALLY 
saving a "password hint" vs. the entire password.

So - when you enter a 75 character password (only slightly absurd these days), 
and if we assume a sha1 password hash, then the "set password" function hashes 
your 75 characters into a 40-character SHA1 hash and saves it into the database 
field that stores up to (magically) 40 characters. (FWIW: when you enter your 
2-character password of "ok", the sha1 algorithm ALSO generates a 40 character 
output!). After is stores the hashed password, it ALSO stores the first 16 
characters of the cleartext password -- because that's the length of the field 
in the database.

When you try to authenticate, the password you provided is re-hashed 
(regardless of its length -- although usually those fields have 64, 72, or 128 
character field limits - depending on the web-page designer/programmer), and 
those 40 characters (the output of the sha1 hash) are compared to your stored 
hash... there is no query of the cleartext password.

Unfortunately, when you attempt to restore your passwords using just the stored 
cleartext passwords, you will find (not surprisingly) that passwords that were 
longer than the 16 chars generate a totally different hash result! (Interesting 
side-note: you could have told your users that their passwords were unchanged, 
but that they had to stop after the 16th character -- and it would have worked!)

I hope this explains a few things!!

Dan


IT4SOHO, LLC
33 4th St N; STE 211
St. Petersburg, FL 33701
+1-877-IT4SOHO
+1-877-484-7646
For service requests, direct your email to serv...@it4soho.com



-Original Message-
From: Eric Broch 
Sent: Friday, September 28, 2018 1:35 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: Fwd: Re: [qmailtoaster] centos 6

Thanks, Andy. Plain text password have been a part of qt for as long as I've 
been using it. I understand you're concern. I'm not sure about the password 
length issue, I don't remember ever changing (patching) vpopmail like that, but 
I'll look into it.


On 9/27/2018 11:28 PM, Andrew Swartz wrote:
> I recently did the backup/restore and I have one hiccup to report.
>
> A few of the account passwords did not work after backup from centos5
> and restore to centos7.
>
> Took some time to troubleshoot, but I poked around in the vpopmail
> database and figured it out.  It was due to the vpopmail database
> schema, which stores a 16 character password AND its hash.  It allowed
> [and worked with] passwords longer than 16 characters (I'm unsure how).
> But after the backup/restore, all passwords longer than 16 characters
> failed.  Problem was fixed by resetting all of these passwords to new
> ones with the proper length.  Luckily there were not many like this.
> But for a large system, this could be a major pain.
>
> This seems like a bug.  If the max password length is 16 characters,
> then the set-password webpage should reject passwords that are too long.
>
> Also, I'm not sure why it stores a plaintext password in addition to
> its hash.  The modern standard is to store only the hash.  This is
> potentially a major security problem.
>
> -Andy
>
>
> On 9/27/2018 8:57 PM, Tony White wrote:
>> Eric,
>>I now have a working v6 COS qmt, thank you for you help an patience.
>> Now the backup and restore...
>>
>> best wishes
>>Tony White
>>
>> On 28/09/18 14:43, Eric 

Re: [qmailtoaster] centos 6

[remo]

I always had clear password but I know that it is possible to remove the clear 
password flag from vpopmail and password will show encrypted only. 

As far as password you could use the learn password with pop3 and the first 
time the user logs in it sets the password. 

Remo

> Il giorno 27 set 2018, alle ore 22:35, Eric Broch  
> ha scritto:
> 
> Thanks, Andy. Plain text password have been a part of qt for as long as I've 
> been using it. I understand you're concern. I'm not sure about the password 
> length issue, I don't remember ever changing (patching) vpopmail like that, 
> but I'll look into it.
> 
> 
>> On 9/27/2018 11:28 PM, Andrew Swartz wrote:
>> I recently did the backup/restore and I have one hiccup to report.
>> 
>> A few of the account passwords did not work after backup from centos5
>> and restore to centos7.
>> 
>> Took some time to troubleshoot, but I poked around in the vpopmail
>> database and figured it out.  It was due to the vpopmail database
>> schema, which stores a 16 character password AND its hash.  It allowed
>> [and worked with] passwords longer than 16 characters (I'm unsure how).
>> But after the backup/restore, all passwords longer than 16 characters
>> failed.  Problem was fixed by resetting all of these passwords to new
>> ones with the proper length.  Luckily there were not many like this.
>> But for a large system, this could be a major pain.
>> 
>> This seems like a bug.  If the max password length is 16 characters,
>> then the set-password webpage should reject passwords that are too long.
>> 
>> Also, I'm not sure why it stores a plaintext password in addition to its
>> hash.  The modern standard is to store only the hash.  This is
>> potentially a major security problem.
>> 
>> -Andy
>> 
>> 
>>> On 9/27/2018 8:57 PM, Tony White wrote:
>>> Eric,
>>>   I now have a working v6 COS qmt, thank you for you help an patience.
>>> Now the backup and restore...
>>> 
>>> best wishes
>>>   Tony White
>>> 
 On 28/09/18 14:43, Eric Broch wrote:
 
 changed now
 
 
> On 9/27/2018 10:41 PM, Tony White wrote:
> Eric,
>   Yes I did run that command.
> 
>   At stage 3 after manually starting qmail at the end of qt-install.
> 
> Stage 3
> 
> rpm -Uvh
> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm
> needs to be
> 
> rpm -Uvh
> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm
> 
> 
> best wishes
>   Tony White
> 
>  ..  ..  ..
> | .--. || .--. || .--. |
> | |      | || | __   | || |___   | |
> | | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
> | |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
> | |\ \/ /| || |  | | | || |   '.___`-.   | |
> | |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
> | |   |__|   | || |   `._.'  | || |  |___.'  | |
> | |  | || |  | || |  | |
> | '--' || '--' || '--' |
>  ''  ''  ''
> 
> http://www.ycs.com.au
> 4 The Crescent
> Yea
> Victoria
> Australia 3717
> 
> Telephone No's
> VIC : 0418 515 717
> 
> Please note: YCS records all calls to better serve you.
> 
> IMPORTANT NOTICE
> 
> This communication including any file attachments is intended solely for
> the use of the individual or entity to whom it is addressed. If you are
> not the intended recipient, or the person responsible for delivering
> this communication to the intended recipient, please immediately notify
> the sender by email and delete the original transmission and its
> contents. Any unauthorised use, dissemination, forwarding, printing or
> copying of this communication including file attachments is prohibited.
> It is your responsibility to scan this communication including any file
> attachments for viruses and other defects. To the extent permitted by
> law, Yea Computing Services and its associates will not be liable for
> any loss or damage arising in any way from this communication including
> any file attachments.
> You may not disclose this information to a third party without written
> permission from the Author.
>> On 28/09/18 14:14, Eric Broch wrote:
>> Excellent!!! Glad to hear it.
>> 
>> 
>>> On 9/27/2018 10:03 PM, Tony White wrote:
>>> Eric,
>>>   Sorry I did not intend to email offlist.
>>> I did a reply to sender not the list.
>>> Apologies.
>>> 
>>> I have reset the VM to give me a blank minimal install again.
>>> It has just finished qt-bootstrp-2 without error.
>>> So far so good.
>>> 
>

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

Thanks, Andy. Plain text password have been a part of qt for as long as 
I've been using it. I understand you're concern. I'm not sure about the 
password length issue, I don't remember ever changing (patching) 
vpopmail like that, but I'll look into it.



On 9/27/2018 11:28 PM, Andrew Swartz wrote:

I recently did the backup/restore and I have one hiccup to report.

A few of the account passwords did not work after backup from centos5
and restore to centos7.

Took some time to troubleshoot, but I poked around in the vpopmail
database and figured it out.  It was due to the vpopmail database
schema, which stores a 16 character password AND its hash.  It allowed
[and worked with] passwords longer than 16 characters (I'm unsure how).
But after the backup/restore, all passwords longer than 16 characters
failed.  Problem was fixed by resetting all of these passwords to new
ones with the proper length.  Luckily there were not many like this.
But for a large system, this could be a major pain.

This seems like a bug.  If the max password length is 16 characters,
then the set-password webpage should reject passwords that are too long.

Also, I'm not sure why it stores a plaintext password in addition to its
hash.  The modern standard is to store only the hash.  This is
potentially a major security problem.

-Andy


On 9/27/2018 8:57 PM, Tony White wrote:

Eric,
   I now have a working v6 COS qmt, thank you for you help an patience.
Now the backup and restore...

best wishes
   Tony White

On 28/09/18 14:43, Eric Broch wrote:


changed now


On 9/27/2018 10:41 PM, Tony White wrote:

Eric,
   Yes I did run that command.

   At stage 3 after manually starting qmail at the end of qt-install.

Stage 3

rpm -Uvh
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm
needs to be

rpm -Uvh
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm


best wishes
   Tony White

  ..  ..  ..
| .--. || .--. || .--. |
| |      | || | __   | || |___   | |
| | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
| |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
| |\ \/ /| || |  | | | || |   '.___`-.   | |
| |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
| |   |__|   | || |   `._.'  | || |  |___.'  | |
| |  | || |  | || |  | |
| '--' || '--' || '--' |
  ''  ''  ''

http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 0418 515 717

Please note: YCS records all calls to better serve you.

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.
On 28/09/18 14:14, Eric Broch wrote:

Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
   Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:

Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap
scripts, my bootstrap's (below in red and green) do not use
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'

Irritatingly, this is because all the mirror maintainers dropped
the ball and didn't bother to let anyone know that they weren't
supporting QMT anymore. If this is a pre-existing machine disable
the qmailtoaster-current repo:

# yum install yum-utils && yum-config-manager --disable
qmailtoaster-current qmailtoaster-current-nodist



#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux,
update everything)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
###

Re: Fwd: Re: [qmailtoaster] centos 6

[Andrew Swartz]

I recently did the backup/restore and I have one hiccup to report.

A few of the account passwords did not work after backup from centos5
and restore to centos7.

Took some time to troubleshoot, but I poked around in the vpopmail
database and figured it out.  It was due to the vpopmail database
schema, which stores a 16 character password AND its hash.  It allowed
[and worked with] passwords longer than 16 characters (I'm unsure how).
But after the backup/restore, all passwords longer than 16 characters
failed.  Problem was fixed by resetting all of these passwords to new
ones with the proper length.  Luckily there were not many like this.
But for a large system, this could be a major pain.

This seems like a bug.  If the max password length is 16 characters,
then the set-password webpage should reject passwords that are too long.

Also, I'm not sure why it stores a plaintext password in addition to its
hash.  The modern standard is to store only the hash.  This is
potentially a major security problem.

-Andy


On 9/27/2018 8:57 PM, Tony White wrote:
> Eric,
>   I now have a working v6 COS qmt, thank you for you help an patience.
> Now the backup and restore...
> 
> best wishes
>   Tony White
> 
> On 28/09/18 14:43, Eric Broch wrote:
> 
>> changed now
>>
>>
>> On 9/27/2018 10:41 PM, Tony White wrote:
>>> Eric,
>>>   Yes I did run that command.
>>>
>>>   At stage 3 after manually starting qmail at the end of qt-install.
>>>
>>> Stage 3
>>>
>>> rpm -Uvh
>>> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm
>>> needs to be
>>>
>>> rpm -Uvh
>>> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm
>>>
>>>
>>> best wishes
>>>   Tony White
>>>
>>>  ..  ..  .. 
>>> | .--. || .--. || .--. |
>>> | |      | || | __   | || |___   | |
>>> | | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
>>> | |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
>>> | |\ \/ /| || |  | | | || |   '.___`-.   | |
>>> | |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
>>> | |   |__|   | || |   `._.'  | || |  |___.'  | |
>>> | |  | || |  | || |  | |
>>> | '--' || '--' || '--' |
>>>  ''  ''  '' 
>>>
>>> http://www.ycs.com.au
>>> 4 The Crescent
>>> Yea
>>> Victoria
>>> Australia 3717
>>>
>>> Telephone No's
>>> VIC : 0418 515 717
>>>
>>> Please note: YCS records all calls to better serve you.
>>>
>>> IMPORTANT NOTICE
>>>
>>> This communication including any file attachments is intended solely for
>>> the use of the individual or entity to whom it is addressed. If you are
>>> not the intended recipient, or the person responsible for delivering
>>> this communication to the intended recipient, please immediately notify
>>> the sender by email and delete the original transmission and its
>>> contents. Any unauthorised use, dissemination, forwarding, printing or
>>> copying of this communication including file attachments is prohibited.
>>> It is your responsibility to scan this communication including any file
>>> attachments for viruses and other defects. To the extent permitted by
>>> law, Yea Computing Services and its associates will not be liable for 
>>> any loss or damage arising in any way from this communication including
>>> any file attachments.
>>> You may not disclose this information to a third party without written
>>> permission from the Author.
>>> On 28/09/18 14:14, Eric Broch wrote:

 Excellent!!! Glad to hear it.


 On 9/27/2018 10:03 PM, Tony White wrote:
> Eric,
>   Sorry I did not intend to email offlist.
> I did a reply to sender not the list.
> Apologies.
>
> I have reset the VM to give me a blank minimal install again.
> It has just finished qt-bootstrp-2 without error.
> So far so good.
>
> cheers.
>
>
> On 28/09/18 13:53, Eric Broch wrote:
>>
>> Tony, If you communicate off list you must whitelist my address
>>
>>
>> Tony,
>>
>> I think (not sure why) you're still using the wrong bootstrap
>> scripts, my bootstrap's (below in red and green) do not use
>> 'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'
>>
>> Irritatingly, this is because all the mirror maintainers dropped
>> the ball and didn't bother to let anyone know that they weren't
>> supporting QMT anymore. If this is a pre-existing machine disable
>> the qmailtoaster-current repo:
>>
>> # yum install yum-utils && yum-config-manager --disable
>> qmailtoaster-current qmailtoaster-current-nodist
>>
>> 
>>
>> #!/bin/bash
>>
>> # Copyright (C) Eric Shubert 
>> #
>> # script to do initial bootstrap processing (disable se

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Eric,
  I now have a working v6 COS qmt, thank you for you help an patience.
Now the backup and restore...

best wishes
  Tony White

On 28/09/18 14:43, Eric Broch wrote:


changed now


On 9/27/2018 10:41 PM, Tony White wrote:

Eric,
  Yes I did run that command.

  At stage 3 after manually starting qmail at the end of qt-install.

Stage 3

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm
needs to be

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm


best wishes
   Tony White

  ..  ..  ..
| .--. || .--. || .--. |
| |      | || | __   | || |___   | |
| | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
| |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
| |\ \/ /| || |  | | | || |   '.___`-.   | |
| |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
| |   |__|   | || |   `._.'  | || |  |___.'  | |
| |  | || |  | || |  | |
| '--' || '--' || '--' |
  ''  ''  ''

http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 0418 515 717

Please note: YCS records all calls to better serve you.

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.
On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap scripts, my bootstrap's (below in red and green) do not 
use 'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the ball and didn't bother to let anyone know that 
they weren't supporting QMT anymore. If this is a pre-existing machine disable the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable qmailtoaster-current 
qmailtoaster-current-nodist



#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update everything)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" $selinux_config
}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum priorities, QMT repo)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

changed now


On 9/27/2018 10:41 PM, Tony White wrote:

Eric,
  Yes I did run that command.

  At stage 3 after manually starting qmail at the end of qt-install.

Stage 3

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm

needs to be

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm



best wishes
   Tony White

  ..  ..  ..
| .--. || .--. || .--. |
| |      | || | __   | || |___   | |
| | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
| |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
| |\ \/ /| || |  | | | || |   '.___`-.   | |
| |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
| |   |__|   | || |   `._.'  | || |  |___.'  | |
| |  | || |  | || |  | |
| '--' || '--' || '--' |
  ''  ''  ''

http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 0418 515 717

Please note: YCS records all calls to better serve you.

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.
On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap 
scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped 
the ball and didn't bother to let anyone know that they weren't 
supporting QMT anymore. If this is a pre-existing machine disable 
the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, 
update everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" 
$selinux_config

}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum 
priorities, QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh 
http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg


# install 

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Eric,
  Yes I did run that command.

  At stage 3 after manually starting qmail at the end of qt-install.

Stage 3

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-5.qt.el6.noarch.rpm
needs to be

rpm -Uvh 
ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/6/current/x86_64/qmt-release-1-6.qt.el6.noarch.rpm


best wishes
  Tony White

 ..  ..  ..
| .--. || .--. || .--. |
| |      | || | __   | || |___   | |
| | |_  _||_  _| | || |   .' ___  |  | || |   /  ___  |  | |
| |   \ \  / /   | || |  / .'   \_|  | || |  |  (__ \_|  | |
| |\ \/ /| || |  | | | || |   '.___`-.   | |
| |_|  |_| || |  \ `.___.'\  | || |  |`\) |  | |
| |   |__|   | || |   `._.'  | || |  |___.'  | |
| |  | || |  | || |  | |
| '--' || '--' || '--' |
 ''  ''  ''

http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 0418 515 717

Please note: YCS records all calls to better serve you.

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap scripts, my bootstrap's (below in red and green) do not 
use 'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the ball and didn't bother to let anyone know that 
they weren't supporting QMT anymore. If this is a pre-existing machine disable the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable qmailtoaster-current 
qmailtoaster-current-nodist



#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update everything)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" $selinux_config
}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum priorities, QMT repo)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg

# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (sc

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

# qmailctl start

# qmailctl stat


On 9/27/2018 10:38 PM, Eric Broch wrote:


what's qt-install look like

did you run this command:

# curl https://www.qmailtoaster.org/qt-install 
>/opt/qmailtoaster-util/bin/qt-install



On 9/27/2018 10:24 PM, Tony White wrote:

Eric,
  ran qt-install...

Oops may have spoken too soon...

screen text:

Cleaning up...



All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


Please enter the MySQL Root Password you just created: Starting 
httpd: httpd: apr_sockaddr_info_get() failed for centos6-10
httpd: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1 for ServerName

   [ OK  ]
Starting Dovecot Imap: [ OK  ]
send: unable to open supervise/ok: file does not exist
smtp: unable to open supervise/ok: file does not exist
submission: unable to open supervise/ok: file does not exist
send/log: unable to open supervise/ok: file does not exist
smtp/log: unable to open supervise/ok: file does not exist
submission/log: unable to open supervise/ok: file does not exist


best wishes
   Tony White

On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap 
scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped 
the ball and didn't bother to let anyone know that they weren't 
supporting QMT anymore. If this is a pre-existing machine disable 
the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, 
update everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" 
$selinux_config

}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum 
priorities, QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh 
http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg


# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl 
https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && 
curl https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
105  1050  105  1050    0 0    931  0 0:00:01  0:00:01 
--:--:--  4133
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
100  1004  100  1004    0 0    890  0 0:00:01  0:00:01 
--:--:--  3968

[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base 

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

what's qt-install look like

did you run this command:

# curl https://www.qmailtoaster.org/qt-install 
>/opt/qmailtoaster-util/bin/qt-install



On 9/27/2018 10:24 PM, Tony White wrote:

Eric,
  ran qt-install...

Oops may have spoken too soon...

screen text:

Cleaning up...



All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


Please enter the MySQL Root Password you just created: Starting httpd: 
httpd: apr_sockaddr_info_get() failed for centos6-10
httpd: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1 for ServerName

   [  OK ]
Starting Dovecot Imap: [  OK ]
send: unable to open supervise/ok: file does not exist
smtp: unable to open supervise/ok: file does not exist
submission: unable to open supervise/ok: file does not exist
send/log: unable to open supervise/ok: file does not exist
smtp/log: unable to open supervise/ok: file does not exist
submission/log: unable to open supervise/ok: file does not exist


best wishes
   Tony White

On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap 
scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped 
the ball and didn't bother to let anyone know that they weren't 
supporting QMT anymore. If this is a pre-existing machine disable 
the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, 
update everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" 
$selinux_config

}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum 
priorities, QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh 
http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg


# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl 
https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && 
curl https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
105  1050  105  1050    0 0    931  0 0:00:01  0:00:01 
--:--:--  4133
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
100  1004  100  1004    0 0    890  0 0:00:01  0:00:01 
--:--:--  3968

[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

On 9/27/2018 10:24 PM, Tony White wrote:

Eric,
  ran qt-install...

Oops may have spoken too soon...

screen text:

Cleaning up...



All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


Please enter the MySQL Root Password you just created: Starting httpd: 
httpd: apr_sockaddr_info_get() failed for centos6-10
httpd: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1 for ServerName

   [  OK ]
Starting Dovecot Imap: [  OK ]
send: unable to open supervise/ok: file does not exist
smtp: unable to open supervise/ok: file does not exist
submission: unable to open supervise/ok: file does not exist
send/log: unable to open supervise/ok: file does not exist
smtp/log: unable to open supervise/ok: file does not exist
submission/log: unable to open supervise/ok: file does not exist


best wishes
   Tony White

On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap 
scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped 
the ball and didn't bother to let anyone know that they weren't 
supporting QMT anymore. If this is a pre-existing machine disable 
the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, 
update everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" 
$selinux_config

}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum 
priorities, QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh 
http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg


# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl 
https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && 
curl https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
105  1050  105  1050    0 0    931  0 0:00:01  0:00:01 
--:--:--  4133
  % Total    % Received % Xferd  Average Speed Time    Time 
Time  Current
 Dload  Upload Total   Spent    
Left  Speed
100  1004  100  1004    0 0    890  0 0:00:01  0:00:01 
--:--:--  3968

[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt-bootstrap-1 - updating all packages (yum update) ...
Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras qmailtoaster-current

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Eric,
  ran qt-install...

Oops may have spoken too soon...

screen text:

Cleaning up...



All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


Please enter the MySQL Root Password you just created: Starting httpd: httpd: 
apr_sockaddr_info_get() failed for centos6-10
httpd: Could not reliably determine the server's fully qualified domain name, 
using 127.0.0.1 for ServerName
   [  OK  ]
Starting Dovecot Imap: [  OK  ]
send: unable to open supervise/ok: file does not exist
smtp: unable to open supervise/ok: file does not exist
submission: unable to open supervise/ok: file does not exist
send/log: unable to open supervise/ok: file does not exist
smtp/log: unable to open supervise/ok: file does not exist
submission/log: unable to open supervise/ok: file does not exist


best wishes
  Tony White

On 28/09/18 14:14, Eric Broch wrote:


Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap scripts, my bootstrap's (below in red and green) do not 
use 'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the ball and didn't bother to let anyone know that 
they weren't supporting QMT anymore. If this is a pre-existing machine disable the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable qmailtoaster-current 
qmailtoaster-current-nodist



#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update everything)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" $selinux_config
}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum priorities, QMT repo)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg

# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && curl 
https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2

  % Total    % Received % Xferd  Average Speed   Time Time Time  Current
 Dload  Upload   Total Spent    Left  Speed
105  1050  105  1050    0 0    931  0  0:00:01 0:00:01 --:--:--  4133
  % Total    % Received % Xferd  Average Speed   Time Time Time  Current
 Dload  Upload   Total Spent    Left  Speed
100  1004  100  1004    0 0    890  0  0:00:01 0:00:01 --:--:--  3968
[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt-bootstrap-1 - updating all packages (yum update) ...
Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras qmailtoaster-current qmailtoaster-current-nodist 
updates
Cleaning up Everything
Clea

Re: Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

Excellent!!! Glad to hear it.


On 9/27/2018 10:03 PM, Tony White wrote:

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap 
scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the 
ball and didn't bother to let anyone know that they weren't 
supporting QMT anymore. If this is a pre-existing machine disable the 
qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update 
everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" 
$selinux_config

}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum 
priorities, QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg

# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl 
https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && curl 
https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2
  % Total    % Received % Xferd  Average Speed   Time Time Time  
Current
 Dload  Upload   Total Spent    
Left  Speed
105  1050  105  1050    0 0    931  0  0:00:01 0:00:01 
--:--:--  4133
  % Total    % Received % Xferd  Average Speed   Time Time Time  
Current
 Dload  Upload   Total Spent    
Left  Speed
100  1004  100  1004    0 0    890  0  0:00:01 0:00:01 
--:--:--  3968

[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt-bootstrap-1 - updating all packages (yum update) ...
Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras qmailtoaster-current 
qmailtoaster-current-nodist updates

Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, priorities
Setting up Update Process
Determining fastest mirrors
Could not retrieve mirrorlist 
http://mirrors.qmailtoaster.com/current/CentOS/mirror.list error was
14: PYCURL ERROR 51 - "SSL: certificate subject name 
'whitehorsetc.com' does not match target host name 
'mirrors.qmailtoaster.com'"

Error: Cannot find a valid baseurl for repo: qmailtoaster-current
qt-bootstrap-1 - rebooting now...
qt-bootstrap-1 - completed
[root@cos6-10-base ~]#
Broadcast message from root@cos6-10-base
    (/dev/pts/0) at 12:49 ...

The system is going down for reboot NOW!

best wishes
   Tony White

On 28/09/18 12:37, Eric Broch wrote:


Tony,

It is working, but...

I can tell by the download of 
'qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm' and the use of 
'mirrors.qmailtoaster.com' in the scripts that you're not following 
the correct instructions.


I'm not sure whether the qmailtoaster.com website (mirrored) has 
completely p

Re: Fwd: Re: [qmailtoaster] centos 6

[Tony White]

Eric,
  Sorry I did not intend to email offlist.
I did a reply to sender not the list.
Apologies.

I have reset the VM to give me a blank minimal install again.
It has just finished qt-bootstrp-2 without error.
So far so good.

cheers.


On 28/09/18 13:53, Eric Broch wrote:


Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap scripts, my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the ball and didn't bother to let anyone know that they 
weren't supporting QMT anymore. If this is a pre-existing machine disable the qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable qmailtoaster-current 
qmailtoaster-current-nodist



#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update everything)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" $selinux_config
}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum priorities, QMT repo)
##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg

# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && curl 
https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2

  % Total    % Received % Xferd  Average Speed   Time Time Time  Current
 Dload  Upload   Total Spent    Left  Speed
105  1050  105  1050    0 0    931  0  0:00:01 0:00:01 --:--:--  4133
  % Total    % Received % Xferd  Average Speed   Time Time Time  Current
 Dload  Upload   Total Spent    Left  Speed
100  1004  100  1004    0 0    890  0  0:00:01 0:00:01 --:--:--  3968
[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt-bootstrap-1 - updating all packages (yum update) ...
Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras qmailtoaster-current qmailtoaster-current-nodist 
updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, priorities
Setting up Update Process
Determining fastest mirrors
Could not retrieve mirrorlist 
http://mirrors.qmailtoaster.com/current/CentOS/mirror.list error was
14: PYCURL ERROR 51 - "SSL: certificate subject name 'whitehorsetc.com' does not match target host name 
'mirrors.qmailtoaster.com'"

Error: Cannot find a valid baseurl for repo: qmailtoaster-current
qt-bootstrap-1 - rebooting now...
qt-bootstrap-1 - completed
[root@cos6-10-base ~]#
Broadcast message from root@cos6-10-base
    (/dev/pts/0) at 12:49 ...

The system is going down for reboot NOW!

best wishes
   Tony White

On 28/09/18 12:37, Eric Broch wrote:


Tony,

It is working, but...

I can tell by the download of 'qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm' and the use of 
'mirrors.qmailtoaster.com' in the scripts that you're not following the correct instructions.


I'm not sure whether the qmailtoaster.com website (mirrored) has completely 
propagated or not.

Go to qmailtoaster.org and follow the instructions there.

Eric



On 9/27/2

Fwd: Re: [qmailtoaster] centos 6

[Eric Broch]

Tony, If you communicate off list you must whitelist my address


Tony,

I think (not sure why) you're still using the wrong bootstrap scripts, 
my bootstrap's (below in red and green) do not use 
'mirrors.qmailtoaster.com' but 'mirror2.qmailtoaster.com'


Irritatingly, this is because all the mirror maintainers dropped the 
ball and didn't bother to let anyone know that they weren't supporting 
QMT anymore. If this is a pre-existing machine disable the 
qmailtoaster-current repo:


# yum install yum-utils && yum-config-manager --disable 
qmailtoaster-current qmailtoaster-current-nodist




#!/bin/bash

# Copyright (C) Eric Shubert 
#
# script to do initial bootstrap processing (disable selinux, update 
everything)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# disable SELINUX
#
a2_disable_selinux(){

selinux_config=/etc/selinux/config

if [ ! -f "$selinux_config" ]; then
  echo "$me - $seclinux_config not found"
  exit 1
fi

echo "$me - disabling SELINUX ..."
sed -i$(date +%Y%m%d) -e "s|^SELINUX=.*$|SELINUX=disabled|" $selinux_config
}

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

a2_disable_selinux

echo "$me - updating all packages (yum update) ..."
yum clean all
yum -y --nogpgcheck update

echo "$me - rebooting now..."
shutdown -r now

echo "$me - completed"
exit 0





#!/bin/bash
# Copyright (C) Eric Shubert 
#
# script to do secondary bootstrap processing (install yum priorities, 
QMT repo)

##
# Change Log
# 12/26/13 written by Eric 'shubes' 
##

##
# main routine begins here
#
me=${0##*/}
myver=v1.0
echo "$me - $myversion"

# install yum-priorities
echo "$me - installing yum-priorities (plugin) ..."
yum -y install yum-priorities

# install qmailtoaster-release
qmt_release_pkg=qmailtoaster-release-2.0-2.qt.nodist.noarch.rpm
echo "$me - installing $qmt_release_pkg (repo) ..."
rpm -ivh http://mirror2.qmailtoaster.com/current/nodist/$qmt_release_pkg

# install qmailtoaster-util (scripts)
echo "$me - installing qmailtoaster-util (scripts) ..."
yum -y install --nogpgcheck qmailtoaster-util

echo "$me - completed"
exit 0




On 9/27/2018 8:50 PM, Tony White wrote:

Eric,
  Step one failed on .org...

[root@cos6-10-base ~]# curl 
https://www.qmailtoaster.org/qt-bootstrap-1 >qt-bootstrap-1 && curl 
https://www.qmailtoaster.org/qt-bootstrap-2 >qt-bootstrap-2
  % Total    % Received % Xferd  Average Speed   Time Time Time  
Current
 Dload  Upload   Total Spent    Left  
Speed
105  1050  105  1050    0 0    931  0  0:00:01 0:00:01 
--:--:--  4133
  % Total    % Received % Xferd  Average Speed   Time Time Time  
Current
 Dload  Upload   Total Spent    Left  
Speed
100  1004  100  1004    0 0    890  0  0:00:01 0:00:01 
--:--:--  3968

[root@cos6-10-base ~]# chmod 755 qt-bootstrap-*
[root@cos6-10-base ~]# ./qt-bootstrap-1
qt-bootstrap-1 -
qt-bootstrap-1 - disabling SELINUX ...
qt-bootstrap-1 - updating all packages (yum update) ...
Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras qmailtoaster-current 
qmailtoaster-current-nodist updates

Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, priorities
Setting up Update Process
Determining fastest mirrors
Could not retrieve mirrorlist 
http://mirrors.qmailtoaster.com/current/CentOS/mirror.list error was
14: PYCURL ERROR 51 - "SSL: certificate subject name 
'whitehorsetc.com' does not match target host name 
'mirrors.qmailtoaster.com'"

Error: Cannot find a valid baseurl for repo: qmailtoaster-current
qt-bootstrap-1 - rebooting now...
qt-bootstrap-1 - completed
[root@cos6-10-base ~]#
Broadcast message from root@cos6-10-base
    (/dev/pts/0) at 12:49 ...

The system is going down for reboot NOW!

best wishes
   Tony White

On 28/09/18 12:37, Eric Broch wrote:


Tony,

It is working, but...

I can tell by the download of 
'qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm' and the use of 
'mirrors.qmailtoaster.com' in the scripts that you're not following 
the correct instructions.


I'm not sure whether the qmailtoaster.com website (mirrored) has 
completely propagated or not.


Go to qmailtoaster.org and follow the instructions there.

Eric



On 9/27/2018 7:56 PM, Tony White wrote:

Hi Eric,
  Sadly it is still not working...
The download of the 
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm 
file will always fail due to it kicking the connection up to

ht

Re: [qmailtoaster] centos 6

[Eric Broch]

Tony,

It is working, but...

I can tell by the download of 
'qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm' and the use of 
'mirrors.qmailtoaster.com' in the scripts that you're not following the 
correct instructions.


I'm not sure whether the qmailtoaster.com website (mirrored) has 
completely propagated or not.


Go to qmailtoaster.org and follow the instructions there.

Eric



On 9/27/2018 7:56 PM, Tony White wrote:

Hi Eric,
  Sadly it is still not working...
The download of the 
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm 
file will always fail due to it kicking the connection up to

https and not leaving it as http.

Screen Dump...
--

[root@cos6-10-base ~]# sh qt-bootstrap-2
qt-bootstrap-2 -
qt-bootstrap-2 - installing yum-priorities (plugin) ...
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: centos.mirror.digitalpacific.com.au
 * extras: centos.mirror.digitalpacific.com.au
 * updates: mirror.as24220.net
Resolving Dependencies
--> Running transaction check
---> Package yum-plugin-priorities.noarch 0:1.1.30-42.el6_10 will be 
installed

--> Finished Dependency Resolution

Dependencies Resolved

===
 Package   Arch Version    
Repository   Size

===
Installing:
 yum-plugin-priorities noarch 
1.1.30-42.el6_10   updates  28 k


Transaction Summary
===
Install   1 Package(s)

Total download size: 28 k
Installed size: 28 k
Downloading Packages:
yum-plugin-priorities-1.1.30-42.el6_10.noarch.rpm |  28 kB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : yum-plugin-priorities-1.1.30-42.el6_10.noarch 1/1
  Verifying  : yum-plugin-priorities-1.1.30-42.el6_10.noarch 1/1

Installed:
  yum-plugin-priorities.noarch 0:1.1.30-42.el6_10

Complete!
qt-bootstrap-2 - installing 
qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm (repo) ...
Retrieving 
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
curl: (51) SSL: certificate subject name 'monk13.stakehouse.io' does 
not match target host name 'mirrors.qmailtoaster.com'
error: skipping 
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm 
- transfer failed

qt-bootstrap-2 - installing qmailtoaster-util (scripts) ...
Loaded plugins: fastestmirror, priorities
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: centos.mirror.digitalpacific.com.au
 * extras: centos.mirror.digitalpacific.com.au
 * updates: mirror.as24220.net
No package qmailtoaster-util available.
Error: Nothing to do
qt-bootstrap-2 - completed


best wishes
   Tony White

On 27/09/18 10:24, Eric Broch wrote:

List,

There were problems with the installation of QMT on CentOS 6 as 
you'all well know since I tested last November (2017). The problems 
existed primarily due to mirrors not being maintained. I've fixed 
these problems...hopefully. If anyone has issue please let me know so 
that they can be fixed.






--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] centos 6

[Tony White]

Hi Eric,
  Sadly it is still not working...
The download of the http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm file 
will always fail due to it kicking the connection up to

https and not leaving it as http.

Screen Dump...
--

[root@cos6-10-base ~]# sh qt-bootstrap-2
qt-bootstrap-2 -
qt-bootstrap-2 - installing yum-priorities (plugin) ...
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: centos.mirror.digitalpacific.com.au
 * extras: centos.mirror.digitalpacific.com.au
 * updates: mirror.as24220.net
Resolving Dependencies
--> Running transaction check
---> Package yum-plugin-priorities.noarch 0:1.1.30-42.el6_10 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===
 Package   Arch Version    
Repository   Size
===
Installing:
 yum-plugin-priorities noarch 1.1.30-42.el6_10   
updates  28 k

Transaction Summary
===
Install   1 Package(s)

Total download size: 28 k
Installed size: 28 k
Downloading Packages:
yum-plugin-priorities-1.1.30-42.el6_10.noarch.rpm |  28 kB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : yum-plugin-priorities-1.1.30-42.el6_10.noarch 1/1
  Verifying  : yum-plugin-priorities-1.1.30-42.el6_10.noarch 1/1

Installed:
  yum-plugin-priorities.noarch 0:1.1.30-42.el6_10

Complete!
qt-bootstrap-2 - installing qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm 
(repo) ...
Retrieving 
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
curl: (51) SSL: certificate subject name 'monk13.stakehouse.io' does not match 
target host name 'mirrors.qmailtoaster.com'
error: skipping http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm - transfer 
failed

qt-bootstrap-2 - installing qmailtoaster-util (scripts) ...
Loaded plugins: fastestmirror, priorities
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: centos.mirror.digitalpacific.com.au
 * extras: centos.mirror.digitalpacific.com.au
 * updates: mirror.as24220.net
No package qmailtoaster-util available.
Error: Nothing to do
qt-bootstrap-2 - completed


best wishes
  Tony White

On 27/09/18 10:24, Eric Broch wrote:


List,

There were problems with the installation of QMT on CentOS 6 as you'all well know since I tested last November (2017). 
The problems existed primarily due to mirrors not being maintained. I've fixed these problems...hopefully. If anyone has 
issue please let me know so that they can be fixed.

Re: [qmailtoaster] centos 6 update

[Eric Broch]

Tudor,

Thanks for bringing this issue up.

I updated the website www.qmailtoaster.com to reflect the necessity of 
higher versions of the MySQL libraries (which Remi provides) when 
upgrading QMT which includes higher versions Dovecot.


Below is the full procedure for from Install to Upgrade:

1) CentOS 6 Minimal Install

2) QMT Install
# curl 
https://raw.githubusercontent.com/QMailToaster/qmailtoaster-util/master/qt-bootstrap-1 
>qt-bootstrap-1

# sh qt-bootstrap-1 (system will reboot)
# curl 
https://raw.githubusercontent.com/QMailToaster/qmailtoaster-util/master/qt-bootstrap-2 
>qt-bootstrap-2

# sh qt-bootstrap-2
# mv /opt/qmailtoaster-util/bin/qt-install 
/opt/qmailtoaster-util/bin/qt-install.bak
# curl -o /opt/qmailtoaster-util/bin/qt-install 
https://raw.githubusercontent.com/qmtoaster/cos6/master/qt-install

# chmod 755 /opt/qmailtoaster-util/bin/qt-install
# qt-install

3) Upgrading QMT
# rpm -Uvh 
https://raw.githubusercontent.com/qmtoaster/cos6/master/qmt-release-1-4.qt.el6.noarch.rpm

# yum install yum-utils
# yum install http://rpms.remirepo.net/enterprise/remi-release-6.rpm
# yum-config-manager --enable remi remi-php56
# yum update
# yum --enablerepo=qmt-testing update

Eric




On 5/17/2017 10:39 AM, Todor Petrov Vmobile wrote:

Hi Eric,
Thank you! The problem is fixed. The softlimit was 1200 now is 
6400. There are no more error messages in the log. Everything 
works perfect, smtp-ssl too.
So - the other problem was installing without using remi repo‎. I will 
include that in my manual. Thank you again.


Sent from my BlackBerry 10 smartphone.
*From: *Eric Broch
*Sent: *17 май 2017, сряда, 18:57
*To: *qmailtoaster-list@qmailtoaster.com
*Reply To: *qmailtoaster-list@qmailtoaster.com
*Subject: *Re: [qmailtoaster] centos 6 update


Hi Tudor,

This looks like a softlimit error.

If you look in /var/log/messages I imagine you'll find a 'segfault' error.

Check for the softlimit line in /var/qmail/supervise/smtp-ssl/run

exec /usr/bin/softlimit -m 6400

Mine is set to 6400. I'm not sure what yours is set to, you might 
want to double it then stop qmail and start it.


# qmailctl stop

# qmailctl start

Eric


On 5/17/2017 9:33 AM, Todor Petrov wrote:


Hi Eric,

Now it is installed perfectly. After adding remi repo the setup was 
successful without any errors. But now smtp-ssl is not working - 
mysql-library again. I find in the log the following error:


/var/qmail/bin/qmail-smtpd: error while loading shared libraries: 
libmysqlclient.so.18: failed to map segment from shared object: 
Cannot allocate memory


The service is up with port 465 but when I try to check ssl version 
from outside with testing script the output is:


Testing protocols:
SSLv2: NO
SSLv3: NO
TLSv1: NO
TLSv1.1: NO
TLSv1.2: NO

And of course the smtp-ssl does not work.

The output of old errors before installing remi repo:

Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
 You could try using --skip-broken to work around the problem

*after the command: yum --enablerepo=remi update*

i have:

Updating:
 clamavx86_64   0.99.2-2.qt.el6 qmt-current   2.7 M
 dovecot   x86_64   1:2.2.24-11.qt.el6 qmt-current   
7.9 M

 mysql x86_64   5.5.56-1.el6.remi remi  5.7 M
 mysql-libsx86_64   5.5.56-1.el6.remi remi  781 k
 mysql-server  x86_64   5.5.56-1.el6.remi remi   10 M
 perl-Compress-Raw-Bzip2   x86_64   2.052-1.el6.rf rpmforge  104 k
 php   x86_64   5.4.45-13.el6.remi remi  
2.8 M
 php-cli   x86_64   5.4.45-13.el6.remi remi  
4.1 M
 php-commonx86_64   5.4.45-13.el6.remi remi  
968 k

 qmailadminx86_64   1.2.16-1.qt.el6 qmt-current   2.2 M
 spamassassin  x86_64   3.4.1-0.qt.el6 qmt-current   1.1 M
 spamdyke  x86_64   5.0.1-0.qt.el6 qmt-current   118 k
Installing for dependencies:
 compat-mysql51x86_64   5.1.73-1.el6.remi remi  1.4 M



On 17-May-17 6:20 PM, Eric Broch wrote:


Hi Tudor,

Remi is not original to qmailtoaster. The only reason I installed 
Remi is for Roundcube on CentOS 6. I wouldn't need it otherwise.


Here's the Remi wizard which will get you started. I'm not sure why 
you can't update, though. Can you  send me all the errors associated 
with yum update?


http://rpms.remirepo.net/wizard/

Eric


On 5/17/2017 8:34 AM, Todor Petrov wrote:


Hi Eric,

Thank you for the

Re: [qmailtoaster] centos 6 update

[Todor Petrov Vmobile]

  Hi Eric,Thank you! The problem is fixed. The softlimit was 1200 now is 6400. There are no more error messages in the log. Everything works perfect, smtp-ssl too.So - the other problem was installing without using remi repo‎. I will include that in my manual. Thank you again.Sent from my BlackBerry 10 smartphone.From: Eric BrochSent: 17 май 2017, сряда, 18:57To: qmailtoaster-list@qmailtoaster.comReply To: qmailtoaster-list@qmailtoaster.comSubject: Re: [qmailtoaster] centos 6 update
  

  
  
Hi Tudor,

This looks like a softlimit error. 

If you look in /var/log/messages I imagine you'll find a
  'segfault' error.

Check for the softlimit line in /var/qmail/supervise/smtp-ssl/run
exec /usr/bin/softlimit -m 6400
Mine is set to 6400. I'm not sure what yours is set to, you
  might want to double it then stop qmail and start it.
# qmailctl stop
# qmailctl start
Eric



On 5/17/2017 9:33 AM, Todor Petrov
  wrote:


  
  Hi Eric,
  Now it is installed perfectly. After adding remi repo the setup
was successful without any errors. But now smtp-ssl is not
working - mysql-library again. I find in the log the following
error:
  /var/qmail/bin/qmail-smtpd: error while loading shared
libraries: libmysqlclient.so.18: failed to map segment from
shared object: Cannot allocate memory
  
  The service is up with port 465 but when I try to check ssl
version from outside with testing script the output is: 
  
  Testing protocols:
SSLv2: NO
SSLv3: NO
TLSv1: NO
TLSv1.1: NO
TLSv1.2: NO
  
  And of course the smtp-ssl does not work.
  The output of old errors before installing remi repo:
  Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires:
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires:
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
 You could try using --skip-broken to work around the problem
  after the command: yum --enablerepo=remi update
  i have: 
  
  Updating:
 clamav    x86_64   0.99.2-2.qt.el6
qmt-current   2.7 M
 dovecot   x86_64   1:2.2.24-11.qt.el6 
qmt-current   7.9 M
 mysql x86_64   5.5.56-1.el6.remi  
remi  5.7 M
 mysql-libs    x86_64   5.5.56-1.el6.remi  
remi  781 k
 mysql-server  x86_64   5.5.56-1.el6.remi  
remi   10 M
 perl-Compress-Raw-Bzip2   x86_64   2.052-1.el6.rf 
rpmforge  104 k
 php   x86_64   5.4.45-13.el6.remi 
remi  2.8 M
 php-cli   x86_64   5.4.45-13.el6.remi 
remi  4.1 M
 php-common    x86_64   5.4.45-13.el6.remi 
remi  968 k
 qmailadmin    x86_64   1.2.16-1.qt.el6
qmt-current   2.2 M
 spamassassin  x86_64   3.4.1-0.qt.el6 
qmt-current   1.1 M
 spamdyke  x86_64   5.0.1-0.qt.el6 
qmt-current   118 k
Installing for dependencies:
 compat-mysql51    x86_64   5.1.73-1.el6.remi  
remi  1.4 M


  
  



  

  

  

  

  


  

  

  

  

  

  
  On 17-May-17 6:20 PM, Eric

Re: [qmailtoaster] centos 6 update

[Eric Broch]

Hi Tudor,

This looks like a softlimit error.

If you look in /var/log/messages I imagine you'll find a 'segfault' error.

Check for the softlimit line in /var/qmail/supervise/smtp-ssl/run

exec /usr/bin/softlimit -m 6400

Mine is set to 6400. I'm not sure what yours is set to, you might 
want to double it then stop qmail and start it.


# qmailctl stop

# qmailctl start

Eric


On 5/17/2017 9:33 AM, Todor Petrov wrote:


Hi Eric,

Now it is installed perfectly. After adding remi repo the setup was 
successful without any errors. But now smtp-ssl is not working - 
mysql-library again. I find in the log the following error:


/var/qmail/bin/qmail-smtpd: error while loading shared libraries: 
libmysqlclient.so.18: failed to map segment from shared object: Cannot 
allocate memory


The service is up with port 465 but when I try to check ssl version 
from outside with testing script the output is:


Testing protocols:
SSLv2: NO
SSLv3: NO
TLSv1: NO
TLSv1.1: NO
TLSv1.2: NO

And of course the smtp-ssl does not work.

The output of old errors before installing remi repo:

Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
 You could try using --skip-broken to work around the problem

*after the command: yum --enablerepo=remi update*

i have:

Updating:
 clamavx86_64   0.99.2-2.qt.el6 qmt-current   2.7 M
 dovecot   x86_64   1:2.2.24-11.qt.el6 qmt-current   7.9 M
 mysql x86_64   5.5.56-1.el6.remi remi  5.7 M
 mysql-libsx86_64   5.5.56-1.el6.remi remi  781 k
 mysql-server  x86_64   5.5.56-1.el6.remi remi   10 M
 perl-Compress-Raw-Bzip2   x86_64   2.052-1.el6.rf rpmforge  104 k
 php   x86_64   5.4.45-13.el6.remi remi  2.8 M
 php-cli   x86_64   5.4.45-13.el6.remi remi  4.1 M
 php-commonx86_64   5.4.45-13.el6.remi remi  968 k
 qmailadminx86_64   1.2.16-1.qt.el6 qmt-current   2.2 M
 spamassassin  x86_64   3.4.1-0.qt.el6 qmt-current   1.1 M
 spamdyke  x86_64   5.0.1-0.qt.el6 qmt-current   118 k
Installing for dependencies:
 compat-mysql51x86_64   5.1.73-1.el6.remi remi  1.4 M



On 17-May-17 6:20 PM, Eric Broch wrote:


Hi Tudor,

Remi is not original to qmailtoaster. The only reason I installed 
Remi is for Roundcube on CentOS 6. I wouldn't need it otherwise.


Here's the Remi wizard which will get you started. I'm not sure why 
you can't update, though. Can you  send me all the errors associated 
with yum update?


http://rpms.remirepo.net/wizard/

Eric


On 5/17/2017 8:34 AM, Todor Petrov wrote:


Hi Eric,

Thank you for the answer. I see that you have remi repo - it is not 
included in the setup procedure. Should I install it first or after 
the setup is complete.


Btw - I cant find remi-php56 for centos 6 - just a 5.4 and 7.0. 
Which repos must be installed additionally (not included in the setup)?



On 17-May-17 3:42 PM, Eric Broch wrote:


Hi Tudor,

Running 'yum provides libmysqlclient_r.so.16' I get the following.

[root@ ~]# yum provides  libmysqlclient_r.so.16
Loaded plugins: fastestmirror, priorities, protectbase, 
refresh-packagekit, security

Determining fastest mirrors
epel/metalink |  11 kB 00:00
 * base: mirrors.cat.pdx.edu
 * epel: ca.mirror.babylon.network
 * extras: mirror.atlantic.net
 * qmailtoaster-current: mirror2.qmailtoaster.com
 * qmailtoaster-current-nodist: mirror2.qmailtoaster.com
 * qmt-current: ftp.whitehorsetc.com
 * remi: rpms.remirepo.net
 * remi-php56: rpms.remirepo.net
 * remi-safe: rpms.remirepo.net
 * rpmforge: www.mirrorservice.org
 * updates: repos.dfw.quadranet.com
 * webtatic: us-east.repo.webtatic.com
base | 3.7 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:01
extras | 3.4 kB 00:00
qmailtoaster-current | 2.9 kB 00:00
qmailtoaster-current-nodist | 2.9 kB 00:00
qmt-current | 2.9 kB 00:00
remi | 2.9 kB 00:00
remi/primary_db | 1.7 MB 00:03
remi-php56 | 2.9 kB 00:00
remi-php56/primary_db | 218 kB 00:01
remi-safe | 2.9 kB 00:00
remi-safe/primary_db | 725 kB 00:02
rpmforge | 1.9 kB 00:00
rspamd/signature |  833 B 00:00
rspamd/signature | 2.9 kB 00:00 ...
rspamd/primary_db | 7.5 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 828 kB 00:01
webtatic | 3.6 kB 00:00
webtatic/primary_db | 218 kB 00:00
28 packages excluded due to repository priority protections
0 packages excluded due to reposi

Re: [qmailtoaster] centos 6 update

[Todor Petrov]

Hi Eric,

Now it is installed perfectly. After adding remi repo the setup was 
successful without any errors. But now smtp-ssl is not working - 
mysql-library again. I find in the log the following error:


/var/qmail/bin/qmail-smtpd: error while loading shared libraries: 
libmysqlclient.so.18: failed to map segment from shared object: Cannot 
allocate memory


The service is up with port 465 but when I try to check ssl version from 
outside with testing script the output is:


Testing protocols:
SSLv2: NO
SSLv3: NO
TLSv1: NO
TLSv1.1: NO
TLSv1.2: NO

And of course the smtp-ssl does not work.

The output of old errors before installing remi repo:

Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Error: Package: qmailadmin-1.2.16-1.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
Error: Package: 1:dovecot-2.2.24-11.qt.el6.x86_64 (qmt-current)
   Requires: libmysqlclient.so.18()(64bit)
 You could try using --skip-broken to work around the problem

*after the command: yum --enablerepo=remi update*

i have:

Updating:
 clamavx86_64   0.99.2-2.qt.el6 qmt-current   2.7 M
 dovecot   x86_64   1:2.2.24-11.qt.el6 qmt-current   7.9 M
 mysql x86_64   5.5.56-1.el6.remi remi  5.7 M
 mysql-libsx86_64   5.5.56-1.el6.remi remi  781 k
 mysql-server  x86_64   5.5.56-1.el6.remi remi   10 M
 perl-Compress-Raw-Bzip2   x86_64   2.052-1.el6.rf rpmforge  104 k
 php   x86_64   5.4.45-13.el6.remi remi  2.8 M
 php-cli   x86_64   5.4.45-13.el6.remi remi  4.1 M
 php-commonx86_64   5.4.45-13.el6.remi remi  968 k
 qmailadminx86_64   1.2.16-1.qt.el6 qmt-current   2.2 M
 spamassassin  x86_64   3.4.1-0.qt.el6 qmt-current   1.1 M
 spamdyke  x86_64   5.0.1-0.qt.el6 qmt-current   118 k
Installing for dependencies:
 compat-mysql51x86_64   5.1.73-1.el6.remi remi  1.4 M



On 17-May-17 6:20 PM, Eric Broch wrote:


Hi Tudor,

Remi is not original to qmailtoaster. The only reason I installed Remi 
is for Roundcube on CentOS 6. I wouldn't need it otherwise.


Here's the Remi wizard which will get you started. I'm not sure why 
you can't update, though. Can you  send me all the errors associated 
with yum update?


http://rpms.remirepo.net/wizard/

Eric


On 5/17/2017 8:34 AM, Todor Petrov wrote:


Hi Eric,

Thank you for the answer. I see that you have remi repo - it is not 
included in the setup procedure. Should I install it first or after 
the setup is complete.


Btw - I cant find remi-php56 for centos 6 - just a 5.4 and 7.0. Which 
repos must be installed additionally (not included in the setup)?



On 17-May-17 3:42 PM, Eric Broch wrote:


Hi Tudor,

Running 'yum provides libmysqlclient_r.so.16' I get the following.

[root@ ~]# yum provides  libmysqlclient_r.so.16
Loaded plugins: fastestmirror, priorities, protectbase, 
refresh-packagekit, security

Determining fastest mirrors
epel/metalink |  11 kB 00:00
 * base: mirrors.cat.pdx.edu
 * epel: ca.mirror.babylon.network
 * extras: mirror.atlantic.net
 * qmailtoaster-current: mirror2.qmailtoaster.com
 * qmailtoaster-current-nodist: mirror2.qmailtoaster.com
 * qmt-current: ftp.whitehorsetc.com
 * remi: rpms.remirepo.net
 * remi-php56: rpms.remirepo.net
 * remi-safe: rpms.remirepo.net
 * rpmforge: www.mirrorservice.org
 * updates: repos.dfw.quadranet.com
 * webtatic: us-east.repo.webtatic.com
base | 3.7 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:01
extras | 3.4 kB 00:00
qmailtoaster-current | 2.9 kB 00:00
qmailtoaster-current-nodist | 2.9 kB 00:00
qmt-current | 2.9 kB 00:00
remi | 2.9 kB 00:00
remi/primary_db | 1.7 MB 00:03
remi-php56 | 2.9 kB 00:00
remi-php56/primary_db | 218 kB 00:01
remi-safe | 2.9 kB 00:00
remi-safe/primary_db | 725 kB 00:02
rpmforge | 1.9 kB 00:00
rspamd/signature |  833 B 00:00
rspamd/signature | 2.9 kB 00:00 ...
rspamd/primary_db | 7.5 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 828 kB 00:01
webtatic | 3.6 kB 00:00
webtatic/primary_db | 218 kB 00:00
28 packages excluded due to repository priority protections
0 packages excluded due to repository protections
mysql-libs-5.1.73-8.el6_8.i686 : The shared libraries required for 
MySQL clients

Repo: base
Matched from:
Other   : libmysqlclient_r.so.16


Eric



On 5/17/2017 1:19 AM, Todor Petrov wrote:


Hi all,

I have a installation of Centos 6 and qmailtoaster. Everything was 
fine before I tried to update from the testing repo.


Now few packages cant update and show errors of missing 
libmysqlclient_r.so.1

Re: [qmailtoaster] centos 6 update

[Eric Broch]

Hi Tudor,

Remi is not original to qmailtoaster. The only reason I installed Remi 
is for Roundcube on CentOS 6. I wouldn't need it otherwise.


Here's the Remi wizard which will get you started. I'm not sure why you 
can't update, though. Can you  send me all the errors associated with 
yum update?


http://rpms.remirepo.net/wizard/

Eric


On 5/17/2017 8:34 AM, Todor Petrov wrote:


Hi Eric,

Thank you for the answer. I see that you have remi repo - it is not 
included in the setup procedure. Should I install it first or after 
the setup is complete.


Btw - I cant find remi-php56 for centos 6 - just a 5.4 and 7.0. Which 
repos must be installed additionally (not included in the setup)?



On 17-May-17 3:42 PM, Eric Broch wrote:


Hi Tudor,

Running 'yum provides libmysqlclient_r.so.16' I get the following.

[root@ ~]# yum provides  libmysqlclient_r.so.16
Loaded plugins: fastestmirror, priorities, protectbase, 
refresh-packagekit, security

Determining fastest mirrors
epel/metalink |  11 kB 00:00
 * base: mirrors.cat.pdx.edu
 * epel: ca.mirror.babylon.network
 * extras: mirror.atlantic.net
 * qmailtoaster-current: mirror2.qmailtoaster.com
 * qmailtoaster-current-nodist: mirror2.qmailtoaster.com
 * qmt-current: ftp.whitehorsetc.com
 * remi: rpms.remirepo.net
 * remi-php56: rpms.remirepo.net
 * remi-safe: rpms.remirepo.net
 * rpmforge: www.mirrorservice.org
 * updates: repos.dfw.quadranet.com
 * webtatic: us-east.repo.webtatic.com
base | 3.7 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:01
extras | 3.4 kB 00:00
qmailtoaster-current | 2.9 kB 00:00
qmailtoaster-current-nodist | 2.9 kB 00:00
qmt-current | 2.9 kB 00:00
remi | 2.9 kB 00:00
remi/primary_db | 1.7 MB 00:03
remi-php56 | 2.9 kB 00:00
remi-php56/primary_db | 218 kB 00:01
remi-safe | 2.9 kB 00:00
remi-safe/primary_db | 725 kB 00:02
rpmforge | 1.9 kB 00:00
rspamd/signature |  833 B 00:00
rspamd/signature | 2.9 kB 00:00 ...
rspamd/primary_db | 7.5 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 828 kB 00:01
webtatic | 3.6 kB 00:00
webtatic/primary_db | 218 kB 00:00
28 packages excluded due to repository priority protections
0 packages excluded due to repository protections
mysql-libs-5.1.73-8.el6_8.i686 : The shared libraries required for 
MySQL clients

Repo: base
Matched from:
Other   : libmysqlclient_r.so.16


Eric



On 5/17/2017 1:19 AM, Todor Petrov wrote:


Hi all,

I have a installation of Centos 6 and qmailtoaster. Everything was 
fine before I tried to update from the testing repo.


Now few packages cant update and show errors of missing 
libmysqlclient_r.so.16(libmysqlclient_16)(64bit)


everything else is fully updated and there are no more packages for 
mysql libs in the repo.


Can someone help me how to fix this issue?

I see the development of qmt for Centos7 is very actual and the 
installation and configuration looks very easy. Is it recommended to 
upgrade to 7?



--



--
Eric Broch
White Horse Technical Consulting (WHTC)




--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] centos 6 update

[Todor Petrov]

Hi Eric,

Thank you for the answer. I see that you have remi repo - it is not 
included in the setup procedure. Should I install it first or after the 
setup is complete.


Btw - I cant find remi-php56 for centos 6 - just a 5.4 and 7.0. Which 
repos must be installed additionally (not included in the setup)?



On 17-May-17 3:42 PM, Eric Broch wrote:


Hi Tudor,

Running 'yum provides libmysqlclient_r.so.16' I get the following.

[root@ ~]# yum provides  libmysqlclient_r.so.16
Loaded plugins: fastestmirror, priorities, protectbase, 
refresh-packagekit, security

Determining fastest mirrors
epel/metalink |  11 kB 00:00
 * base: mirrors.cat.pdx.edu
 * epel: ca.mirror.babylon.network
 * extras: mirror.atlantic.net
 * qmailtoaster-current: mirror2.qmailtoaster.com
 * qmailtoaster-current-nodist: mirror2.qmailtoaster.com
 * qmt-current: ftp.whitehorsetc.com
 * remi: rpms.remirepo.net
 * remi-php56: rpms.remirepo.net
 * remi-safe: rpms.remirepo.net
 * rpmforge: www.mirrorservice.org
 * updates: repos.dfw.quadranet.com
 * webtatic: us-east.repo.webtatic.com
base | 3.7 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:01
extras | 3.4 kB 00:00
qmailtoaster-current | 2.9 kB 00:00
qmailtoaster-current-nodist | 2.9 kB 00:00
qmt-current | 2.9 kB 00:00
remi | 2.9 kB 00:00
remi/primary_db | 1.7 MB 00:03
remi-php56 | 2.9 kB 00:00
remi-php56/primary_db | 218 kB 00:01
remi-safe | 2.9 kB 00:00
remi-safe/primary_db | 725 kB 00:02
rpmforge | 1.9 kB 00:00
rspamd/signature |  833 B 00:00
rspamd/signature | 2.9 kB 00:00 ...
rspamd/primary_db | 7.5 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 828 kB 00:01
webtatic | 3.6 kB 00:00
webtatic/primary_db | 218 kB 00:00
28 packages excluded due to repository priority protections
0 packages excluded due to repository protections
mysql-libs-5.1.73-8.el6_8.i686 : The shared libraries required for 
MySQL clients

Repo: base
Matched from:
Other   : libmysqlclient_r.so.16


Eric



On 5/17/2017 1:19 AM, Todor Petrov wrote:


Hi all,

I have a installation of Centos 6 and qmailtoaster. Everything was 
fine before I tried to update from the testing repo.


Now few packages cant update and show errors of missing 
libmysqlclient_r.so.16(libmysqlclient_16)(64bit)


everything else is fully updated and there are no more packages for 
mysql libs in the repo.


Can someone help me how to fix this issue?

I see the development of qmt for Centos7 is very actual and the 
installation and configuration looks very easy. Is it recommended to 
upgrade to 7?



--



--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] centos 6 update

[Eric Broch]

Hi Tudor,

Running 'yum provides libmysqlclient_r.so.16' I get the following.

[root@ ~]# yum provides  libmysqlclient_r.so.16
Loaded plugins: fastestmirror, priorities, protectbase, 
refresh-packagekit, security

Determining fastest mirrors
epel/metalink |  11 kB 00:00
 * base: mirrors.cat.pdx.edu
 * epel: ca.mirror.babylon.network
 * extras: mirror.atlantic.net
 * qmailtoaster-current: mirror2.qmailtoaster.com
 * qmailtoaster-current-nodist: mirror2.qmailtoaster.com
 * qmt-current: ftp.whitehorsetc.com
 * remi: rpms.remirepo.net
 * remi-php56: rpms.remirepo.net
 * remi-safe: rpms.remirepo.net
 * rpmforge: www.mirrorservice.org
 * updates: repos.dfw.quadranet.com
 * webtatic: us-east.repo.webtatic.com
base | 3.7 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:01
extras | 3.4 kB 00:00
qmailtoaster-current | 2.9 kB 00:00
qmailtoaster-current-nodist | 2.9 kB 00:00
qmt-current | 2.9 kB 00:00
remi | 2.9 kB 00:00
remi/primary_db | 1.7 MB 00:03
remi-php56 | 2.9 kB 00:00
remi-php56/primary_db | 218 kB 00:01
remi-safe | 2.9 kB 00:00
remi-safe/primary_db | 725 kB 00:02
rpmforge | 1.9 kB 00:00
rspamd/signature |  833 B 00:00
rspamd/signature | 2.9 kB 00:00 ...
rspamd/primary_db | 7.5 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 828 kB 00:01
webtatic | 3.6 kB 00:00
webtatic/primary_db | 218 kB 00:00
28 packages excluded due to repository priority protections
0 packages excluded due to repository protections
mysql-libs-5.1.73-8.el6_8.i686 : The shared libraries required for MySQL 
clients

Repo: base
Matched from:
Other   : libmysqlclient_r.so.16


Eric



On 5/17/2017 1:19 AM, Todor Petrov wrote:


Hi all,

I have a installation of Centos 6 and qmailtoaster. Everything was 
fine before I tried to update from the testing repo.


Now few packages cant update and show errors of missing 
libmysqlclient_r.so.16(libmysqlclient_16)(64bit)


everything else is fully updated and there are no more packages for 
mysql libs in the repo.


Can someone help me how to fix this issue?

I see the development of qmt for Centos7 is very actual and the 
installation and configuration looks very easy. Is it recommended to 
upgrade to 7?



--



--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] CentOS 6 install

[Eric Broch]

Hello again,

Also I noticed that 'bind' is not installed. Is this not necessary anymore?

EricB

On 11/17/2014 10:54 AM, Eric Broch wrote:
> Hello,
>
> I just installed QMT on CentOS 6. When running qt-install I got the
> following NON-FATAL errors:
>
>  Installing :
> clamav-0.98.4-2.qt.el6.x86_64 
> 
> 35/103
> 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
> 
> 93/103
> 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
>
>
> Is there anything to worry about?
>
> EricB
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

RE: [qmailtoaster] CentOS 6

[sysadmin]

All the New VM`s are running Centos6

http://techyguru.com/downloads.html

Dave M


-Original Message-
From: "Randy Katz" 
Sent: Monday, May 12, 2014 6:42am
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] CentOS 6

Hi,

I have been watching this list for a few years and it never ceases to
amaze me that there
is no CentOS 6 supported, at least not on the website. I would really
like to replace one
of my old qmail toaster installations with a VM running CentOS 6. Please
advise if there
is currently a way to get this working, thank you in advance.
-- 
--> Randy Katz - *SimplicityHosting.Com, Inc.* - Premium Web Hosting
Services
?H cPanel Shared, VPS, Dedicated, eCommerce, Affiliates
S? Custom Configurations and Pricing Available to your Need
--> http://www.simplicityhosting.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] CentOS 6 supported or not?

[Dave M]

Centos6 is currently a work in progress,


On 1/28/2014 8:12 AM, erik.wram...@codemint.com wrote:

Hello,

Please excuse me if this is obvious. Some old posts mention CentOS or Red
Hat 6. Several people seemed to have working installations way back, but
the Wiki and serveral posts indicate that CentOS 5 remains the only
supported CentOS release.

I would like to use qmailtoaster with qmailtoasterplus on CentOS 6. I
cannot use CentOS 5, so unless I can get it working I need to switch mail
server or installation method. The setup with all the qtp-commands for
maintenance has worked great for years on other servers, so I would prefer
to stay with it.

If I run qtp-whatami it seems CentOS 6 is supported:

qtp-whatami v0.3.8 Tue Jan 28 15:15:51 CET 2014
REAL_DIST=CentOS
DISTRO=CentOS
OSVER=6.5
QTARCH=x86_64
QTKERN=2.6.32-431.3.1.el6.x86_64
BUILD_DIST=cnt6064
BUILD_DIR=/usr/src/redhat
This machine's OS is supported and has been tested

So far so good, but qtp-install-rpmforge fails:

qtp-install-rpmforge v0.4.0 - getting latest version of rpmforge-release ...
qtp-install-rpmforge - rpmforge-release not installed, installing ...
qtp-install-rpmforge - your distro/ver is not supported by RPMforge, exiting.

If I install rpmforge manually that works, but then qtp-dependencies
fails. Some packages are not found and some Perl packages conflict with
versions from the base repository.

So, what should I do? Is CentOS 6 supposed to be supported by the qtp
scripts? If not, is it in the works? I don't want to push, I just want to
know what my options are.

-Erik


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] CentOS 6 (and 5) rpms

[Nikolay Mitev]

Hi Eric,

Perfectly job, Congratulations !

Best regards,
Nikolay


On Thu, Nov 21, 2013 at 9:53 AM, Sebastian Grewe  wrote:

> Hey Eric,
>
> This is great. Is that an actual repo that I can use in Chef to trigger a
> regular RPM/YUM based installation? Then I will re-factor my cookbook and
> start using this - then it should work once we are on repoforge.
>
> Cheers,
> Sebastian
>
> On Nov 21, 2013, at 8:46 AM, Chandran Manikandan 
> wrote:
>
> Thanks Eric,
> Shall i do same installed procedure for centos 6 with qmailtoaster which
> is showing in Wiki for centos 5 qmailtoaster.
>
>
> On Wed, Nov 20, 2013 at 11:11 PM, Eric Shubert  wrote:
>
>> Binary rpms can now be found at
>> http://mirrors.qmailtoaster.com/repos/testing
>>
>> While packages in /testing should be considered beta, when they end up
>> being migrated to /current there will be no need to update them (so long as
>> you've installed the final testing version).
>>
>> I'm presently getting the qmailtoaster-release package built, which will
>> provide yum capability. I just thought that some of you might want to do
>> some initial testing.
>>
>> Thanks.
>>
>> --
>> -Eric 'shubes'
>>
>>
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>>
>
>
> --
> *Thanks,*
> *Manikandan.C*
> *System Administrator*
>
>
>

Re: [qmailtoaster] CentOS 6 (and 5) rpms

[Sebastian Grewe]

Hey Eric,

This is great. Is that an actual repo that I can use in Chef to trigger a 
regular RPM/YUM based installation? Then I will re-factor my cookbook and start 
using this - then it should work once we are on repoforge.

Cheers,
Sebastian

On Nov 21, 2013, at 8:46 AM, Chandran Manikandan  wrote:

> Thanks Eric,
> Shall i do same installed procedure for centos 6 with qmailtoaster which is 
> showing in Wiki for centos 5 qmailtoaster.
> 
> 
> On Wed, Nov 20, 2013 at 11:11 PM, Eric Shubert  wrote:
> Binary rpms can now be found at
> http://mirrors.qmailtoaster.com/repos/testing
> 
> While packages in /testing should be considered beta, when they end up being 
> migrated to /current there will be no need to update them (so long as you've 
> installed the final testing version).
> 
> I'm presently getting the qmailtoaster-release package built, which will 
> provide yum capability. I just thought that some of you might want to do some 
> initial testing.
> 
> Thanks.
> 
> -- 
> -Eric 'shubes'
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 
> 
> 
> 
> -- 
> Thanks,
> Manikandan.C
> System Administrator

Re: [qmailtoaster] CentOS 6 (and 5) rpms

[Chandran Manikandan]

Thanks Eric,
Shall i do same installed procedure for centos 6 with qmailtoaster which is
showing in Wiki for centos 5 qmailtoaster.


On Wed, Nov 20, 2013 at 11:11 PM, Eric Shubert  wrote:

> Binary rpms can now be found at
> http://mirrors.qmailtoaster.com/repos/testing
>
> While packages in /testing should be considered beta, when they end up
> being migrated to /current there will be no need to update them (so long as
> you've installed the final testing version).
>
> I'm presently getting the qmailtoaster-release package built, which will
> provide yum capability. I just thought that some of you might want to do
> some initial testing.
>
> Thanks.
>
> --
> -Eric 'shubes'
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>


-- 
*Thanks,*
*Manikandan.C*
*System Administrator*

Re: [qmailtoaster] CentOS 6 (and 5) rpms

[Constantin IOAJA]

Pe 20.11.2013 17:27, Eric Broch a scris:

On 11/20/2013 8:11 AM, Eric Shubert wrote:

Binary rpms can now be found at
http://mirrors.qmailtoaster.com/repos/testing

While packages in /testing should be considered beta, when they end up
being migrated to /current there will be no need to update them (so
long as you've installed the final testing version).

I'm presently getting the qmailtoaster-release package built, which
will provide yum capability. I just thought that some of you might
want to do some initial testing.

Thanks.


ES.,

Nothing there! Is this the one:
http://mirrors.qmailtoaster.com/testing/centos/6/

EB.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




Try this link:

http://mirror2.qmailtoaster.com/testing/centos/

--
=

Constantin IOAJA

Network Administrator C.N.S. Cartel ALFA




smime.p7s
Description: Semnătură criptografică S/MIME

Re: [qmailtoaster] CentOS 6 (and 5) rpms

[Eric Broch]

On 11/20/2013 8:11 AM, Eric Shubert wrote:
> Binary rpms can now be found at
> http://mirrors.qmailtoaster.com/repos/testing
>
> While packages in /testing should be considered beta, when they end up
> being migrated to /current there will be no need to update them (so
> long as you've installed the final testing version).
>
> I'm presently getting the qmailtoaster-release package built, which
> will provide yum capability. I just thought that some of you might
> want to do some initial testing.
>
> Thanks.
>
ES.,

Nothing there! Is this the one:
http://mirrors.qmailtoaster.com/testing/centos/6/

EB.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Centos 6

[Dave MacDonald]

I will check it out again..
Thanks Dan

Dave
On 2013-01-06 11:27 PM, "Dan McAllister"  wrote:

>  On 1/7/2013 1:07 AM, Sebastian Grewe wrote:
>
> Only a chef cookbook, not a script by itself.
>
> Cheers,
> Sebastian
>
> On 07.01.2013, at 05:13, Dave MacDonald  wrote:
>
>   Hi all
> Any one got a working install script for centos 6
>
> Thanks
> Dave
>
>  Check the wiki -- I had an install script that worked with COS6.0 & 6.1,
> but some changes in perl deps mean it needs tweaking for COS 6.2 & 6.3
> I've been overworked lately with real stuff to do... once I get a free
> hour or so I'll update and check the script again...
>
> Dan
> IT4SOHO
> QMT DNS/Mirror Admin
>
> --
>
> IT4SOHO, LLC
> PO Box 507
> St. Petersburg, FL 33731-0507
>
> CALL TOLL FREE:
>   877-IT4SOHO
>
> We have support plans for QMail!
>
>
>

Re: [qmailtoaster] Centos 6

[Dan McAllister]

On 1/7/2013 1:07 AM, Sebastian Grewe wrote:

Only a chef cookbook, not a script by itself.

Cheers,
Sebastian

On 07.01.2013, at 05:13, Dave MacDonald > wrote:



Hi all
Any one got a working install script for centos 6

Thanks
Dave

Check the wiki -- I had an install script that worked with COS6.0 & 6.1, 
but some changes in perl deps mean it needs tweaking for COS 6.2 & 6.3
I've been overworked lately with real stuff to do... once I get a free 
hour or so I'll update and check the script again...


Dan
IT4SOHO
QMT DNS/Mirror Admin

--

IT4SOHO, LLC
PO Box 507
St. Petersburg, FL 33731-0507

CALL TOLL FREE:
  877-IT4SOHO

We have support plans for QMail!

Re: [qmailtoaster] Centos 6

[Sebastian Grewe]

Only a chef cookbook, not a script by itself.

Cheers,
Sebastian

On 07.01.2013, at 05:13, Dave MacDonald  wrote:

> Hi all
> Any one got a working install script for centos 6
> 
> Thanks
> Dave

Re: [qmailtoaster] Centos 6 script

[Dan McAllister]

The version of my script released 202.10.27 has some dependency issues 
with the perl modules...


I will release a new script when time permits, but I'm swamped with 
other issues at this moment.


Thanks,

Dan McAllister


On 12/17/2012 3:03 PM, Gman wrote:


Hi list

Testing on a fresh install, Centos 6.3 ( 64 Bit ), all updates

Qmail install script from Dan, CentOS 6 - Version 2012.10.27

Getting *epel-release*

./QMT-CentOS6-12.10.27.sh

QMailToaster UNOFFICIAL Build/Update for RHEL/CentOS 6 - Version 
2012.10.27


Building for x86_64 on CentOS release 6.3 (Final)

Removing conflicting mail packages...   [ DONE ]

Updating existing packages...   [ DONE ]

Checking for EPEL repository/QMT-CentOS6-12.10.27.sh: Failed to 
download latest *epel-release*... update script & re-run


Please advise.

Thanks

Dave




--

IT4SOHO, LLC
PO Box 507
St. Petersburg, FL 33731-0507

CALL TOLL FREE:
  877-IT4SOHO

We have support plans for QMail!

Re: [qmailtoaster] Centos 6 x64 Installation Notes

[Dan McAllister]

If you are on 32-bit hardware, I recommend staying with CentOS 5.6... 
but if you're insistent that you upgrade to version 6, who am I to argue...


Regardless, you are (pending 3rd-party development that may or may not 
ever arrive) looking at a "clean install" to properly upgrade from 
CentOS 5.x to CentOS 6. There does not (yet) exist a clean upgrade path 
(any more than there was a clean upgrade path from Windows XP to Windows 
Vista!)


But with regards to QMail, while trying to install on a CentOS 6 x86 
(32-bit) OS, you will have the following "issues":
 - PHP is updated to 5.3 (from 5.1) which causes many problems -- 
mostly for the toaster-admin package. Fixes are in the works, but if you 
are used to the toaster's web-based interface, you'll be very unhappy in 
CentOS 6 (the web interface is virtually blank, and therefore useless)

- If you use the vpopmail/bin command line utilities, you'll be fine
 - MySQL is updated to 5.1 (from 5.0), which won't be a problem for 
vpopmail, but may be a problem with other services or apps you may be 
running
 - BIND is updated to 9.7 (from 9.3), which wants to use DNSSEC -- if 
you're not familiar with how to do that, you'll need to learn.
- If you're using the QMT recommended djbdns, this won't be a 
problem, as you won't be using BIND at all
 - The location of the RPMBUILD folder has changed -- depending on how 
you partition your disk space, this may or not be an issue
- As noted in the earlier post, you can bypass the change with a 
symbolic link -- these 3 commands are destructive, so should be used 
only on a NEW CentOS 6 system and only used once:

   rm -rf /root/rpmbuild /usr/src/redhat
   mkdir -p /usr/src/redhat
   ln -s ../usr/src/redhat /root/rpmbuild
 - You should then be able to follow Natalio's outline and get QMT 
running on CentOS 6 32-bit just fine! The dependencies are the same.


I hope this helps...

Dan
IT4SOHO



On 7/27/2011 8:54 AM, Natalio Gatti wrote:

No, I have not installed it in 32 bits hardware.

On 7/26/2011 7:04 AM, User Qmail wrote:

Have you tried on the usual 32 bits? I wish to upgrade my centos
5.6 to centos 6.



On Tue, Jul 26, 2011 at 8:35 AM, Natalio Gatti mailto:nga...@gmail.com>> wrote:

I have just finished the installation of QT in a Centos 6 x64
box. I just wanted to my installation notes. It is not
intended to be a Howto or a Step by Step instructions. Maybe
they are usefull for someone else:

_Centos 6 x64 Install Notes - Centos Minimal Installation_

Re: [qmailtoaster] Centos 6 x64 Installation Notes

[Natalio Gatti]

No, I have not installed it in 32 bits hardware.

On 7/26/2011 7:04 AM, User Qmail wrote:
>
> Have you tried on the usual 32 bits? I wish to upgrade my centos 5.6 to
> centos 6.
>
>
>
> On Tue, Jul 26, 2011 at 8:35 AM, Natalio Gatti  wrote:
>
>> I have just finished the installation of QT in a Centos 6 x64 box. I just
>> wanted to my installation notes. It is not intended to be a Howto or a Step
>> by Step instructions. Maybe they are usefull for someone else:
>>
>>  *Centos 6 x64 Install Notes - Centos Minimal Installation*
>>
>>
>>

Re: [qmailtoaster] Centos 6 x64 Installation Notes

[Dan McAllister]

"the usual 32-bits"?

Just an opinion, but if you're running 32-bit CentOS on 32-bit hardware, 
you should stay with CentOS 5.6 for a while... it's scheduled to remain 
under full support until March 2014, and extended support for 3 more 
years after that. By that time, you should be upgraded to 64-bit 
hardware (or at least more than 4GB of RAM).


Now I don't just say that because I'm some kind of "64-bit snob" -- but 
because there is no supported upgrade from RHEL 5.x to 6 (just as there 
was no supported upgrade from RHEL 3.x to 4, or 4.x to 5). [Note: the 
jump from RHEL 3 to 4 was more significant than most because of the jump 
from the 2.4 to 2.6 in kernel versions]. In a perusal of several Linux 
and RedHat (as well as CentOS) user sites, I've seen numerous posts of 
people trying the old "burn a DVD & install it as an upgrade" method, 
only to find it just doesn't work probably because few things in 
software (much less OS software) works "by accident" -- and RedHat never 
had any intention of (and thus put no effort into) making an automatic 
upgrade path from RHEL 5 (CentOS 5) to version 6.


So where does that leave you (and why should you stay with CentOS 5.6 
for now)
 1) Some 3rd party will likely come up with an upgrade methodology for 
RHEL/CentOS 5 to 6 which will make your job relatively easy, or
 2) You'll upgrade your hardware within the next 3 years, and upgrading 
to CentOS 6 (or 7)  will be a necessity anyways (if only to access more 
than 4GB of RAM!)


Either way, if you try the upgrade now, it's gonna be time consuming and 
painful -- and a process that will likely have to be repeated when you 
want/need more than 4GB of RAM in the near future! So by holding off the 
jump into CentOS 6 for a while you'll save yourself the pain of having 
to do a complete re-build and data-copy more than once!


But there is an exception to my advise:  If your hardware is already 
64-bit and you're just not utilizing it, then I think you should rebuild 
with CentOS 6 64-bit now & get it over with.


Just my opinion -- before you complain, remember how much you paid for it!

Dan
IT4SOHO



On 7/26/2011 7:04 AM, User Qmail wrote:
Have you tried on the usual 32 bits? I wish to upgrade my centos 5.6 
to centos 6.




On Tue, Jul 26, 2011 at 8:35 AM, Natalio Gatti > wrote:


I have just finished the installation of QT in a Centos 6 x64 box.
I just wanted to my installation notes. It is not intended to be a
Howto or a Step by Step instructions. Maybe they are usefull for
someone else:

_Centos 6 x64 Install Notes - Centos Minimal Installation_

Dependencies Notes:

  * No installed: automake17 and compat-libgcc
  * Package compat-libf2c replaced by compat-libf2c-34
  * Package compat-libsdc++-33 replaced by compat-libstdc++-33
  * Centos 6 does not include sendmail, instead it includes
postfix by default
  * When postfix is removed, it also removes "crontabs" and "mrtg"
which I added later
  * When postfix is removed, it does not remove the user "postfix"
with UID 89 which conflicts with vpopmail UID

Command executed:

  * yum install make compat-libf2c-34 compat-libstdc++-33 aspell
  * yum remove postfix
  * userdel postfix

Perl Dependencies Notes:

  * Install rpmforge manually:
  o rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
  o rpm -Uvh

http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

  * Install qtp
  * Run qtp-dependencies
  * Install perl SPF package manually:
  o yum install perl-Mail-SPF-Query

Make Symbolic Link becouse centos 6 change the default rpmbuild
directory

  * ln -s /root/rpmbuild/ /usr/src/redhat

QmailToaster Installation Notes:

  * Execute install script cnt5064-install-script.sh
until installation of
"qmailadmin-toaster"
  * Install mrtg and crontabs via yum
  o yum install mrtg crontabs
  * Continue with installation script

Salutti,

Natalio.

Re: [qmailtoaster] Centos 6 x64 Installation Notes

[User Qmail]

Have you tried on the usual 32 bits? I wish to upgrade my centos 5.6 to
centos 6.



On Tue, Jul 26, 2011 at 8:35 AM, Natalio Gatti  wrote:

> I have just finished the installation of QT in a Centos 6 x64 box. I just
> wanted to my installation notes. It is not intended to be a Howto or a Step
> by Step instructions. Maybe they are usefull for someone else:
>
> *Centos 6 x64 Install Notes - Centos Minimal Installation*
>
> Dependencies Notes:
>
>- No installed: automake17 and compat-libgcc
>- Package compat-libf2c replaced by compat-libf2c-34
>- Package compat-libsdc++-33 replaced by compat-libstdc++-33
>- Centos 6 does not include sendmail, instead it includes postfix by
>default
>- When postfix is removed, it also removes "crontabs" and "mrtg" which
>I added later
>- When postfix is removed, it does not remove the user "postfix" with
>UID 89 which conflicts with vpopmail UID
>
> Command executed:
>
>- yum install make compat-libf2c-34 compat-libstdc++-33 aspell
>- yum remove postfix
>- userdel postfix
>
> Perl Dependencies Notes:
>
>- Install rpmforge manually:
>   - rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
>   - rpm -Uvh
>   
> http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
>
>
>- Install qtp
>- Run qtp-dependencies
>- Install perl SPF package manually:
>   - yum install perl-Mail-SPF-Query
>
> Make Symbolic Link becouse centos 6 change the default rpmbuild directory
>
>- ln -s /root/rpmbuild/ /usr/src/redhat
>
> QmailToaster Installation Notes:
>
>- Execute install script cnt5064-install-script.sh until installation
>of "qmailadmin-toaster"
>- Install mrtg and crontabs via yum
>   - yum install mrtg crontabs
>- Continue with installation script
>
> Salutti,
>
> Natalio.
>

Re: [qmailtoaster] centos 6

[mattias]

thanks
Dan McAllister skrev 7/22/2011 5:47 PM:
As I previously posted, I was successful at installing the QMT using 
the install script -- with one problem that had to be resolved manually.


The problem was the ezmlm-toaster package would fail dependencies for 
the gcc-compat32 libraries (which are not available for CentOS-6)... 
so I "winged it" and manually re-built with a --nodeps option and it 
built OK... (lots of warnings, no errors).


Once installed, I did test the ezmlm functionality, and it seems to 
work fine... obviously I didn't test everything, but my one mailing 
list seems to be doing what it's supposed to do.


Once I successfully re-built the ezmlm-toaster package, the remainder 
of the Install script ran just fine...


I hope this helps!

Dan
IT4SOHO


On 7/21/2011 5:56 PM, mattias wrote:

anyone running qmt on centos 6?
ny guide about how to install it there?

- 

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and 
installations.

 If you need professional help with your setup, contact them today!
- 

Please visit qmailtoaster.com for the latest news, updates, and 
packages.
 To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





- 

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and 
installations.

 If you need professional help with your setup, contact them today!
- 

Please visit qmailtoaster.com for the latest news, updates, and 
packages.
 To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com







-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] centos 6

[Dan McAllister]

As I previously posted, I was successful at installing the QMT using the 
install script -- with one problem that had to be resolved manually.


The problem was the ezmlm-toaster package would fail dependencies for 
the gcc-compat32 libraries (which are not available for CentOS-6)... so 
I "winged it" and manually re-built with a --nodeps option and it built 
OK... (lots of warnings, no errors).


Once installed, I did test the ezmlm functionality, and it seems to work 
fine... obviously I didn't test everything, but my one mailing list 
seems to be doing what it's supposed to do.


Once I successfully re-built the ezmlm-toaster package, the remainder of 
the Install script ran just fine...


I hope this helps!

Dan
IT4SOHO


On 7/21/2011 5:56 PM, mattias wrote:

anyone running qmt on centos 6?
ny guide about how to install it there?

- 

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and 
installations.

 If you need professional help with your setup, contact them today!
- 

Please visit qmailtoaster.com for the latest news, updates, and 
packages.
 To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] CentOS 6 / RHEL 6

[Jake Vickers]

On 07/19/2011 03:56 AM, Digital Instruments wrote:
I wrote, a couple of weeks ago, something to Erik about the 
short_open_tag problem.
Basically, since it's a PHP_DIR configuration option, you can add in 
.htaccess file of the toaster-admin folder short_open_tag = 1

This will change short_open_tag behavior only in toaster-admin folder.

/Cheers
A.


On 18/07/2011 20:17, Dan McAllister wrote:

Just an FYI --

I have successfully installed QMT (although not QTP) onto CentOS 6 
64-bit. However, I did have to manually build the ezmlm package 
because the gcc-compat-32 package isn't available for CentOS 6 (only 
compat-34)... never the less, with a little tweaking of the 
dependencies, I think the toaster is already reasonably compatible.


One other issue -- the toaster-admin web pages (which are all php 
scripted) don't work correctly under php 5.3.3 ... I've not yet 
looked into this (because I personally prefer to use the vpopmail 
binaries), but I'll look into the php sources once I get a free 
weekend... I'm thinking August... 2032! :-)


Dan
IT4SOHO






You meant me - unless you also emailed Erik :)
That code was all written back when PHP 4.3 was current, and there have 
been very little changes made to it since then. I'd be grateful if 
someone would submit a patch to make any coding changes to allow this to 
work with CentOS 6. If not, it is low on my list to correct at this 
time, but it will happen in the future.

Re: [qmailtoaster] CentOS 6 / RHEL 6

[Digital Instruments]

I wrote, a couple of weeks ago, something to Erik about the 
short_open_tag problem.
Basically, since it's a PHP_DIR configuration option, you can add in 
.htaccess file of the toaster-admin folder short_open_tag = 1

This will change short_open_tag behavior only in toaster-admin folder.

/Cheers
A.


On 18/07/2011 20:17, Dan McAllister wrote:

Just an FYI --

I have successfully installed QMT (although not QTP) onto CentOS 6 
64-bit. However, I did have to manually build the ezmlm package 
because the gcc-compat-32 package isn't available for CentOS 6 (only 
compat-34)... never the less, with a little tweaking of the 
dependencies, I think the toaster is already reasonably compatible.


One other issue -- the toaster-admin web pages (which are all php 
scripted) don't work correctly under php 5.3.3 ... I've not yet looked 
into this (because I personally prefer to use the vpopmail binaries), 
but I'll look into the php sources once I get a free weekend... I'm 
thinking August... 2032! :-)


Dan
IT4SOHO

Re: [qmailtoaster] CentOS 6 / RHEL 6

[Martin Waschbüsch IT-Dienstleistungen]

Hi there,

some of the problems with the admin-pages are due to short open tags in php, 
which no longer work in php53 (and they are bad style anyway).
I also tried to get a toaster running on CentOS 6, but some of the dependencies 
were tricky.

Btw, qtp works, too. But you have to manually install rpmforge for CentOS 6, so 
that things like qtp-dependencies will run.

I decided to wait for QMTv2 for any OS upgrades. Who knows, maybee that'll be 
out before you get around to looking at the php sources. ;-) - One can always 
hope.

Cheers, 

Martin

--
Martin Waschbüsch
IT-Dienstleistungen
Lautensackstr. 16
80687 München

Telefon: +49 89 57005708
Fax: +49 89 57868023
Mobil: +49 170 2189794
serv...@waschbuesch.it
http://www.waschbuesch.it

Am 18.07.2011 um 20:17 schrieb Dan McAllister:

> Just an FYI --
> 
> I have successfully installed QMT (although not QTP) onto CentOS 6 64-bit. 
> However, I did have to manually build the ezmlm package because the 
> gcc-compat-32 package isn't available for CentOS 6 (only compat-34)... never 
> the less, with a little tweaking of the dependencies, I think the toaster is 
> already reasonably compatible.
> 
> One other issue -- the toaster-admin web pages (which are all php scripted) 
> don't work correctly under php 5.3.3 ... I've not yet looked into this 
> (because I personally prefer to use the vpopmail binaries), but I'll look 
> into the php sources once I get a free weekend... I'm thinking August... 
> 2032! :-)
> 
> Dan
> IT4SOHO
> 
> 
> -- 
> 
> IT4SOHO, LLC
> PO Box 507
> St. Petersburg, FL 33731-0507
> 
> CALL TOLL FREE:
> 877-IT4SOHO
> 
> 877-484-7646 Phone
> 727-490-4394 Fax
> 
> "We make IT work for small business!"
> 
> 
> 
> -
> Qmailtoaster is sponsored by Vickers Consulting Group 
> (www.vickersconsulting.com)
>  Vickers Consulting Group offers Qmailtoaster support and installations.
>If you need professional help with your setup, contact them today!
> -
>   Please visit qmailtoaster.com for the latest news, updates, and packages.
>To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>   For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 
> 


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] CentOS 6

[South Computers]

If anyone wants to get ahead of the game, you might try scientificlinux. 
Another nice (well supported) rebuild of RHel. Got a box running it here 
if anyone (that I know) wants access.


Eric Shubert wrote:
Just an FYI, COS6 is scheduled to be rolling out to mirrors this 
coming Sunday 6/12, which means it should be available for download on 
Monday. Anyone planning to do a QMT install on one right away?




-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] CentOS 6

[Dan McAllister]

This won't be a simple PLUG-n-PLAY -- there are many significant updates 
to CentOS 6 (MySQL and PHP among the ones I suspect will give us grief!)


That being said, we're a CentOS mirror site, so I'll be able to start 
work on something like a QMT install as early as Monday... and I have a 
free 64-bit box, so I can test both 64-bit & 32-bit builds.


Dan McAllister
IT4SOHO

On 6/8/2011 6:40 PM, Eric Shubert wrote:
Just an FYI, COS6 is scheduled to be rolling out to mirrors this 
coming Sunday 6/12, which means it should be available for download on 
Monday. Anyone planning to do a QMT install on one right away?




-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com