From mboxrd@z Thu Jan 1 00:00:00 1970 From: lukasz.stelmach@iem.pw.edu.pl (=?utf-8?Q?=C5=81ukasz?= Stelmach) Subject: Re: Sending org-mode nodes Date: Fri, 20 Nov 2009 14:35:20 +0100 Message-ID: <3291978dbeaae3c6ed3b832cce64e3b1-B@dasa3> References: <87aayjaih8.fsf@dasa3.iem.pw.edu.pl> <873a4a29ce.wl%maus.david@gmail.com> <87hbsqu86y.fsf@dasa3.iem.pw.edu.pl> <87skca93a9.fsf@gmx.de> <874ooqty72.fsf@dasa3.iem.pw.edu.pl> <873a4a8t5b.fsf@gmx.de> <87lji2saz4.fsf@dasa3.iem.pw.edu.pl> <87hbsq5q8e.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBTeS-0005Cb-LY for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 08:35:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBTeO-000584-1l for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 08:35:52 -0500 Received: from [199.232.76.173] (port=56814 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBTeN-00057z-Sv for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 08:35:47 -0500 Received: from lo.gmane.org ([80.91.229.12]:42129) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NBTeN-0006Iu-Fx for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 08:35:47 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NBTeG-0000M6-Rj for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 14:35:40 +0100 Received: from dasa3.iem.pw.edu.pl ([194.29.147.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Nov 2009 14:35:40 +0100 Received: from lukasz.stelmach by dasa3.iem.pw.edu.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Nov 2009 14:35:40 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Sebastian Rose writes: > lukasz.stelmach@iem.pw.edu.pl (Łukasz Stelmach) writes: >> Sebastian Rose writes: >>> Not sure. I only remember bad things with self generated >>> message-IDs. But I never tried it myself. Reading the RFCs will help. >> >> RFC 2822 >> The "Message-ID:" field provides a unique message identifier that >> refers to a particular version of a particular message. The >> uniqueness of the message identifier is guaranteed by the host that >> generates it (see below). (...) > > Still, not sure. From what I read about message IDs, they are to be > produced by mail servers - not email clients. Take a look at this for example: http://www2.gnu-pascal.de/crystal/gpc/en/raw-mail13179.html This is a message created with Pine for Linux (look at Message-ID) > If my provider (gmx) receives my outgoing mail, it deletes the > Message-ID and generates a new one. They do not want Humpdy Dumpdy to > send mails with their own Message-ID, because there's a risk: it might > not be world-wide unique. I would do that, too. This is wrong. They should do it if the message lacks it but it's not thier problem if it's not unique. They pass the message and forget about it. As far as I know no MTA even logs Message-ID. > I cannot set the Message-ID in mailers like Gnus, Evolution, Outlook, > Thunderbird. *You* can't do it which doesn't mean your MUA doesn't do it behind the scenes. You can do it with mutt. When you edit with headers and put Message-ID you get it sent. > If I'm wrong, I'd be interested in a way to that - so I could try it > myself. I'm giving Gnus a try now the message id of this post should be <3291978dbeaae3c6ed3b832cce64e3b1-B@dasa3> I've just put the header above the --text follows this line-- -- Miłego dnia, Łukasz Stelmach