From: Cheng Gao <chenggao@gmail.com>
Subject: Feature Request -Customizable FQDN
Date: Thu, 23 Sep 2004 12:22:23 +0800 [thread overview]
Message-ID: <citj20$2at$1@sea.gmane.org> (raw)
(Yesterday I tried to post this message to ding via news.gnus.org, but
seems it's not posted. So I resend it via gmane.)
Just found an annoying thing in Gnus.
I use Gnus to manage my work and personal emails together, and read NGs.
And for convenience I setup user-mail-address to my personal email as
shown in this post.
I setup all my work emails in groups as 'nnml+label:biz\..*', and I use
posting styles to setup work email and organizaiton etc. Everything is
OK.
And the problem is with Message-ID.
Function message-make-fqdn always uses global `user-mail-address to
generate Message-ID (I set message-user-fqdn to nil).
I know there is way to generate message id for news and mail messages
differently. But this wont solve my problem. Coz for mail messages, I
need FQDN for work and personal use seperately.
And I think it's very reasonable to add message-user-fqdn into
customizable list of Posting Style or Group Parameter.
Just like:
(setq gnus-posting-styles '(("nntp.*" (fqdn "fornews.fqdn"))
("nnml.*" (fqdn "formail.fqdn"))
))
Or I think most reasonable:
(setq gnus-parameters '(("nntp.*" (fqdn . "fornews.fqdn"))
("nnml.*" (fqdn . "forpersonalmail.fqdn"))
("nnml.*:biz.*" (fqdn . "forworkmail.fqdn"))
)
)
OT:
Personally I think posting style should be merged into Group Parameters
entirely. I know I can setup posting-style in parameters now, but it's
feature-limited. Topic Paramters->Groups Parameters (with regexp) ->
Specific Group Parameter can be a very reasonable cascading setup tree
just like what CSS (Cascading Style Sheet) does.
CG
--
酌贪泉而觉爽,处涸辙以犹欢
next reply other threads:[~2004-09-23 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:22 Cheng Gao [this message]
2004-09-23 17:46 ` Reiner Steib
2004-09-24 6:56 ` Cheng Gao
2004-09-24 7:42 ` Reiner Steib
2004-09-24 8:02 ` Cheng Gao
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='citj20$2at$1@sea.gmane.org' \
--to=chenggao@gmail.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).