<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Why on earth did my email to a public folder go there?</title><link>http://blogs.technet.com/exchange/archive/2004/09/10/228114.aspx</link><description>The following has come up in various guises in internal questions and so I thought it was about time this was given to a wider audience. I’ve just sent an email to a public folder – how did it actually get there, given I have multiple replicas of the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Why on earth did my email to a public folder go there?</title><link>http://blogs.technet.com/exchange/archive/2004/09/10/228114.aspx#228685</link><pubDate>Mon, 13 Sep 2004 09:21:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:228685</guid><dc:creator>Neil Riches</dc:creator><description>Interesting article, thanks.&lt;br&gt;&lt;br&gt;It does put an interesting wrinkle on the old Ex 5.5 practice of not having a PF Store on an external-facing bridgehead server.  It would seem for performance reasons you'd want a store on the bridgehead with no replicas (so it holds the hierarchy only).  Assuming you have a lot of mail-enabled PFs that is.&lt;br&gt;&lt;br&gt;Food for thought :)&lt;br&gt;&lt;br&gt;Cheers again,&lt;br&gt;&lt;br&gt;Neil</description></item><item><title>re: Why on earth did my email to a public folder go there?</title><link>http://blogs.technet.com/exchange/archive/2004/09/10/228114.aspx#232805</link><pubDate>Wed, 22 Sep 2004 13:02:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:232805</guid><dc:creator>Robert Hupf</dc:creator><description>We're having an issue where emails to a mail-enabled public folder (that was working at one time mind you) in another site/admin group are going to a local delivery queue on a server in our site and just sitting there.  Further investigation has revealed that we may have a duplicate MESO object problem.  While troubleshooting that (don't you hate it when digging up one problem uncovers 10 more!) we found that when I created a new public folder in this remote site, and then mail-enabled it that it was not getting stamped with an email address.  I have been getting conflicting information about whether public folders are stamped by the Enterprise RUS or the domain RUS.  Any thoughts?&lt;br&gt;&lt;br&gt;P.S. I love your TechEd sessions, I always look for them when I go!</description></item></channel></rss>