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.43.69] (unknown [182.2.69.153]) by gnuweeb.org (Postfix) with ESMTPSA id AD33D7E6B6; Sun, 6 Mar 2022 13:06:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1646571993; bh=dUgM3Q9Qs6IiR08n4IczJ4ePdNFwOmB3l23XVnRw3qg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=C43OdfiqgProKIwyGTiD/IpTefupZipix6iG1sY4SXsqfQZBMHwLjXO8j5N6dMJjj IMZyi9EqBF2ROLlSPASHm6FrPY5jZ1lH+m7AfLu5GbVagrq2yMAdUNjhPrVGQMSecQ RUIF8fVUrM75ayyyhcDNaGeMX81c8l7EGAsHkL23Nyq37yP1r2b9BWVy567JD9kbuU Xl2NuCmpAolcdL8A9+5xcjN0ZG1zNBWHGhUWxWAiNjmP+Rfm4vtrcufTPNqSDa9TDe sgYycYOBo1+SAHRojfGlWLG3btmAhRRUZs6WYeCFy8jB1+eVhdWlPKBhPwFTd2pgZ/ p0b349Y/2ahIw== Message-ID: <061ff990-fc8f-8ad5-1eda-4ea2c875b720@gnuweeb.org> Date: Sun, 6 Mar 2022 20:06:17 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: test debug Content-Language: en-US To: Alviro Iskandar Setiawan Cc: Alviro Iskandar Setiawan , GNU/Weeb Mailing List , Faris Suryanto References: <20220306130024.520329-1-alviro.iskandar@gnuweeb.org> From: Ammar Faizi In-Reply-To: <20220306130024.520329-1-alviro.iskandar@gnuweeb.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 3/6/22 8:00 PM, Alviro Iskandar Setiawan wrote: > Subject: [PATCH pit v1] bin/public-inbox-tg: Fix regex pattern for headers > From: Alviro Iskandar Setiawan > > When testing email with Faris, we found that Faris' emails don't get > processed. They appear on the lore, but don't appear on Telegram. Sir > Ammar debugged this bug and the log said: "Cannot get the \"message-id\" > line". > > It turned out that the regex pattern for headers was wrong, if the > header to be matched happens to be at the end of the headers, it will > not have a double LF because previously we have already split the > double LF with explode(). Fix this by changing the pattern to match the > header if it happens to be at the end of the headers. Applied, thanks! -- Ammar Faizi