From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/7814 Path: main.gmane.org!not-for-mail From: Sudish Joseph Newsgroups: gmane.emacs.gnus.general Subject: Re: how do I fcc: a nnml folder? and what is gcc? (gnus 5.3) Date: 04 Sep 1996 23:43:53 -0400 Sender: sj@atreides.erehwon.org Message-ID: References: <199609041433.HAA17952@kelly.teleport.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.69) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035148075 8608 80.91.224.250 (20 Oct 2002 21:07:55 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:07:55 +0000 (UTC) Cc: "Randal L. Schwartz" Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id VAA29748 for ; Wed, 4 Sep 1996 21:01:21 -0700 Original-Received: from sudish.users.MindSpring.COM (qmailr@user-168-121-167-78.dialup.mindspring.com [168.121.167.78]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Thu, 5 Sep 1996 05:43:41 +0200 Original-Received: (qmail-queue invoked by uid 501); 5 Sep 1996 03:43:53 -0000 Original-To: The Ding list In-Reply-To: Raja R Harinath's message of 04 Sep 1996 20:01:29 -0500 Original-Lines: 39 X-Mailer: Red Gnus v0.23/XEmacs 19.14 Xref: main.gmane.org gmane.emacs.gnus.general:7814 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:7814 Raja R Harinath writes: > Steven L Baur writes: >> What I do is let Gnus process Fcc's as if they were incoming >> messages. Put a line like: >> Fcc: ~/spool/sent.spool > It's useful, but not safe. (push "~/spool/sent.not-nnml-procmail-suffix" nnmail-spool-file) in conjunction with a fixed Fcc to the same file will do the job safely, with or w/o procmail. This is assuming that headers in outgoing mail contain sufficient info to let you split them correctly...this is usually true. [ good stuff on procmail locking deleted ] > You can craft a lock aware `message-fcc-handler-function', that uses the > lockfile(1) program that comes with procmail (Also, such a handler > function won't cause harm on non spool folders either.) Only then is it > safe to Fcc: to a mail spool. The problem with this is the handler runs synchronously...you do not want to wait for the procmail process running on the way overloaded mail hub to deliver to the heavily banged upon spool partition and relinquish the lock under your (possibly NFS-mounted on the mailhub, eww) $HOME for every message you send. An asynch variation is to just hand a copy of the message to a procmail sub-process from the fcc handler. However, since this assumes that the message contains sufficient info in the headers to be split appropriately, it is entirely equivalent to using "Bcc: me" and loses for the same reasons; using nnmail-spool-file with a fixed Fcc is better for the same assumptions. -Sudish "managed not to rant on true asynch delivery, yay" Joseph PS: How about renaming it to nnmail-spool-files, like vm-spool-files? Backward compatibility is easy enough.