Application Development Software

Hi,
this is more a FYI rather than a question.

We have a Netscape messaging fetching the userbase from a JES Directory Server. Multiple email domains are hosted there.

In the past, realms were implemented appending !realm to the UID, so that uid uniqueness would be granted across the whole user tree. So, some communities have logins as:

me!comm1
me!comm2
you!comm2
...

I am now testing the migration to JES Messaging 6 (schema 1), slowly adding new domains to the test platform.

I have been struggling for one day after a domain that would not accept mail, even if all the objectclasses and attributes were properly set (another working domain was taken as reference).

With a deep debug run ( imsimta test -rewrite -debug email@address.com ) I found out that JES Messaging 6 (2004Q2) does not accept mail for addresses whose corresponding UID attribute contains:

! (exclamation point)
@ (at)
# (pound)
* (star)
$ (dollar sign)
% (percent)

The debug returns these lines before bailing out:
09:57:18.12: Domain is active
09:57:18.12: Mail domain is active
09:57:18.12: Mail user status = active
09:57:18.12: User is active
09:57:18.12: User UID user!realm found.
09:57:18.12: UID contains illegal character(s)

I have not found any mention in the messaging documentation about allowed chars in the uid attribute, which is defined as "Directory String" and thus should accept those chars. See RFC2252, paragraph 6.10 for details.

This Messaging requirement (?) breaks compatibility with existing trees and standard LDAP schema.

Would a tech support call produce a patch?

HTH,
Paolo