<?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"
	>
<channel>
	<title>Comments on: Rant! Another Rediculous BlackBerry Limitation?</title>
	<atom:link href="http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/</link>
	<description>BlackBerry News and Reviews</description>
	<pubDate>Thu, 24 Jul 2008 09:30:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ronen Halevy</title>
		<link>http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2770</link>
		<dc:creator>Ronen Halevy</dc:creator>
		<pubDate>Thu, 10 Apr 2008 16:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2770</guid>
		<description>I think the funniest part is that this is by design and not a bug</description>
		<content:encoded><![CDATA[<p>I think the funniest part is that this is by design and not a bug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David B</title>
		<link>http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2768</link>
		<dc:creator>David B</dc:creator>
		<pubDate>Thu, 10 Apr 2008 16:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2768</guid>
		<description>Yahoo mail was like this too (and may still be).  My previous employer used Yahoo Business Mail, and we had to get Yahoo to make a special concession for our account addresses as Yahoo was tripping of recipient lists over 32 addresses even when directly accessing via POP3.  The 32 limit in that case was applied to each field, so there could be 32 in the TO and 32 in the CC , but any more than that you would see (as you do on a Blackberry) the message that the distribution was truncated.

In a way, it has a side benefit.  If your email address is 33rd or higher, at least when idiots do a Reply-All instead of just a Reply, you won't see it if they are replying from their BB! ;)

But sometimes it is REALLY annoying, and I wish RIM would eliminate the limit (or apply the limit only to BCC field, who needs to BCC more than a couple folks honestly).</description>
		<content:encoded><![CDATA[<p>Yahoo mail was like this too (and may still be).  My previous employer used Yahoo Business Mail, and we had to get Yahoo to make a special concession for our account addresses as Yahoo was tripping of recipient lists over 32 addresses even when directly accessing via POP3.  The 32 limit in that case was applied to each field, so there could be 32 in the TO and 32 in the CC , but any more than that you would see (as you do on a Blackberry) the message that the distribution was truncated.</p>
<p>In a way, it has a side benefit.  If your email address is 33rd or higher, at least when idiots do a Reply-All instead of just a Reply, you won&#8217;t see it if they are replying from their BB! <img src='http://www.berryreview.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>But sometimes it is REALLY annoying, and I wish RIM would eliminate the limit (or apply the limit only to BCC field, who needs to BCC more than a couple folks honestly).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luciano ES</title>
		<link>http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2767</link>
		<dc:creator>Luciano ES</dc:creator>
		<pubDate>Thu, 10 Apr 2008 16:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.berryreview.com/2008/04/10/rant-another-rediculous-blackberry-limitation/#comment-2767</guid>
		<description>The spam idea is bogus. There must be some clause in the EULA that forbids spam, and tracking/identifying a spammer with a Blackberry would be so easy it would spoil the fun.</description>
		<content:encoded><![CDATA[<p>The spam idea is bogus. There must be some clause in the EULA that forbids spam, and tracking/identifying a spammer with a Blackberry would be so easy it would spoil the fun.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
