Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: message.el: mail-host-address ignored
Date: 11 Nov 1999 21:00:49 +0000	[thread overview]
Message-ID: <uaeoku4ji.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Raymond Scholz's message of "11 Nov 1999 21:39:16 +0100"

Raymond> Raymond Scholz <URL:mailto:rscholz@tzi.de>

0> In article <m3hfisu5jf.fsf@rscholz.dyndns.org>, Raymond wrote:

Raymond> Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

>> What would be even better is if someone defined a "Message-ID by
>> UDP or TCP" service one could connect to for unique IDs.

Raymond> I use `mail-host-address' for kinda such thing.  If I dial
Raymond> up at my ISP, I get a dynamic IP address.  After that I
Raymond> use a tools from DynDNS (http://www.dyndns.org) to point
Raymond> rscholz.dyndns.org on my dynamic address. So the message
Raymond> IDs are RFC-conform (or whatever).

I don't think we're talking about the same thing.  In my Ideal
Universe(TM), I'd connect to the message-id port of some host
(perhaps localhost), and it would reply with a valid message-id.
A bit like how the chargen service works.  Then Gnus and all the
other systems out there using message-ids wouldn't have to each
implement their own generators, and there'd be less chance of
collisions.  But I think that now is too late to put the genie
back into the bottle.



  reply	other threads:[~1999-11-11 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-10 18:24 Raymond Scholz
1999-11-11  1:31 ` Rene H. Larsen
1999-11-11 12:41   ` Toby Speight
1999-11-11 18:45     ` Rene H. Larsen
1999-11-11 20:39     ` Raymond Scholz
1999-11-11 21:00       ` Toby Speight [this message]
1999-11-11 16:38   ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uaeoku4ji.fsf@lanber.cam.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).