From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.1.2] (unknown [101.128.125.123]) by gnuweeb.org (Postfix) with ESMTPSA id BC81480908; Fri, 21 Oct 2022 10:52:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1666349554; bh=EM1VgfLsRjlVtsA2L7RIz+zzNalJeWelPV0Khm/oD40=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=cgM7fsgrV8K4jplUjVLOaC2r6DVxcpCmiHa5Zj138El3ba5fPtm1HEsX+umUDNUds olPFoTrVzfzKCdu5adN9pnrXBu1lrReRgbH0/mb+Wpezi87172YjDcEm4EK4Gn2FVM IFMOTYC7OnwT/MIL/0xHLJX3wI3UyKB5jitnMCA1kx0MKgLPXy6c1h1lq+G9ID9Jq7 1nz/XA9OWH1K0U6fA0OZoMkcqNxeqK7F9blUT2JOH78JeMt/I2GEHTceArZb9CgEG5 sipkM2aMOEVyLieQSBpMIwFSUZNM2+DzcMTMAdnoJ/hdZsRMRw2p5WbVBs3CGrMTn4 +msvgdf9Kw1pw== Message-ID: <7bf0d319-cedc-3cc3-e440-c63bb5980dc4@gnuweeb.org> Date: Fri, 21 Oct 2022 17:52:30 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3 Subject: Re: [PATCH v2 4/8] atom: Small change for fix_utf8_char() Content-Language: en-US To: Ammar Faizi Cc: Alviro Iskandar Setiawan , GNU/Weeb Mailing List References: <20221020083845.907-1-kiizuha@gnuweeb.org> <20221020083845.907-5-kiizuha@gnuweeb.org> <553365db-106b-dc91-108c-38b3d9b0bbba@gnuweeb.org> <1af6bd52-d817-c22f-f757-9fa034e2a166@gnuweeb.org> From: Muhammad Rizki In-Reply-To: <1af6bd52-d817-c22f-f757-9fa034e2a166@gnuweeb.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 21/10/2022 17.50, Ammar Faizi wrote: > On 10/21/22 5:44 PM, Muhammad Rizki wrote: >> The text content that I'm printing out in the send_text_mail() in the >> telegram/packages/client.py is: > > After reading the output you just sent, I think there are two > possibilities here: > > 1) You use the Telegram library wrong. Or ... > > 2) It's a bug in the Telegram library itself. > > What do you think? > Hmm, I didn't realize it's a bug. Because it is very weird when you tested it and the email payload is empty after sent to Telegram. But, mine doesn't.