Hello! Again, the same weirdness. My recipient got this.
MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Message-Id: 0KHQsNC9INCh0LDQvdGL0YcsDQoNCtCa0L7RgNC+0YLQutC+LCDRh9C10Lwg0LzRiyDQt9Cw0L3Q uNC80LDQtdC80YHRjyBodHRwOi8vd3d3LnN5Y29yZS5vcmcgLiDQntC00LjQvSDQuNC3INC90LDR iNC40YUNCtC40LfQstC10YHRgtC90YvRhSDQv9GA0L7QtdC60YLQvtCyINCyINGB0LXRgtC4IGh0 dHA6Ly93d3cuZ290YWxrLnJ1L2R0YWxrLmh0bWwNCg0K0JIg0L7QsdGJ0LXQvCwg0LzRiyDRgNCw 0LfRgNCw0LHQsNGC0YvQstCw0LXQvCDRgNCw0LfQvdC+0L7QsdGA0LDQt9C90L7QtSDQn9CeLiDQ mtC+0L3QutGA0LXRgtC90L4sINC70LjRh9C90L4g0Y8g0LINCtC00LDQvdC90YvQuSDQvNC+0LzQ ... This time, however, I can read the outgoing message on my box. Definitely, there is a serious bug, but it's not easily reproduced. -- Rgds Alexey Today is Boomtime, the 10th day of The Aftermath in the YOLD 3174 _______________________________________________ info-gnus-english mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-gnus-english
