none
What is an X-Header and how can I check the x-headers allowed by my Exchange? RRS feed

  • Question

  • Hi,

     

    Help, please.

     

    What is an X-Header and how can I check the x-headers allowed by my Exchange?

     

    I am having problem with SharePoint 2007 and according to the MOSS forum the issue is caused by Exchange.  Please, take a look:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/434c3e5e-2b95-4008-b810-adee6875e492

    It seems that Exchange is stripping or blocking the following headers: 

     

    ·                  X-Sharing-WSSBaseUrl

    ·                  X-AlertWebSoap

    ·                  X-Sharing-ItemID

    ·                  X-Sharing-Remote-Uid

    ·                  X-Sharing-Config-Url

    ·                  X-AlertServerType

    ·                  X-AlertWebUrl

    ·                  X-AlertId

    ·                  X-AlertTitle

    ·                  X-Sharing-Title

    How can I check the headers in my Exchange Svr?

    By the way, we are using Exchange 2007!

    Thanks in advanced.

    Wednesday, December 14, 2011 7:09 PM

Answers

  • On Wed, 14 Dec 2011 23:40:15 +0000, efebo wrote:
     
    >On Wed, 14 Dec 2011 19:09:58 +0000, efebo wrote: >What is an X-Header It's an eXperimental header not defined in RFCs. >and how can I check the x-headers allowed by my Exchange? http://blogs.technet.com/b/exchange/archive/2009/04/06/3407221.aspx http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx If Exchange didn't put the X-header into the message then, pretty much, it isn't going to be promoted to a MAPI property. >I am having problem with SharePoint 2007 and according to the MOSS forum the issue is caused by Exchange. Is your Sharepoint server sending its e-mail using anonymous SMTP sessons? If so, have it start using authenticated SMTP sessions. --- Rich Matheisen MCSE+I, Exchange MVP
    >--- Rich Matheisen MCSE+I, Exchange MVP
    >
    >
    >
    >Yes, I am using anonymous SMTP. But they were working just fine; a few days ago the issue came out. What could cause this? Exchange is configured to support relying from SharePoint.
     
    Unless you've changed Exchange (installed a service pack or update
    rollup) between the time it was "working" and the time is stopped
    "working" then your problem is something other than the absense of
    X-headers.
     
    Relaying isn't the problem. If those messages are addressed to
    mailboxes in your Exchange organization then they aren't being
    relayed. If the messages that you're having a problem with are being
    delivered to some other organization then perhaps the changes took
    place at the other organization?
     
    I think you should configure that Sharepoint server to use
    autneiticated connections if you want those X-headers to be promoted
    to MAPi properties in your organization's mailbox database(s). You'll
    have to arrange with any external organization that's using Exchange
    to acquire the necessary account and password to use authentication
    when you send e-mail to them.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Sophia Xu Friday, December 16, 2011 6:14 AM
    • Marked as answer by Sophia Xu Wednesday, December 21, 2011 8:27 AM
    Thursday, December 15, 2011 12:41 AM

All replies

  • On Wed, 14 Dec 2011 19:09:58 +0000, efebo wrote:
     
     
    >What is an X-Header
     
    It's an eXperimental header not defined in RFCs.
     
    >and how can I check the x-headers allowed by my Exchange?
     
    http://blogs.technet.com/b/exchange/archive/2009/04/06/3407221.aspx
    http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx
     
    If Exchange didn't put the X-header into the message then, pretty
    much, it isn't going to be promoted to a MAPI property.
     
    >I am having problem with SharePoint 2007 and according to the MOSS forum the issue is caused by Exchange.
     
    Is your Sharepoint server sending its e-mail using anonymous SMTP
    sessons? If so, have it start using authenticated SMTP sessions.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Wednesday, December 14, 2011 9:05 PM
  • Not exchange, probably the firewall
    Sukh
    Wednesday, December 14, 2011 10:24 PM
  • Not exchange, probably the firewall
    Sukh

    Firewall?

    Explain, please. 

    Thanks!

    Wednesday, December 14, 2011 11:35 PM
  • On Wed, 14 Dec 2011 19:09:58 +0000, efebo wrote:
     
     
    >What is an X-Header
     
    It's an eXperimental header not defined in RFCs.
     
    >and how can I check the x-headers allowed by my Exchange?
     
    http://blogs.technet.com/b/exchange/archive/2009/04/06/3407221.aspx
    http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx
     
    If Exchange didn't put the X-header into the message then, pretty
    much, it isn't going to be promoted to a MAPI property.
     
    >I am having problem with SharePoint 2007 and according to the MOSS forum the issue is caused by Exchange.
     
    Is your Sharepoint server sending its e-mail using anonymous SMTP
    sessons? If so, have it start using authenticated SMTP sessions.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP

    Yes, I am using anonymous SMTP. But they were working just fine; a few days ago the issue came out. What could cause this? Exchange is configured to support relying from SharePoint.

    Thanks in advanced! 

       

    Wednesday, December 14, 2011 11:40 PM
  • On Wed, 14 Dec 2011 23:40:15 +0000, efebo wrote:
     
    >On Wed, 14 Dec 2011 19:09:58 +0000, efebo wrote: >What is an X-Header It's an eXperimental header not defined in RFCs. >and how can I check the x-headers allowed by my Exchange? http://blogs.technet.com/b/exchange/archive/2009/04/06/3407221.aspx http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx If Exchange didn't put the X-header into the message then, pretty much, it isn't going to be promoted to a MAPI property. >I am having problem with SharePoint 2007 and according to the MOSS forum the issue is caused by Exchange. Is your Sharepoint server sending its e-mail using anonymous SMTP sessons? If so, have it start using authenticated SMTP sessions. --- Rich Matheisen MCSE+I, Exchange MVP
    >--- Rich Matheisen MCSE+I, Exchange MVP
    >
    >
    >
    >Yes, I am using anonymous SMTP. But they were working just fine; a few days ago the issue came out. What could cause this? Exchange is configured to support relying from SharePoint.
     
    Unless you've changed Exchange (installed a service pack or update
    rollup) between the time it was "working" and the time is stopped
    "working" then your problem is something other than the absense of
    X-headers.
     
    Relaying isn't the problem. If those messages are addressed to
    mailboxes in your Exchange organization then they aren't being
    relayed. If the messages that you're having a problem with are being
    delivered to some other organization then perhaps the changes took
    place at the other organization?
     
    I think you should configure that Sharepoint server to use
    autneiticated connections if you want those X-headers to be promoted
    to MAPi properties in your organization's mailbox database(s). You'll
    have to arrange with any external organization that's using Exchange
    to acquire the necessary account and password to use authentication
    when you send e-mail to them.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Sophia Xu Friday, December 16, 2011 6:14 AM
    • Marked as answer by Sophia Xu Wednesday, December 21, 2011 8:27 AM
    Thursday, December 15, 2011 12:41 AM