<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Sailing</title>
	<atom:link href="http://ams1.x31.com/~andy/sailing/feed/" rel="self" type="application/rss+xml" />
	<link>http://ams1.x31.com/~andy</link>
	<description>Telecommunications Consultant</description>
	<lastBuildDate>Wed, 04 Aug 2010 10:49:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Andy</title>
		<link>http://ams1.x31.com/~andy/sailing/comment-page-1/#comment-4741</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 07 Jul 2010 07:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://ams1.x31.com/~andy/?page_id=461#comment-4741</guid>
		<description>It appears that QTEL are now periodically performing
deep-packet-inspection (DPI) where they look inside the data stream and
identify the protocols being used.

This is different to the original problem where they simply blocked port
25.  The use of DPI means they will detect and block all SMTP (mail)
traffic.

I&#039;ve just implemented SSL tunnels between my server in Amsterdam and the
mailserver here. This allows me to encrypt all traffic thereby making it
impossible for QTEL to eavesdrop on my communications.

You need to ask your provider if they can do SSL for mail - so that the
HELO, EHLO messages etc. in the data streams are not visible to QTEL. I
use stunnel for this purpose.

Hope this helps,

I&#039;m happy to meet up for a coffee and chat if you like - there are many
ways of working around the issue depending on your systems so you don&#039;t
have to pay to use the stupidly-expensive QTEL MPLS service for email.</description>
		<content:encoded><![CDATA[<p>It appears that QTEL are now periodically performing<br />
deep-packet-inspection (DPI) where they look inside the data stream and<br />
identify the protocols being used.</p>
<p>This is different to the original problem where they simply blocked port<br />
25.  The use of DPI means they will detect and block all SMTP (mail)<br />
traffic.</p>
<p>I&#8217;ve just implemented SSL tunnels between my server in Amsterdam and the<br />
mailserver here. This allows me to encrypt all traffic thereby making it<br />
impossible for QTEL to eavesdrop on my communications.</p>
<p>You need to ask your provider if they can do SSL for mail &#8211; so that the<br />
HELO, EHLO messages etc. in the data streams are not visible to QTEL. I<br />
use stunnel for this purpose.</p>
<p>Hope this helps,</p>
<p>I&#8217;m happy to meet up for a coffee and chat if you like &#8211; there are many<br />
ways of working around the issue depending on your systems so you don&#8217;t<br />
have to pay to use the stupidly-expensive QTEL MPLS service for email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zabed</title>
		<link>http://ams1.x31.com/~andy/sailing/comment-page-1/#comment-4711</link>
		<dc:creator>Zabed</dc:creator>
		<pubDate>Tue, 06 Jul 2010 06:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://ams1.x31.com/~andy/?page_id=461#comment-4711</guid>
		<description>Dear Mr. Fletcher
I have googled regarding email problem of Q-Tel and then I have found this nice site. Our problem is Q-Tel is blocking our outgoing mail frequently like once in a month and it opens after 2-3 days but webmail is working continuously. We are using mail server of   our web hosting provider and port is 26. Can u please suggest, how to get rid of from this issue.
Thank you very much.</description>
		<content:encoded><![CDATA[<p>Dear Mr. Fletcher<br />
I have googled regarding email problem of Q-Tel and then I have found this nice site. Our problem is Q-Tel is blocking our outgoing mail frequently like once in a month and it opens after 2-3 days but webmail is working continuously. We are using mail server of   our web hosting provider and port is 26. Can u please suggest, how to get rid of from this issue.<br />
Thank you very much.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
