From: Rasmus <rasmus@gmx.us>
To: info-gnus-english@gnu.org
Subject: Re: New error message about Message-ID
Date: Wed, 22 Mar 2017 13:21:50 +0100 [thread overview]
Message-ID: <87efxp4i3l.fsf@gmx.us> (raw)
In-Reply-To: <87wpbhh67p.fsf@lago>
Julien Cubizolles <j.cubizolles@free.fr> writes:
> I recently noticed that gnus complains about the Message-ID of outoing
> posts (to gmane) with:
>
> The Message-ID looks strange: "<871stpikxi.fsf@lago>". Really post? (y
> or n) y
>
> lago is the hostname of the machine I'm using. Did something recently
> change about the check of the message-ID or the message-ID creation ?
See,
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25702
I work around this bug by adding this to init.el
(with-eval-after-load 'message
(setq message-bogus-system-names
(regexp-opt '("W530" "X200" "X200s"))))
Hope it helps,
Rasmus
--
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio
_______________________________________________
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:[~2017-03-22 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:00 Julien Cubizolles
2017-03-22 12:21 ` Rasmus [this message]
2017-04-04 16:46 ` Julien Cubizolles
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=87efxp4i3l.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).