Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: email address attribute is funky

121 views
Skip to first unread message

a...@novell.com

unread,
Nov 10, 2009, 3:22:54 PM11/10/09
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like you are wanting something a bit more like a plain old e-mail
attributes. Look in 'mail'.

Good luck.

kjhurni wrote:
> I'm not sure if this is an eDir issue or a GroupWise issue.
>
> My guess is that it's both.
>
> For eDir ONLY users (these users have NO groupwise associations, etc.
> at all with them).
>
> If I look at their emailaddress attribute via the Apache Directory
> Studio, it's in a funky format:
>
> some random number, followed by a "#" and then the email address. So
> it's not consistent for every user.
>
> Example:
>
> emailaddress = 0#some...@yahoo.com
> or
> emailaddress = 7#kit...@hotmail.com
>
> For a groupwise user, it's even weirder:
>
> emailaddress = 7#use...@po.domain
> emailaddress=use...@somewhere.com
>
>
> I guess I'm a bit confused as to why the random numeric value, then a
> pound sign and then the email address.
>
> From a newly created user, it seems to be they all get "zeros".
>
> Is this a bug or how to fix it? It seems to be messing up a bunch of
> our ldap things that use these for email address lookups to send out
> email because there's no such:
> 0#some...@yahoo.com
>
> The groupwise users are even worse to deal with.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJK+cueAAoJEF+XTK08PnB5isgQAM2JUuL7DnlxprZybd2sXIco
jzVpYMBoSM+WvrQqD/O79G++8apGYA1vIzhzFEDRm54NEF9EkH7vL1xN3+XqA58y
+hlCLEFUicVrij1doIifZA0jqy2R9MHhFrhn9O3qieywRy2aCaDUfFo05uSmKrXF
asCiEhE3lONBUipR1f4QU+A8wtiD83T92Tzoj4u1aIv91O1/jCXymgoHV0jzgjK8
sfBHm8c4Es5Pu7AjxBqxwp5bc19c9oSTYBntZca0gOD603kSkgluDWSd7SQvXxXF
ynyHHTZRrhFsTJ1t/OR4/FaVAOWXw9qChUYULIZEd2Bs9rfqrRXYiQtjG7Ny+Rs9
DmrpqHFBKMcFuWu1uhwgoD9SlISWQ7OoTabocobpCWByJks4URSewAb2veSGF4kT
UykCN+RnlBzBP3wzTUNNxpMNBpNNeGs0JPFY1EwsYM+hqxL0+7bV+7MUwpOhCCAK
0UFDEHqGWBrg8214yUrGRtiaj0xKemdiIfX7CGiyNbRbno6U/N2101Bfu+j6vVOI
2COG+6YFYtptStVyfykcAbfEE89xal8FbVMz3ZwBC0QOqtAC3pyvQGggJ/pyIbUc
PQ71fIy6XQYTArMvaUqmZRF5wxid60IAVHHEdWouJ7qWmaTTOD5e3L/Qv2xh8wEp
Gdn1csuF4BKwQzAUaJra
=9V/P
-----END PGP SIGNATURE-----

a...@novell.com

unread,
Nov 10, 2009, 4:47:02 PM11/10/09
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maybe this will help:

http://www.novell.com/documentation/gw8/gw8_admin/data/bc1owws.html#bc1owws

If not you're probably best off asking in a GW forum as they will likely
know how to populate the correct syntax of e-mail address back to eDirectory.

Good luck.

