From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: message-ignored-mail-headers is ignored
Date: Sat, 30 Apr 2016 11:15:12 +0200 [thread overview]
Message-ID: <87a8kbihjz.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87r3dnpj5d.fsf@libertad.pw>
niasterisk@grrlz.net writes:
> No matter what I try and set in message-ignored-mail-headers,
> gnus always sets the user-agent, even if ignored. Is there a
> mistake in these settings or something I need to add?
An alternative is to set the variable gnus-user-agent to nil.
Best regards,
Adam
--
"Do you really think that you're lost? Adam Sjøgren
And that you'll never find the way" asjo@koldfront.dk
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2016-04-30 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 8:58 niasterisk
2016-04-30 9:15 ` Adam Sjøgren [this message]
2016-04-30 9:53 ` niasterisk
2016-04-30 9:52 ` Emanuel Berg
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=87a8kbihjz.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).