Re: message-ids

Re: message-ids

[Kai Großjohann]

Jan Exner <exner@gmx.net> writes:

> Is there a way to tell Oort what the hostname part of the id should
> be? Or can I make gnushush work again?

In Emacs, you can set the variable system-name.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: message-ids

[Jan Exner]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> In Emacs, you can set the variable system-name.

That works!

Glenn Morris <gmorris+news@ast.cam.ac.uk> writes:

> Doesn't it work to say:
>
> (require 'gnushush)
> (setq gnushush-enable-p t
>       gnushush-fqdn "hostname_part_of_id")

Yes, it does work, too!

I just had (require...) in my .emacs, not the (setq...) part. I wonder
why that worked with 5.8.8...

Cool, thanks very much!
Jan

-- 
Jan Exner · exner@gmx.net · 0x9E0D3E98 · http://www.jan-exner.de/

Neues aus Frankreich http://www.jan-exner.de/france.html

Re: message-ids

[Glenn Morris]

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