kjhurni wrote:
> Only problem is that not all users have "mail"
>
> Some users have JUST "mail" which shows the same thing, BTW.
>
> Some users have "emailaddress"
>
> Keep in mind, we've had groupwise and NDS for a LONG time, so it's
> possible some of this is leftovers.
>
> Brand new users created from scratch, only have:
> emailaddress
> for the attribute (that's what is in iManager and ConsoleOne). And
> it's populated like:
> number#value
>
> older users seem to have "mail" and/or "emailaddress"
>
> Populated pretty much the same way:
>
> number#something
> number#some...@po.domain (for groupwise)


>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJK+d9WAAoJEF+XTK08PnB576cQAKC4hurRoZJdJ6Jh+6QpLi5p
b4fKnbXlsf595csnCxybs55pf8fVAQoyRUl+TDAmwjOjit1srmYqlJE9Vjbpz3lb
Iuqd2JhLF5TBxHcRbcghFqkqBSyLcW6U+L5pXlbSMT+G5IPh3aCYtMaFJ5tWSR6W
bWJ7JLKdWLMq7P1NQ4+/+hn5M8ZcFctS1r9ZTE2xH7XiokPt1Lcn0mDhWtnQ6fpo
XjNIe8745YxeuP7W1k6wL51UG2Pn65M7Ng2ZXYui3vDnQcbDB04h6/yjWuuQJzcN
uRTWj1RuyQKrfDKYWGz8huikCg1Tbnw78tfRN3nE91De/Aajrswkny8+6IUSb7pE
Azifwp7eiN5YRYOM4/iteGsqdJbyyUld9+/uZwB9tr5yxd8ecZM54Vf8Z7+Qgv3o
yJDtdJXS7LFMfsqR8Whj2N7jsBWlt4cifgbCLO5Foq0uePKLw6gxNimIamr8dXb/
t1GcSHnfzbBS0m7oibFTW06vjzLH4Yv8o7X2yyw9kd9SdJCouPS5diDmW1XkZjsy
DKBFpcSoR1fkce6rqaUzCF2dV7tYKUIlHBJNRDJwkcwP7Ai07YjAvi2Z620ACtxd
gzovGXh4CBlLD8bASiH7UZXFX8VbM2UIrUhBZU3bV4ntNSZp6ku1cKrVjuj4syXN
9UAp1+uYwSiSHMehxtc9
=u4BW
-----END PGP SIGNATURE-----

Wolfgang Schreiber

unread,
Nov 10, 2009, 5:20:05 PM11/10/09
to
kjhurni,

eDirectory comes with 2 attributes for Email Addresses:

"EMail Address" (Syntax: EMail Address, see
http://developer.novell.com/documentation/ndslib/schm_enu/data/sdk1106.html)
and "Internet Email Address" (Syntax: Case Ignore String, see
http://developer.novell.com/documentation/ndslib/schm_enu/data/sdk1282.html)

For LDAP, these eDir attribute names will be mapped to LDAP-compatible
attribute names like "mail" ("Internet Email Address") and "emailAddress"
("EMail Address") - these mappings can be found in the properties of your
LDAP server.

The syntax for "emailAddress" consists of an integer and a string - how (and
if) these two are used may depend on the email application. See
http://developer.novell.com/documentation/ndslib/schm_enu/data/sdk5589.html

GroupWise will use the "mail" ("Internet Email Address") attribute and store
info about userId and domain. GW will also use all thes ngw* attributes for
storing user information.

I do not see an issue here, and if this 'seems to be messing up a bunch of
our ldap things', you might have to review your LDAP things, which might use
some erroneous assumptions.


Wolfgang


Peter Kuo

unread,
Nov 10, 2009, 7:27:36 PM11/10/09
to
kjhurni wrote:

> So is it normal for eDirectory to put a random number, then a # sign
> and then the value of the attribute?

It is NOT a random number; you really need to check the application that
creates such entries as they are application-specific. In general, a zero
means it is not a MHS-type email address, whereas 7 is a GroupWise
address. However, Novell only predefines a handful (about 5) values and
email applications are free to create/use their own values and eDir does
not (and could not) validate such values - its up to the applications to.

Given that EMail Address is a "structured" data type (composing of an
integer that corresponds to address type, followed by a string for the
value), LDAP RFC specifies that a # is used to delimit between each value
within the attribute.


--


Peter
eDirectory Rules!
http://www.DreamLAN.com

Peter Kuo

unread,
Nov 12, 2009, 7:12:00 PM11/12/09
to
What you see on the 'pages' are, "unforuantely", predetermined by the
snapins (this is true for iMan, C1, NWAdmin, etc.), and what gets
populated are also controlled by the snapins. You can edit attributes that
are not 'supported' by the pages using the Others page.

Wolfgang Schreiber

unread,
Nov 19, 2009, 2:32:22 PM11/19/09
to
explained in my comment

Wolfgang

"kjhurni" <kjh...@no-mx.forums.novell.com> wrote in message
news:kjhurni...@no-mx.forums.novell.com...

>> 'DreamLAN Network Consulting Ltd. - Leading Authority on eDirectory and
>> LDAP technologies' (http://www.DreamLAN.com)
>
> I guess my point was that if you use iManager, even with plugin studio
> you can ONLY choose:
> emailaddress
>
> not
> mail
>
> And they appear to behave differently.
>
> Groupwise snapins use "mail" and write the value differently into
> "emailaddress" than iManager does.
>
> Thus, making ldap lookups with third party items a bit tricky (most
> ldap things are expecting):
> use...@domain.com
>
> not
>
> use...@po.domain
>
>
> --
> kjhurni
> ------------------------------------------------------------------------
> kjhurni's Profile: http://forums.novell.com/member.php?userid=734
> View this thread: http://forums.novell.com/showthread.php?t=392181
>


0 new messages