From: Amin Bandali <bandali@gnu.org>
To: Pankaj Jangid <p4j@j4d.net>
Cc: Emacs mailing list <help-gnu-emacs@gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: Is Gnus mailing list active?
Date: Tue, 19 Nov 2019 13:36:04 -0500 [thread overview]
Message-ID: <87d0dnu31n.fsf@gnu.org> (raw)
In-Reply-To: <0100016e84eefb24-369c05a0-5fb1-4149-b62d-7c631b74f001-000000@email.amazonses.com>
Pankaj Jangid <p4j@j4d.net> writes:
[...]
>
> Finally, I got to know that ding-request@gnus.org require one to send
> "subscribe" string (without quotes) in the *body*. Huh! So much
> diversity in mailing list software.
>
Yes, that’s what I’ve been trying to convey in
my earlier messages! :D The list software used
there is different from mailman (used for GNU
lists). It’s fairly strict with respect to its
accepted input(s), including the formatting and
in which part of the email they’re found in.
prev parent reply other threads:[~2019-11-19 18:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 20:07 Is Gnus mailing list active? Pankaj Jangid
2019-11-15 21:05 ` Amin Bandali
2019-11-16 2:18 ` Pankaj Jangid
2019-11-16 2:50 ` Amin Bandali
2019-11-16 10:50 ` Pankaj Jangid
2019-11-16 3:55 ` Lars Ingebrigtsen
2019-11-16 4:15 ` Amin Bandali
2019-11-16 4:22 ` Lars Ingebrigtsen
2019-11-16 10:08 ` Pankaj Jangid
2019-11-16 13:27 ` 황병희
2019-11-16 15:26 ` Pankaj Jangid
2019-11-16 13:37 ` Amin Bandali
2019-11-16 15:26 ` Pankaj Jangid
2019-11-19 4:45 ` Pankaj Jangid
2019-11-19 4:52 ` Amin Bandali
2019-11-19 6:38 ` Pankaj Jangid
2019-11-19 7:08 ` Amin Bandali
2019-11-19 11:44 ` 황병희
2019-11-25 5:25 ` [Q] What is this? 황병희
2019-11-25 5:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2019-11-25 5:44 ` 황병희
[not found] ` <m24kz0l69y.fsf@j4d.net>
2019-11-19 18:31 ` Is Gnus mailing list active? Pankaj Jangid
2019-11-19 18:36 ` Amin Bandali [this message]
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=87d0dnu31n.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=larsi@gnus.org \
--cc=p4j@j4d.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.