Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Glenn Morris <gmorris+news@ast.cam.ac.uk>
Subject: Re: message-ids
Date: Wed, 28 Aug 2002 13:16:03 +0100	[thread overview]
Message-ID: <w0adn7dvr0.fsf@ast.cam.ac.uk> (raw)
In-Reply-To: <e1adn7xla5.fsf@chef.local>

Jan Exner wrote:

> I just discovered that upgrading from 5.8.8 to Oort 0.07 broke my
> message-ids. I used gnushush.el to prevent gnus from generating them,
> because leafnode was doing it.
>
> Is there a way to tell Oort what the hostname part of the id should
> be? Or can I make gnushush work again?

Doesn't it work to say:

(require 'gnushush)
(setq gnushush-enable-p t
      gnushush-fqdn "hostname_part_of_id")

This does the job for me with Oort-0.07, gnushush-1.0


      parent reply	other threads:[~2002-08-28 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e1adn7xla5.fsf@chef.local>
2002-08-28 11:52 ` message-ids Kai Großjohann
2002-08-28 15:53   ` message-ids Jan Exner
2002-08-28 12:16 ` Glenn Morris [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=w0adn7dvr0.fsf@ast.cam.ac.uk \
    --to=gmorris+news@ast.cam.ac.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).