[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

SP2 broke 'Change Mail Class' script running on Exchange 2003 (Converts post to mail items)

Posted on 2006-07-03
5
Medium Priority
?
327 Views
Last Modified: 2010-03-06
We used to use a script called 'Change Mail Class' on our Exchange 2003 servers.

It basically converted post items to mail items in a public folder which staff have access to. The original article I followed to achieve this can be found here:

http://www.msexchange.org/articles/MF021.html 

Since installing Exchange 2003 SP2 this script no longer works. I have unregistered the script and tried to re-register it but it doesnt work.

So can anyone give me another method of preventing mail that is sent to a public folder from being sent as post items? or advice on why the script wont work anymore.

Regards

Guy_Adams
0
Comment
Question by:Guy_Adams
  • 3
  • 2
5 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 17030449
The functionality to change the message format is now built in.
You just need to make a registry change then bounce the services.

http://support.microsoft.com/default.aspx?kbid=817809

Simon.
0
 
LVL 2

Author Comment

by:Guy_Adams
ID: 17031111
Simon,

Thank you for your swift response.

Iam a little confused, I admit it doesnt take much!

The article describes and correct me if Iam wrong, how to add a registry setting to convert mail items which arrive in a public folder to IPM.Note instead of IPM.Post.

The problem with our setup is that mail that is sent to a public folder from external senders lands in the public folder as IPM.Note, we would like it as IPM.Post

Could you explain a little further please?

Many thanks

Guy_Adams
0
 
LVL 2

Author Comment

by:Guy_Adams
ID: 17031146
Simon,

I must apologise.

I have changed the registry setting to 1 from 0 and now it works.

Thank you so much for your response, its much appreciated.

I have accepted your answer.

Regards

Guy_Adams
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17031401
The naming convention used by Microsoft is a little confusing, but shouldn't cause too many issues once you get your head around it.

Simon.
0
 
LVL 2

Author Comment

by:Guy_Adams
ID: 17031577
Thanks again.

Its quite a privilege to get a response from such a highly regarded expert.

Many regards

Guy_Adams
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month20 days, 6 hours left to enroll

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question