<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.mail.ims.general">
    <title>gmane.mail.ims.general</title>
    <link>http://blog.gmane.org/gmane.mail.ims.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7048"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7047"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7046"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7045"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7034"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7033"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7026"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7020"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7016"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7011"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7004"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/7001"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6986"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6983"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6979"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6976"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6974"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6971"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6968"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.ims.general/6963"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7048">
    <title>problem in messaging server 7 patch 28</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7048</link>
    <description>&lt;pre&gt;Hello,

I applied messaging server server 7 patch 28 on one of my production
server. Oracle Communications Messaging Server 7u5-28.21(7.0.5.28.0) 64bit
(built Apr 8 2013).

After applying the patch I am not able to send mails to the lists mentioned
in alias file.

If I revert the patch to older version i.e. patch 27, I can send mail to
the list mentioned in alias file.

I have many mailing lists mentioned in the alias file. Is there any work
around to this problem?

Regards,

Adi Narayana
&lt;/pre&gt;</description>
    <dc:creator>Adi Narayana</dc:creator>
    <dc:date>2013-05-18T03:20:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7047">
    <title>spamfilterX_string_action sieve filter memberof LDAP lookup</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7047</link>
    <description>&lt;pre&gt;
I thought that I have seen this before, but I can't find it now. :)

I would like to have a spamfilterX_string_action filter that can 
determine if a user is a member of a certain class/group.

