 




<?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: Mailbox size problem!!!!</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/mailbox-size-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/mailbox-size-problem/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 01:41:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: stevesz</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/mailbox-size-problem/#comment-41389</link>
		<dc:creator>stevesz</dc:creator>
		<pubDate>Thu, 25 Jan 2007 21:38:58 +0000</pubDate>
		<guid isPermaLink="false">#comment-41389</guid>
		<description><![CDATA[You need to make the change in ADUC and in Exchange. The size set in ADUC for a user, if it exceeds the Exchange limit, means nothing as this limit overrides the ADUC size limit.

Setting such a high limit opens you to other problems, however. E-mail is not meant to handle such large attachments. An attachment of this size should be placed on an FTP site for the recipient to download. It could be your site or the recipient&#039;s site. With the mailbox size limits imposed by some companies, one or two messages with attachments of this size would effectively shut down the user&#039;s mailbox for, at least. sending mail. Also think of the effect if the recipient&#039;s mailserver does not allow mail of that size to be received. You get the bounce, with a 27+ MB attachment.

Another factor to consider is that if you do it for one user, you&#039;ll get another user who wants an increased limit, and eventually you will have a snowball effect on your mail infrastructure.

One of my clients has a very generous limit of 15 MB for attachments, mainly for the editorial department who deal with large graphic files. Anything above that limit is to be placed on the FTP server maintained for that purpose only. High quality photo files can easily exceed 30 MB. This has worked very well for them (except when they forget the instructions to give the sender to access the server).]]></description>
		<content:encoded><![CDATA[<p>You need to make the change in ADUC and in Exchange. The size set in ADUC for a user, if it exceeds the Exchange limit, means nothing as this limit overrides the ADUC size limit.</p>
<p>Setting such a high limit opens you to other problems, however. E-mail is not meant to handle such large attachments. An attachment of this size should be placed on an FTP site for the recipient to download. It could be your site or the recipient&#8217;s site. With the mailbox size limits imposed by some companies, one or two messages with attachments of this size would effectively shut down the user&#8217;s mailbox for, at least. sending mail. Also think of the effect if the recipient&#8217;s mailserver does not allow mail of that size to be received. You get the bounce, with a 27+ MB attachment.</p>
<p>Another factor to consider is that if you do it for one user, you&#8217;ll get another user who wants an increased limit, and eventually you will have a snowball effect on your mail infrastructure.</p>
<p>One of my clients has a very generous limit of 15 MB for attachments, mainly for the editorial department who deal with large graphic files. Anything above that limit is to be placed on the FTP server maintained for that purpose only. High quality photo files can easily exceed 30 MB. This has worked very well for them (except when they forget the instructions to give the sender to access the server).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: petroleumman</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/mailbox-size-problem/#comment-41390</link>
		<dc:creator>petroleumman</dc:creator>
		<pubDate>Wed, 24 Jan 2007 11:20:33 +0000</pubDate>
		<guid isPermaLink="false">#comment-41390</guid>
		<description><![CDATA[Hello,

You can set your server limits (ESM =&gt; Global =&gt; Message Delivery properties)default value for sending message size to no limit then use ADUC properties to restrict message size on a per user basis to solve your problem.

One thing you should not overlook is any SMTP firewall policy settings that you have in place. Make sure your firewall policy has a value equal or greater than your server or users ADUC properties are set or this will become your point of failure. 

Good luck!]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>You can set your server limits (ESM =&gt; Global =&gt; Message Delivery properties)default value for sending message size to no limit then use ADUC properties to restrict message size on a per user basis to solve your problem.</p>
<p>One thing you should not overlook is any SMTP firewall policy settings that you have in place. Make sure your firewall policy has a value equal or greater than your server or users ADUC properties are set or this will become your point of failure. </p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadyj</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/mailbox-size-problem/#comment-41391</link>
		<dc:creator>shadyj</dc:creator>
		<pubDate>Wed, 24 Jan 2007 09:38:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-41391</guid>
		<description><![CDATA[You need to make this change in the Delivery Restrictions section, not the Storage Limits:Warning section.]]></description>
		<content:encoded><![CDATA[<p>You need to make this change in the Delivery Restrictions section, not the Storage Limits:Warning section.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.039 seconds using memcached
Object Caching 295/301 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-23 04:09:31 -->