Categories
Uncategorized

How to delete emails from qmail queue on H-Sphere

First check the status of your queue:

# /var/qmail/bin/qmail-qstat
messages in queue: 6751
messages in queue but not yet preprocessed: 56

After you find and stop the spammer, you now have a bunch of email on your QMail queue. Here’s how to remove it

take a “user@domain.com” that happens in emails from the spammer (usually the sender) and run this command:

grep -R user@domain.com /var/qmail/queue/mess/* | awk -F”:” ‘{print “rm -f ” $1}’ | sh

make sure the quotes and single quotes are straight, not round upon copy/paste

That will delete the emails that contain that user@domain.com

but it would leave behind various indexes and later on your users would start receiving bouncebacks for emails they’ve never sent!

BETTER USE:
qmHandle/qmhandle-1.3.2/qmHandle -Fuser@domain.com

this removes not only messages, but all the mentioning of those messages from everywhere. (sasa4uk)

Categories
Uncategorized

Hsphere file paths

Mysql:
======
Socket file: /var/lib/mysql/mysql.sock
Database file: /var/lib/mysql
mysql password file: /var/lib/mysql/.my.cnf
Error log: /var/log/mysql/error.log

Ftp:
=====

Proftpd is default with hsphere.

Configuration file: /hsphere/shared/config/ftpd/proftpd.conf
Log file: /hsphere/local/var/proftpd/xferlog

Php:
=====

Categories
networking Uncategorized

Cannot Map NAS in Windows 10 Pro x64

I have purchased a D-link DNS 321, and after several hours of trying I could not map the NAS as a drive nor access it using NFS

Objective: use NAS as network file server.

Go to Programs and Features in Windows 10 Control Panel. Click Turn Windows features on or off link.
Scroll down to SMB 1.0/CIFS File Sharing Support and check all of the features. Click OK.
Once all of the installation is done, click Restart now.
In Windows Explorer go to Network => Storage (or whatever your NAS’ name is) and you will be presented with all the Volumes available.
Categories
Uncategorized

CURL ERROR: SSL certificate problem: self signed certificate in certificate chain (Authorize.net)

Recently there was a spike in Authorize.net customers that reported their sites credit card processing errors which, according to log files resulted in the following error produced:

CURL ERROR: SSL certificate problem: self signed certificate in certificate chain

Fix:

Testing (oneliner):

echo | openssl s_client -connect apitest.authorize.net:443 -showcerts -verify 10 -CAfile /home/path/to/cert.pem

Make sure to replace “/home/path/to/cert.pem” with the real path. If all is good you’ll get something like this at the end:

Verify return code: 0 (ok)

Otherwise you’ll see:

Verify return code: 19 (self signed certificate in certificate chain)