Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Andy Burns Newsgroups: comp.mobile.android Subject: Re: For those using Google messages with RCS with iPhone owners... Date: Mon, 7 Jul 2025 15:27:26 +0100 Lines: 13 Message-ID: References: <1042bom$28bd$1@nnrp.usenet.blueworldhosting.com> <104gkv7$fpb$1@nnrp.usenet.blueworldhosting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net wTm4Mb7++ekXb+QfHqz0jAWrThY9m5dY7dnU+e462/yT0xKQPW Cancel-Lock: sha1:AGhKsjv81bHe9XBE+5G+kLxzJBQ= sha256:tdT+/NBGxCvwHqCl/5ejgjooH8386kJ7Tf+xqfIQPRo= User-Agent: Mozilla Thunderbird Content-Language: en-GB In-Reply-To: <104gkv7$fpb$1@nnrp.usenet.blueworldhosting.com> Xref: csiph.com comp.mobile.android:149670 Marion wrote: > I seem to remember a "cancel" mechanism of Usenet in the olden days. > Does it still exist? > > If you made a boo boo, you could cancel an article, fix it, & then resend. Yesbut ... In those days propagation delays were higher, so there was more time to send out the cancel, now you probably haven't got time. Plenty of servers implement a cryptographic cancel-lock (see headers) others ignore cancels.