From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/35275 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: drafts/queue and edited messages. Date: 09 Mar 2001 15:08:00 -0800 Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035171043 2085 80.91.224.250 (21 Oct 2002 03:30:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:30:43 +0000 (UTC) Return-Path: Original-Received: (qmail 10767 invoked by alias); 9 Mar 2001 23:08:06 -0000 Original-Received: (qmail 10762 invoked from network); 9 Mar 2001 23:08:06 -0000 Original-Received: from mail.networkone.net (209.144.112.246) by gnus.org with SMTP; 9 Mar 2001 23:08:06 -0000 Original-Received: (qmail 17039 invoked from network); 9 Mar 2001 23:08:05 -0000 Original-Received: from unknown (HELO reader.local.lan) (209.144.117.151) by mail.networkone.net with SMTP; 9 Mar 2001 23:08:05 -0000 Original-Received: (from reader@localhost) by reader.local.lan (8.11.0/8.11.0) id f29N80527322; Fri, 9 Mar 2001 15:08:00 -0800 X-Authentication-Warning: reader.local.lan: reader set sender to reader@newsguy.com using -f Original-To: ding@gnus.org User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7 Original-Lines: 20 Xref: main.gmane.org gmane.emacs.gnus.general:35275 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:35275 This has come up a few times but I've lost track of any resolution to it. Using a semi-stock outgoing message archive and then several particular groups where I've set gcc in the group params. If I happen to edit a message that has collected in ~/News/drafts/queue The archived or gcc'ed copy is no longer a faithful copy. Is this just unavoidable or can we have code that governs drafts/queue and knows where the message came from, its file number and whether it is gcc'ed? If so write them back to the sending group overwriting the original. Maybe the same with the global archive, if the message is not gcc'ed. Maybe make it a requirement for this code that all groups involved be under that same backend. Avoiding that major problem.