Re: [qmailtoaster] Crontab message

[Peter Peterse]

Hi Eric,

Thanks for this solution.
So this was a left over of the update. What does dh_key do?

Regards,
Peter


Eric Broch  schreef op 23 april 2024 15:18:38 CEST:
> vi /etc/crontab
>
>remove
>
> 01 01 * * * root /var/qmail/bin/dh_key 2>&1 > /dev/null
>
>
>On 4/23/2024 7:10 AM, Eric Broch wrote:
>> look in the cron file and delete the call to dh_key
>> 
>> On 4/23/2024 2:49 AM, pe...@peterse-uithuizen.com wrote:
>>> Hello list,
>>> 
>>> Do you also get every night the message:
>>> /bin/bash: line 1: /var/qmail/bin/dh_key: No such file or directory
>>> 
>>> I've seen this message after the update of qmail. Is it a new setting?
>>> 
>>> Regards,
>>> Peter P.
>>> 
>>> -
>>> 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
>> 
>
>-
>To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>

Re: [qmailtoaster] error message spamd: still running as root

[Peter Peterse]

Hi Eric,

My /etc/sysconfig/spamassassin looks like:

# Options to spamd
SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"


I will try yours.

thanks,
Peter

On 4-4-2024 23:56, Eric Broch wrote:

# cat  /etc/sysconfig/spamassassin
# Options to spamd
#SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"

SPAMDOPTIONS="--create-prefs -m10 -q -x -u clamscan"

What's in your /etc/sysconfig/spamassassin file?

On 4/4/2024 2:21 PM, Peter Peterse wrote:
still running as root: user not specified with -u, not found, or set 
to root, falling back to nobody


-
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

[qmailtoaster] error message spamd: still running as root

[Peter Peterse]

Hi list,

In my logfile /var/log/maillog I see multiple times the message:
spamd: still running as root: user not specified with -u, not found, or 
set to root, falling back to nobody


Is this what I should want? I guess not, but how can I solve this.

Regards,
Peter

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

Re: [qmailtoaster] Certificate Error

[Peter Peterse]

Yeh, but the email software didn't accept the ecdsa key. I've tried the key 
order but keeps failing. But now I've seen this thread it could be a config 
option.

Greets,
Peter

Gary Bowling  schreef op 23 maart 2024 12:36:21 CET:
>
>Thanks Peter, good to know as it looks like they are going to ecdsa for the 
>default.
>
>
>On 3/23/2024 3:18 AM, Peter Peterse wrote:
>
>Hi,
>
> Letsencrypt van generate rsa keys by using --key-type rsa 
>
> The order in my servercert.pem is private key followed by the fullchain file. 
> I'm using Almalinux 9
>
> Regards,
> Peter
>
>
>
>g...@gbco.us <mailto:g...@gbco.us> schreef op 23 maart 2024 00:05:48 CET:
>
> It looks like letsencrypt is now using ecdsa by default. So I went back and 
> copied my certs off my old server, probably not what I really want to do. But 
> it did give me a different error. Now I'm getting this one. Sending of the 
> message failed. The Outgoing server (SMTP) mail.gbco.us does not seem to 
> support encrypted passwords. If you just set up the account, try changing the 
> 'Authentication method' in 'Account settings | Outgoing server (SMTP)' to 
> 'Normal password'. I thought I tested this before with the new server, but 
> maybe I didn't test it correctly. Anyone got any ideas? On 2024-03-22 18:29, 
> g...@gbco.us <mailto:g...@gbco.us> wrote: 
>
>I can send mail via the roundcube web mail. That's where this message is 
>coming from. When sending mail from thunderbird, I have my smtp server set up 
>in my client as Port 587 startTLS Encrypted Password This is the same as I had 
>with a number of clients on my old server. When I try to send email, I get 
>this error. Sending of the message failed. An error occurred while sending 
>mail: Outgoing server (SMTP) error. The server responded: TLS no valid RSA 
>private key: error:8002:system library::No such file or directory 
>(#4.3.0). To create certificates on my new server. I retrieved certs from 
>letencrypt and then did this. cp -p /var/qmail/control/servercert.pem 
>/var/qmail/control/servercert.pem.lastmonth cat 
>/etc/letsencrypt/live/mail.gbco.us/{cert,chain,fullchain,privkey}.pem 
>
>/var/qmail/control/servercert.pem 
>
> chown vpopmail:qmail /var/qmail/control/servercert.pem chmod 640 
> /var/qmail/control/servercert.pem Any idea what's going on with this error? 
> thanks, Gary
>To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
><mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> For additional 
>commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
><mailto:qmailtoaster-list-h...@qmailtoaster.com> 
>
>To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
><mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> For additional 
>commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
><mailto: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] Certificate Error

[Peter Peterse]

Hi,

Letsencrypt van generate rsa keys by using --key-type rsa 

The order in my servercert.pem is private key followed by the fullchain file. 
I'm using Almalinux 9

Regards,
Peter


