<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel>
	  <title>Ask MetaFilter questions tagged with personaldomain</title>
      <link>http://ask.metafilter.com/tags/personaldomain</link>
      <description>Questions tagged with 'personaldomain' at Ask MetaFilter.</description>
	  <pubDate>Thu, 10 Apr 2008 11:49:20 -0800</pubDate> <lastBuildDate>Thu, 10 Apr 2008 11:49:20 -0800</lastBuildDate>

      <language>en-us</language>
	  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
	  <ttl>60</ttl>	  
	<item>
	<title>What&apos;s my ISP up to?</title>
	<link>http://ask.metafilter.com/88446/Whats%2Dmy%2DISP%2Dup%2Dto</link>	
	<description>Starting this week, we had to &quot;register&quot; our non-&lt;strong&gt;@&lt;em&gt;mybigtimeserviceprovider&lt;/em&gt;.com &lt;/strong&gt;email addresses in order to be able to send out email.
Both my wife and I have our own domains that we use for web sites and our personal email addresses.&lt;br&gt;
When those domains were initially set up, we were able to simply point our email clients to our remote domain email servers (mail.domainname.com) for outgoing and inbound email. We happily sent and received our email through that remote server, over our home connection.&lt;br&gt;
&lt;em&gt;Then&lt;/em&gt; our ISP put a block on that kind of activity: though we were still able to receive email from mail.domainname.com, we had to use our ISP&apos;s SMTP server (we&apos;ll call it smtp.mybigtimeserviceprovider.com) to &lt;em&gt;send&lt;/em&gt; our mail. This was annoying. It also seemed to me that despite the ISP&apos;s assurances that this was for our protection, it actually increased the likelihood that my outbound emails would look like spam to people I sent them to, as they arrived from one SMTP server, bearing an email address from another server. (correct me if this is wrong thinking)&lt;br&gt;
&lt;br&gt;
Last week, my wife, in whose name our household ISP account is held, received an email informing her that (paraphrased here, I don&apos;t have the email at work):&lt;br&gt;
&lt;br&gt;
&lt;blockquote&gt;&quot;We have noticed that you often use non-&lt;strong&gt;@&lt;em&gt;mybigtimeserviceprovider&lt;/em&gt;.com&lt;/strong&gt; email addresses for your outgoing mail** and want you to know that, due to certain new security features we&apos;ve installed &lt;em&gt;for your protection&lt;/em&gt; you will need to add these addresses to a list of verified addresses through our webmail panel. Failure to add these addresses will result in you getting a &lt;strong&gt;503: unable to send&lt;/strong&gt; error message from our servers for your outbound mail.&quot;&lt;/blockquote&gt;&lt;br&gt;
&lt;br&gt;
Is there any good reason that they would need to have a record of my personal, non-&lt;strong&gt;@&lt;em&gt;mybigtimeserviceprovider&lt;/em&gt;.com&lt;/strong&gt; email addresses &quot;for security reasons?&quot;&lt;br&gt;
&lt;br&gt;
This is feeling like the straw that breaks my back where this service provider is concerned...&lt;br&gt;
&lt;br&gt;
** &lt;small&gt;WTF? they&apos;re spying on my email addresses? what else are they scanning for?&lt;/small&gt;</description>
	<guid isPermaLink="false">tag:ask.metafilter.com,2008:site.88446</guid>
	<pubDate>Thu, 10 Apr 2008 11:49:20 -0800</pubDate>
	<category>emailsecurity</category>
	<category>personaldomain</category>
	<category>personalemail</category>
	<category>popemail</category>
	<category>smtpemail</category>
	<dc:creator>I, Credulous</dc:creator>
	</item>
	
	</channel>
</rss>