For example ClamAV is integrated via libclamav as a 
sourcespamfilterXoptin on the enqueuing channel, we want all mail to be 
scanned, but certain accounts/addresses to accept messages that contain 
malware like our "report-a-suspect" message address.  So we basically 
have two "virus" class of services.  First, let us call it 
"RECIPIENT_IS_VIRUS_OPT_IN" is the normal (99.999% of users) where a 
message is scanned and rejected (refused) if it tests positive.  Clean 
messages get a header added with $U and passed on.  The second class, 
lets call it "RECIPIENT_IS_VIRUS_OPT_OUT" is where a message is scanned, 
accepted, header added with $U and passed on.  (Note that opt-in or 
opt-out deals more with the action after a messages is scanned, not that 
the user is opt'd-out or -in _for_ scanning.  All messages are to be&lt;/pre&gt;</description>
    <dc:creator>Derek Diget</dc:creator>
    <dc:date>2013-05-16T16:46:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7046">
    <title>Hosting the "Info-iMS" mailing list</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7046</link>
    <description>&lt;pre&gt;Old friends:

Info-iMS-QMRIvgJGioDQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org was set up in March, 2002, to provide a stable place 
to discuss the succession of products descended from the iPlanet 
Messaging Server.  There are currently over 350 subscribers and 100 
Mbytes of archives from the last eleven years.

However, I am further narrowing my Internet footprint in retirement, and
specifically, will no longer operate Arnold.com, so I'd like to find a
new place for the list.  It's quite basic, really.  Anyone with a list 
manager could do it.  However, it would still need a coordinator to
assist folks in managing subscriptions and culling bad addresses.  The 
new list owner can either populate the list from the current 
subscriptions (recommended) or require new subscriptions.  I've managed 
to keep the list clean over the years by deleting bad addresses.

There is also the question of the archives.  These are in 115 plain text 
files in message digest format, one file for each month.  This is not as 
unreasonable as it&lt;/pre&gt;</description>
    <dc:creator>Steve Arnold</dc:creator>
    <dc:date>2013-05-02T05:40:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7045">
    <title>AUTO : Non-disponible</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7045</link>
    <description>&lt;pre&gt;
Je serai absent(e) du  11/13/2012 au 01/31/2014.

Je ne suis plus employé chez Vidéotron. I am no longer an employee of
Vidéotron

Contactez Ross Beaudoin - please Contact Ross Beaudoin


Remarque : ceci est une réponse automatique à votre message  "Re:
[Info-iMS] MTA fix MIME structure?" envoyé le 05/01/2013 9:15:47.

C'est la seule notification que vous recevrez pendant l'absence de cette
personne.


&lt;/pre&gt;</description>
    <dc:creator>Sylvain.Cousineau-XzQKRVe1yT2aMJb+Lgu22Q&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-01T14:04:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7034">
    <title>MTA fix MIME structure?</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7034</link>
    <description>&lt;pre&gt;We've got an odd situation where our MTA (allegedly) is modifying the 
MIME structure of some incorrectly structured messages.  Or maybe it's 
the milter doing it?  Or maybe

Any comments regarding the appropriateness of the MTA/milter fixing 
incorrectly structured MIME messages in transit?

spamfilter1_library=...libmilter.so
spamfilter1_config_file=...milter.opt
spamfilter1_string_action=data:,$M
spamfilter1_optional=0
spamfilter1_final=2

MTA version is 7u4-26.01

milter is PureMessage 5.  As far as I can tell from the logs, 
PureMessage did not intentionally modify the message (strip a virus 
part, or whatever).

Here is the message as received (modified form) by the recipient:

&amp;lt;snip headers&amp;gt;
MIME-version: 1.0
Content-type: multipart/alternative;
  boundary="Boundary_(ID_UgfE+cHbb0j1JWMh6bZdTg)"; charset=utf-8
&amp;lt;snip headers&amp;gt;

--=======G88546249933746096=
Content-Type: text/plain; charset"us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit


Your email client doesn't support HTML emails. Either &lt;/pre&gt;</description>
    <dc:creator>Jesse Thompson</dc:creator>
    <dc:date>2013-04-09T19:12:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7033">
    <title>Netapp data stores</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7033</link>
    <description>&lt;pre&gt;Hi everyone, just trying to do some due diligence. Our environment consists of messaging servers running a mix of 7u4-20.01, and 6.3-16.01, and NetApp filers for actual mailbox data storage. The current filers have OS v 7.X, but we are looking  to upgrade to some faster heads. The new NetApp filer heads come with NetApp OS v 8.X. Oracle support says that they don't qualify filers with the messaging server, so they cannot tell me if there are any issues with this newer NetApp OS release. If any of you folks might already be using this combo in your own environment, I'd appreciate hearing about your experiences. 

Thanks!

-Peter Kaldis




&lt;/pre&gt;</description>
    <dc:creator>Peter Kaldis</dc:creator>
    <dc:date>2013-03-18T16:45:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7026">
    <title>reprocess channel - how to not inherit transactionlimit?</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7026</link>
    <description>&lt;pre&gt;It appears that the reprocess channel inherits the transactionlimit 
setting from the original inbound channel.

So, when it has a large queue it's processing, it can't actually finish 
processing all of the messages.

Setting transactionlimit on the channel definition does not seem to 
override this behavior.  Am I missing something?

Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit 
(built Aug 30 2012)

Jesse

&lt;/pre&gt;</description>
    <dc:creator>Jesse Thompson</dc:creator>
    <dc:date>2013-03-05T17:09:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7020">
    <title>Sieve vacation message size limit</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7020</link>
    <description>&lt;pre&gt;I have a user who wants to send a very large vacation reply message.  'Very Large' as in, about 10k bytes.

It appears that the message gets truncated at 8k bytes.  Exactly 8192 bytes.

Is there a way to change the message size limit?

Alan

------------------------------------------------------------
Capitan Holy Hippie
Commander, Commune Ship LaPaz NCC170126-L

&lt;/pre&gt;</description>
    <dc:creator>Capitan Holy Hippie</dc:creator>
    <dc:date>2013-02-25T22:43:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7016">
    <title>STARTTLS encryption ciphers and logging</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7016</link>
    <description>&lt;pre&gt;
7u4 Solaris 10 SPARC with SUNWtls patch 125358-15

Sorry for the long post...I had tried some stuff before starting this 
message and then kept trying things as I wrote this post. :(  It 
probably should be a blog post if I had one....


I am looking at the Certificate Based Authentication for Messaging 
Server web page at 
&amp;lt;https://wikis.oracle.com/display/CommSuite/Certificate+Based+Authentication+for+Messaging+Server&amp;gt; 
since it seems to be the place where a good deal of the NSS (SSL/TLS)
stuff is documented.

In looking at the Messaging Transfer Agent (MTA) SSL-related Channel 
Keywords section I am wondering if there is a way to log the SSL/TLS 
negotiation (especially the cipher suites offered with the SSL/TLS 
CLIENT_HELLO) for either an in-bound message to a slave debug or an 
out-bound message to a master debug file?  Or, anywhere for that matter. 
Reason that I am asking is we have a site (hosting company so the 
destination domains we are sending to are unknown ahead of time) that 
our out-bound c&lt;/pre&gt;</description>
    <dc:creator>Derek Diget</dc:creator>
    <dc:date>2013-02-15T07:11:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7011">
    <title>Two copies of one message, adding headerline</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7011</link>
    <description>&lt;pre&gt;Hi, all,

running:

Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)
libimta.so 7u4-24.01 64bit (built 10:55:13, Nov 17 2011)
Using /usr/appl/comms/messaging/config/imta.cnf (compiled)
Linux hostname 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

Suppose the system running iMS receives Internet mail from an intermediate system, which is located in a DMZ-like environment. This intermediate system cannot be changed, it is not managed by my customer, but by a 3rd party. The iMS system hosts two domains, domainA.example.com and domainB.example.com. One address within domainB.example.com:address-y3PpSDMNKEOFwOAa1kfzE0EOCMrvLtNR&amp;lt; at &amp;gt;public.gmane.org  resolves to two addresses on two different hosts within the intra network:address-gElWsGx5A1KFwOAa1kfzE0EOCMrvLtNR&amp;lt; at &amp;gt;public.gmane.org  andaddress-0P8jFap3+7OFwOAa1kfzE+jAqQFK86Wj&amp;lt; at &amp;gt;public.gmane.org LDAP schema 2 is used; both domains are defined as associatedDomain in LDAP. The address-y3PpSDMNKEOFwO&lt;/pre&gt;</description>
    <dc:creator>Rolf E. Sonneveld</dc:creator>
    <dc:date>2013-01-14T21:34:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7004">
    <title>metermaid state replication</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7004</link>
    <description>&lt;pre&gt;I seem to recall that metermaid does/will support state replication 
across multiple servers.  I can't find any information about that.  My 
goal would be so that clients who are being throttled or greylisted by 
metermaid on one MTA would get the appropriate handling when the 
subsequent attempts go to another MTA.

Jesse

&lt;/pre&gt;</description>
    <dc:creator>Jesse Thompson</dc:creator>
    <dc:date>2012-12-26T19:52:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/7001">
    <title>Two Questions: vacation "mailAlternateAddress" and editing a user's mailbox</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/7001</link>
    <description>&lt;pre&gt;Folks:

We have recently upgraded to Comm Suite 7 and are migrating a few users 
from a PMDF/OpenVMS system over to the Comm Suite system.

Two functions that worked well in PMDF/OpenVMS have me a bit confused. 
I have done some preliminary scanning through the manuals, but haven't 
found the answers.

1) In the PMDF/OpenVMS web interface, when setting up a vacation 
message, the user gets to put in a list of "To" addresses.  In the 
end-user GUI of Convergence 7, this field is missing.  I have found the 
option that lets me say "pay attention to mailAlternateAddress LDAP 
attribute" for the "To" addresses, but I have not found any way to let 
the user easily update their list of "To"/mailAlternateAddress addresses.

