X
Xingren Ying
We implement our MAPI store service provider using Outlook talking to our
IMAP server. When a local MAPI folder is created during the logon, it will
try to map to the same name IMAP folder of the server.
Outlook 2003 automatically creates a "Junk Email" local MAPI folder when
user first login a new profile. If server has a same name "Junk Email" IMAP
folder, it does not map to it but change the name to "Junk Email 1". This
"Junk Email n" number n keeps increasing to n+1 if "Junk Email n" IMAP folder
has been in server for every new login profile.
Question:
1. What is the special thing of Outlook 2003 "Junk Email" folder in MAPI
property prospect?
2. How is PR_ADDITIONAL_REN_ENTRYIDS used for Junk mail?
3. Is there any MAPI property value which can prevent Outlook 2003 creating
different name (like "Junk Mail n") Junk Mail folder in new profile login?
4. If all of above do not hit the point, what should store provider need to
take care in order to solve the problem.
Thanks!
IMAP server. When a local MAPI folder is created during the logon, it will
try to map to the same name IMAP folder of the server.
Outlook 2003 automatically creates a "Junk Email" local MAPI folder when
user first login a new profile. If server has a same name "Junk Email" IMAP
folder, it does not map to it but change the name to "Junk Email 1". This
"Junk Email n" number n keeps increasing to n+1 if "Junk Email n" IMAP folder
has been in server for every new login profile.
Question:
1. What is the special thing of Outlook 2003 "Junk Email" folder in MAPI
property prospect?
2. How is PR_ADDITIONAL_REN_ENTRYIDS used for Junk mail?
3. Is there any MAPI property value which can prevent Outlook 2003 creating
different name (like "Junk Mail n") Junk Mail folder in new profile login?
4. If all of above do not hit the point, what should store provider need to
take care in order to solve the problem.
Thanks!