Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Haines Brown <brownh@hartford-hwp.com>
Subject: Re: No Followup-To header defaults
Date: Wed, 24 Aug 2005 22:52:15 GMT	[thread overview]
Message-ID: <87y86rgd7d.fsf@teufel.hartford-hwp.com> (raw)
In-Reply-To: <86wtmbnrjm.fsf@free.fr>

Bernard Adrian <bernadrian@free.fr> writes:

> Haines Brown <brownh@hartford-hwp.com> a écrit : 
>
>> When I moved to a set up on a new machine, my gnus (still emacs
>> version 21.4.2) acts differently. I should add that I moved all
>> statements related to gnus from my ~/.emacs file to a ~/.gnus file,
>> but none seem relevant to the issue.
>>
>> When I reply to a message that was originally sent to multiple groups,
>> I get: 
>>
>>   Followups to (default: no Followup-To header)
>>
>
> [...]
>
>
>> Just in case, here's my ~/.gnus file:
>>
>>   (setq user-mail-address "...")
>>   (setq user-full-name "...")
>>   (setq mail-host-address "...")
>>   (setq gnus-system-name "...")
>>   (setq gnus-select-method '(nntp "..."))
>>   (setq gnus-verbose 10)
>>   (setq gnus-verbose-backends 10)
>
> In mine there is the line below 
>
> (require 'message)
>
> this package contains functions and variables which take care about
> cross-posting and follow-up 

Bernard,

Thanks for the suggestion, but it didn't work, unfortunately.

-- 
 
       Haines Brown
       KB1GRM       


  reply	other threads:[~2005-08-24 22:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 17:31 Haines Brown
2005-08-24 18:00 ` Bernard Adrian
2005-08-24 22:52   ` Haines Brown [this message]
2005-08-25 10:15   ` Reiner Steib
2005-08-25 15:25     ` Bernard Adrian
2005-08-25 17:47     ` Haines Brown
2005-08-28 17:28       ` Reiner Steib
2005-08-29  1:10         ` Haines Brown
2005-09-03 16:16           ` Reiner Steib
2005-08-24 22:47 ` Katsumi Yamaoka

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=87y86rgd7d.fsf@teufel.hartford-hwp.com \
    --to=brownh@hartford-hwp.com \
    /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).