From: Dmitry Alexandrov <dag@gnui.org>
To: Rafi Khan <rafi@rafikhan.io>
Cc: info-gnus-english@gnu.org
Subject: Re: Test email
Date: Thu, 09 Jul 2020 11:17:10 +0300 [thread overview]
Message-ID: <sge1umpl.dag@gnui.org> (raw)
In-Reply-To: <87eeplxo93.fsf@rafikhan.io> (Rafi Khan's message of "Thu, 09 Jul 2020 01:15:36 -0400")
[-- Attachment #1.1: Type: text/plain, Size: 1718 bytes --]
Rafi Khan <rafi@rafikhan.io> wrote:
> I am new to gnus and mailing lists and have just setup Emacs with GNUS and my email account.
Welcome!
> This is just a test email so that I can confirm things are setup as intended.
You are posting via Gmane, are not you? Thatʼs sort of fine for that list (and any list on (non)gnu.org), but not for every one on the Net. Posting in a normal way — by mailing to a list address (here: info-gnus-english@gnu.org) via your mailserver (smtp.googlemail.com in your case) is generally more reliable.
> Further, is there a guide I can read to learn more about how to use mailing lists?
Lots of such guides were accumulated over the Net for decades, but I do not know any, thatʼs worth reading. They commonly contain not very relevant info, that overwhelm the newcomer, often — local-specific and outdated info, and sometimes — simply bullshit.
Basically, there is nothing to explain: mailing lists are supposed to be naturally familiar for anyone who is familiar with mail, that is simply to anyone. And despite all the joint efforts of some list-hosters, mail useragent designers and individuals to derail it, they are mostly indeed are.
The only mistake UI designers succeeded to teach users, though, is to to command ‘Reply to sender only’ instead of ‘Reply to all’, which is of course is not what you want while discussing things publicly. Yet in too many MUAs the latter in too concealed. Gnus, of course, is not one those, so you are safe here.
> There's a lot of terminology in the gnus documentation ‹…› Some of this can be inferred from the documentation and context, but others are not so clear to me.
Feel free to ask.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
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:[~2020-07-09 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 5:15 Rafi Khan
2020-07-09 7:31 ` Alberto Luaces
2020-07-10 0:14 ` Rafi Khan
2020-07-10 7:54 ` Adam Sjøgren via info-gnus-english
2020-07-10 23:47 ` Rafi Khan
2020-07-10 13:18 ` ‘Reply’ vs ‘followup’ (was: Test email) Dmitry Alexandrov
2020-07-10 14:14 ` ‘Reply’ vs ‘followup’ Alberto Luaces
2020-07-10 15:28 ` Adam Sjøgren via info-gnus-english
2020-07-10 23:51 ` Rafi Khan
2020-07-09 8:17 ` Dmitry Alexandrov [this message]
[not found] ` <87imewz0ui.fsf@rafikhan.io>
2020-07-10 4:26 ` Get list address for Gmane group (was: Test email) Dmitry Alexandrov
2020-08-06 12:53 ` Test email 황병희
2020-08-07 4:01 ` Rafi Khan
2020-08-08 2:31 ` 황병희
2020-08-08 15:39 ` Emanuel Berg via info-gnus-english
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=sge1umpl.dag@gnui.org \
--to=dag@gnui.org \
--cc=info-gnus-english@gnu.org \
--cc=rafi@rafikhan.io \
/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).