From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/13651 Path: news.gmane.org!not-for-mail From: Tim Landscheidt Newsgroups: gmane.emacs.gnus.user Subject: Re: Delayed messages with "revealing" Date header? Date: Fri, 12 Feb 2010 22:36:27 +0000 Organization: Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1266014226 10106 80.91.229.12 (12 Feb 2010 22:37:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Feb 2010 22:37:06 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Fri Feb 12 23:37:01 2010 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ng489-0001cI-12 for gegu-info-gnus-english@m.gmane.org; Fri, 12 Feb 2010 23:36:57 +0100 Original-Received: from localhost ([127.0.0.1]:59361 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ng488-00023S-Cm for gegu-info-gnus-english@m.gmane.org; Fri, 12 Feb 2010 17:36:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ng486-000238-9b for info-gnus-english@gnu.org; Fri, 12 Feb 2010 17:36:54 -0500 Original-Received: from [140.186.70.92] (port=59819 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ng485-00022i-Kd for info-gnus-english@gnu.org; Fri, 12 Feb 2010 17:36:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ng484-0001JK-P2 for info-gnus-english@gnu.org; Fri, 12 Feb 2010 17:36:53 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:47084) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ng484-0001JA-89 for info-gnus-english@gnu.org; Fri, 12 Feb 2010 17:36:52 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ng482-0001XV-Uo for info-gnus-english@gnu.org; Fri, 12 Feb 2010 23:36:50 +0100 Original-Received: from e177159073.adsl.alicedsl.de ([85.177.159.73]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Feb 2010 23:36:50 +0100 Original-Received: from tim by e177159073.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Feb 2010 23:36:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: info-gnus-english@gnu.org Original-Lines: 65 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: e177159073.adsl.alicedsl.de Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:9WUD8O2Dih4veec6OEVbK9OuHDY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:13651 Archived-At: Katsumi Yamaoka wrote: >> When I delay a message with C-c C-j, the message gets a >> Date header with the current time (visible in the delayed >> group) that is not filtered when the message is sent. This >> results in a message sent at time Y that is clearly labelled >> as having been written at time X - though in most cases I >> would assume the intention would be to pretend it having >> been written at time Y. Is this an issue with my setup >> (Gnus 5.13) or is my use case so uncommon? :-) > The present behavior seems faithful to RFC2822: > ,---- > | 3.6.1. The origination date field 3.6.1. > | [...] > | The origination date specifies the date and time at which the > | creator of the message indicated that the message was complete > | and ready to enter the mail delivery system. For instance, this > | might be the time that a user pushes the "send" or "submit" > | button in an application program. In any case, it is > | specifically not intended to convey the time that the message is > | actually transported, but rather the time at which the human or > | other creator of the message has put the message into its final > | form, ready for transport. (For example, a portable computer > | user who is not connected to a network might queue a message for > | delivery. The origination date is intended to contain the date > | and time that the user queued the message, not the time when the > | user connected to the network to send the message.) > `---- Well, it probably depends whether Gnus considers itself a MUA or a MTA :-). *If* the latter, I would expect a delay string of "when online on network X" rather than wall-clock time :-). > You can easily override it though. ;-p > (defadvice gnus-draft-send (around remove-date-header-from-delayed-message > activate) > "Remove Date header from delayed message in order to be redone." > (if (equal (ad-get-arg 1) "nndraft:delayed") > (let ((gnus-message-setup-hook > (cons (lambda nil > (save-restriction > (message-narrow-to-headers) > (if (re-search-forward "^Date:.*\n" nil t) > (replace-match "")))) > gnus-message-setup-hook))) > ad-do-it) > ad-do-it)) I *wanted* to ask why not to advise gnus-delay-send-queue, which seems to be the more "natural" place to do so, then I wondered how you could then set a Date header if you wanted to, so I started debugging where the Date header actually comes from :-). The result was that the Date header gets in- serted due to message-draft-headers. Deleting Date from that solved the issue. The only downside I could find so far was that the drafts and delayed groups can no longer be sorted by date; are there any other disadvantages I overlooked? Tim