I'd add the -v option in the rm command and see what error you're
getting in the
So, change from rm -rf \ to rm -rfv \ and you should get a reason
for failure to remove in you nightly log
EricB
On 1/26/2015 3:36 AM, ChandranManikandan wrote:
Hi Sebastian,
I have modified as per your
Brand new install of QMT on CentOS 6.6 minimal 64 bit.
Running on a dedicated server under VirtualBox 4 latest
4GB memory single core i7-2600
Using the instructions of Eric Shubert at
https://github.com/QMailToaster/QMailToaster/wiki/RPM-Installation-Procedure
After the install I had to turn
Hi Edwin.
Try to increase the softlimit in the /var/qmail/supervise/submission/run
file.
Mine is set to 1 !
Regards,
Finn
(I've just struggled with same issue after an update )
Den 26-01-2015 kl. 23:01 skrev Edwin C:
Brand new install of QMT on CentOS 6.6 minimal 64 bit.
Running
I have installed on a VPS under Linode 1GB Memory 1 CPU a QMT on CentOS6 64bit
I found a definite bug in QmailAdmin Change Password with Dovecot Update Lagging
So I can go to qmailadmin and change my user password...
...but when I log out and try to login again with the NEW password I get an
Hi folks,
Has anyone any idea how to safely change links in emails to force them to not
autorun?
A client recently had an email that had a link to ransomware which encrypted
not only
the users local drive but the mapped drives as well.
Luckily we had a backup from the prior night so not too
Hi Sebastian,
I have modified as per your suggestion but still come with the same files.
how to fix this issue on the qt-backup script.
On Fri, Jan 23, 2015 at 3:27 PM, Sebastian Grewe sebast...@grewe.ca wrote:
$backupdest\$gzmysqldata \
I think that backslash shouldn't be there and
Thanks Finn, the change of the softlimit in /var/qmail/supervise/submission/run
to 1 did part of the trick for me...
The next problem was a new squirrelmail error message:
451 mail server temporarily rejected message (#4.3.0)
A quick search in the forum gave me the idea to upgrade the
We had a problem where users were receiving the output from `spam --help` as a
message to their inbox. I discovered this was caused when a message was
delivered to -u...@example.com (notice initial dash), which was passed to
spamc as:
\_ /usr/bin/spamdyke --config-file /etc/spamdyke.conf […]