Size: 13282
Comment: Added internal link referring to message threading.
|
Size: 12576
Comment: cleanup
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
[[http://www.debian.org/MailingLists|debian.org/MailingLists]] - Official information about mailing lists | [[https://www.debian.org/MailingLists/|debian.org/MailingLists]] - Official information about mailing lists |
Line 8: | Line 8: |
First see [[http://www.debian.org/MailingLists/|the official information]]. | First see [[https://www.debian.org/MailingLists/|the official information]]. |
Line 15: | Line 15: |
Find a list in [[http://lists.debian.org/completeindex.html|lists.debian.org]] or on [[AdditionalDebianMailingLists|other locations]]. A click on a list name yields this information. |
Find a list in [[https://lists.debian.org/completeindex.html|lists.debian.org]] or on [[AdditionalDebianMailingLists|other locations]]. A click on a list name yields this information: |
Line 23: | Line 24: |
A list can be read ''via'' these mechanisms. | A list can be read ''via'' these mechanisms: |
Line 25: | Line 27: |
* A Web browser viewing the archives, which are public. Open {{{http://lists.debian.org/<listname>/}}}. Subscription is not necessary. | * A Web browser viewing the archives, which are public. Open {{{https://lists.debian.org/<listname>/}}}. Subscription is not necessary. |
Line 29: | Line 31: |
Each list has two addresses. | Each list has two addresses: |
Line 31: | Line 34: |
* {{{<listname>-REQUEST@lists.debian.org}}} to which an administrative request can be sent. Subscription and unsubscription requests are examples. More information is available in [[http://www.debian.org/MailingLists/index.en.html#subunsub|the Debian support page]] on debian.org. |
* {{{<listname>-REQUEST@lists.debian.org}}} to which an administrative request can be sent. Subscription and unsubscription requests are examples. More information is available in [[https://www.debian.org/MailingLists/index.en.html#subunsub|the Debian support page]] on debian.org. |
Line 35: | Line 37: |
[[http://lists.debian.org/users.html|debian-user]] is probably the most frequented mailing list for users. | [[https://lists.debian.org/users.html|debian-user]] is probably the most frequented mailing list for users. |
Line 37: | Line 40: |
This list receives up to 300--yes, three hundred--mails per day. Other lists are dedicated to other natural languages and to specific subjects. |
This list receives a large volume of email per day. Other lists are dedicated to other human languages and to specific subjects. |
Line 43: | Line 46: |
[[http://www.debian.org/MailingLists/#codeofconduct|The official rules of conduct]] The answer to a question might already have been answered. Check these areas before posting. * [[http://lists.debian.org/search.html|Search the Debian User Lists]]. Instructions for searching are in the [[DebianMailingLists/SearchHowto|SearchHowto]]. {i} Additionally you can install a [[https://addons.mozilla.org/en-us/firefox/addon/debian-user/?src=collection&collection_id=cabee24f-258b-43d0-a60f-119ad725db60|Search Bar plugin for Iceweasel/Firefox]] to search the last month of Debian-user postings for a search-term. * [[DebianResources]] |
[[https://www.debian.org/MailingLists/#codeofconduct|The official rules of conduct]] The answer to a question might already have been answered. Check these areas before posting: * [[https://lists.debian.org/search.html|Search the Debian User Lists]]. Instructions for searching are in the [[DebianMailingLists/SearchHowto|SearchHowto]] * [[DebianResources|Debian resources]] |
Line 52: | Line 55: |
Read first the official [[http://www.debian.org/MailingLists#codeofconduct|code of conduct]]. These points should be born in mind. | Read first the official [[https://www.debian.org/MailingLists#codeofconduct|code of conduct]]. These points should be born in mind: |
Line 85: | Line 88: |
[[http://tools.ietf.org/html/rfc5322#section-3.6.4|RFC 5322]]. | [[https://tools.ietf.org/html/rfc5322#section-3.6.4|RFC 5322]]. |
Line 97: | Line 100: |
only the antecedent Message-ID as the value for References. Otherwise an old message can be read from the archive with a browser and a reply can be created with an email client. No email client can extract the Message-id field from the html version of an archived message. In this situation, unless the user correctly inserts values for In-Reply-To and References a new thread is created. Some email clients allow the user to construct these fields. [[https://wiki.debian.org/|Mutt]], for example, has the -H option. |
only the antecedent Message-ID as the value for References. When reading messages via the web archives, you can click the "Reply to" mailto links at the bottom of the posts to compose a new email with the correct headers. Most graphical mail clients will support these reply links. For clients that do not support these reply links, some email clients allow the user to construct these fields. [[Mutt|mutt]], for example, has the -H option. |
Line 110: | Line 108: |
[[https://lists.debian.org/debian-user/2020/01/msg00480.html|https://lists.debian.org/debian-user/2020/01/msg00480.html]].<<BR>> ===========Web view of message being replied to===========<<BR>> ` To: debian-user@lists.debian.org`<<BR>> ` Subject: Re: xdvi refresh`<<BR>> ` From: ...`<<BR>> ` Date: Wed, 15 Jan 2020 10:51:47 -0600`<<BR>> ` Message-id: <[🔎] 20200115165147.GB3320@wren.corp>`<<BR>> ` Reply-to: debian-user@lists.debian.org`<<BR>> ` In-reply-to: <[🔎] 20200115070050.GB10975@tuxteam.de>`<<BR>> ` References: <[🔎] 20200114201617.vbbxu7hest5oozvl@rlharris.org> <[🔎] 20200115070050.GB10975@tuxteam.de>`<<BR>> <<BR>> `<message body>`<<BR>> ===========Web view of message being replied to===========<<BR>> =============plain text content of draft file=============<<BR>> `To: debian-user@lists.debian.org`<<BR>> `In-Reply-To: <20200115165147.GB3320@wren.corp>`<<BR>> `References: <20200114201617.vbbxu7hest5oozvl@rlharris.org> <20200115070050.GB10975@tuxteam.de> <20200115165147.GB3320@wren.corp>`<<BR>> `Subject: Re: how to seamlessly play audio clip`<<BR>> <<BR>> `<message body>`<<BR>> =============plain text content of draft file============= |
<<mid(20200115165147.GB3320@wren.corp)>>: Web view of message being replied to: {{{ To: debian-user@lists.debian.org Subject: Re: xdvi refresh From: ... Date: Wed, 15 Jan 2020 10:51:47 -0600 Message-id: <[🔎] 20200115165147.GB3320@wren.corp> Reply-to: debian-user@lists.debian.org In-reply-to: <[🔎] 20200115070050.GB10975@tuxteam.de> References: <[🔎] 20200114201617.vbbxu7hest5oozvl@rlharris.org> <[🔎] 20200115070050.GB10975@tuxteam.de> <message body> }}} plain text content of draft file: {{{ To: debian-user@lists.debian.org In-Reply-To: <20200115165147.GB3320@wren.corp> References: <20200114201617.vbbxu7hest5oozvl@rlharris.org> <20200115070050.GB10975@tuxteam.de> <20200115165147.GB3320@wren.corp> Subject: Re: how to seamlessly play audio clip <message body> }}} |
Line 134: | Line 137: |
* The origin of the thread is the first Reference, message `<20200114201617.vbbxu7hest5oozvl@rlharris.org>`. | * The origin of the thread is the first Reference, message <<mid(20200114201617.vbbxu7hest5oozvl@rlharris.org)>>. |
Line 139: | Line 142: |
Line 142: | Line 144: |
Some Debian lists (including debian-devel-announce) only allow posts which are signed by a Debian developer key to be submitted. This system does not allow unsigned content at the beginning of a PGP/MIME message, which means that messages sent by Thunderbird/Icedove will be blackholed (see https://sourceforge.net/p/enigmail/bugs/349/ for more information about this problem). = HowTo send plain text emails to the list = |
Some Debian lists (including debian-devel-announce) only allow posts which are signed by a Debian Developer key to be submitted. This system does not allow unsigned content at the beginning of a PGP/MIME message, which means that messages sent by Thunderbird/Icedove will be blocked (see https://sourceforge.net/p/enigmail/bugs/349/ for more information about this problem). = How to send plain text emails to the list = |
Line 147: | Line 149: |
Line 150: | Line 153: |
Line 154: | Line 158: |
Line 157: | Line 162: |
Line 164: | Line 170: |
Line 167: | Line 174: |
Line 170: | Line 178: |
Line 176: | Line 185: |
Line 180: | Line 190: |
Line 184: | Line 195: |
Line 191: | Line 203: |
Line 196: | Line 209: |
Line 199: | Line 213: |
Line 202: | Line 217: |
Line 206: | Line 222: |
Line 213: | Line 230: |
Line 220: | Line 238: |
Line 224: | Line 243: |
Line 228: | Line 248: |
Line 231: | Line 252: |
Line 238: | Line 260: |
Translation(s): English - Español - Français - Italiano
debian.org/MailingLists - Official information about mailing lists
First see the official information.
Introduction
There are over one hundred mailing lists, each focused on a specific topic.
Find a list in lists.debian.org or on other locations.
A click on a list name yields this information:
- A description of the subject.
- An index to archived messages.
- An interface for subscribing and for cancelling subscription.
- Statistics concerning activity.
A list can be read via these mechanisms:
- Email when subscribed to the list.
A Web browser viewing the archives, which are public. Open https://lists.debian.org/<listname>/. Subscription is not necessary.
- Usenet with Network News (Transfer|Transport) Protocol, NNTP.
The mail-to-news gateways linux.debian.*. Install a news reader and subscribe to the linux-gate admin.
Each list has two addresses:
<listname>@lists.debian.org to which a list message can be sent.
<listname>-REQUEST@lists.debian.org to which an administrative request can be sent. Subscription and unsubscription requests are examples. More information is available in the Debian support page on debian.org.
For users
debian-user is probably the most frequented mailing list for users. Any problem using Debian can be discussed there in English. This list receives a large volume of email per day.
Other lists are dedicated to other human languages and to specific subjects.
Posting Rules, Guidelines, and Tips
The answer to a question might already have been answered. Check these areas before posting:
Search the Debian User Lists. Instructions for searching are in the SearchHowto
Most lists are unmoderated and will accept a submission from an address which is not subscribed.
Read first the official code of conduct. These points should be born in mind:
- Help is provided voluntarily. However dissatisfied a questioner is with an answer, anger or rudeness is inappropriate.
Please post only in plain text. Do not submit HTML, h4x0r or sp34k.
- Please do not use offensive language - these lists go out over radio and language rules for radio are not the same as local laws.
Avoid sending large attachments. Consider using paste.debian.net and including a link in your post.
- Do not flame or troll.
Respond in Interleaved style. Unnecessary quotes should be trimmed and a question should precede an answer.
- Aim for standard grammar and spelling.
- Set linewrap to 65-78 characters. 72 is a popular setting.
Flow quoted text if possible. "qv}" in vim.
Use standard and conventional abbreviations in the Subject field.
Use the standard prefix characters '> ' or '>'. Other notations can interfere with quoting or wrapping.
- Attribute quotes accurately.
Use a concise and descriptive subject line. When the sender has no clue where the problem is hidden extra care should be taken in choosing the subject. A subject such as "help" is non-specific and likely to be ignored. Avoid redundant information as in "I need help setting up X with Debian GNU/Linux". That help is needed and that this is a Debian issue is already known. ?MicroContent is maximized with the concise, descriptive "setting up X 4.1 with Matrox G550".
- Debian lists are for discussion of Debian issues. Discussion of other distributions, or other operating systems, unless related to a Debian issue, are inappropriate.
- For the benefit of others, keep a discussion on the list. Avoid making it a private conversation with the author.
- Use the 'reply' function of your mail-program. That should include a reference to the original message so that the connection of reply and question are evident.
- Trim Cc:'s. Many or most list members do not want two copies of a message.
Why all these rules? Busy people spend valuable time monitoring lists and responding to questions. The recommended practices make these activities more efficient and pleasant.
Message Threading and Replying
Typically there is at least one reply to a question in the list. The sequence comprising the original message and the replies is commonly referred to as a thread. The software which manages Debian mailing lists stores every submitted message in an archive. When an archived message is displayed by a Web browser, links to antecedent messages and replies are displayed allowing a thread to be followed through the archive. The mailing list software creates these links by referring to the "Message-ID", "In-Reply-To" and "References" fields in the message header as described in RFC 5322. Typically, when an email client is used to read a message and create a reply, it automatically takes the value from the Message-id field of the antecedent and inserts it as the value of the In-Reply-To field in the reply. Also according to RFC 5322 the client should take the complete value of the References field from the antecedent, append the Message-ID of the antecedent and insert the result as the value for References in the reply.
A thread is easily broken so that links to antecedent messages do not appear correctly in the archive. For example an email client might use only the antecedent Message-ID as the value for References.
When reading messages via the web archives, you can click the "Reply to" mailto links at the bottom of the posts to compose a new email with the correct headers. Most graphical mail clients will support these reply links. For clients that do not support these reply links, some email clients allow the user to construct these fields. mutt, for example, has the -H option. Fields To, In-Reply-To, References and Subject and the message body are placed in a file, named "draft" for example. Then "mutt -H draft" will issue the threaded reply. To illustrate, this is the head of the draft to create a reply to <20200115165147.GB3320@wren.corp>:
Web view of message being replied to:
To: debian-user@lists.debian.org Subject: Re: xdvi refresh From: ... Date: Wed, 15 Jan 2020 10:51:47 -0600 Message-id: <[🔎] 20200115165147.GB3320@wren.corp> Reply-to: debian-user@lists.debian.org In-reply-to: <[🔎] 20200115070050.GB10975@tuxteam.de> References: <[🔎] 20200114201617.vbbxu7hest5oozvl@rlharris.org> <[🔎] 20200115070050.GB10975@tuxteam.de> <message body>
plain text content of draft file:
To: debian-user@lists.debian.org In-Reply-To: <20200115165147.GB3320@wren.corp> References: <20200114201617.vbbxu7hest5oozvl@rlharris.org> <20200115070050.GB10975@tuxteam.de> <20200115165147.GB3320@wren.corp> Subject: Re: how to seamlessly play audio clip <message body>
Notable points.
The origin of the thread is the first Reference, message <20200114201617.vbbxu7hest5oozvl@rlharris.org>.
All "<" and ">" enclosing message identifiers are retained.
- All magnifying glass links are omitted.
- The In-Reply-To identifier and the last Reference identifier are identical.
PGP-based approvals
Some Debian lists (including debian-devel-announce) only allow posts which are signed by a Debian Developer key to be submitted. This system does not allow unsigned content at the beginning of a PGP/MIME message, which means that messages sent by Thunderbird/Icedove will be blocked (see https://sourceforge.net/p/enigmail/bugs/349/ for more information about this problem).
How to send plain text emails to the list
Alpine/Pine
No configuration necessary.
AIM Mail
To set plain text as default - (before composing)
Navigation Bar => Settings => Authoring - unselect Use Rich Text / HTML Editing => Save => OK.
AOL Mail
See instructions for AIM Mail.
(Apple) Mail
To set plain text as default
Toolbar => Mail => Preferences... => Composing => Message Format (Format) select Plain text.
To set plain text for a single message - (before hitting Send)
Toolbar => Format => Make Plain text.
ATmail Webmail
ATmail doesn't support plain text. Please don't use this email client to post to the list.
Claws
No configuration necessary.
Eudora
To set plain text as default
Toolbar => Tools => Options... => Styled Text select Ask me every time for When sending mail with styled text (HTML).
Don't insert images or use the Formatting tools or message will cease to be plain text. If that happens you'll be prompted to select the format when you select Send. Choose Plain text. (Click OK if prompted).
Evolution
To set plain text for a single message - (while composing your post)
Toolbar => Format - unselect HTML.
Gmail
To set plain text for a single message - (while composing your post)
More Options.. (the arrow down symbol - bottom-right of the Compose windows, beside the Rubbish Bin icon) => Plain text mode from the pop-up list.
FastMail.FM
To set plain text for a single message - (while composing your post)
Formatting Toolbar => Edit as Text.
If using the Advanced Compose mode
Formatting Toolbar => HTML(near headers) => Edit as Text.
Kmail
Default is plain text. To disable HTML
Toobar => Options => untick Formatting (HTML).
Mutt
No configuration necessary.
Oberon
No configuration necessary. Maintain a thread by following the instructions above.
Outlook
To set plain text for a single message - (before hitting composing)
Toolbar => Actions => New Mail Message Using => Plain text.
Outlook Express
To set plain text as default
Toolbar => Tools => Options... => Send => Mail Sending Format select Plain text => OK.
To set plain text for a single message - (before hitting Send)
Toolbar => Format => Plain text.
Icedove/Thunderbird
To set plain text as default
Toolbar => Edit => Account Settings... => Composition & Addressing unselect Compose messages in HTML => OK.
To set plain text for a single message - (while composing your post)
Toolbar => Options => Format => Select Plain Text Only.
Pegasus
To set plain text for a single message - (while composing your post)
Ctrl+F8 - unselect Rich text.
Windows Live Hotmail
To set plain text for a single message - (while composing your post)
Toolbar => Rich Text => Plain Text => OK.
Windows Mail
See instructions for Outlook Express.
Yahoo! Mail
To set plain text for a single message - (while composing your post)
Select Plain text (near end of Subject line) => OK.
Yahoo! Classic To set plain text for a single message - (before composing your post)
Navigation Bar => Options => Management => General Preferences => Composing E-mails - select Compose messages as plain text => Save.