| Newsgroups |
gmane.linux.drivers.gammu |
| Message-ID |
<[email protected]> |
This is a multi-part message in MIME format.
--===============3020993454286590368==
Content-Type: multipart/alternative;
boundary="------------4BA40ED4BEBDAB1DECAB9789"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------4BA40ED4BEBDAB1DECAB9789
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hey,
Can someone explain why is the following (decoded) message cut correctly
at the 160th character, as expected:
|00000000010000000002000000000300000000040000000005000000000600000000070000000008000000000900000000100000000011000000001200000000130000000014000000001500000000160000000017000000001800000000190000000020
|
The destination receives:
|0000000001000000000200000000030000000004000000000500000000060000000007000000000800000000090000000010000000001100000000120000000013000000001400000000150000000016
|
While the following message (TextDecoded) is just ending up empty at the
destination:
|[aaaaaa] bbbbbbbb | cccc_ccc \_ dd (eeeeeeee) \_ fff ff - f.fff ffffff
ffffffff ffff ff ffffffff.ffff.ff ffff 389 \_ 2020-07-07 20:10:27 +0200
\_ ggggg ggggg ggggggggg GGG gg gggggggg g ggggg gg gggggggg ggg gggg
gggg ggg ggggggg: hhhhh
Y44wCg6vu8m6CeG5ZB8MA2nif9l0nG7/Nceec5NA7UjZO+OKHOAjCy5hdeAdt+WVD2U=|n |
(Unless I cut it around the timestamp, which is at about 110 characters
from the start)
I'm simply inserting it into outbox. I know I should use
outbox_multipart for longer messages, but that is not the question. I am
wondering why the second message is ending up empty at the destination
while the first is just cut off.
(Gammu 1.39 on SLES15)
Thanks.
bye,
Marki
--------------4BA40ED4BEBDAB1DECAB9789
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="post-text" itemprop="text">
<p>Hey,<br>
</p>
<p>Can someone explain why is the following (decoded) message cut
correctly at the 160th character, as expected:</p>
<pre><code>00000000010000000002000000000300000000040000000005000000000600000000070000000008000000000900000000100000000011000000001200000000130000000014000000001500000000160000000017000000001800000000190000000020
</code></pre>
<p>The destination receives:</p>
<pre><code>0000000001000000000200000000030000000004000000000500000000060000000007000000000800000000090000000010000000001100000000120000000013000000001400000000150000000016
</code></pre>
<p>While the following message (TextDecoded) is just ending up
empty at the destination:</p>
<pre><code>[aaaaaa] bbbbbbbb | cccc_ccc
\_ dd (eeeeeeee)
\_ fff ff - f.fff ffffff ffffffff ffff ff ffffffff.ffff.ff ffff 389
\_ 2020-07-07 20:10:27 +0200
\_ ggggg ggggg ggggggggg GGG gg gggggggg g ggggg gg gggggggg ggg gggg gggg ggg ggggggg:
hhhhh Y44wCg6vu8m6CeG5ZB8MA2nif9l0nG7/Nceec5NA7UjZO+OKHOAjCy5hdeAdt+WVD2U=|n
</code></pre>
<p>(Unless I cut it around the timestamp, which is at about 110
characters from the start)<br>
</p>
<p>I'm simply inserting it into outbox. I know I should use
outbox_multipart for longer messages, but that is not the
question. I am wondering why the second message is ending up
empty at the destination while the first is just cut off.</p>
<p>(Gammu 1.39 on SLES15)</p>
<p>Thanks.<br>
bye,</p>
<p>Marki<br>
</p>
</div>
</body>
</html>
--------------4BA40ED4BEBDAB1DECAB9789--
--===============3020993454286590368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============3020993454286590368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Gammu-users mailing list - https://lists.sourceforge.net/lists/listinfo/gammu-users
--===============3020993454286590368==--