You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2019. It is now read-only.
What steps will reproduce the problem?
1. Convert .nsf file
2. Examine resulting .mbox file
3. Search for 'cn='
What is the expected output? What do you see instead?
- Expected: 'name surname/organization'
- Instead: 'cn=name surname/o=organization'
What version of the product are you using? On what operating system?
- Latest
- Windows XP / 7 (not relevant)
Please provide any additional information below.
- On Notes, users appear in the From and To fields as 'name
surname/organization'.
The script adds 'cn=' as prefix and 'o=' after the bar.
Original issue reported on code.google.com by pastr...@gmail.com on 16 Feb 2012 at 4:16
The text was updated successfully, but these errors were encountered:
Well, this is still related to #10
Do you mean "cn=name surname/o=organization" should be converted to something
like :
"name surname/organization" <surname.name@organisation>
Original comment by hugues.b...@gmail.com on 19 Feb 2012 at 6:49
[Edited because of errors]
Not really, because there's no need for "<surname.name@organization>"; just
"name surname/organization".
This is because Internet addresses may not follow a regular pattern: instead of
"surname.name@organization.com", they may have been assigned as
"n.surname@organization.com" for example, or even "ns@organization.com".
Also:
in my case, the majority of internal (Notes) addresses are like: "name
surname/organization" but there are also a few "name middlename
surname/organization"
and at least one "name.surname/organization".
Because of this, it would be probably better just to strip off "cn=" and "o=".
Original comment by pastr...@gmail.com on 19 Feb 2012 at 1:08
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Original issue reported on code.google.com by
pastr...@gmail.com
on 16 Feb 2012 at 4:16The text was updated successfully, but these errors were encountered: