From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: good address gives "may be bogus"
Date: Thu, 14 Apr 2016 16:40:23 +0200 [thread overview]
Message-ID: <87vb3kdzjc.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87shyo34rj.fsf@fsfe.org>
Kevin writes:
> Where can I put exceptions to the "address x may be bogus" warning? (I
> got this for a good @ehu.eus address.)
Looks like the huge regexp you want to change is:
,----[ C-h v message-valid-fqdn-regexp RET ]
| message-valid-fqdn-regexp is a variable defined in `message.el'.
| Its value is
| "[a-z0-9][-.a-z0-9]+\\.\\([a-z][a-z]\\|aero\\|arpa\\|....
|
| Documentation:
| Regular expression that matches a valid FQDN.
|
| You can customize this variable.
|
| This variable was introduced, or its default value was changed, in
| version 25.1 of Emacs.
`----
Found in the function message-bogus-recipient-p in message.el:
,----[ C-h f message-bogus-recipient-p RET ]
| message-bogus-recipient-p is a compiled Lisp function in `message.el'.
|
| (message-bogus-recipient-p RECIPIENTS)
|
| Check if a mail address in RECIPIENTS looks bogus.
|
| RECIPIENTS is a mail header. Return a list of potentially bogus
| addresses. If none is found, return nil.
|
| An address might be bogus if the domain part is not fully
| qualified, see `message-valid-fqdn-regexp', or if there's a
| matching entry in `message-bogus-addresses'.
`----
Best regards,
Adam
--
(Pithy optimistic saying goes here. Remember to edit Adam Sjøgren
this line!) 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-14 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 9:42 Kevin Brubeck Unhammer
2016-04-14 14:40 ` Adam Sjøgren [this message]
2016-04-20 12:23 ` Kevin Brubeck Unhammer
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=87vb3kdzjc.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).