Once a Webimport Email contains a charset property special characters are destroyed during the WebImport

Version 1

    Details

    Once a Webimport Email contains a charset property special characters are destroyed during the WebImport

    [PRE-REQUISITES]

    -  There are 7 eml files with the following charsets in the header (this  might be common for customers when they are using own scripts)
    >> Content-Type: text/plain; charset="iso-8859-15" (Rübe15_2 as Company)
    >> Content-Type: text/plain; charset=iso-8859-15 (Rübe15_1 as Company)
    >> Content-Type: text/plain; charset="iso-8859-1" (Rübe1_2 as Company)
    >> Content-Type: text/plain; charset=iso-8859-1 (Rübe1_1 as Company)
    >> Content-Type: text/plain; charset="UTF-8" (RübeU_2 as Company)
    >> Content-Type: text/plain; charset=UTF-8 (RübeU_1 as Company)
    >> Content-Type: text/plain; (RübeNO as Company)

    [STEPS TO PREPARE]
    Technically not necessary but in order to keep the messages and see manually what would be created per email
    1. Tools > Options
    2. E-mail Tab
    3. More Options Button
    4. Advanced Tab
    5. Uncheck all settings on the right bottom for Web-Import
    6. OK > OK




    [STEPS TO REPRODUCE]
    1. Go to > Mail
    2. Go on the online folder where the above emails are now available for download
    3. Get the 7 emails into the inbox (for example Highlighting them and Right Click > Get Selected items)
    4. In the inbox per email
    a. Open the email in read mode
    b. Review the data from the mail (some of them are already scrambled but for example the UTF8 examples look still right






    c. Make sure that GoldMine recognizes that this is a WebImport email (all are valid Web Import emails)
    d. Press WebImport
    e.  Verify the created Contact records for the appearance of the special  characters which should be straight available after the WebImport was successful

    [RESULT]

    >> Content-Type: text/plain; charset="iso-8859-15" (Rübe15_2 as Company), Special Characters destroyed



    >> Content-Type: text/plain; charset=iso-8859-15 (Rübe15_1 as Company), Special Characters destroyed




    >> Content-Type: text/plain; charset="iso-8859-1" (Rübe1_2 as Company), Special Characters destroyed



    >> Content-Type: text/plain; charset=iso-8859-1 (Rübe1_1 as Company), Special Characters destroyed



    >> Content-Type: text/plain; charset="UTF-8" (RübeU_2 as Company), Special Characters destroyed



    >> Content-Type: text/plain; charset=UTF-8 (RübeU_1 as Company), Special Characters destroyed



    >> Content-Type: text/plain; (RübeNO as Company), Special Characters correct (opening and full header show that  GoldMine seemed to add a charset=iso-8859-1 which was not there in the  original email (verify the eml file)






    Resolution

    [CAUSE]
    - RM # 239621

    [WORKAROUND]

    - Adjust the original Web Import script to remove any charset property and verify again, from GoldMine Technical Support all Web import with foreign special characters were imported correctly when using as a sample header

    Content-Type: text/plain

    [Data]
    COMPANY=RübeNO
    CONTACT=Märia
    EMAIL=bla@bla.com


    - Existing impacted records will need to be corrected manually