Has anyone come up with an easy way to adjust the Convergence GUI so 
that the user gets a place they can update mailAlternateAddress (or, 
frankly, any other LDAP field)?

2) In OpenVMS, it was pretty easy for a system manager to go into a 
user's mailbox to clear out chunks of messages upon us&lt;/pre&gt;</description>
    <dc:creator>Joel M Snyder</dc:creator>
    <dc:date>2012-12-19T17:30:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6986">
    <title>Should SPF HELO logging make a J record entry?</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6986</link>
    <description>&lt;pre&gt;
7u4-27

I was researching a problem of a SPF PermError on HELO and was wondering 
if the "500 5.5.2 Permanent error in SPF verification of HELO domain" 
rejection should be making it into the mail.log_current?


Our option.dat has the following:

! Set our MTA logging option detail
LOG_FORMAT=2
! What we want logged
LOG_CONNECTION=255
LOG_DIAGNOSTICS=3
LOG_ENVELOPE_ID=1
LOG_FILENAME=1
LOG_FILTER=1
!LOG_HEADER=1
LOG_MESSAGE_ID=1
LOG_NODE=1
LOG_NOTARY=1
LOG_PRIORITY=1
LOG_PROCESS=1
LOG_QUEUE_TIME=1
LOG_REASON=1
LOG_SENSITIVITY=1
LOG_USERNAME=1

