Skip to content

Wordpress

Exim Error: Exit R=virtual_aliases: No Such User Here

T he following Exim mail servers error was encountered while sending out mails. The original error was experienced by Gravity Forms WordPress plugin. However, I was able to test it out by using command line to rule out the plugin.

someone@domain.com R=virtual_aliases: No Such User Here

The debug message I received via Gravity Forms is the following. This confirms the mail has been passed on from WordPress to the mail server.

2016-03-25 11:06:04.042599 - DEBUG --> GFCommon::send_email(): Result from wp_mail(): 1
2016-03-25 11:06:04.042748 - DEBUG --> GFCommon::send_email(): Mail was passed from WordPress to the mail server.
2016-03-25 11:06:04.153172 - DEBUG --> GFFormDisplay::handle_confirmation(): Sending confirmation.

Before I go any further, I would like to give some background information on domain.com, which the following aspects are hosted as below.

Read more

How to stop WordPress Brute-force login attack

Wordpress admin login easily be filtered by IP Address. This method is especially useful as a measure to tackle Brute-force login attack. This is achieved by placing a .htaccess in the wp-admin directory with the following… Order Deny,Allow Allow from IP.IP.IP.IP Allow from IP.IP.IP.0/24 Deny from all You can also use the CIDR notation to Allow/Deny a range of IP addresses.

WordPress Find and Replace String

I had to do a find and replace a string on all of the wordpress post. This can only be done via a MySQL query and won’t take more than a minute. This is how it’s done. In the following example, I will be finding X and replacing it with Y The string will find X in every single post and replace it with Y. This also works with phrases, URLs etc.. update wp_posts set post_content = replace(post_content, 'X', 'Y')

How to 301 Redirect WordPress Posts To New Domain

301 Redirect is considered as a permanent redirect compared to a 302 redirect which is temporary. Therefore when moving wordpress to a new domain, it is a good idea to redirect all the posts to the new domain. This way all the search engine records will be kept intact and this means you won’t lose any traffics / hits to the website. This doesn’t mean redirecting from fnode.com to nish.com, it will also redirect every single URL associated with fnode.com to nish.com. For instance, if a user is looking for a particular post and goes to fnode.com, they will be redirected to the corresponding post on nish.com Here is an example of one of the most popular post on the site… http://www.fnode.com/2007/06/02/make-bisoncam-work-on-windows-vista/ When users clicks on the above link, they will be automatically redirect to http://www.nish.com/2007/06/02/make-bisoncam-work-on-windows-vista/ This way, the user won’t notice the domain change because it is 99% directed via search engine or linked URL. Read more

Moving wordpress blog to new domain

This is how I moved my wordpress blog from fnode.com to nish.com Install wordpress on nish.com Went to fnode.com and copied the wp-content Directory and replaced it with the Directiory on nish.com (So all the theme, plug-in and the uploaded contents are all there…) Went to fnode.com and used phpMyAdmin to drum an .sql file of the database. (You may prefer .gz depending on the file size) Went to nish.com and used phpMyAdmin to drop all the tables on the wordpress database. Imported the backed up database from fnode.com Ran the following SQL Queries… <br /> UPDATE wp_options SET option_value = replace(option_value, 'http://www.fnode.com', 'http://www.nish.com') WHERE option_name = 'home' OR option_name = 'siteurl';<br /> UPDATE wp_posts SET guid = replace(guid, 'http://www.fnode.com','http://www.nish.com');<br /> UPDATE wp_posts SET post_content = replace(post_content, 'http://www.fnode.com', 'http://www.nish.com');<br /> That’s it, All set, now you can tweek the blog!