<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MIME Corruption in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585798#M32422</link>
    <description>I use /BINARY, so it's Base64, Octet/Stream.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
    <pubDate>Wed, 20 Jul 2005 02:41:11 GMT</pubDate>
    <dc:creator>Robert Atkinson</dc:creator>
    <dc:date>2005-07-20T02:41:11Z</dc:date>
    <item>
      <title>MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585793#M32417</link>
      <description>Our support company is looking at this problem, but I wanted to know if anyone else has any clues.&lt;BR /&gt;&lt;BR /&gt;I'm using MIME.EXE to Mime-encode a PDF file.&lt;BR /&gt;If I then extract the file back out, I find it's changed.&lt;BR /&gt;&lt;BR /&gt;For instance, the first 4 lines change from this :-&lt;BR /&gt;&lt;BR /&gt;%PDF-1.3&lt;BR /&gt;%JetForm PDF Support Version 2.3.000&lt;BR /&gt;%EncodingObject=0&lt;BR /&gt;%ûüÿ␊&lt;BR /&gt;&lt;BR /&gt;...to this....&lt;BR /&gt;&lt;BR /&gt;%PDF-1.3%JetForm PDF Support Version 2.3.000%EncodingObject=0%ûüÿ&lt;BR /&gt;&lt;BR /&gt;This has been tried on another system using MIME 1.7, 1.8 and 1.9, but works fine.&lt;BR /&gt;&lt;BR /&gt;I've taken their 1.7 and our 1.8, but both fail. I'm now wondering if a patch has upset this utility.&lt;BR /&gt;&lt;BR /&gt;Rob.&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Jul 2005 08:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585793#M32417</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2005-07-19T08:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585794#M32418</link>
      <description>do the file attributes change?</description>
      <pubDate>Tue, 19 Jul 2005 08:36:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585794#M32418</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-07-19T08:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585795#M32419</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;Check the line termination characters and record formats of both files. I suspect that you losing one or the other (i.e., if the file was variable length with implied carriage control, and then was output as a LF-UNIX style file), that would explain the problem.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Tue, 19 Jul 2005 09:33:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585795#M32419</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2005-07-19T09:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585796#M32420</link>
      <description>The PDF starts life as Stream. After being extracted, it ends up as Stream_LF.&lt;BR /&gt;&lt;BR /&gt;If I use EXTRACT/FDL= with a Stream FDL, the attributes are then OK, but the file is still corrupt.&lt;BR /&gt;&lt;BR /&gt;My feeling is that it's corrupted when stored.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Wed, 20 Jul 2005 01:41:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585796#M32420</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2005-07-20T01:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585797#M32421</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;to compare the actual file contents, consider to use DUMP/BL=COUNT=1 on the original file and the corrupted one.&lt;BR /&gt;&lt;BR /&gt;How is the attached file encoded in the MIME message (MIME&amp;gt; LIST) ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 20 Jul 2005 02:32:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585797#M32421</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-07-20T02:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585798#M32422</link>
      <description>I use /BINARY, so it's Base64, Octet/Stream.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Wed, 20 Jul 2005 02:41:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585798#M32422</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2005-07-20T02:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585799#M32423</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;MIME uses about 13 shareable images (SDA&amp;gt; SHOW PROC/IMA/ID=&lt;PID-OF-PROCESS-RUNNING-MIME&gt;).&lt;BR /&gt;&lt;BR /&gt;You could compare their versions using anal/ima/select=(ident,build,link_time) sys$library:filename between the working and failing environments. If you believe you've found the 'bad' one, you could try to use a 'good' one in your process by defining a process logical pointing to a 'working' copy of the godd shareable library.&lt;BR /&gt;&lt;BR /&gt;If you copy the MIME-encoded file from the failing to the working environment and extract the .PDF there, you can prove, if your theory (corruption during encoding) is right.&lt;BR /&gt;&lt;BR /&gt;Volker.&lt;/PID-OF-PROCESS-RUNNING-MIME&gt;</description>
      <pubDate>Wed, 20 Jul 2005 02:54:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585799#M32423</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-07-20T02:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: MIME Corruption</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585800#M32424</link>
      <description>Cheers Volker.&lt;BR /&gt;&lt;BR /&gt;We've identified the shareable images already and I'm checking these against patch kits we've applied to see if I can see anything.&lt;BR /&gt;&lt;BR /&gt;I'm pretty confident that it's the packing, as when I email the MIME file, the attachment is corrupt, which is how I found the problem originally.&lt;BR /&gt;&lt;BR /&gt;Unfortunately, I don't have a system that is working locally, but I might get our support company to send their files over, to test against.&lt;BR /&gt;&lt;BR /&gt;Cheers, Rob.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Jul 2005 03:02:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mime-corruption/m-p/3585800#M32424</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2005-07-20T03:02:00Z</dc:date>
    </item>
  </channel>
</rss>