We do get the O(pen) and C(lose) entries from the connecting IP, which I 
then went and found the slave debug file to find the reason the 
connection was rejected.

Are we missing something to get the rejection logged?


------

Note the rejection ended up being because of the bug in treating 
mechanisms as case-sensitive when the spec says they are case 
blind.  I thought that I had gotten a bug id for that back 
March 2010 (25-Mar-2010 "[Info-iMS] SPF mechinism chara&lt;/pre&gt;</description>
    <dc:creator>Derek Diget</dc:creator>
    <dc:date>2012-12-04T20:14:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6983">
    <title>authrewrite - header other than Sender?</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6983</link>
    <description>&lt;pre&gt;We recently enabled 'authrewrite' on our submission channels for a few 
reasons:

1) easier to identify the authenticated user without needing to grep 
logs, which is especially useful for tracking down compromised accounts

2) allowed us to add additional metermaid throttling based on 
authenticated user, instead of relying on env-from and ip-addr

     - FWIW, we plan to put a fence around the ability to forge 
addresses in the future, but we aren't ready to take that step yet.

3) PureMessage can look at the Sender header to identify messages sent 
from authenticated users.  When we were using the conversion channel for 
spam scanning, we relied on the "ESMTPSA" in the Recieved header (which 
isn't available with libmilter spam scanning).

     - Note: we haven't fleshed this out yet... We're still running with 
the conversion channel spam scanning until we do.


Now... on to my question: We have some customers complaining that 
Outlook displays those messages as: From "foo" on behalf of "bar"

Is there a&lt;/pre&gt;</description>
    <dc:creator>Jesse Thompson</dc:creator>
    <dc:date>2012-12-04T18:37:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6979">
    <title>sieve to trigger channel rewrite</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6979</link>
    <description>&lt;pre&gt;Is it possible to use sieve (in imta.filter) to trigger a channel 
rewrite?  Specifically, I'm looking for ways to segregate user-forwarded 
mail that is rated as spam, as indicated by X-headers set by a libmilter 
anti-spam application, from non-spam onto alternate channels/interfaces.

Jesse

&lt;/pre&gt;</description>
    <dc:creator>Jesse Thompson</dc:creator>
    <dc:date>2012-12-03T18:28:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6976">
    <title>AUTO : Non-disponible</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6976</link>
    <description>&lt;pre&gt;
Je serai absent(e) du  11/13/2012 au 01/31/2014.

Je ne suis plus employé chez Vidéotron. I am no longer an employee of
Vidéotron

Contactez Ross Beaudoin - please Contact Ross Beaudoin


Remarque : ceci est une réponse automatique à votre message  "Re:
[Info-iMS] Rollback scenario for mailstore migration" envoyé le 11/27/2012
8:25:17.

C'est la seule notification que vous recevrez pendant l'absence de cette
personne.


&lt;/pre&gt;</description>
    <dc:creator>Sylvain.Cousineau-XzQKRVe1yT2aMJb+Lgu22Q&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-11-27T15:07:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6974">
    <title>Rollback scenario for mailstore migration</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6974</link>
    <description>&lt;pre&gt;Hi, all,

For a migration,

from: a Solaris Sparc system running messaging server 6.3
to: a RedHat 5 system running messaging server 7.0 update 4

we're planning to export all mailboxes using imsexport on the old server 
and then to import them using imsimport on the new server. AFAIK this is 
the recommended migration scenario for this type of migration (if not, 
please let me know which alternatives there are).

Now my question is: the owner of the system wants to have a fallback 
scenario, in case something would go wrong during the first few hours 
(or days) after the migration. My question is: would the reverse path 
(i.e.: imsexport from the new message store on the Redhat platform and 
an imsimport into the old message store on the Solaris Sparc system 
work, and if yes, what are the prerequisites, requirements, steps etc.? 
If this fallback scenario is not a viable approach, then the question 
is: why not? Any alternatives for a fallback strategy?

Thanks,
/rolf

&lt;/pre&gt;</description>
    <dc:creator>Rolf E. Sonneveld</dc:creator>
    <dc:date>2012-11-26T22:21:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6971">
    <title>LDAP_PERSONAL_NAME "rewrite" only for submit From: addresses?</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6971</link>
    <description>&lt;pre&gt;
7u25

We set LDAP_PERSONAL_NAME=displayName in option.dat.  Personal Names are 
being set the displayName value as expected.  But....

Is there a way to only "rewrite" the From: header personal name if the 
address is local?  I.e. for mail sent via local accounts we want the 
From: personal name to be the value of the user's displayName attribute, 
but we don't want to rewrite the To: header if the address is local. 
Similar for in-bound messages from the Internet - From: won't (shouldn't) 
be a local address and thus no rewrite and we don't want to rewrite the 
To: personal name.

Message source: submit

 From: local  -&amp;gt; rewrite
 From: remote -&amp;gt; leave alone

 To: local  -&amp;gt; leave alone
 To: remote -&amp;gt; leave alone


Message source: Internet

 From: local  -&amp;gt; leave alone
 From: remote -&amp;gt; leave alone

 To: local  -&amp;gt; leave alone
 To: remote -&amp;gt; leave alone


Thanks.

&lt;/pre&gt;</description>
    <dc:creator>Derek Diget</dc:creator>
    <dc:date>2012-10-26T23:06:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6968">
    <title>ODSEE11.1.1.5.1 vs. OUD 11gR2</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6968</link>
    <description>&lt;pre&gt;Hi folks, I realize this is slightly off-topic, but I thought I'd throw it out there in case anyone already has any experience with this, since Directory Server and Messaging Server are tightly integrated.

We're moving to RHEL6 as a standard platform for all our internal services. Oracle support tells me that ODSEE11.1.1.5.1 is only supported on RHEL5 and that I'll need to move to OUD 11gR2 if I want to run on RHEL6. I have a couple of questions:

1) Can I run the latest ODSEE11.1.1.5.1 on RHEL6 even though its not a supported platform? If so are there any gotcha's I should know about?

