Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. SmtpClient uses lowercase headers

SmtpClient uses lowercase headers

Scheduled Pinned Locked Moved C#
helpquestion
5 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Baz
    wrote on last edited by
    #1

    Hi there, Got a strange problem here... Basically, our application sends out an email with a custom X-Header. On the dev box, the header comes out in mixed case (eg "X-EmailID"), but when we move the app to the live box, the header in the email is converted to lower case (e.g. "x-emailid") I need to keep the capitalisation. Has anyone seen this before, and did you find a solution? I've googled this but haven't found much, other than people saying they have seen the problem but no fix - there has to be some config that is different between the two boxes, surely!?! Any help greatly appreciated Baz

    Mircea PuiuM 1 Reply Last reply
    0
    • B Baz

      Hi there, Got a strange problem here... Basically, our application sends out an email with a custom X-Header. On the dev box, the header comes out in mixed case (eg "X-EmailID"), but when we move the app to the live box, the header in the email is converted to lower case (e.g. "x-emailid") I need to keep the capitalisation. Has anyone seen this before, and did you find a solution? I've googled this but haven't found much, other than people saying they have seen the problem but no fix - there has to be some config that is different between the two boxes, surely!?! Any help greatly appreciated Baz

      Mircea PuiuM Offline
      Mircea PuiuM Offline
      Mircea Puiu
      wrote on last edited by
      #2

      Try to use the System.Web.Mail classes, which make use of Microsoft's Collaboration Data Objects to send emails. Ignore compiler's warning messages for obsolete classes.

      SkyWalker

      B 1 Reply Last reply
      0
      • Mircea PuiuM Mircea Puiu

        Try to use the System.Web.Mail classes, which make use of Microsoft's Collaboration Data Objects to send emails. Ignore compiler's warning messages for obsolete classes.

        SkyWalker

        B Offline
        B Offline
        Baz
        wrote on last edited by
        #3

        Strangely enough, I'm just investigating that now! Will report back if it works Still don't understand why it works on the dev box but not on live...? :wtf: Cheers! Baz

        B 1 Reply Last reply
        0
        • B Baz

          Strangely enough, I'm just investigating that now! Will report back if it works Still don't understand why it works on the dev box but not on live...? :wtf: Cheers! Baz

          B Offline
          B Offline
          Baz
          wrote on last edited by
          #4

          oki doki - System.Web.Mail works, but I'd prefer to use System.Net.Mail if possible, as System.Web.Mail is depreciated in .NET 2.0 So has anyone got any ideas as to why this works on the dev box but not on the live? All config files are identical, so it's nothing in there... :mad: Cheers! Baz

          B 1 Reply Last reply
          0
          • B Baz

            oki doki - System.Web.Mail works, but I'd prefer to use System.Net.Mail if possible, as System.Web.Mail is depreciated in .NET 2.0 So has anyone got any ideas as to why this works on the dev box but not on the live? All config files are identical, so it's nothing in there... :mad: Cheers! Baz

            B Offline
            B Offline
            Baz
            wrote on last edited by
            #5

            Ah haaa!!!! .NET 2.0 SP1 fixes this issue Hope that helps someone else... :-D Baz

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups