<?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>Sys Sandbox</title>
	<atom:link href="http://sandbox.frontline.ro/feed/" rel="self" type="application/rss+xml" />
	<link>http://sandbox.frontline.ro</link>
	<description>Tech blog @ frontline.ro</description>
	<lastBuildDate>Thu, 21 Jan 2010 14:47:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Courier-IMAP-SSL/TLS: Thunderbird error</title>
		<link>http://sandbox.frontline.ro/2009/10/07/courier-imap-ssl-tls-thunderbird-error/</link>
		<comments>http://sandbox.frontline.ro/2009/10/07/courier-imap-ssl-tls-thunderbird-error/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 13:38:22 +0000</pubDate>
		<dc:creator>sorin.pohontu</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[courier]]></category>
		<category><![CDATA[Courier-IMAP]]></category>
		<category><![CDATA[IMAP]]></category>
		<category><![CDATA[IMAP TLS]]></category>
		<category><![CDATA[QMail]]></category>
		<category><![CDATA[TLS]]></category>

		<guid isPermaLink="false">http://sandbox.frontline.ro/?p=64</guid>
		<description><![CDATA[The problem: Using an IMAP TLS mail account on Thunderbird could give an error: 
Thunderbird can&#8217;t connect securely to  because the site uses a security protocol which isn&#8217;t enabled.
Why: Looking at the the maillog (tail -f /usr/local/psa/var/log/maillog) we got:
imapd: couriertls: accept: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number
Solution: Edit /etc/courier-imap/imapd-ssl and check the values to match this:
# [...]]]></description>
		<wfw:commentRss>http://sandbox.frontline.ro/2009/10/07/courier-imap-ssl-tls-thunderbird-error/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to recalculate traffic and disk usage in Plesk Unix</title>
		<link>http://sandbox.frontline.ro/2009/09/21/plesk-howto-recalculate-traffic-and-disk-usage/</link>
		<comments>http://sandbox.frontline.ro/2009/09/21/plesk-howto-recalculate-traffic-and-disk-usage/#comments</comments>
		<pubDate>Mon, 21 Sep 2009 10:15:34 +0000</pubDate>
		<dc:creator>sorin.pohontu</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[plesk disk usage]]></category>
		<category><![CDATA[plesk traffic usage]]></category>

		<guid isPermaLink="false">http://sandbox.frontline.ro/?p=39</guid>
		<description><![CDATA[The problem: There are some updates on client files, but the changes are not seen in Plesk interface.

Why: Plesk counts statistics once a day (at 4:07 AM by default) with the help of the {Plesk_installation_dir}/admin/sbin/statistics utility, but not every time when you look at domain statistics. (see http://kb.parallels.com/en/752).

The solution: To update traffic and disk usage [...]]]></description>
		<wfw:commentRss>http://sandbox.frontline.ro/2009/09/21/plesk-howto-recalculate-traffic-and-disk-usage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plesk Linux Domain Alias 301 HTTP Redirect</title>
		<link>http://sandbox.frontline.ro/2009/08/13/plesk-linux-domain-alias-301-http-redirect/</link>
		<comments>http://sandbox.frontline.ro/2009/08/13/plesk-linux-domain-alias-301-http-redirect/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 09:18:19 +0000</pubDate>
		<dc:creator>sorin.pohontu</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[mod_rewrite]]></category>

		<guid isPermaLink="false">http://sandbox.frontline.ro/?p=16</guid>
		<description><![CDATA[The problem: A Plesk client has one or more domain aliases defined in Plesk Linux. In this article we&#8217;ll suppose that the main domain is my-domain.com, having my-domain.net as a domain alias.
In this case, the domain alias my-domain.net will appear as separate site to search engines (Google, Yahoo, MSN and so on). This situation can [...]]]></description>
		<wfw:commentRss>http://sandbox.frontline.ro/2009/08/13/plesk-linux-domain-alias-301-http-redirect/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Plesk Backup to Amazon S3: testing phase</title>
		<link>http://sandbox.frontline.ro/2008/10/31/plesk-backup-to-amazon-s3-testing-phase/</link>
		<comments>http://sandbox.frontline.ro/2008/10/31/plesk-backup-to-amazon-s3-testing-phase/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 16:50:30 +0000</pubDate>
		<dc:creator>sorin.pohontu</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Amazon S3]]></category>
		<category><![CDATA[JungleDisk]]></category>
		<category><![CDATA[rsync]]></category>
		<category><![CDATA[s3fs]]></category>
		<category><![CDATA[subcloud]]></category>

		<guid isPermaLink="false">http://sandbox.frontline.ro/?p=7</guid>
		<description><![CDATA[We are currently testing some solutions to an efficient way of syncing the Plesk Backups (see the previous post about creating them) to Amazon S3.
So far, the candidates are:
- s3fs, Fuse Over Amazon project on Google Code
- Subcloud, the commercial supported version of s3fs
- JungleDisk, Desktop Edition, with support for Linux, MacOS and Windows
What we [...]]]></description>
		<wfw:commentRss>http://sandbox.frontline.ro/2008/10/31/plesk-backup-to-amazon-s3-testing-phase/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Plesk 8.6.0 inetd changes</title>
		<link>http://sandbox.frontline.ro/2008/08/13/plesk-860-inetd-changes/</link>
		<comments>http://sandbox.frontline.ro/2008/08/13/plesk-860-inetd-changes/#comments</comments>
		<pubDate>Wed, 13 Aug 2008 08:11:46 +0000</pubDate>
		<dc:creator>sorin.pohontu</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[inetd]]></category>
		<category><![CDATA[xinetd]]></category>

		<guid isPermaLink="false">http://sandbox.frontline.ro/?p=6</guid>
		<description><![CDATA[On 28 July 2008, Parallels have released Parallels Plesk Control Panel 8.6.0.
It seems (for unknown reasons) that they changed from xinetd config files to the old inetd style. There&#8217;s no more /etc/xinetd.d/smtp_psa files and alike, instead Plesk is now using /etc/inetd.conf.
Keep this in mind when upgrading from ealier version, could save some time and problems [...]]]></description>
		<wfw:commentRss>http://sandbox.frontline.ro/2008/08/13/plesk-860-inetd-changes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

