When you try to password protect a WordPress subdirectory by adding .htaccess and .htpasswd under subdirectory, you sometimes (in fact most of the times) get Error 404 – Page not found when you visit that subdirectory location in the browser.
To fix this error, add the following line at the top of .htaccess located in the root of your WordPress installation (yes, root .htaccess and not .htaccess of your password protected subdirectory), and you’re good to go now.
ErrorDocument 401 default
Do you have any different solution? I would love to hear your comments.
amavisd-new is a high-performance interface between mailer (MTA) and content checkers: virus scanners, and/or SpamAssassin.
Clam AntiVirus (ClamAV) is a free and open-source, cross-platform antivirus software toolkit able to detect many types of malicious software, including viruses. One of its main uses is on mail servers as a server-side email virus scanner.
SpamAssassin is a mail filter to identify spam. It is an intelligent email filter which uses a diverse range of tests to identify unsolicited bulk email, more commonly known as Spam.
yum install amavisd-new
☑ This will install amavisd-new and a bunch of dependencies. It will also install SpamAssassin by default.
yum install clamav clamav-update
☑ This will install ClamAV.
☑ This will update the ClamAV database.
☑ Edit amavisd.conf.
Change the following lines like this…
$mydomain = ‘domain.com’; # a convenient default for other settings
$myhostname = 'mail.domain.com’; # must be a fully-qualified domain name and same as reverse DNS lookup
☑ Make sure everything is set in postfix’s configuration file master.cf
On top of master.cf, you should have something like…
smtp inet n - n - - smtpd
Most developers (and companies) choose Git over SVN as their version control system. However, they have to use SVN to ship updates to WordPress.org plugin repo.
Ship is a new application designed to help developers deploy plugins directly from GitHub to WordPress.org repo. All you have to do is tag the release on GitHub and it will automatically push updates to the plugin’s official SVN repo on WordPress.org.
In order to use Ship, you must have already submitted your plugin zip file to WordPress.org. You can then sign into the Ship with GitHub account and authorize its access to your repositories.
Ship will then fetch all of your repositories and you’ll have to select the ones you want to hook up with a WordPress.org SVN address in order to start syncing updates.