<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>lekkimworld.commailsettings</title>
    <link>http://lekkimworld.com/tags/mailsettings/</link>
    <description>IBM Lotus Notes/Domino, Websphere, IBM Connections, mobile, web, JavaScript, Java...</description>
    <language>en</language>
    <copyright>Mikkel Flindt Heisterberg (mh [at] intravision [dot] dk</copyright>
    <pubDate>Sat, 19 May 2012 06:50:25 GMT</pubDate>
    <dc:creator>Mikkel Flindt Heisterberg (mh [at] intravision [dot] dk</dc:creator>
    <dc:date>2012-05-19T06:50:25Z</dc:date>
    <dc:language>en</dc:language>
    <dc:rights>Mikkel Flindt Heisterberg (mh [at] intravision [dot] dk</dc:rights>
    <image>
      <title>lekkimworld.commailsettings</title>
      <url>http://lekkimworld.com/tags/mailsettings/</url>
    </image>
    <item>
      <title>PMR at Lotus Support</title>
      <link>http://lekkimworld.com/2006/07/05/pmr_at_lotus_support.html</link>
      <content:encoded>&lt;p&gt;
Just got a call from Lotus Support confirming that the &lt;a href="http://lekkimworld.com/2006/06/22/force_application_of_mail_settings.html"&gt;issue mentioned previously&lt;/a&gt; with mail settings not being correctly applied is indeed a bug in the software. In short the bug implies that a mail setting that requires an agent to be enabled (e.g. the "Allow Notes to update To Do status and dates for incomplete entries" setting on the calendar profile) will not be correctly applied to user mail databases.
&lt;/p&gt;
&lt;p&gt;
For the time being you can use &lt;a href="http://lekkimworld.com/2006/04/07/1144399348102.html"&gt;the agent mentioned previously&lt;/a&gt; to work around the problem.
&lt;/p&gt;</content:encoded>
      <category domain="http://lekkimworld.com/categories/ibm_products/">IBM</category>
      <category domain="http://lekkimworld.com/tags/lotussupport/">lotussupport</category>
      <category domain="http://lekkimworld.com/tags/mailsettings/">mailsettings</category>
      <category domain="http://lekkimworld.com/tags/policies/">policies</category>
      <pubDate>Wed, 05 Jul 2006 10:00:47 GMT</pubDate>
      <guid isPermaLink="false">tag:lekkimworld.com,2006-07-05:default/1152093647134</guid>
      <dc:date>2006-07-05T10:00:47Z</dc:date>
    </item>
    <item>
      <title>Force application of mail settings</title>
      <link>http://lekkimworld.com/2006/06/22/force_application_of_mail_settings.html</link>
      <content:encoded>&lt;p&gt;
As previously reported I think I've found a bug in how Domino applied mail settings to users mail databases - at least when the setting requires an agent to be enabled as well (the "Allow Notes to update To Do status and dates for incomplete entries" setting on the calendar profile). For those who want to read the previous posts the first one is &lt;a href="http://lekkimworld.com/2006/03/31/1143811194087.html"&gt;here&lt;/a&gt; ("Loving policies - especially mail settings") and the second one is &lt;a href="http://lekkimworld.com/2006/04/07/1144399348102.html"&gt;here&lt;/a&gt; (Re: Loving policies - especially mail settings).
&lt;/p&gt;
&lt;p&gt;
I finally got around to bringing the issue up before Lotus Support and as part of the support process I learned a new AdminP command:
&lt;pre class="code"&gt;
Tell AdminP Process Mail Policy
&lt;/pre&gt;
The command will force AdminP to apply mail settings immediately. Nice. Some might know the command already but I sure didn't.
&lt;/p&gt;</content:encoded>
      <category domain="http://lekkimworld.com/categories/ibm_products/">IBM</category>
      <category domain="http://lekkimworld.com/tags/domino/">domino</category>
      <category domain="http://lekkimworld.com/tags/mailsettings/">mailsettings</category>
      <category domain="http://lekkimworld.com/tags/policies/">policies</category>
      <pubDate>Thu, 22 Jun 2006 15:01:57 GMT</pubDate>
      <guid isPermaLink="false">tag:lekkimworld.com,2006-06-22:default/1150988517807</guid>
      <dc:date>2006-06-22T15:01:57Z</dc:date>
    </item>
  </channel>
</rss>


