From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RDNS_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: (qmail 10462 invoked from network); 23 Mar 2020 02:53:30 -0000 Received: from unknown (HELO lists1.math.uh.edu) (129.7.128.208) by inbox.vuxu.org with ESMTP; 23 Mar 2020 02:53:30 -0000 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92.3) (envelope-from ) id 1jGDCi-0001lJ-9o; Sun, 22 Mar 2020 21:52:40 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jGDCd-0001iS-HV for ding@lists.math.uh.edu; Sun, 22 Mar 2020 21:52:35 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jGDCb-000783-SD for ding@lists.math.uh.edu; Sun, 22 Mar 2020 21:52:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Reply-To: References:Message-ID:Date:Subject:From:To:Sender:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=yWxRymlYA8aECG6/b16rqzh9iC5MIBsldUCkzIdbqxU=; b=ak5g2bLboqhWDMypTtJcNtyUfa Nrmk/MJgPIeBc4/PVGoJamU21jz/IHsMzDf7/jovrTuraeZOFOu+9GkeyAT9r0XM7Ebp4khWb02op s/QYJro3FX8Rie3VK3rMCZUzHb6Dn7ie5dgzr4MsXTorAvJGKLcpVAH+N8FxCZp0eFCA=; Received: from ciao.gmane.io ([159.69.161.202]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jGDCU-0007jn-2h for ding@gnus.org; Mon, 23 Mar 2020 03:52:29 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jGDCT-000VVn-LN for ding@gnus.org; Mon, 23 Mar 2020 03:52:25 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org To: ding@gnus.org From: Helmut Waitzmann Subject: Re: Delayed messages, postponing Date: until sending by default? Date: Mon, 23 Mar 2020 03:51:58 +0100 Message-ID: <87tv2f4wbb.fsf@helmutwaitzmann.news.arcor.de> References: <87v9n6pnb3.fsf@tullinup.koldfront.dk> <874kujrnot.fsf@ericabrahamsen.net> <874kuj0yhz.fsf@ericabrahamsen.net> <87d0976k1r.fsf@gnu.org> <87lfnvymm5.fsf@ericabrahamsen.net> <87imiyyikr.fsf@ericabrahamsen.net> Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:hefB2vwevuDMZ919P1hdRbX/4C0= Mail-Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c Mail-Copies-To: nobody List-ID: Precedence: bulk Eric Abrahamsen : >Eric Abrahamsen writes: >> Amin Bandali writes: >>> Eric Abrahamsen writes: >>>> Eric Abrahamsen writes: >>>>> Adam Sj=C3=B8gren writes: >>>>> >>>>>> Recently I read a blog post about delayed messages in Gnus:=20 >>>>>> >>>>>> >>>>>> =C2=B7 https://tech.toryanderson.com/2020/02/21/emacs-gnus-delay-sc= hedule-email-sending/ >>>>>> >>>>>> And I could help myself nerdsplaining the configuration I use for=20 >>>>>> delayed messages. >>>>>> >>>>>> One of the things is:=20 >>>>>> >>>>>> >>>>>> ; Remove date, so delayed messages (C-c C-j) don't get a date until >>>>>> ; sent, from : >>>>>> (setq message-draft-headers '(References From)) >>>>> >>>>> Huh, I didn't realize that the Date header was set as=20 >>>>> time-of-delay, not time-of-send. Confirming for myself by=20 >>>>> delaying this message by a day. No harm done, as it is=20 >>>>> totally useless! >>>> >>>> Huh, no kidding. I can't think of any reason we'd want to=20 >>>>send delayed messages out with the original Date header... >>> >>> +1; I think it would be a more sensible default to use the=20 >>>Date of send. I think it can be especially confusing for the=20 >>>receiver seeing a message dated, say, 1 day before, but only=20 >>>just appearing in their inbox. >> >> And even with regular (non-delayed) drafts, why would we want=20 >>to date it from when we *started* writing the message, rather=20 >>than when we sent it? >> >> I've opened bug#40151 for this. > >And it's in! Is it possible for the user to select the other behavior: send a=20 message with the date when the message was finished writing?=C2=A0 If=20 not, I'd beg not to change that.=C2=A0 On the other hand:=C2=A0 If I want to send a message with the date of=20 sending rather than writing, I just save it as a draft.=C2=A0 Then,=20 before sending, I reedit the message to get the current date.=C2=A0 Adhering to the general principle: provide mechanism not policy=C2=A0=E2=80= =93=20 I'd like to select the policy for myself.=C2=A0