Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Problem with Message-ID and agent Unplugged
Date: Thu, 01 May 2003 14:15:31 +0200	[thread overview]
Message-ID: <m34r4e50d8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <v93cjyc34r.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> But the agent maybe could remove those fudged MIDs before actually
> sending the message, If `message-required-{news,mail}-headers' doesn't
> contain MID?

Perhaps, but...

> IMHO, Gnus should support it, for people not having an own FQDN.

... everybody has something that they can put in the RHS of a
Message-ID.  

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen



      reply	other threads:[~2003-05-01 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 15:43 Thomas Havlovec
2003-05-01  7:07 ` Lars Magne Ingebrigtsen
2003-05-01 11:33   ` Reiner Steib
2003-05-01 12:15     ` Lars Magne Ingebrigtsen [this message]

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=m34r4e50d8.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    /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).