<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ramblings from MostlyChris &#187; Plesk</title>
	<atom:link href="http://blog.mostlychris.com/tag/plesk/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mostlychris.com</link>
	<description>Tech stuff and a bit more</description>
	<lastBuildDate>Tue, 27 Dec 2011 14:23:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Sending a Copy of Email to Another Account with Qmail</title>
		<link>http://blog.mostlychris.com/2010/03/sending-a-copy-of-email-to-another-account-with-qmail/</link>
		<comments>http://blog.mostlychris.com/2010/03/sending-a-copy-of-email-to-another-account-with-qmail/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 12:50:49 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Qmail]]></category>
		<category><![CDATA[mail copy]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=645</guid>
		<description><![CDATA[Suppose you would like to send a copy of an incoming email to another account while the email still goes to the original account. You can do this by modifying the .qmail file of the original recipient and adding an entry that looks like the following: &#38;user@domain.com On a Plesk server, a full .qmail file [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2010/03/sending-a-copy-of-email-to-another-account-with-qmail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change Plesk TTL (Bulk edit)</title>
		<link>http://blog.mostlychris.com/2009/12/change-plesk-ttl-bulk-edit/</link>
		<comments>http://blog.mostlychris.com/2009/12/change-plesk-ttl-bulk-edit/#comments</comments>
		<pubDate>Sat, 12 Dec 2009 07:59:49 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=608</guid>
		<description><![CDATA[If you need to change the TTLs on all domains in Plesk at once, you can massage the database with the following command: mysql&#62; UPDATE `dns_zone` SET `ttl` = '300', `ttl_unit` = '60' WHERE `id` &#62;1; Substitute the TTL values for what you need. Since the flat files are still used by named to provide [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/12/change-plesk-ttl-bulk-edit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plesk 9.x Upgrades and Overuse Policy</title>
		<link>http://blog.mostlychris.com/2009/11/plesk-upgrades-overuse-policy/</link>
		<comments>http://blog.mostlychris.com/2009/11/plesk-upgrades-overuse-policy/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 05:48:07 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[domain_pref]]></category>
		<category><![CDATA[overuse]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=598</guid>
		<description><![CDATA[I had occassion to run across the following question recently: "Plesk was just upgraded to version 9.2.x and all domains now have an overuse policy set to not allow overuse. I can manually change this to allow overuse, but is there a way to do this through the database so I don't have to do [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/11/plesk-upgrades-overuse-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Migrating IP Addresses in Plesk</title>
		<link>http://blog.mostlychris.com/2009/08/migrating-ip-addresses-in-plesk/</link>
		<comments>http://blog.mostlychris.com/2009/08/migrating-ip-addresses-in-plesk/#comments</comments>
		<pubDate>Sat, 15 Aug 2009 13:11:27 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[migration]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=556</guid>
		<description><![CDATA[There are times when you may need to migrate many IP addresses in Plesk. You could either do this by hand, one domain at a time or you can modify the database by hand which will save countless years of your life. I will assume you have logged into mysql and have selected the psa [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/08/migrating-ip-addresses-in-plesk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable Submission Port on a Plesk Server</title>
		<link>http://blog.mostlychris.com/2009/04/enable-submission-port-on-a-plesk-server/</link>
		<comments>http://blog.mostlychris.com/2009/04/enable-submission-port-on-a-plesk-server/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 12:35:01 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Qmail]]></category>
		<category><![CDATA[smtp]]></category>
		<category><![CDATA[submission port]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=474</guid>
		<description><![CDATA[First, copy the smtp_psa file. cp /etc/xinetd.d/smtp_psa /etc/xinetd.d/smtp_additional Edit the newly copied file and replace the first line. Replace 'service smtp' with 'service submission' vi /etc/xinetd.d/smtp_additional Restart xinetd.d service xinetd restart Check that port 587 is listening on the server netstat -ltnp]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/enable-submission-port-on-a-plesk-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading Plesk Without Using the Updater (Deprecated)</title>
		<link>http://blog.mostlychris.com/2009/04/upgrading-plesk-without-using-the-updater/</link>
		<comments>http://blog.mostlychris.com/2009/04/upgrading-plesk-without-using-the-updater/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 23:09:50 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Upgrades]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=448</guid>
		<description><![CDATA[NOTE: Most of this is now deprecated. You can use the autoupdater included in the ~[plesk]/bin directory to do the updates. Just make sure you back things up first! Back everything up! ifconfig eth0; hostname cat /etc/hosts ## Verify that the primary IP matches hostname and hosts file &#160; &#160; Backups mkdir plesk_upgrade cp -a [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/upgrading-plesk-without-using-the-updater/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Miagrating IP addresses on Plesk</title>
		<link>http://blog.mostlychris.com/2009/04/miagrating-ip-addresses-on-plesk/</link>
		<comments>http://blog.mostlychris.com/2009/04/miagrating-ip-addresses-on-plesk/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 22:49:32 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[migration]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=441</guid>
		<description><![CDATA[When having to migrate hugh numbers of IP addresses on Plesk, here is a way to manipulate the database to do it without having to use the panel to do them one at a time. mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa mysql&#62; SELECT * FROM IP_Addresses; mysql&#62; UPDATE Repository SET component_id = &#91;new ip id&#93; WHERE [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/miagrating-ip-addresses-on-plesk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

