Documentation about the structure of o=pab
Hello,
For some reasons, we want to use another webmail in place of Messenger Express but we would like to remain compatible in case of future changes...
We have already create the interface for the SIEVE filters and we want now create an interface for the AdressBook.
Is there some documentation about
- how to create an AdressBook : why the name AdressBookc9a643a ?
where do the string c9a643a come from ?
- how to create entry in the address book
Exemple : PascalMaesd2cb535 where do the "d2cb535" come from ?
Thanks
# imsimta version
Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
libimta.so 6.2-3.04 (built 01:32:55, Jul 15 2005)
SunOS mailstore-2-1 5.10 Generic_Patch i86pc i386 i86pc
# 1
Hi,
> For some reasons, we want to use another webmail in
> place of Messenger Express but we would like to
> remain compatible in case of future changes...
No problem there, Sun is also using another interface, Comms Express :) I should point out that in Comms Express, the PAB format is actually different (refer to the following site for a migration tool):
http://www.sun.com/blueprints/1206/820-0618.html
> Is there some documentation about
>
> - how to create an AdressBook : why the name
> AdressBookc9a643a ?
>where do the string c9a643a come from ?
> - how to create entry in the address book
> Exemple : PascalMaesd2cb535 where do the
> "d2cb535" come from ?
No public documentation that I am aware of exists, but then again it isn't really needed. It should be straight-forward enough to reverse-engineer the structure.
From memory the random looking strings are just that -- some unique identifier generated to reduce the possibility of clashes. So if you were to use some kind of timestamp/username hash has you could generate your own string and that should be fine.
Basically it's a case of trial/error to see what generated strings are accepted by the existing messenger express installation.
Regards,
Shane.
# 2
> Hi,
>
> > For some reasons, we want to use another webmail
> in
> > place of Messenger Express but we would like to
> > remain compatible in case of future changes...
>
> No problem there, Sun is also using another
> interface, Comms Express :) I should point out that
> in Comms Express, the PAB format is actually
> different (refer to the following site for a
> migration tool):
>
> http://www.sun.com/blueprints/1206/820-0618.html
>
>[...]
> Regards,
>
> Shane.
I have read the document but did not find any pab2abs.pl on http://www.sun.com/blueprints/tools !
