This is a feature tracking bug for LDAP replication. We're going to improve on the 4.5 replication feature by making client changes get replicated to the server, as well as server to client.
This is not going to make it for Seamonkey. Putting on the help wanted list.
Assignee: phil → nobody
Status: ASSIGNED → NEW
Moving way out there.
Target Milestone: --- → Future
Summary: [FEATURE] Two way LDAP replication → [FEATURE] [LDAP] Two way LDAP replication
Getting this on the radar and assigning proper owners and cc.
Assignee: nobody → jpm
QA Contact: pmock → yulian
Scott, please find a new home for these bugs. Thx!
Assignee: jpm → putterman
reassigning to rdayal.
Assignee: putterman → rdayal
removed jhooker from cc: list
taking so this bug at least has a home...
Assignee: rdayal → bienvenu
Lets move this to the correct component.
Assignee: bienvenu → nobody
Severity: normal → enhancement
Component: MailNews: Backend → MailNews: LDAP Integration
QA Contact: yulian → ldap-integration
Summary: [FEATURE] [LDAP] Two way LDAP replication → Two way LDAP replication (sync changes to server)
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.