Here’s a list of variables relevant to both mailing and posting:
If your news server offers groups that are really mailing lists
gatewayed to the NNTP server, you can read those groups without
problems, but you can’t post/followup to them without some difficulty.
One solution is to add a
to-address to the group parameters
(see Group Parameters). An easier thing to do is set the
gnus-mailing-list-groups to a regexp that matches the groups that
really are mailing lists. Then, at least, followups to the mailing
lists will work most of the time. Posting to these groups (a) is
still a pain, though.
This variable controls which information should be exposed in the
User-Agent header. It can be a list of symbols or a string. Valid
gnus (show Gnus version) and
emacs (show Emacs
version). In addition to the Emacs version, you can add
(show (S)XEmacs codename) or either
config (show system
type (show system type). If you set it to a
string, be sure to use a valid format, see RFC 2616.
You may want to do spell-checking on messages that you send out. Or, if
you don’t want to spell-check by hand, you could add automatic
spell-checking via the
(add-hook 'message-send-hook 'ispell-message)
If you want to change the
ispell dictionary based on what group
you’re in, you could say something like the following:
(add-hook 'gnus-select-group-hook (lambda () (cond ((string-match "^de\\." (gnus-group-real-name gnus-newsgroup-name)) (ispell-change-dictionary "deutsch")) (t (ispell-change-dictionary "english")))))
Modify to suit your needs.
t, different levels of
citations are highlighted like in Gnus article buffers also in message