g...@gbco.us schreef op 23 maart 2024 00:05:48 CET:
>
>It looks like letsencrypt is now using ecdsa by default.
>
>So I went back and copied my certs off my old server, probably not what I 
>really want to do. But it did give me a different error. Now I'm getting this 
>one.
>
>Sending of the message failed.
>The Outgoing server (SMTP) mail.gbco.us does not seem to support encrypted 
>passwords. If you just set up the account, try changing the 'Authentication 
>method' in 'Account settings | Outgoing server (SMTP)' to 'Normal password'.
>
>
>I thought I tested this before with the new server, but maybe I didn't test it 
>correctly. Anyone got any ideas?
>
>
>
>
>On 2024-03-22 18:29, g...@gbco.us wrote:
>> I can send mail via the roundcube web mail. That's where this message
>> is coming from.
>> 
>> When sending mail from thunderbird, I have my smtp server set up in my 
>> client as
>> 
>> Port 587
>> startTLS
>> Encrypted Password
>> 
>> This is the same as I had with a number of clients on my old server.
>> 
>> When I try to send email, I get this error.
>> 
>> Sending of the message failed.
>> An error occurred while sending mail: Outgoing server (SMTP) error.
>> The server responded:  TLS no valid RSA private key:
>> error:8002:system library::No such file or directory
>> (#4.3.0).
>> 
>> 
>> To create certificates on my new server. I retrieved certs from
>> letencrypt and then did this.
>> 
>> cp -p /var/qmail/control/servercert.pem
>> /var/qmail/control/servercert.pem.lastmonth
>> cat
>> /etc/letsencrypt/live/mail.gbco.us/{cert,chain,fullchain,privkey}.pem
>> > /var/qmail/control/servercert.pem
>> 
>> chown vpopmail:qmail /var/qmail/control/servercert.pem
>> chmod 640 /var/qmail/control/servercert.pem
>> 
>> 
>> 
>> Any idea what's going on with this error?
>> 
>> thanks, Gary
>> 
>> -
>> 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
>

[qmailtoaster] Authentication on new qmailtoaster

[Peter Peterse]

Hi list,

On my new mail server AlmaLinux 9.2 the authentication doesn't work.

While trying to get the message from my server thunderbird reply

The incommingserver (IMAP) mymailserver.example.com does not seem to 
support encrypted passwords. If you just set up the account, try 
changing the 'Authentication method' in 'Account settings | Outgoing 
server (SMTP)' to 'Normal password'.


I've migrate the server with the procedure described on 
http://www.qmailtoaster.com/migrate.html


Did I've done something wrong?

When I change my configuration in Thunderbird so that it uses plaintext 
passwords it looks like it works, but than all my users needs to change 
there configfiles.


Thanks for helping me.

Regards,

Peter



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

Re: [qmailtoaster] Migrate from CentOS 7 to Alma 9.3

[Peter Peterse]

Yes I found it.

https://raw.githubusercontent.com/qmtoaster/scripts/master/convpop

wget https://raw.githubusercontent.com/qmtoaster/scripts/master/convpop

chmod a+x convpop

./convpop

Now the table vpopmail will be created and after as start/stop of 
qmailtoaster I can login into roundcube.


Thanks for your help.

Regards,

Peter Peterse

On 28-1-2024 20:06, Peter Peterse wrote:


Hi Remo,

That part looks just like mine. It comes from: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/dovecot-sql.conf.ext


Do you have a table vpopmail? I don't and also don't understand where 
it should be created.


Peter


On 28-1-2024 19:57, Remo Mattei wrote:

Here is mine

default_pass_scheme = MD5-CRYPT


# passdb query to retrieve the password. It can return fields:
password_query = SELECT CONCAT( pw_name ,'@', pw_domain ) AS user, \
     pw_passwd AS password, \
     pw_dir as userdb_home, \
     89 AS userdb_uid, \
     89 AS userdb_gid \
     FROM vpopmail vp \
     LEFT JOIN aliasdomains ad ON ad.alias = '%d' \
     WHERE  ( vp.pw_domain = ad.domain  OR vp.pw_domain = '%d') AND ( 
vp.pw_name = '%n' )



#password_query = SELECT CONCAT(pw_name, '@', '%d') AS user, \
#  pw_passwd AS password, \
#  pw_dir as userdb_home, \
#  89 AS userdb_uid, \
#  89 AS userdb_gid \
#  FROM `vpopmail` \
#  WHERE pw_name = '%n' AND pw_domain = '%d'

# userdb query to retrieve the user information. It can return fields:
# (Thanks to Arturo Blanco for his hints concerning vpopmail limits)
user_query = \
  SELECT pw_dir AS home, \
  89 AS uid, \
  89 AS gid \
  FROM vpopmail \
  WHERE pw_name = '%n' AND pw_domain = '%d' \
  AND ('%a'!='995' or !(pw_gid & 2)) \
  AND ('%r'!='[WEBMAIL-IP]' or !(pw_gid & 4)) \
  AND ('%r'='[WEBMAIL-IP]' or '%a'!='993' or !(pw_gid & 8))

# [WEBMAIL-IP] is the IP of your webmail web server.
# I'm assuming that the imap connection is only on port 993 and the 
pop3 connection is on port 955.

# Adjust to your needs
#
# logically this means:
# SELECT user
# WHEN POP is not disabled for that user connecting on port 995 (995 
is the pop3s port allowed from remote in my configuration)
# AND WHEN webmail access is not disabled for that user when 
connecting from [WEBMAIL-IP]
# AND WHEN IMAP is not disabled for that user connecting on port 993 
(993 is the imaps port allowed from remote
# in my configuration) unless his remote ip the one belonging to the 
webmail


# Query to get a list of all usernames.
iterate_query = SELECT CONCAT(pw_name,'@',pw_domain) AS username FROM 
`vpopmail`




Here is my dovecot.conf part

protocol imap {
  imap_client_workarounds = "delay-newmail"
  mail_plugins = $mail_plugins imap_quota
  mail_max_userip_connections = 150
}

protocol pop3 {
  pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
  pop3_fast_size_lookups = yes
  pop3_lock_session = yes
  mail_max_userip_connections = 50
# pop3_uidl_format = UID%u-%v
}

plugin {
  quota = maildir:ignore=Trash
  quota_rule = ?:storage=0
}

passdb {
  driver = sql
  args = /etc/dovecot/dovecot-sql.conf.ext
}

userdb {
  driver = sql
  args = /etc/dovecot/dovecot-sql.conf.ext
}



service stats {
# unix_listener stats-reader {
#     group =
#     mode = 0666
#     user =
#   }
   unix_listener stats-writer {
     group = dovecot
     mode = 0666
#user =
   }
  }

!include local.conf




On Jan 28, 2024, at 19:33, Peter Peterse 
 wrote:


Hello,

Remo, thanks fot the fast answer. I've changed the file 
/etc/dovecot/dovecot.conf back to how it was after the script 
qt_install.


Dovecot logs now:

Jan 28 18:24:28 auth-worker(63869): Warning: sqlpool(mysql): Query 
failed, retrying: Table 'vpopmail.vpopmail' doesn't exist
Jan 28 18:24:28 auth-worker(63869): Error: conn unix:auth-worker 
(pid=63867,uid=97): auth-worker<1>: 
sql(pe...@example.com,::1,): 
Password query failed: Table 'vpopmail.vpopmail' doesn't exist


In the file dovecot-sql.conf.ext the credentials are correct and the 
database vpopmail exists but there is no table vpopmail created, so 
probebly this is the problem. Where is this table created?


Regards,

Peter Peterse

On 28-1-2024 18:52, Remo Mattei wrote:

It’s now sql not vpopmail

--
Sent from iPhone

On domenica, gen 28, 2024 at 18:41, Peter Peterse
 wrote:
Hello list,

I'm trying to migrate from CentOS 7 to AlmaLinux 9.3. I'm using
the
steps from:

http://qtp.qmailtoaster.com/#rhel9

and

http://www.qmailtoaster.com/migrate.html

In this process I've changed the database passwords in the files:

/home/vpopmail/etc/vpopmail.mysql
/etc/roundcubemail/config.inc.php
/etc/dovecot/dovecot-sql.conf.ext
/etc/dspam.conf

After starting the mailserver and logging in with roundcube the
logs
from dovecot says:

Jan 28 17:29:53 master: Info: Dovecot v2.3.16 (7e2e900c1a)
starting up
for imap, pop3 (core dumps disabled)
Jan 28 17:30:15 auth: Fatal: Unknown passdb driver 'vpopmail'
Jan 28 17:30:15

Re: [qmailtoaster] Migrate from CentOS 7 to Alma 9.3

[Peter Peterse]

Hi Remo,

That part looks just like mine. It comes from: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/dovecot-sql.conf.ext


Do you have a table vpopmail? I don't and also don't understand where it 
should be created.


Peter


On 28-1-2024 19:57, Remo Mattei wrote:

Here is mine

default_pass_scheme = MD5-CRYPT


# passdb query to retrieve the password. It can return fields:
password_query = SELECT CONCAT( pw_name ,'@', pw_domain ) AS user, \
     pw_passwd AS password, \
     pw_dir as userdb_home, \
     89 AS userdb_uid, \
     89 AS userdb_gid \
     FROM vpopmail vp \
     LEFT JOIN aliasdomains ad ON ad.alias = '%d' \
     WHERE  ( vp.pw_domain = ad.domain  OR vp.pw_domain = '%d') AND ( 
vp.pw_name = '%n' )



#password_query = SELECT CONCAT(pw_name, '@', '%d') AS user, \
#  pw_passwd AS password, \
#  pw_dir as userdb_home, \
#  89 AS userdb_uid, \
#  89 AS userdb_gid \
#  FROM `vpopmail` \
#  WHERE pw_name = '%n' AND pw_domain = '%d'

# userdb query to retrieve the user information. It can return fields:
# (Thanks to Arturo Blanco for his hints concerning vpopmail limits)
user_query = \
  SELECT pw_dir AS home, \
  89 AS uid, \
  89 AS gid \
  FROM vpopmail \
  WHERE pw_name = '%n' AND pw_domain = '%d' \
  AND ('%a'!='995' or !(pw_gid & 2)) \
  AND ('%r'!='[WEBMAIL-IP]' or !(pw_gid & 4)) \
  AND ('%r'='[WEBMAIL-IP]' or '%a'!='993' or !(pw_gid & 8))

# [WEBMAIL-IP] is the IP of your webmail web server.
# I'm assuming that the imap connection is only on port 993 and the 
pop3 connection is on port 955.

# Adjust to your needs
#
# logically this means:
# SELECT user
# WHEN POP is not disabled for that user connecting on port 995 (995 
is the pop3s port allowed from remote in my configuration)
# AND WHEN webmail access is not disabled for that user when 
connecting from [WEBMAIL-IP]
# AND WHEN IMAP is not disabled for that user connecting on port 993 
(993 is the imaps port allowed from remote
# in my configuration) unless his remote ip the one belonging to the 
webmail


# Query to get a list of all usernames.
iterate_query = SELECT CONCAT(pw_name,'@',pw_domain) AS username FROM 
`vpopmail`




Here is my dovecot.conf part

protocol imap {
  imap_client_workarounds = "delay-newmail"
  mail_plugins = $mail_plugins imap_quota
  mail_max_userip_connections = 150
}

protocol pop3 {
  pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
  pop3_fast_size_lookups = yes
  pop3_lock_session = yes
  mail_max_userip_connections = 50
# pop3_uidl_format = UID%u-%v
}

plugin {
  quota = maildir:ignore=Trash
  quota_rule = ?:storage=0
}

passdb {
  driver = sql
  args = /etc/dovecot/dovecot-sql.conf.ext
}

userdb {
  driver = sql
  args = /etc/dovecot/dovecot-sql.conf.ext
}



service stats {
# unix_listener stats-reader {
#     group =
#     mode = 0666
#     user =
#   }
   unix_listener stats-writer {
     group = dovecot
     mode = 0666
#user =
   }
  }

!include local.conf




On Jan 28, 2024, at 19:33, Peter Peterse 
 wrote:


Hello,

Remo, thanks fot the fast answer. I've changed the file 
/etc/dovecot/dovecot.conf back to how it was after the script qt_install.


Dovecot logs now:

Jan 28 18:24:28 auth-worker(63869): Warning: sqlpool(mysql): Query 
failed, retrying: Table 'vpopmail.vpopmail' doesn't exist
Jan 28 18:24:28 auth-worker(63869): Error: conn unix:auth-worker 
(pid=63867,uid=97): auth-worker<1>: 
sql(pe...@example.com,::1,): 
Password query failed: Table 'vpopmail.vpopmail' doesn't exist


In the file dovecot-sql.conf.ext the credentials are correct and the 
database vpopmail exists but there is no table vpopmail created, so 
probebly this is the problem. Where is this table created?


Regards,

Peter Peterse

On 28-1-2024 18:52, Remo Mattei wrote:

It’s now sql not vpopmail

--
Sent from iPhone

On domenica, gen 28, 2024 at 18:41, Peter Peterse
 wrote:
Hello list,

I'm trying to migrate from CentOS 7 to AlmaLinux 9.3. I'm using the
steps from:

http://qtp.qmailtoaster.com/#rhel9

and

http://www.qmailtoaster.com/migrate.html

In this process I've changed the database passwords in the files:

/home/vpopmail/etc/vpopmail.mysql
/etc/roundcubemail/config.inc.php
/etc/dovecot/dovecot-sql.conf.ext
/etc/dspam.conf

After starting the mailserver and logging in with roundcube the
logs
from dovecot says:

Jan 28 17:29:53 master: Info: Dovecot v2.3.16 (7e2e900c1a)
starting up
for imap, pop3 (core dumps disabled)
Jan 28 17:30:15 auth: Fatal: Unknown passdb driver 'vpopmail'
Jan 28 17:30:15 master: Error: service(auth): command startup
failed,
throttling for 2.000 secs

Does anyone knows what I've missed?

    Thanks for the help.

Peter Peterse


-

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

Re: [qmailtoaster] Migrate from CentOS 7 to Alma 9.3

[Peter Peterse]

Hello,

Remo, thanks fot the fast answer. I've changed the file 
/etc/dovecot/dovecot.conf back to how it was after the script qt_install.


Dovecot logs now:

Jan 28 18:24:28 auth-worker(63869): Warning: sqlpool(mysql): Query 
failed, retrying: Table 'vpopmail.vpopmail' doesn't exist
Jan 28 18:24:28 auth-worker(63869): Error: conn unix:auth-worker 
(pid=63867,uid=97): auth-worker<1>: 
sql(pe...@example.com,::1,): Password 
query failed: Table 'vpopmail.vpopmail' doesn't exist


In the file dovecot-sql.conf.ext the credentials are correct and the 
database vpopmail exists but there is no table vpopmail created, so 
probebly this is the problem. Where is this table created?


Regards,

Peter Peterse

On 28-1-2024 18:52, Remo Mattei wrote:

It’s now sql not vpopmail

--
Sent from iPhone

On domenica, gen 28, 2024 at 18:41, Peter Peterse
 wrote:
Hello list,

I'm trying to migrate from CentOS 7 to AlmaLinux 9.3. I'm using the
steps from:

http://qtp.qmailtoaster.com/#rhel9

and

http://www.qmailtoaster.com/migrate.html

In this process I've changed the database passwords in the files:

/home/vpopmail/etc/vpopmail.mysql
/etc/roundcubemail/config.inc.php
/etc/dovecot/dovecot-sql.conf.ext
/etc/dspam.conf

After starting the mailserver and logging in with roundcube the logs
from dovecot says:

Jan 28 17:29:53 master: Info: Dovecot v2.3.16 (7e2e900c1a)
starting up
for imap, pop3 (core dumps disabled)
Jan 28 17:30:15 auth: Fatal: Unknown passdb driver 'vpopmail'
Jan 28 17:30:15 master: Error: service(auth): command startup failed,
throttling for 2.000 secs

Does anyone knows what I've missed?

Thanks for the help.

    Peter Peterse


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

[qmailtoaster] Migrate from CentOS 7 to Alma 9.3

[Peter Peterse]

Hello list,

I'm trying to migrate from CentOS 7 to AlmaLinux 9.3. I'm using the 
steps from:


http://qtp.qmailtoaster.com/#rhel9

and

http://www.qmailtoaster.com/migrate.html

In this process I've changed the database passwords in the files:

/home/vpopmail/etc/vpopmail.mysql
/etc/roundcubemail/config.inc.php
/etc/dovecot/dovecot-sql.conf.ext
/etc/dspam.conf

After starting the mailserver and logging in with roundcube the logs 
from dovecot says:


Jan 28 17:29:53 master: Info: Dovecot v2.3.16 (7e2e900c1a) starting up 
for imap, pop3 (core dumps disabled)

Jan 28 17:30:15 auth: Fatal: Unknown passdb driver 'vpopmail'
Jan 28 17:30:15 master: Error: service(auth): command startup failed, 
throttling for 2.000 secs


Does anyone knows what I've missed?

Thanks for the help.

Peter Peterse


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

[qmailtoaster] Https error on www.qmailtoaster.org

[Peter Peterse]

Hello all,

I am trying tot install qmailtoaster, but it's complaining that the certificate 
is not valid. 
Because it is a Lets encrypt certificate I think the acme proces is not up2date.

Regards,
Peter

-- 
Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.

Re: [qmailtoaster] Clam AV - Epel

[Peter Peterse]

Hello,

I had the same problems. Also after the:
yum --disablerepo=qmt-current update

I reboot the system and httpd won't start. After removing the line:
Include /etc/httpd/conf/squirrelmail.conf

httpd will start without any problems.

regards, Peter

Op 11-8-2020 om 02:59 schreef Gary Bowling:



Yes Remo, not a clamav thing. Just something that happened when I 
updated my machine. Just added it in case anyone else had the same 
problem.



I also have now found that "mailman" was also enabled when I updated 
my machine. I started getting kicked back messages in the postmaster 
mailbox that were addressed to "mail...@mail.gbco.us" I've never used 
mailman for anything, so not sure how that got enabled. Was easy to 
take care of with a systemctl stop mailman and a systemctl disable 
mailman.



Thanks, Gary



On 8/10/2020 8:49 PM, r...@mattei.org wrote:

That should not depend on clamav

Remo
Il giorno 10 ago 2020, alle ore 17:26, Gary Bowling  ha 
scritto:





Thanks Eric, that worked a charm.


However, the update busted httpd. Turns out the httpd.conf file had 
this at the end.



Include /etc/httpd/conf/squirrelmail.conf


But that file no longer exists. Since it does exist in 
/etc/httpd/conf.d/ which gets loaded as well, I commented it out in 
the httpd.conf file. Seems to work and squirrelmail seems to be ok.



All is well. Thanks!


Gary



On 8/10/2020 8:05 PM, Eric Broch wrote:


add --disablerepo=qmt-current

On 8/10/2020 5:57 PM, Gary Bowling wrote:



Just tried "yum updating" my server. I recall some notes back and 
forth about updating clamav since we're moving to the epel 
version. Just want to make sure I don't screw something up.



Below is what I got when I tried to update. I think what I need to 
do is remove the old clamav, clamav-lib, clamav-filesystem and 
then install them again via epel? Or should I just do a "yum 
update --skip-broken" ?



Thanks in advance for the advice.


Error: Package: clamav-0.102.3-1.el7.x86_64 (@epel)
   Requires: clamav-lib = 0.102.3-1.el7
   Removing: clamav-lib-0.102.3-1.el7.x86_64 (@epel)
   clamav-lib = 0.102.3-1.el7
   Updated By: clamav-lib-0.102.4-1.el7.x86_64 (epel)
   clamav-lib = 0.102.4-1.el7
Error: Package: clamav-0.102.3-1.el7.x86_64 (@epel)
   Requires: clamav-filesystem = 0.102.3-1.el7
   Removing: clamav-filesystem-0.102.3-1.el7.noarch (@epel)
   clamav-filesystem = 0.102.3-1.el7
   Updated By: clamav-filesystem-0.102.4-1.el7.noarch (epel)
   clamav-filesystem = 0.102.4-1.el7
Error: clamav-filesystem conflicts with clamav-0.102.3-1.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest



--

Gary Bowling
The Moderns on Spotify 



- 
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


-
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 



--
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

Re: [qmailtoaster] letsencrypt certificate issue

[Peter Peterse]

Hi,

Are the dovecot and qmail services restarted?

Regarts,
Peter

Solo  schreef op 29 april 2020 11:42:10 CEST:
>
>Hi.
>
>I think Letsencrypt are for websites/servers and not for the specifik 
>email which require another type of certificate than Letsencrypt issues
>
>- usually that is set up when qmail is installed (openssl) and placed 
>/var/qmail/
>
>/Finn vB
>
>Den 29-04-2020 kl. 10:52 skrev ChandranManikandan:
>> Hi Remo,
>> 
>> FYI
>> ssl_cert = > 
>> ssl_key = > 
>> # the following will likely be the default at some point
>> ssl_dh_parameters_length = 2048
>> 
>> 
>> On Wed, Apr 29, 2020 at 11:48 AM Remo Mattei > > wrote:
>> 
>> You need to check the /etc/dovecot/toaster.conf file that’s where
>> the cert for outlook and thunder lives.
>> 
>> Remo
>> 
>>> On Apr 28, 2020, at 20:38, ChandranManikandan >> > wrote:
>>>
>>> Hi Friends,
>>>
>>> certbot renew command showing below message
>>> Saving debug log to /var/log/letsencrypt/letsencrypt.log
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>-
>>> - - - - - - -
>>> Processing /etc/letsencrypt/renewal/xxx.com.conf
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>-
>>> - - - - - - -
>>> Cert not yet due for renewal
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>-
>>> - - - - - - -
>>>
>>> The following certs are not due for renewal yet:
>>>   /etc/letsencrypt/live/xxx.com/fullchain.pem
>>>  expires on 2020-06-27 (skipped)
>>> No renewals were attempted.
>>> - - - - - - - - - - - - - - -
>>>
>>> But outlook, thunderbird showing the certificate issue and
>>> certificate expire date is showing 28-Apr-2020 in thunderbird,
>>> I have checked in website in the same certificate expiry date is
>>> showing 27-06-2020.
>>>
>>> Do i anything done mistake.
>>> How do i check and fix the above issue.
>>> Could anyone help me.
>>> Appreciate your help.
>>>
>>> Note: Centos 7 with qmailtoaster
>>> -- 
>>> */Regards,
>>> Manikandan.C
>>> /*
>> 
>> 
>> 
>> -- 
>> */Regards,
>> Manikandan.C
>> /*
>
>-
>To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>For additional commands, e-mail:
>qmailtoaster-list-h...@qmailtoaster.com

-- 
Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.

Re: [qmailtoaster] qmailadmin stopped working.

[Peter Peterse]

Backup the old server
Install CentOS 7!
Restore a backup.

Don't user CentOS 5 any more.

Regards,
Peter



"Tommi Järvilehto"  schreef op 1 juli 2017 
11:14:34 CEST:
>What is the best way to src rebuild and reinstall just the qmailadmin?
>
>On 5.6.2017 9:14, Tommi Järvilehto wrote:
>> Hello,
>>
>> We have couple of CentOs5 qmailtoaster servers that has problem with 
>> qmailadmin. Web browser gives 500 internal server error
>>
>> These servers has been running fine dont know when this problem has 
>> started. Only thing that has changed on those are 'yum update' and
>the 
>> https ciphers has been made stronger. No other additional installs.
>>
>> httpd error log:
>>
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] *** glibc
>detected 
>> *** /usr/share/qmailadmin/index.cgi: free(): invalid next size
>(fast): 
>> 0x0811c308 ***
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] ===
>Backtrace: 
>> =
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /lib/libc.so.6[0xc0ea15]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /lib/libc.so.6(cfree+0x59)[0xc12a89]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /usr/share/qmailadmin/index.cgi[0x804b3ec]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /usr/share/qmailadmin/index.cgi[0x804a344]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /lib/libc.so.6(__libc_start_main+0xdc)[0xbbaedc]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 
>> /usr/share/qmailadmin/index.cgi[0x804a1c1]
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] === Memory 
>> map: 
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 001ee000-0030f000
>
>> r-xp  fd:00 92995597 /usr/lib/mysql/libmysqlclient.so.15.0.0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0030f000-00351000
>
>> rwxp 0012 fd:00 92995597 /usr/lib/mysql/libmysqlclient.so.15.0.0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00351000-00352000
>
>> rwxp 00351000 00:00 0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 003ca000-00405000
>
>> r-xp  fd:00 112757752 /lib/libsepol.so.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00405000-00406000
>
>> rwxp 0003b000 fd:00 112757752 /lib/libsepol.so.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00406000-0041
>
>> rwxp 00406000 00:00 0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00412000-00428000
>
>> r-xp  fd:00 112757753 /lib/libselinux.so.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00428000-0042a000
>
>> rwxp 00015000 fd:00 112757753 /lib/libselinux.so.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00498000-004ad000
>
>> r-xp  fd:00 112754991 /lib/libnsl-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 004ad000-004ae000
>
>> r-xp 00014000 fd:00 112754991 /lib/libnsl-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 004ae000-004af000
>
>> rwxp 00015000 fd:00 112754991 /lib/libnsl-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 004af000-004b1000
>
>> rwxp 004af000 00:00 0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 004b3000-004fa000
>
>> r-xp  fd:00 43450397 /lib/libssl.so.0.9.8e
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 004fa000-004fe000
>
>> rwxp 00046000 fd:00 43450397 /lib/libssl.so.0.9.8e
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0051e000-00648000
>
>> r-xp  fd:00 112757756 /lib/libcrypto.so.0.9.8e
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00648000-0065b000
>
>> rwxp 0012a000 fd:00 112757756 /lib/libcrypto.so.0.9.8e
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0065b000-0065f000
>
>> rwxp 0065b000 00:00 0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00851000-00862000
>
>> r-xp  fd:00 112757751 /lib/libresolv-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00862000-00863000
>
>> r-xp 0001 fd:00 112757751 /lib/libresolv-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00863000-00864000
>
>> rwxp 00011000 fd:00 112757751 /lib/libresolv-2.5.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00864000-00866000
>
>> rwxp 00864000 00:00 0
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 00868000-0086a000
>
>> r-xp  fd:00 112757750 /lib/libkeyutils-1.2.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0086a000-0086b000
>
>> rwxp 1000 fd:00 112757750 /lib/libkeyutils-1.2.so
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0087d000-0087f000
>
>> r-xp  fd:00 112757754 /lib/libcom_err.so.2.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0087f000-0088
>
>> rwxp 1000 fd:00 112757754 /lib/libcom_err.so.2.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 0089a000-008c
>
>> r-xp  fd:00 84027848 /usr/lib/libk5crypto.so.3.1
>> [Mon Jun 05 08:11:30 2017] [error] [client x.x.x.x] 008c-008c1000
>
>> rwxp 

Re: [qmailtoaster] SMTP run script

[Peter Peterse]

Tony,

Thanks a lot. It's working again.

Regards,
Peter

Tony White  schreef op 10 februari 2017 14:41:01 CET:
>Any help to you?
>
>#!/bin/sh
>QMAILDUID=`id -u vpopmail`
>NOFILESGID=`id -g vpopmail`
>MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
>SPAMDYKE="/usr/local/bin/spamdyke"
>SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
>SMTPD="/var/qmail/bin/qmail-smtpd"
>TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
>HOSTNAME=`hostname`
>VCHKPW="/home/vpopmail/bin/vchkpw"
>REQUIRE_AUTH=0
>
>exec /usr/bin/softlimit -m 6400 \
>  /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
>  -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
>  $SPAMDYKE --config-file $SPAMDYKE_CONF \
>  $SMTPD $VCHKPW /bin/true 2>&1
>
>best wishes
>   Tony White
>
>
>On 10/02/2017 23:20, pe...@peterse-uithuizen.com wrote:
>> Hello all,
>>
>> does anyone knows where to find a right copy of the script
>/var/qmail/supervise/smtp/run?
>>
>> I screwed the file by accident.
>>
>> Regards,
>> Peter
>>
>> -
>> 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

-- 
Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.

Re: [qmailtoaster] qmailtoaster very slow

[Peter Peterse]

Maybe an update could give you some security fixes.

Giuseppe Perna gpe...@csait.eu schreef op 5 februari 2015 20:39:38 CET:
Hello ,
i have qmailtoaster-plus-0.2.14-1.317
vpopnmail-toaster5.4.17-1.3.4
vqadmin-toaster 2.3.4-1.3.3
ecc..

my server is a centos 4.6 i686
There are about 1000 mailboxes
this server inherited, at certain times of the day is very slow, the
webmail does not work and the SMTP connection is rejected with error:
user does not exist on the system.

maybe I could use a good anti-spam spamdyke type, but are still not
sure, how do I do a bit of trabolsutting?

thank all

-- 




Giuseppe

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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [qmailtoaster] Re: Install QT on CentOS 6.6 x64

[Peter Peterse]

Eric Shubert schreef op 3-12-2014 1:49:
 This looks like you pasted the same thing twice in the message, and I
 don't see anything that indicate an error other than the 2 You could
 try ... lines.

 Again?
 Thanks.

Hello Eric,

it looks like there were some repositories last monday not online. Today
the installation script works great.


-- 
regards,

Peter Peterse

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

[qmailtoaster] Install QT on CentOS 6.6 x64

[Peter Peterse]

Hello List,

I'm trying to install Qmailtoaster on a minimal installation of CentOS 6.6.
The installation steps are from:
https://github.com/QMailToaster/qmailtoaster-util/blob/master/README.install
steps 1 and 2 are working but with step qt-install it looks like there
are missing packages.
There is no mysql server, Perl, httpd and libev.

Am I missing some other? Is there a change in de minimal installation of
CentOS 6.6, so that the script qt-install need to be changed?

-- 
Regards,

Peter Peterse

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

Re: [qmailtoaster] Install QT on CentOS 6.6 x64

[Peter Peterse]

Hello all,

Some additional information:

The script qt-install say:
===
--- Package spamassassin.x86_64 0:3.3.2-2.qt.el6 will be installed
-- Processing Dependency: perl-Razor-Agent for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Net::Ident) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Mail::SPF::Query) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Mail::DomainKeys) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
--- Package vpopmail.x86_64 0:5.4.33-0.qt.el6 will be installed
-- Processing Dependency: libev for package:
vpopmail-5.4.33-0.qt.el6.x86_64
-- Processing Dependency: libev.so.4()(64bit) for package:
vpopmail-5.4.33-0.qt.el6.x86_64
-- Running transaction check
--- Package dovecot.x86_64 1:2.2.7-0.qt.el6 will be installed
-- Processing Dependency: perl(JSON::XS) for package:
1:dovecot-2.2.7-0.qt.el6.x86_64
--- Package kernel-headers.x86_64 0:2.6.32-504.1.3.el6 will be installed
--- Package spamassassin.x86_64 0:3.3.2-2.qt.el6 will be installed
-- Processing Dependency: perl-Razor-Agent for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Net::Ident) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Mail::SPF::Query) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
-- Processing Dependency: perl(Mail::DomainKeys) for package:
spamassassin-3.3.2-2.qt.el6.x86_64
--- Package vpopmail.x86_64 0:5.4.33-0.qt.el6 will be installed
-- Processing Dependency: libev for package:
vpopmail-5.4.33-0.qt.el6.x86_64
-- Processing Dependency: libev.so.4()(64bit) for package:
vpopmail-5.4.33-0.qt.el6.x86_64
-- Finished Dependency Resolution
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
===

How can I fix this problem?

Regards,
Peter Peterse



Peter Peterse schreef op 1-12-2014 22:40:
 Hello List,

 I'm trying to install Qmailtoaster on a minimal installation of CentOS 6.6.
 The installation steps are from:
 https://github.com/QMailToaster/qmailtoaster-util/blob/master/README.install
 steps 1 and 2 are working but with step qt-install it looks like there
 are missing packages.
 There is no mysql server, Perl, httpd and libev.

 Am I missing some other? Is there a change in de minimal installation of
 CentOS 6.6, so that the script qt-install need to be changed?




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

Re: [qmailtoaster] Re: Need to update clamav toaster

[Peter Peterse]

Hello Eric,

When will the update be there?
Or should I create some time to update my server to CentOS 6 and the new
version of Qmail toaster?

Thanks for you answer.

regards,
Peter

Eric Shubert schreef op 26-11-2014 1:33:
 I'll see what I can do to get 0.98.5 available for legacy
 clamav-toaster. Shouldn't take too much work. Then everyone should be
 able to use qtp-newmodel to update it.


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

Re: [qmailtoaster] MYSQL replication question.

[Peter Peterse]

Hi Richard,

is there a firewall between the two servers which block port 3306 on
server2?

Regards,
Peter

rich...@avits.ca schreef op 12-4-2014 1:47:
 Shouldn't the wildcard grant cover that? I have tried a number of
 combinations, IP with the wildcard, just the IP, and wildcard without
 the IP entry. Same issue every time. 

 I have flushed privs and reloaded the grants table, no change. 

 Thanks,
 Richard

 *From: *Wim Godden
 *Sent: *Friday, April 11, 2014 16:41
 *To: *qmailtoaster-list@qmailtoaster.com
 *Reply To: *qmailtoaster-list@qmailtoaster.com
 *Subject: *Re: [qmailtoaster] MYSQL replication question.


 Have you tried setting it up as 'mail1_user'@'mail.avits.ca' ? Because
 that's the one being specified... MySQL is very picky on this.

 On 12/04/2014 0:53, Richard Whittaker wrote:
 Hi.

 I'm following Jake's video on setting up a replicating toaster setup,
 and have hit a pretty solid brick wall, and can't figure out how to
 get around it.

 I have the 2 MySQL servers setup, and running. Replication seems to
 be working fine in one direction, but not in the other.

 The slave thread on server1 fails with this error:

 140411 15:02:27 [ERROR] Slave I/O thread: error connecting to master
 'mail1_user@192.168.64.4:3306': Error: 'Access denied for user
 'mail1_user'@'mail.avits.ca' (using password: YES)'  errno: 1045
 retry-time: 60  retries: 86400

 I know the grants on server2 are setup on the target database. I have
 tried specific IP address and wildcard, and neither has worked.

 mysql show grants for mail1_user;
 +--+

 | Grants for mail1_user@% |
 +--+

 | GRANT REPLICATION SLAVE ON *.* TO 'mail1_user'@'%' IDENTIFIED BY
 PASSWORD 'blah' |
 +--+

 1 row in set (0.00 sec)

 mysql show grants for mail1_user@192.168.0.4;
 ++

 | Grants for mail1_user@192.168.0.4 |
 ++

 | GRANT REPLICATION SLAVE ON *.* TO 'mail1_user'@'192.168.0.4'
 IDENTIFIED BY PASSWORD 'blah' |
 ++

 1 row in set (0.00 sec)

 I can connect using the MySQL client as the use mail1_user and that
 password with no issues.

 Thoughts, suggestions?

 Thanks,
 Richard.



 -
 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 


-- 
Met vriendelijke groet,

Peter Peterse

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 8-4-2014 18:16:
 This is making me crazy.
 Please try version 182 from the qtp subversion repo.
 I'm pretty sure I got it right this time.
 Thanks.

Hi Eric,

you are not the only one.

I've just test 182 and it this script don't give me the wanted result.
[root@mail qmailbkup]# ll /backup/qmailbkup
total 2315800
-rw-r--r-- 1 root root 780691347 Apr  6 00:14 20140406-backup.tar.gz
-rw-r--r-- 1 root root 793295168 Apr  8 00:15 20140408-backup.tar.gz
-rw-r--r-- 1 root root   204 Apr  8 20:43 201404082030-assign.tar.bz2
-rw-r--r-- 1 root root   223 Apr  8 20:30
201404082030-qmailadminpasswd.tar.bz2
-rw-r--r-- 1 root root  8764 Apr  8 20:30
201404082030-qmailcontrol.tar.bz2
-rw-r--r-- 1 root root   2258592 Apr  8 20:30
201404082030-spamassassin-files.tar.bz2
-rw-r--r-- 1 root root46 Apr  8 20:30
201404082030-squirrelmail-plugins.tar.bz2
-rw-r--r-- 1 root root 14392 Apr  8 20:30
201404082030-squirrelmail-prefs.tar.bz2
-rw-r--r-- 1 root root  2261 Apr  8 20:43 201404082030-vpopmail.sql.gz
-rw-r--r-- 1 root root 792746759 Apr  8 20:43 201404082030-vpopmail.tar.bz2

In the home from the root user:
# ll
total 1448
-rw-r--r-- 1 root root 45 Apr  8 20:43 201404082030-backup.tar.gz

The script creates the backup command:

tar --create \
--gzip \
--file 201404082030-backup.tar.gz \
  201404082030-qmailcontrol.tar.bz2 \
  201404082030-squirrelmail-prefs.tar.bz2 \
  201404082030-squirrelmail-plugins.tar.bz2 \
  201404082030-qmailadminpasswd.tar.bz2 \
  201404082030-spamassassin-files.tar.bz2 \
  201404082030-vpopmail.tar.bz2 \
  201404082030-vpopmail.sql.gz \
  201404082030-assign.tar.bz2 \
   /dev/null 21

When I change the command to:

tar --create \
--directory /backup/qmailbkup/ \
--gzip \
--file /backup/qmailbkup/201404082030-backup.tar.gz \
  201404082030-qmailcontrol.tar.bz2 \
  201404082030-squirrelmail-prefs.tar.bz2 \
  201404082030-squirrelmail-plugins.tar.bz2 \
  201404082030-qmailadminpasswd.tar.bz2 \
  201404082030-spamassassin-files.tar.bz2 \
  201404082030-vpopmail.tar.bz2 \
  201404082030-vpopmail.sql.gz \
  201404082030-assign.tar.bz2 \
   /dev/null 21

I've changed the script and it's running now.

Regards,
Peter



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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 8-4-2014 21:01:
 On 04/08/2014 09:16 AM, Eric Shubert wrote:
 This is making me crazy.
 Please try version 182 from the qtp subversion repo.
 I'm pretty sure I got it right this time.
 Thanks.


 Let me know how this works for you.
 It worked for me (finally).

Hi,

does the script cleanup you backup directory? In my case NOT. I'm
running a new test with the change:
rm -rf \
  $backupdest/$QMAILCONTROL \
  $backupdest/$SQMAILPREFS \
  $backupdest/$SQMAILPLUGS \
  $backupdest/$QMAILADMINPASSWD \
  $backupdest/$SPAMASSASSINFILES \
  $backupdest/$VPOPMAIL \
  $backupdest/$gzmysqldata \
  $backupdest/$usersassign

Also in the summery I've changed:
tar -tzvf $backupdest/$curlfile  /tmp/emailmsg.txt

Peter

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 8-4-2014 21:53:
 On 04/08/2014 12:27 PM, Peter Peterse wrote:
 Eric Shubert schreef op 8-4-2014 21:01:
 On 04/08/2014 09:16 AM, Eric Shubert wrote:
 This is making me crazy.
 Please try version 182 from the qtp subversion repo.
 I'm pretty sure I got it right this time.
 Thanks.


 Let me know how this works for you.
 It worked for me (finally).

 Hi,

 does the script cleanup you backup directory? In my case NOT. I'm
 running a new test with the change:
 rm -rf \
$backupdest/$QMAILCONTROL \
$backupdest/$SQMAILPREFS \
$backupdest/$SQMAILPLUGS \
$backupdest/$QMAILADMINPASSWD \
$backupdest/$SPAMASSASSINFILES \
$backupdest/$VPOPMAIL \
$backupdest/$gzmysqldata \
$backupdest/$usersassign

 Also in the summery I've changed:
 tar -tzvf $backupdest/$curlfile  /tmp/emailmsg.txt

 Peter

 -

 Thanks Peter.

 I see my problem now. I was thinking that the full path $backupdest
 was already in the full file name. I've changed the scripts that way
 now, version 183 in qtp svn repo.

 My testing wasn't exactly thorough. It only worked for me because I
 was in that directory already. (Doh!)

 Should be good to go now.

 P.S. I also modified backup to grab whole qmail/users directory, as it
 wasn't grabbing the cdb file there. There are some other configuration
 settings it should be getting as well. I know it needs to be updated
 for spamdyke. Now that I'm thinking of it, I believe that tcp.smtp is
 missing too.

Hi Eric,

I should prefer no to use the absolute path for the files which have to
be backup. When restoring the configuration it store the files in 1
subdirectory and not in X subdirectory's.

Peter

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

Re: [qmailtoaster] heartbleed bug

[Peter Peterse]

Finn Buhelt schreef op 8-4-2014 21:53:
 Hi list

 Will this affects QMT ? ( latest release uses openssl-1.01 which is hit)

 New security holes are always showing up. The latest one, the
 so-called http://heartbleed.com/Heartbleed Bug http://heartbleed.com/
  in the OpenSSL https://www.openssl.org/ cryptographic library, is
 an especially bad one  - taken from zdnet.com


 Regards,
 Finn

Hi Finn,

I've read CentOS 6 is affected and CentOS 5 not.

CentOS 5.10 contains OpenSSL 0.9.8e

Regards,
Peter

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 8-4-2014 22:09:
 On 04/08/2014 01:02 PM, Peter Peterse wrote:
 Hi Eric,

 I should prefer no to use the absolute path for the files which have to
 be backup. When restoring the configuration it store the files in 1
 subdirectory and not in X subdirectory's.

 Peter

 I agree. Backups should have no absolute paths.
 (which is one reason I changed users/assign)
 Thanks for all your testing on this.

Hi Eric,

Script 184 has ended:

# qtp-backup
tar: /backup/qmailbkup/201404082211-backup.tar.gz: Cannot open: No such
file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
 Backup is complete and located in: /backup/qmailbkup

So no luck.


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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 8-4-2014 22:50:
 If you concur, I'll cut another QTP release
it is running. I will let you sweat for 15 minutes ;-)

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Peter Peterse schreef op 8-4-2014 22:57:
 Eric Shubert schreef op 8-4-2014 22:50:
 If you concur, I'll cut another QTP release
 it is running. I will let you sweat for 15 minutes ;-)

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

Hi Eric,

I can confirm  that de qtp-backup script is working again as it should
on my system (CentOS 5.10)
Tonight it will start via the crontab. This is my final test.

Regards and thanks for all your time,
Peter

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Hi Eric,

The script run also succesfull from the crontab.


 Op 8 apr. 2014 om 23:27 heeft Eric Shubert e...@shubes.net het volgende 
 geschreven:
 
 On 04/08/2014 02:13 PM, Peter Peterse wrote:
 Regards and thanks for all your time,
 
 Likewise.
 
 -- 
 -Eric 'shubes'
 
 
 -
 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] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting --directory worked?

 Thanks.

Hello Eric,

Yes when I've change the script to:
==
cd $backupdest
tar -C $backupdest \
-czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
==

The script worked correctly.
It look like the last $DATENAME-* don't work with the tar command on
this way.

$ touch /tmp/testfile.txt
$ tar -C /tmp -czf /tmp/test.tgz testfile*
tar: testfile*: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

While it will work when I use the next command
$ tar -C /tmp -czf /tmp/test.tgz testfile.txt

There are more backup files not correct:
-rw-r--r-- 1 root root46 Apr  7 06:35
201404070635-squirrelmail-plugins.tar.bz2
-rw-r--r-- 1 root root46 Apr  7 06:35
201404070635-squirrelmail-prefs.tar.bz2
These to are empty tar files.

Regards,
Peter

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
  -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -

 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be fixed
 so that it works on both COS5 and COS6. It might be a while before I
 get to look at it, as what time I have is being spent on finishing up
 the COS6 release.

 Thanks.



Hi Eric,

It looks like a issue with the combination between shell and tar:
http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern

Does it work on your CentOS 6 system, because I've test it on one of my
CentOS 6.5 systems and the result is:
# ls -l  /tmp/testfile.txt
-rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
# tar -C /tmp -czf /tmp/test.tgz testfile*
tar: testfile*: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

Regards,
Peter

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
   -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -

 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be fixed
 so that it works on both COS5 and COS6. It might be a while before I
 get to look at it, as what time I have is being spent on finishing up
 the COS6 release.

 Thanks.



 Hi Eric,

 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern


 Does it work on your CentOS 6 system, because I've test it on one of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -

 I should've caught that.

 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.

Hi Eric,

Sorry but on both of my systems it don't work:

CentOS 5.10:
# touch /tmp/testfile.txt
# tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
tar: testfile*: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

On CentOS 6.5:
# touch /tmp/testfile.txt
# tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
tar: testfile*: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

Regards,
Peter

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 22:19:
 On 04/07/2014 01:12 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
-czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -


 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be
 fixed
 so that it works on both COS5 and COS6. It might be a while before I
 get to look at it, as what time I have is being spent on finishing up
 the COS6 release.

 Thanks.



 Hi Eric,

 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern



 Does it work on your CentOS 6 system, because I've test it on one
 of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -

 I should've caught that.

 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.

 Hi Eric,

 Sorry but on both of my systems it don't work:

 CentOS 5.10:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 On CentOS 6.5:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -

 What about with single quotes? e.g.:
 'testfile*'

Still the same.

CentOS 5.10:
# tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
tar: testfile*: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

CentOS 6.5:
# tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
tar: testfile*: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

System Admin schreef op 7-4-2014 23:42:
 Dumb question.
 did you try to run qtp-backup script before any modifications to it?

 Dave M

Hi Dave,

I've saw that the backup data was not big enough. So I've start looking
what was wrong.

It looks like on my system the command ala:

tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*

don't work. This problem started 31 march 2014 before that my
backupfiles where correct. I'm guessing that day I did an yum update of
the system.

Regards,
Peter


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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 22:49:
 On 04/07/2014 01:24 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:19:
 On 04/07/2014 01:12 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
 -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar
 command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -



 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be
 fixed
 so that it works on both COS5 and COS6. It might be a while
 before I
 get to look at it, as what time I have is being spent on
 finishing up
 the COS6 release.

 Thanks.



 Hi Eric,

 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern




 Does it work on your CentOS 6 system, because I've test it on one
 of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -


 I should've caught that.

 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.

 Hi Eric,

 Sorry but on both of my systems it don't work:

 CentOS 5.10:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 On CentOS 6.5:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -

 What about with single quotes? e.g.:
 'testfile*'

 Still the same.

 CentOS 5.10:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 CentOS 6.5:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

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



 Ok, I think I've fixed both backup and restore scripts now, including
 the squirrelmail prefs.

 Please try scripts in qtp svn repo:
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-restore

 If they work I'll cut another qtp release.

 Thanks. Your help is greatly appreciated.

Hello Eric,

when I do a:
wget http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup

I get an file which is created on May 30 2013

I don't see any changes between the version on my system and the one Ive
júst downloaded.

Regards,
Peter

-- 
Met vriendelijke groet,

Peter Peterse

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 23:01:
 On 04/07/2014 01:52 PM, Peter Peterse wrote:
 System Admin schreef op 7-4-2014 23:42:
 Dumb question.
 did you try to run qtp-backup script before any modifications to it?

 Dave M

 Hi Dave,

 I've saw that the backup data was not big enough. So I've start looking
 what was wrong.

 It looks like on my system the command ala:

 tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*

 don't work. This problem started 31 march 2014 before that my
 backupfiles where correct. I'm guessing that day I did an yum update of
 the system.

 Regards,
 Peter


 -

 You're correct, Peter. That error was introduced in the latest QTP
 package. Please accept my apologies.



No problem, I was only try to summarize it to Dave.






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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 23:12:
 On 04/07/2014 02:04 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:49:
 On 04/07/2014 01:24 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:19:
 On 04/07/2014 01:12 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting
 --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
  -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar
 command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -




 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be
 fixed
 so that it works on both COS5 and COS6. It might be a while
 before I
 get to look at it, as what time I have is being spent on
 finishing up
 the COS6 release.

 Thanks.



 Hi Eric,

 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern





 Does it work on your CentOS 6 system, because I've test it on one
 of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -



 I should've caught that.

 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.

 Hi Eric,

 Sorry but on both of my systems it don't work:

 CentOS 5.10:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 On CentOS 6.5:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -


 What about with single quotes? e.g.:
 'testfile*'

 Still the same.

 CentOS 5.10:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 CentOS 6.5:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

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



 Ok, I think I've fixed both backup and restore scripts now, including
 the squirrelmail prefs.

 Please try scripts in qtp svn repo:
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-restore

 If they work I'll cut another qtp release.

 Thanks. Your help is greatly appreciated.

 Hello Eric,

 when I do a:
 wget http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup

 I get an file which is created on May 30 2013

 I don't see any changes between the version on my system and the one Ive
 júst downloaded.

 Regards,
 Peter


 Sorry. Hadn't committed changes.
 s/178/179/


Hi Eric,

the backup is running. I will answer the result when it's done.

-- 
Met vriendelijke groet,

Peter Peterse

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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Eric Shubert schreef op 7-4-2014 23:12:
 On 04/07/2014 02:04 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:49:
 On 04/07/2014 01:24 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:19:
 On 04/07/2014 01:12 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?

 I take it doing a cd before the command and omitting
 --directory
 worked?

 Thanks.

 Hello Eric,

 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
  -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==

 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar
 command on
 this way.

 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt

 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.

 Regards,
 Peter

 -




 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.

 Would someone care to look into this in detail? This needs to be
 fixed
 so that it works on both COS5 and COS6. It might be a while
 before I
 get to look at it, as what time I have is being spent on
 finishing up
 the COS6 release.

 Thanks.



 Hi Eric,

 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern





 Does it work on your CentOS 6 system, because I've test it on one
 of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -



 I should've caught that.

 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.

 Hi Eric,

 Sorry but on both of my systems it don't work:

 CentOS 5.10:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 On CentOS 6.5:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

 Regards,
 Peter

 -


 What about with single quotes? e.g.:
 'testfile*'

 Still the same.

 CentOS 5.10:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 CentOS 6.5:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors

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



 Ok, I think I've fixed both backup and restore scripts now, including
 the squirrelmail prefs.

 Please try scripts in qtp svn repo:
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-restore

 If they work I'll cut another qtp release.

 Thanks. Your help is greatly appreciated.

 Hello Eric,

 when I do a:
 wget http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup

 I get an file which is created on May 30 2013

 I don't see any changes between the version on my system and the one Ive
 júst downloaded.

 Regards,
 Peter


 Sorry. Hadn't committed changes.
 s/178/179/


Eric,

the new script didn't worked correctly.
In the dir /backup/qmailbkup the are now the next files:
-rw-r--r-- 1 root root   204 Apr  7 23:33 201404072319-assign.tar.bz2
-rw-r--r-- 1 root root   223 Apr  7 23:19
201404072319-qmailadminpasswd.tar.bz2
-rw-r--r-- 1 root root  8753 Apr  7 23:19
201404072319-qmailcontrol.tar.bz2
-rw-r--r-- 1 root root   2258146 Apr  7 23:19
201404072319-spamassassin-files.tar.bz2
-rw-r--r-- 1 root root46 Apr  7 23:19
201404072319-squirrelmail-plugins.tar.bz2
-rw-r--r-- 1 root root 14392 Apr  7 23:19
201404072319

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Hi Eric

This one didn't work either.

 Op 8 apr. 2014 om 00:18 heeft Eric Shubert e...@shubes.net het volgende 
 geschreven:
 
 On 04/07/2014 02:38 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 23:12:
 On 04/07/2014 02:04 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:49:
 On 04/07/2014 01:24 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:19:
 On 04/07/2014 01:12 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 22:01:
 On 04/07/2014 12:46 PM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 20:54:
 On 04/07/2014 11:47 AM, Peter Peterse wrote:
 Eric Shubert schreef op 7-4-2014 18:29:
 What was the error? Same?
 
 I take it doing a cd before the command and omitting
 --directory
 worked?
 
 Thanks.
 Hello Eric,
 
 Yes when I've change the script to:
 ==
 cd $backupdest
 tar -C $backupdest \
  -czf $backupdest/$curlfile $DATENAME-*  /dev/null 21
 ==
 
 The script worked correctly.
 It look like the last $DATENAME-* don't work with the tar
 command on
 this way.
 
 $ touch /tmp/testfile.txt
 $ tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors
 
 While it will work when I use the next command
 $ tar -C /tmp -czf /tmp/test.tgz testfile.txt
 
 There are more backup files not correct:
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-plugins.tar.bz2
 -rw-r--r-- 1 root root46 Apr  7 06:35
 201404070635-squirrelmail-prefs.tar.bz2
 These to are empty tar files.
 
 Regards,
 Peter
 
 -
 
 That's very strange to me. Using the -C option is supposed to be
 preferable to doing a cd before the tar command.
 
 Would someone care to look into this in detail? This needs to be
 fixed
 so that it works on both COS5 and COS6. It might be a while
 before I
 get to look at it, as what time I have is being spent on
 finishing up
 the COS6 release.
 
 Thanks.
 
 Hi Eric,
 
 It looks like a issue with the combination between shell and tar:
 http://superuser.com/questions/266422/tar-c-with-a-wildcard-file-pattern
 
 
 
 
 
 Does it work on your CentOS 6 system, because I've test it on one
 of my
 CentOS 6.5 systems and the result is:
 # ls -l  /tmp/testfile.txt
 -rw-r--r-- 1 root root 0 Apr  7 21:41 /tmp/testfile.txt
 # tar -C /tmp -czf /tmp/test.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors
 
 Regards,
 Peter
 
 -
 
 I should've caught that.
 
 Does testfile* work?
 (putting the string with wildcard in quotes)
 I expect it will.
 Hi Eric,
 
 Sorry but on both of my systems it don't work:
 
 CentOS 5.10:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors
 
 On CentOS 6.5:
 # touch /tmp/testfile.txt
 # tar -C /tmp -zcvf /tmp/testbackup.tgz testfile*
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors
 
 Regards,
 Peter
 
 -
 
 What about with single quotes? e.g.:
 'testfile*'
 
 Still the same.
 
 CentOS 5.10:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors
 
 CentOS 6.5:
 # tar -C /tmp -zcvf /tmp/testbackup.tgz 'testfile*'
 tar: testfile*: Cannot stat: No such file or directory
 tar: Exiting with failure status due to previous errors
 
 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail:
 qmailtoaster-list-h...@qmailtoaster.com
 
 Ok, I think I've fixed both backup and restore scripts now, including
 the squirrelmail prefs.
 
 Please try scripts in qtp svn repo:
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup
 http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-restore
 
 If they work I'll cut another qtp release.
 
 Thanks. Your help is greatly appreciated.
 Hello Eric,
 
 when I do a:
 wget http://qtp.qmailtoaster.com/trac/export/178/bin/qtp-backup
 
 I get an file which is created on May 30 2013
 
 I don't see any changes between the version on my system and the one Ive
 júst downloaded.
 
 Regards,
 Peter
 
 Sorry. Hadn't committed changes.
 s/178/179/
 
 Eric,
 
 the new script didn't worked correctly.
 In the dir /backup/qmailbkup the are now the next files:
 -rw-r--r-- 1 root root   204 Apr  7 23:33 201404072319-assign.tar.bz2
 -rw-r--r-- 1 root root   223 Apr  7 23:19
 201404072319-qmailadminpasswd.tar.bz2
 -rw-r--r-- 1 root root  8753 Apr  7 23:19
 201404072319-qmailcontrol.tar.bz2
 -rw-r--r-- 1 root

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Hello Eric,

I've solved it by set a change directory before the problematic tar command. 
The suggested change will be tested tonight.

I'm using CentOS 5 latest update (5.10). Qtp:
 qmailtoaster-plus-0.3.2-1.4.20

Thanks,
Peter

 Oorspronkelijk bericht 
Van Eric Shubert e...@shubes.net 
Datum: 06-04-2014  02:49  (GMT+01:00) 
Aan qmailtoaster-list@qmailtoaster.com 
Onderwerp [qmailtoaster] Re: qtp-backup won't work 
 
On 04/05/2014 11:13 AM, Peter Peterse wrote:
 Hello list,

 on my qtp installation the backup doesn't work any more. I don't
 remember that I've change something in the script, so maybe it's an
 issue one of the yum update processes.

 I've trace the issue to the next command which is located in the script:
 tar -C $backupdest \
  -czf $backupdest/$curlfile $DATENAME-*

 When I start the command on the console it result to an error:
 [root@mail ~]# tar -C /backup/qmailbkup  -czf
 /backup/qmailbkup/201404052008-backup.tar.gz 201404052008-*
 tar: 201404052008-*: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors

 When I look in the directory /backup/qmailbkup I see the next files:
 201404052008-assign.tar.bz2
 201404052008-backup.tar.gz
 201404052008-qmailadminpasswd.tar.bz2
 201404052008-qmailcontrol.tar.bz2
 201404052008-spamassassin-files.tar.bz2
 201404052008-squirrelmail-plugins.tar.bz2
 201404052008-squirrelmail-prefs.tar.bz2
 201404052008-vpopmail.sql.gz

 The problem is that I don't see the difference with command which is
 also in the qtp-backup script:
    tar -C /var/lib/squirrelmail/prefs \
    -cjf $backupdest/$SQMAILPREFS *

 I hope one of you can see the problem.

 Regards,
 Peter

 -

My apologies for breaking this. I don't see the difference either to be 
honest. I thought this version had been run already, and perhaps it was 
with an older version where it worked.

tar is a little squirrelly with the options. It doesn't appear to be 
picking up the -C option properly, for whatever reason.

Please try this:
# tar --create --gzip --file $backupdest/$curlfile \
   --directory $backupdest $DATENAME-*

and let us know if that works.

P.S. Which versions are you running (OS and qtp)?

-- 
-Eric 'shubes'


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

Re: [qmailtoaster] Re: qtp-backup won't work

[Peter Peterse]

Gekko Erik,

Unfortunaly, the proposed command does not work.

Regards,
Peter

 Op 6 apr. 2014 om 08:13 heeft Peter Peterse pe...@peterse-uithuizen.com het 
 volgende geschreven:
 
 Hello Eric,
 
 I've solved it by set a change directory before the problematic tar command. 
 The suggested change will be tested tonight.
 
 I'm using CentOS 5 latest update (5.10). Qtp:
  qmailtoaster-plus-0.3.2-1.4.20
 
 Thanks,
 Peter
 
 
 
  Oorspronkelijk bericht 
 Van Eric Shubert e...@shubes.net 
 Datum: 06-04-2014 02:49 (GMT+01:00) 
 Aan qmailtoaster-list@qmailtoaster.com 
 Onderwerp [qmailtoaster] Re: qtp-backup won't work 
 
 
 On 04/05/2014 11:13 AM, Peter Peterse wrote:
  Hello list,
 
  on my qtp installation the backup doesn't work any more. I don't
  remember that I've change something in the script, so maybe it's an
  issue one of the yum update processes.
 
  I've trace the issue to the next command which is located in the script:
  tar -C $backupdest \
   -czf $backupdest/$curlfile $DATENAME-*
 
  When I start the command on the console it result to an error:
  [root@mail ~]# tar -C /backup/qmailbkup  -czf
  /backup/qmailbkup/201404052008-backup.tar.gz 201404052008-*
  tar: 201404052008-*: Cannot stat: No such file or directory
  tar: Error exit delayed from previous errors
 
  When I look in the directory /backup/qmailbkup I see the next files:
  201404052008-assign.tar.bz2
  201404052008-backup.tar.gz
  201404052008-qmailadminpasswd.tar.bz2
  201404052008-qmailcontrol.tar.bz2
  201404052008-spamassassin-files.tar.bz2
  201404052008-squirrelmail-plugins.tar.bz2
  201404052008-squirrelmail-prefs.tar.bz2
  201404052008-vpopmail.sql.gz
 
  The problem is that I don't see the difference with command which is
  also in the qtp-backup script:
 tar -C /var/lib/squirrelmail/prefs \
 -cjf $backupdest/$SQMAILPREFS *
 
  I hope one of you can see the problem.
 
  Regards,
  Peter
 
  -
 
 My apologies for breaking this. I don't see the difference either to be 
 honest. I thought this version had been run already, and perhaps it was 
 with an older version where it worked.
 
 tar is a little squirrelly with the options. It doesn't appear to be 
 picking up the -C option properly, for whatever reason.
 
 Please try this:
 # tar --create --gzip --file $backupdest/$curlfile \
--directory $backupdest $DATENAME-*
 
 and let us know if that works.
 
 P.S. Which versions are you running (OS and qtp)?
 
 -- 
 -Eric 'shubes'
 
 
 -
 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

[qmailtoaster] qtp-backup won't work

[Peter Peterse]

Hello list,

on my qtp installation the backup doesn't work any more. I don't
remember that I've change something in the script, so maybe it's an
issue one of the yum update processes.

I've trace the issue to the next command which is located in the script:
tar -C $backupdest \
-czf $backupdest/$curlfile $DATENAME-*

When I start the command on the console it result to an error:
[root@mail ~]# tar -C /backup/qmailbkup  -czf
/backup/qmailbkup/201404052008-backup.tar.gz 201404052008-*
tar: 201404052008-*: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

When I look in the directory /backup/qmailbkup I see the next files:
201404052008-assign.tar.bz2
201404052008-backup.tar.gz
201404052008-qmailadminpasswd.tar.bz2
201404052008-qmailcontrol.tar.bz2
201404052008-spamassassin-files.tar.bz2
201404052008-squirrelmail-plugins.tar.bz2
201404052008-squirrelmail-prefs.tar.bz2
201404052008-vpopmail.sql.gz

The problem is that I don't see the difference with command which is
also in the qtp-backup script:
  tar -C /var/lib/squirrelmail/prefs \
  -cjf $backupdest/$SQMAILPREFS *

I hope one of you can see the problem.

Regards,
Peter

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

Re: [qmailtoaster] clamav-toaster-0.97.8-1.4.4 released

[Peter Peterse]

Hello Eric,

I've just updated my system. No problems found yet.

Regards,
Peter

Op 14-5-2013 17:50, Eric Shubert schreef:
 I hope I'm not the only one who has been running this release, which
 has been in the testing branch for a week or so now. ;)

 I've had no problems with it, so I've promoted it to current. Please
 allow up to an hour for the mirrors to sync it up.

 Thanks go to Eric Broch for getting this release put together.



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

[qmailtoaster] vpopmail database contains plaintext password

[Peter Peterse]

Hello,

the table {domainname} in the database vpopmail contains a column 
pw_clear_passwd.

What is the correct way to remove this column out this database?
I'm alway deploy qmail-toaster by the qtp-newmodel and it works
fantastic, but such security issue stays in the database or is there an
option in qtp-newmodel to remove this feature?

Thanks for your reply.

Peter Peterse

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

Re: [qmailtoaster] Uninstall Fail2ban

[Peter Peterse]

How did you install fail2ban

When you used yum I think you should try:

yum remove fail2ban


Regards,
Peter


-
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] Fail2ban and Qmailtoaster

[Peter Peterse]

Hello List,

I think (hope) that I have a better filter for vpopmail-fail
It checks also on u...@example.com

# Fail2Ban configuration file for vpopmail
#
# Author: Lawrence Sheed
#
# $Revision: 1.0 $
#

[Definition]

# Option: failregex
# Notes.: regex to match the password failures messages in the logfile.
# Values: TEXT
#
failregex = vchkpw-pop3: vpopmail user not found .*@.*:HOST$

# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT
#
ignoreregex =


happy banning.
Peter

-
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] Fail2ban and Qmailtoaster

[Peter Peterse]

wou good of me. I read a few message back and see that you can use

failregex = vchkpw-pop3: vpopmail user not found .*:HOST$

Where I find .*@:HOST$ I can't remember.
Peter

Op 12-3-2011 9:36, Peter schreef:
 Hello List,

 I think (hope) that I have a better filter for vpopmail-fail
 It checks also on u...@example.com
 
 # Fail2Ban configuration file for vpopmail
 #
 # Author: Lawrence Sheed
 #
 # $Revision: 1.0 $
 #

 [Definition]

 # Option: failregex
 # Notes.: regex to match the password failures messages in the logfile.
 # Values: TEXT
 #
 failregex = vchkpw-pop3: vpopmail user not found .*@.*:HOST$

 # Option:  ignoreregex
 # Notes.:  regex to ignore. If this regex matches, the line is ignored.
 # Values:  TEXT
 #
 ignoreregex =
 

 happy banning.
 Peter



-
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] Re: SMTP attack

[Peter Peterse]

HOST is an alias for a regular expression to find the ip address. Which
is defined in the code.

Succes,
Peter.



 Nice, that's great! :)
 Just a little question: I don't get this HOST (I've also read the wiki
 but it's not clear)

 can you do an example, please?

 Thanks,
 Cheers!

 Il 05/03/2011 23:26, Sergio M ha scritto:
 Eric Shubert escribió:
 Timing is good on this. :)

 http://wiki.qmailtoaster.com/index.php?title=Fail2Banaction=edit

 Have at it. I've added a link to this page under the Configuration-
 Security section. It's a start (albeit not much of one).

 Hey guys, I created a basic article, but have trouble with formatting.
 Can anyone take a look at it? this is how I meant it to look ;-)

 == '''Basic fail2ban installation and setup''' ==


 fail2ban homepage: http://www.fail2ban.org.
 Please check [0] and [1] for more details.

 

 == 1. Installation. ==

 Enable the EPEL repos [1] and then 'yum install fail2ban'



 == 2. Setup: ==

 To work with Qmail/vpopmail, a filter and jail should be defined.
 '''a.''' # mcedit /etc/fail2ban/filter.d/vpopmail-fail.conf

 [Definition]
 #Looks for failed password logins to SMTP
 failregex = vchkpw-smtp: password fail ([^)]*) [^@]*@[^:]*:HOST

 ignoreregex =

 '''b.''' # mcedit /etc/fail2ban/jail.conf   (add this)

 [vpopmail-fail]
 enabled  = true
 filter   = vpopmail-fail
 action   = iptables[name=SMTP, port=smtp, protocol=tcp]
 logpath  = /var/log/maillog
 maxretry = 1
 bantime  = 604800
 findtime = 3600

 '''c. Test the filter file:'''
 # fail2ban-regex /var/log/maillog
 /etc/fail2ban/filter.d/vpopmail-fail.conf

 Returns something like this, with n matches for the regex or 0 if no
 matches:

 Failregex
 |- Regular expressions:
 |  [1] vchkpw-smtp: password fail ([^)]*) [^@]*@[^:]*:HOST
 |
 `- Number of matches:
   [1] 123 match(es)


 '''d. Reload config:'''
 # fail2ban-client stop/start

 '''e. Check the status of a jail:'''

 # fail2ban-client status vpopmail-fail

 Status for the jail: vpopmail-fail
 |- filter
 |  |- File list:/var/log/maillog
 |  |- Currently failed: 7
 |  `- Total failed: 225
 `- action
   |- Currently banned: 109

 | `- IP list: 200.207.49.13 84.79.73.123 187.35.209.243 (...)
 187.6.106.201 187.63.80.134 187.52.195.234 187.4.200.17

   `- Total banned: 109

 '''NOTE:''' Once its starts running and the logs have matching
 strings, it will create iptables rules dropping that IP. But... when
 fail2ban reload and/or iptables restart and/or rebooting and/or the
 weekly logrotate, those rules are gone. bye bye!
 So... what to do?

 - Before changes, do a '# service iptables save' and it will write
 them to a file, and after any change do '# service iptables restart'
 to make it load the saved set of rules;
 - Tune fail2ban to write IPs to /etc/fail2ban/ip.deny [3].


 == 3.A little basic admin stuff ==

 '''a. Check banned IPs:'''
 - by fail2ban:# fail2ban-client status vpopmail-fail
 - current iptables rules: # iptables -L -nv
 - To see IPs that fail2ban is saving for the next reload:
 # cat /etc/fail2ban/ip.deny

 '''b. How to unblock an IP:'''
 1) Delete it from the current iptables rules:
 # iptables -D fail2ban-SMTP -s 11.22.33.44 -j DROP
 2) remove it from /etc/fail2ban/ip.deny (maybe listed several times).
 3) remove it from /etc/sysconfig/iptables (maybe listed several times).


 


 == 4. References: ==

 [0]
 http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg30514.html
 [1]
 http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg30551.html
 [2] http://fedoraproject.org/wiki/EPEL/FAQ#howtouse
 [3] http://n8wood.wordpress.com/2009/06/22/fail2ban-permanent-ssh-bans/


 

 Nessun virus nel messaggio.
 Controllato da AVG - www.avg.com http://www.avg.com
 Versione: 10.0.1204 / Database dei virus: 1435/3480 - Data di
 rilascio: 03/03/2011

 -
 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 

Re: [qmailtoaster] Freshclam not running after clamav update

[Peter Peterse]

Hello Jake,

I had the same problem. It was with qtp-newmodel
Ik had seen it also with 0.96 and now I was aware of it so I did restart
freshclam right a way after the update.
# service freshclam restart

Regards,
Peter

Op 25-2-2011 20:49, Jake Vickers schreef:
 On 02/25/2011 01:47 PM, Thomas M. Jaeger wrote:
 I had the same issue and did a reboot (CentOS 5 x86_64) and it seems
 fine
 now.


 This was using qtp-newmodel, or a manual rebuild?


 -

 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] New clamav version

[Peter Peterse]

Hello,

does anyone knows when the update comes for Clamav 0.96.5?

Thanks anyway.
Regards,
Peter.

-
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] clamav-toaster-0.96.4-1.3.39 upgrade

[Peter Peterse]

Hello Eric,

my freshclam has also not start the right way after the update.

It seems that it start automatically somewhere between sat and sun.

regards,
Peter

On 13-12-2010 20:38, Eric Shubert wrote:

 The 2nd thing is, I wonder why freshclam wasn't (re)started
 successfully with the upgrade. It started fine with a service
 freshclam start command. Has anyone noticed freshclam not running
 after the upgrade?



-
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] clamav-toaster-0.96.4-1.3.39 upgrade

[Peter Peterse]

F.y.i.

The logrotate coinfiguration started my freshclam, sunday morning at 4
o'clock.

Regards,
Peter.

On 13-12-2010 20:54, Peter Peterse wrote:
 Hello Eric,

 my freshclam has also not start the right way after the update.

 It seems that it start automatically somewhere between sat and sun.

 regards,
 Peter

 On 13-12-2010 20:38, Eric Shubert wrote:
 The 2nd thing is, I wonder why freshclam wasn't (re)started
 successfully with the upgrade. It started fine with a service
 freshclam start command. Has anyone noticed freshclam not running
 after the upgrade?




-
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] Update clamav in qtp-newmodel

[Peter Peterse]

 Peter Peterse wrote:
 Hello,

 I'm trying to update clamav in qtp-newmodel.

 At the end it fails:

 Installing clamav-toaster-0.93.1-1.3.19 in the sandbox ...
 Preparing...
 ##
 clamav-toaster
 ##
 rpmdb: close: Operation not supported
 rpmdb: close: Bad file descriptor


 Whats going wrong here?

 Peter.


 Sorry for the late reply, Peter. I've been away.

 Likely is a problem with the unionfs. Which dist/kernel version are you
 running? Are you running a unionfs sandbox? I'm guessing that a copied or
 linked sandbox would work. It'd be nice to get the problem fixed
 regardless.

 --
 -Eric 'shubes'

Hello Eric,


Im running on CentOS 4.6 on kernel: 2.6.9-67.0.20.EL

qtp-newmodel starts with:
==
qtp-newmodel v0.3 starting Fri Jul 18 13:28:56 CEST 2008
qtp-whatami v0.3
DISTRO=CentOS
OSVER=4.6
QTARCH=i686
BUILD_DIST=cnt40
BUILD_DIR=/usr/src/redhat
This machine's OS is supported, but this version/arch has not been tested.
==

I'm creating almost every time a new sandbox (unioned)
Do I need to say N on the question Would you like a unioned sandbox?

greetings

Peter.


-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Update clamav in qtp-newmodel

[Peter Peterse]

Hello Eric,

thanks for your support.
I've update my system now. I've used the option copied sandbox. Indeed 
you can drink a cup of coffee. (hole can for me)


Peter

Eric Shubert schreef:

Peter Peterse wrote:
  

Peter Peterse wrote:
  

Hello,

I'm trying to update clamav in qtp-newmodel.

At the end it fails:

Installing clamav-toaster-0.93.1-1.3.19 in the sandbox ...
Preparing...
##
clamav-toaster
##
rpmdb: close: Operation not supported
rpmdb: close: Bad file descriptor


Whats going wrong here?

Peter.



Sorry for the late reply, Peter. I've been away.

Likely is a problem with the unionfs. Which dist/kernel version are you
running? Are you running a unionfs sandbox? I'm guessing that a copied or
linked sandbox would work. It'd be nice to get the problem fixed
regardless.

--
-Eric 'shubes'
  

Hello Eric,


Im running on CentOS 4.6 on kernel: 2.6.9-67.0.20.EL

qtp-newmodel starts with:
==
qtp-newmodel v0.3 starting Fri Jul 18 13:28:56 CEST 2008
qtp-whatami v0.3
DISTRO=CentOS
OSVER=4.6
QTARCH=i686
BUILD_DIST=cnt40
BUILD_DIR=/usr/src/redhat
This machine's OS is supported, but this version/arch has not been tested.
==

I'm creating almost every time a new sandbox (unioned)
Do I need to say N on the question Would you like a unioned sandbox?

greetings

Peter.




That would probably be the best route to take at this point. I don't want to
 waste much (of Justin's) time trying to get the unionfs feature working on
older kernel versions.

  


-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Update clamav in qtp-newmodel

[Peter Peterse]

Hello,

I'm trying to update clamav in qtp-newmodel.

At the end it fails:

Installing clamav-toaster-0.93.1-1.3.19 in the sandbox ...
Preparing...   
##
clamav-toaster 
##

rpmdb: close: Operation not supported
rpmdb: close: Bad file descriptor


Whats going wrong here?

Peter.

-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] UPDATED PACKAGE: ClamAV

[Peter Peterse]

Hello Erik,

thanks for the job.

But how do's it work with qtp-newmodel?

I get an error:
===
Installing clamav-toaster-0.93-1.3.18 in the sandbox ...
error: Failed dependencies:
   libclamunrar_iface.so.3 is needed by clamav-toaster-0.93-1.3.18.i686
===
Peter.


Erik A. Espinoza wrote:

As mentioned on the web site, be sure to remove prior versions of
ClamAV before building this new one, otherwise it will cause a
circular dependency


-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]