I recently had a frustrating problem where I couldn’t upload files into MailWizz host. This also causes problems with command line CSV imports. I discovered I had to open up /etc/my.cnf and edit the following line to
max_allowed_packet = 110M
then in /etc/php.ini I changed the following two lines
post_max_size = 200M
upload_max_filesize = 500M
service mariadb restart
Under settings, import/export on the backend I set CLI Import Enabled to Yes and Url Import Enabled to Yes.
I recently need to block Barracuda network ips from accessing my mail server, MailWizz. I did the typical
iptables -A INPUT -s 22.214.171.124/20 -j DROP
iptables -A INPUT -s 126.96.36.199/21 -j DROP
iptables -A INPUT -s 188.8.131.52/27 -j DROP
iptables -A INPUT -s 184.108.40.206/27 -j DROP
iptables -A INPUT -s 220.127.116.11/24 -j DROP
iptables -A INPUT -s 18.104.22.168 -j DROP
iptables -A INPUT -s 22.214.171.124 -j DROP
service iptables save
service iptables end
the problem with this setup is that those rules end up getting appended to the end and never get blocked. It’s better to go into the iptables directly. ON Centos 7, that is located in /etc/sysconfig/iptables. I added these lines directly before any of the rules were executed.
-A INPUT -s 126.96.36.199/20 -j DROP
-A INPUT -s 188.8.131.52/21 -j DROP
-A INPUT -s 184.108.40.206/27 -j DROP
-A INPUT -s 220.127.116.11/27 -j DROP
-A INPUT -s 18.104.22.168/24 -j DROP
-A INPUT -s 22.214.171.124/32 -j DROP
-A INPUT -s 126.96.36.199/32 -j DROP
I’m also putting in a post on how to block Amazon Bots. However you’ll need to redo the above after running these commands in Centos 7
I recently had a project with SQL Server 2014 utilizing the Visual Studio 2015 shell for a Sql Server Integration Project. I tried to run the SSIS task in Visual Chron and kept getting errors. After exhaustive research I discovered that I had to make sure to go into the project properties and choose SQL Server 2014 as your TargetServerVersion. Once I did this and recompiled one of my scripts, it worked.
At my company we regularly send out email marketing and emails for our vendors. We needed a solution that could utilize multiple domains and multiple IPS. We decided to host our email solution on a Linux VM using VirtualMin. Here’s … Continue reading →
I recently migrated a SQL Server 2008 R2 database to SQL Server 2014. We host with Rackspace, so I had them restore our databases from backup to the new server. I was left with database users that weren’t linked to SQL Server Users. Even after I added the users they were still not linked together and the system wouldn’t offer me the option. The following SQL allowed me to fix the problem.
Assign ownership of the database to a current user on the new server Alter authorization on database::[DATABASENAME] to [DOMAIN\USERNAME]
Find the users that aren’t associated with their SQL Login with Exec sp_change_users_login ‘Report’
Autofix the logins to link the SQL Server Database User to the SQL Server Login User exec sp_change_users_Login ‘Auto_Fix’,’USERNAME’
The new database clearly won’t have the SQL Server Login Users until you add them so add them manually before you run the above routines.