Open Bug 17884 Opened 25 years ago Updated 2 years ago

Two way LDAP replication (sync changes to server)

Categories

(MailNews Core :: LDAP Integration, enhancement, P3)

Product:
MailNews Core
Component:
LDAP Integration
Type:
enhancement

Tracking

(Not tracked)

Milestone:
Future

People

(Reporter: phil, Unassigned)

References

Details

(Keywords: helpwanted) 

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.
Blocks: 10791
QA Contact: lchiang → pmock
Status: NEW → ASSIGNED
Target Milestone: M16
This is not going to make it for Seamonkey. Putting on the help wanted list.
Assignee: phil → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted
Target Milestone: M16
Moving way out there.
Target Milestone: --- → Future
Blocks: 36557
Summary: [FEATURE] Two way LDAP replication → [FEATURE] [LDAP] Two way LDAP replication
No longer blocks: 36557
Depends on: 59038
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
If this bug enables addressbook, bookmark and perhaps mail folders
synchronization, then maybe after 1.0 it can get some lovin' -> how about the
keyword: mozilla1.1?

This could solve: bug 17048, bug 18043, bug 86405
reassigning to rdayal.
Assignee: putterman → rdayal
removed jhooker from cc: list
taking so this bug at least has a home...
Assignee: rdayal → bienvenu
Product: MailNews → Core
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
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.