Hi all, I need a support on how to add new named properties into Exchange 2007 without the use of any programming, just by using the exchange management console or any other simple way. Our application reads e-mails from Exchange 2007 only using the IMAP interface and it depends on special x-<my company> headers present on incomming email message headers to take appropriate actions. I identified that after Exchange Server SP1 RU8, there is a "fix" on Exchange that prevent X- headers on e-mail messages to be promoted to named properties if the sender is a no authenticated user. I consulted the following links about this issue: http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx http://technet.microsoft.com/en-us/library/ee221163(EXCHG.80).aspx The MS fix 948856 (part of Exch SP1 RU8) is responsible for this new behaviour, that will occur for later Exchange 2007 releases also (SP2 and Exch 2010) The problem is that when our application reads the e-mail messages using the IMAP interface, the special X-<my company> headers are removed from the message Our customers that were using our application and upgraded from previous versions of Exchange don't have the problem because that special headers were already promoted to named properties. The customers who installed directly Exchange 2007 SP2 cannot use our application due to this problem. I need to know the step-by-step on how to add new x- headers as named properties by just using the exchange management console in order to recommend this action to our customers, but I could not find anything on the internet. I found only tips to create properties using EWS or custom programs using MAPI interface, but this is out of scope as a valid solution for our case. Note: We're not having any problem with event ID 9667 being generated, so it's not a mather of named property quota. I tried to create a transport rule like the following: Apply rule to messages when the Subject field contains fixheader set X-MY-COMPANY with test but it didn't work. After creating this transport rule I received a messsage from the internet and from another Exchange user on the same domain (which I sppose to be an authenticated source) but it didn't work Any directions on this will be helpfull. Thanks!

On Thu, 23 Sep 2010 19:06:28 +0000, mgsan wrote: > > >Hi all, I need a support on how to add new named properties into Exchange 2007 without the use of any programming, just by using the exchange management console or any other simple way. Our application reads e-mails from Exchange 2007 only using the IMAP interface and it depends on special x-<my company> headers present on incomming email message headers to take appropriate actions. I identified that after Exchange Server SP1 RU8, there is a "fix" on Exchange that prevent X- headers on e-mail messages to be promoted to named properties if the sender is a no authenticated user. > >I consulted the following links about this issue: http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx http://technet.microsoft.com/en-us/library/ee221163(EXCHG.80).aspx > >The MS fix 948856 (part of Exch SP1 RU8) is responsible for this new behaviour, that will occur for later Exchange 2007 releases also (SP2 and Exch 2010) > >The problem is that when our application reads the e-mail messages using the IMAP interface, the special X-<my company> headers are removed from the message Our customers that were using our application and upgraded from previous versions of Exchange don't have the problem because that special headers were already promoted to named properties. The customers who installed directly Exchange 2007 SP2 cannot use our application due to this problem. > >I need to know the step-by-step on how to add new x- headers as named properties by just using the exchange management console in order to recommend this action to our customers, but I could not find anything on the internet. > >I found only tips to create properties using EWS or custom programs using MAPI interface, but this is out of scope as a valid solution for our case. Note: We're not having any problem with event ID 9667 being generated, so it's not a mather of named property quota. > >I tried to create a transport rule like the following: Apply rule to messages when the Subject field contains fixheader set X-MY-COMPANY with test > >but it didn't work. After creating this transport rule I received a messsage from the internet and from another Exchange user on the same domain (which I sppose to be an authenticated source) but it didn't work > >Any directions on this will be helpfull. Thanks! Why not just send an e-mail with that header (or those headers) from an authenticated client? Once the header's in the database it should no longer be a problem. Since you write applications it shouldn't be a stretch to build a small tool to accomplish that task. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Rich, in fact we would like an option to add the necessary headers using directly the Exchange management console, in order to give simple and clear instructions to Exchange administrators where our application is being used. Some customers have the exchange server solely for our application and refuse to add extra e-mail clients. An option is to use telnet to connect to SMTP port and send an special message with the headers. To build a small tool to do that is currently not an option due to lack of resources and know-how in C#/MAPI programming. Do you think there are no other way to add the custom headers without programming or sending special messages? Thanks!

On Fri, 24 Sep 2010 21:23:40 +0000, mgsan wrote: >in fact we would like an option to add the necessary headers using directly the Exchange management console, in order to give simple and clear instructions to Exchange administrators where our application is being used. Consider the forum in which you're asking your question. This is a forum for general Exchange questions, not a forum for developers. :-) >Some customers have the exchange server solely for our application and refuse to add extra e-mail clients. I didn't say they should. I said that if you want to add X-headers to the database then you should write a small tool that uses an authenticated SMTP session to send an e-mail that contains those headers. Make the tool part of the installation process, or have it available to run post-istallation. >An option is to use telnet to connect to SMTP port and send an special message with the headers. Whatever floats your boat! If you think entering the necessary "stuff" by hand in a raw telnet session is appropriate then go for it. OTOH, if anyone told me I'd have to do that to install a piece of software it'd be the last time I took a phone call from THAT company! >To build a small tool to do that is currently not an option due to lack of resources and know-how in C#/MAPI programming. You don't need MAPI. Just an authenticated SMTP connection. >Do you think there are no other way to add the custom headers without programming or sending special messages? Perl programmers use this a lot: TMTOWTDI (There's More Than One Way To Do It). If you can't figure it out then hire a contract programmer that can. But, seriously, move your question to a developers forum. You're much more likely to get a meaningful answer there. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

You can do it quite easily with Outlook Spy Install Outlook Spy (just google for it) Open an INTERNET message (that has other X-Headers) Click the Outlook Spy / IMessage option Click the Get Props tab Click Add Property "This is a named property" GUID: PS_INTERNET_HEADERS KIND: MNID_STRING ID: x-whatever (your new header, in lowecase, exchange/outlook will munge it to lower case) TYPE: PT_UNICODE VALUE: <some value - you need to set it to something for this to take affect> and click OK Wait a couple of minutes, and try sending yourself a message with the X-Whatever header now...