2) If I move to OUD 11gR2 will it support my Oracle Communications Messaging Exchange Server 7u4-20.01 servers? Again, if so, are there any gotcha's.

Any advice is greatly appreciated.


-Peter Kaldis


&lt;/pre&gt;</description>
    <dc:creator>Peter Kaldis</dc:creator>
    <dc:date>2012-10-04T17:29:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6963">
    <title>Messaging Server - moving users from one domain to another</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6963</link>
    <description>&lt;pre&gt;# ./imsimta version
Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)
libimta.so 7u2-7.02 64bit (built 02:28:03, Apr 16 2009)
Using /opt/sun/comms/messaging64/config/imta.cnf (compiled)

I have been tasked with consolidating users who are split between two
hosted domains on a single host/single partition system into one single
domain.  There are about 700 users that need to move from our "old"
(currently the default) domain into our new domain.  The users exist in
LDAP already in the new domain.  They are synchronized with AD using
Identity Synchronization for Windows. Those users don't log in with those
accounts yet though.  I was asked if there was a way to map these 700 user
accounts in the new domain to their existing mail store mailbox.  Is there
any way to do that?  I know you can use hashdir to get the mailstore
directory for a user.  Any way to assign that mapping to the user account
in the new domain so I don't have to move anything around in the mailstore?
 Also, the new domai&lt;/pre&gt;</description>
    <dc:creator>Scott Heger</dc:creator>
    <dc:date>2012-09-14T16:43:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.ims.general/6959">
    <title>Exception to auth-from matching rule</title>
    <link>http://comments.gmane.org/gmane.mail.ims.general/6959</link>
    <description>&lt;pre&gt;We have a FROM_ACCESS rule restricting the tcp_submit chanel to 
authenticated addresses.  The problem is that we have an account that 
wants to use their mailAlternateAddress instead.  Is there a way to make 
an exception for this account or verify the mailAlternateAddress?

mappings:
...
FROM_ACCESS
...
    *|SMTP*|*|tcp_submit|*|$3*    $Y
    *|SMTP*|*|tcp_submit|*|*      $NThe$ email$ address$ you$ provided$ 
could$ not$ be$ authenticated

Version:
# imsimta version
Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)
libimta.so 6.3-8.03 (built 18:51:22, Apr 24 2009; 32bit)
SunOS proxy2 5.10 Generic_141414-10 sun4u sparc SUNW,Sun-Fire-880

&lt;/pre&gt;</description>
    <dc:creator>Chad Cordero</dc:creator>
    <dc:date>2012-08-30T21:27:33</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.mail.ims.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.mail.ims.general</link>
  </textinput>
</rdf:RDF>
