<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Pain in the rear.... in </title>
<link>http://www.dslreports.com/forum/r20230213</link>
<description></description>
<language>en</language>
<pubDate>Fri, 29 Aug 2008 21:11:54 EDT</pubDate>
<lastBuildDate>Fri, 29 Aug 2008 21:11:54 EDT</lastBuildDate>

<item>
<title>Re: Pain in the rear....</title>
<link>http://www.dslreports.com/forum/remark,20231320</link>
<description><![CDATA[<A HREF="/useremail/u/904015"><b>Rockrz</b></A> : Best way (ONLY way, actually) to deal with spam is to use MailWasher at &raquo;<A HREF="http://www.firetrust.com/products/mailwasher-pro" >www.firetrust.com/products/mailwasher-pro</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20231320</guid>
<pubDate>Wed, 26 Mar 2008 21:09:29 EDT</pubDate>
</item>

<item>
<title>Pain in the rear....</title>
<link>http://www.dslreports.com/forum/remark,20230213</link>
<description><![CDATA[<A HREF="/useremail/u/679831"><b>fancydancer</b></A> : that's the only way I can describe their email server management.  I never know what they are going to screw up next in regards to email.   :mad:  <br>Unfortunately, I manage customers with Exchange servers (which send non-RFC compliant messages) and have opted every single one of them out of the port 25 blocking but ATT still finds a way to screw me by pulling this crap.  Just stick to smtp auth without all the SSL bs, for crying out loud.  <br><small>--<br>Thank you for keeping this a work-free environment!</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20230213</guid>
<pubDate>Wed, 26 Mar 2008 18:02:34 EDT</pubDate>
</item>

</channel>
</rss>
