Annotation of www/mail.html, Revision 1.156
1.57 horacio 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.147 tj 4: <title>OpenBSD: Mailing Lists</title>
1.57 horacio 5: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.139 tj 6: <meta name= "copyright" content= "This document copyright 1996-2016
7: by OpenBSD.">
1.144 tb 8: <meta name="viewport" content="width=device-width, initial-scale=1">
9: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.148 tb 10: <link rel="canonical" href="https://www.openbsd.org/mail.html">
1.151 tb 11: <style type="text/css">
12: h2 { color: #e00000; }
13: </style>
1.1 deraadt 14: </head>
15:
1.76 david 16: <body bgcolor="#ffffff" text="#000000">
1.1 deraadt 17:
1.144 tb 18: <h2>
1.145 tb 19: <a href="index.html">
1.144 tb 20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">Mailing Lists</font>
22: </h2>
1.57 horacio 23: <hr>
1.144 tb 24: <p>
1.7 downsj 25:
1.66 nick 26: Mailing lists are an important means of communication among users and
1.139 tj 27: developers of OpenBSD.
28: With the exception of <b>announce</b>, the lists are not moderated.
29: We deliberately restrict the number of different mailing lists.
30: This helps reduce the amount of cross-posting and makes sure that
31: the information gets distributed to a wide audience.
32:
1.151 tb 33: <h2 id="Netiquette">Netiquette</h2>
1.66 nick 34:
1.28 louis 35: Be considerate of other subscribers on the mailing lists.
1.139 tj 36:
1.28 louis 37: <dl>
1.66 nick 38: <dt><b>Plain text, 72 characters per line</b>
39: <dd>Many subscribers and developers read their mail on text-based mailers
1.151 tb 40: like <a href="http://man.openbsd.org/mail">mail(1)</a>,
1.139 tj 41: emacs or mutt, and they often find HTML-formatted messages (or lines that
42: stretch beyond 72 characters) unreadable.
43: Most OpenBSD mailing lists strip messages of MIME content before sending
44: them out to the rest of the list.
45: If you don't use plain text, your messages will be reformatted or, if they
46: cannot be reformatted, summarily rejected.
47: The only mailing lists that allow file attachments are the <b>bugs</b>,
48: <b>ports</b> and <b>tech</b> lists.
49: They will be removed from messages on the others.
1.66 nick 50:
51: <dt><b>Do your homework before you post</b>
1.139 tj 52: <dd>If you have an installation question, make sure that you have read
1.146 tj 53: the relevant documents, such as the <tt>INSTALL.*</tt> text files in the
1.139 tj 54: installation directories, the <a href="faq/index.html">FAQ</a> and the
55: relevant man pages (start with
1.151 tb 56: <a href= "http://man.openbsd.org/afterboot">afterboot(8)</a>).
1.139 tj 57: Also check the mailing list <a href="#Archives">archives</a>.
1.66 nick 58: We want to help, but we wouldn't want to deprive you of a valuable
59: learning experience, and no one wants to see the same question on the
60: lists for the fifth time in a month.
61:
62: <dt><b>Include a useful Subject line</b>
1.45 millert 63: <dd>Messages with an empty Subject will get bounced to the list manager and
1.139 tj 64: will take longer to show up.
65: Including a relevant Subject in the message
1.45 millert 66: will ensure that more people actually read what you've written.
67: Also, avoid Subject lines with excessive capitalization.
1.96 jmc 68: "Help!" or "I can't get it to work!" are not useful subject lines.
1.139 tj 69: Do not change the subject line while on the same topic.
70: YOU may know what it is regarding, the rest of us who get several hundred
71: messages a day will have no idea.
1.66 nick 72:
73: <dt><b>Trim your signature</b>
74: <dd>Keep the signature lines at the bottom of your mail to a reasonable
1.139 tj 75: length.
76: PGP signatures and those automatic address cards are merely annoying and
77: are stripped out.
78: Legal disclaimers and advisories are also very annoying, and inappropriate
79: for public mailing lists.
1.66 nick 80:
81: <dt><b>Stay on topic</b>
1.28 louis 82: <dd>Please keep the subject of the post relevant to users of OpenBSD.
1.66 nick 83:
84: <dt><b>Include important information</b>
85: <dd>Don't waste everyone's time with a hopelessly incomplete question.
86: No one other than you has the information needed to resolve your
1.139 tj 87: problem, it is better to provide more information than needed than not
88: enough detail.
89: All questions should include at least the <a href="faq/faq5.html#Flavors">
90: version</a> of OpenBSD.
91: Any hardware-related questions should mention the platform (i386, amd64,
92: etc.) and provide a full
1.151 tb 93: <a href="http://man.openbsd.org/dmesg">dmesg(8)</a>.
1.66 nick 94: Hardware model numbers, unfortunately, don't indicate much about the
95: actual content of a particular machine or accessory, and are useless to
96: anyone who doesn't have that exact machine sitting where they can easily
1.139 tj 97: recognize it.
98: The dmesg(8) output tells us exactly what is IN your machine, not what
99: stickers are on the outside.
1.66 nick 100:
101: <dt><b>Respect differences in opinion and philosophy</b>
1.139 tj 102: <dd>Intelligent people may look at the same set of facts and come to very
103: different conclusions.
104: Repeating the same points that didn't convince someone previously rarely
105: changes their mind, and irritates all the other readers.
1.66 nick 106:
107: <dt><b>Do not cross-post or repeat post</b>
108: <dd>Posting the same message to multiple lists and/or multiple times
1.139 tj 109: does not increase the likelihood of getting a useful response, and is
110: likely to irritate the people you want to help you.
111: If you didn't get a satisfactory response the first time you posted to an
112: appropriate list, it is usually because you provided insufficient or unclear
113: information.
1.66 nick 114: Don't simply repost the same message.
1.28 louis 115: </dl>
1.1 deraadt 116:
1.151 tb 117: <h2 id="spam">Spam</h2>
1.139 tj 118:
1.151 tb 119: The OpenBSD lists use <a href="http://man.openbsd.org/spamd">spamd(8)</a>
120: and <a href="http://www.spamassassin.org">SpamAssassin</a> to keep down the
121: spam volume, but things do sneak through from time to time -- deal with it.
1.139 tj 122: In addition, the list server also has regex-based rules to reject emails
1.87 millert 123: based on some common spam and virus telltales.
124: If you get spam through one of the OpenBSD mailing lists, you don't need to
1.139 tj 125: send a copy to the list owner -- chances are he's already seen it.
1.87 millert 126: Also, please do <b>not</b> submit spam received through the
1.139 tj 127: mailing lists to <a href="http://spamcop.net">spamcop</a>,
1.87 millert 128: as this will result in the list server being added to their RBL.
1.139 tj 129: Complaining about and commenting upon spam on the list proper is
130: counter-productive, as it generates more traffic than the spam itself.
131:
1.87 millert 132: <p>
1.139 tj 133: Note that if you are sending mail from a dynamic IP address, you
1.77 millert 134: will probably <b>not</b> be able to post to the mailing lists.
1.136 tb 135: In this case, you should use a <em>smart host</em> mail configuration
1.139 tj 136: that utilizes your ISP's mail server.
137: See the examples in
1.151 tb 138: <a href="http://man.openbsd.org/smtpd.conf">smtpd.conf(5)</a> for how
139: to do this.
1.66 nick 140:
1.151 tb 141: <h2 id="Lists">General interest lists</h2>
1.33 millert 142:
1.66 nick 143: These lists are of interest to most users of OpenBSD.
1.1 deraadt 144: <dl>
1.66 nick 145:
146: <dt><b>misc</b>
1.139 tj 147: <dd>User questions and answers, general questions.
148: This is the most active list.
149: Please, <a href="faq/index.html">read the FAQ</a> and the installation
150: documents, and see <a href="report.html">how to report a problem</a>
151: before posting.
1.66 nick 152:
153: <dt><b>advocacy</b>
1.139 tj 154: <dd>Promoting the use of OpenBSD.
1.66 nick 155:
156: <dt><b>announce</b>
1.139 tj 157: <dd>Important announcements.
158: This low volume list is excellent for people who just want occasional news
1.154 tj 159: about the project.
1.66 nick 160:
161: <dt><b>ports</b>
1.156 ! tj 162: <dd>Discussions about using and contributing to the ports tree.
1.66 nick 163:
1.127 tedu 164: </dl>
165:
1.151 tb 166: <h3>Developer lists</h3>
1.139 tj 167:
168: These lists are for technical discussions of aspects of OpenBSD.
169: They are NOT for beginning or average users, they are not for problem
170: reporting (unless you are including a good fix) and they are not for
171: installation problems.
172: If you have any question about if a message should be posted to any of
173: these lists, it probably should not.
174: Use <b>misc</b> instead.
175: Again, <b>do not cross post to multiple lists</b>.
1.66 nick 176:
177: <dl>
178: <dt><b>bugs</b>
1.57 horacio 179: <dd><a href="report.html">Bug reports</a> as sent in via
1.151 tb 180: <a href="http://man.openbsd.org/sendbug">sendbug(1)</a>
1.139 tj 181: and follow-up discussions.
1.66 nick 182:
183: <dt><b>tech</b>
184: <dd>Discussion of technical topics for OpenBSD developers and advanced
1.139 tj 185: users.
186: This is <b>not</b> a "tech support" forum; do not use it as such.
1.86 nick 187: OpenBSD developers will often make patches to implement new features
188: and other important changes available for public testing through this
189: list.
1.134 doug 190:
191: <dt><b>libressl</b>
192: <dd>Technical discussion about native and portable LibreSSL.
193: Users of LibreSSL on any operating system are welcome to participate.
194: Patches for the native LibreSSL should be sent to this list and use
195: OpenBSD's CVS tree or a git mirror of it.
196: Patches for the portable bits should be pull requests on
197: <a href="https://github.com/libressl-portable">github</a>.
198: </dl>
199:
1.151 tb 200: <h3>Security lists</h3>
1.139 tj 201:
1.134 doug 202: These private lists are for reporting vulnerabilities to the OpenBSD team.
203:
204: <dl>
205: <dt><b>libressl-security</b>
206: <dd>Report vulnerabilities related to OpenSSL or LibreSSL to the core
207: LibreSSL team.
1.151 tb 208: <dt><b>security</b>
209: <dd>Report vulnerabilities related to OpenBSD.
1.123 deraadt 210: </dl>
1.66 nick 211:
1.151 tb 212: <h3>Platform-specific lists</h3>
1.139 tj 213:
1.66 nick 214: These lists are focused on user issues and development on individual
215: platforms.
1.139 tj 216:
1.66 nick 217: <dl>
218: <dt><b>alpha</b>
219: <dd>OpenBSD/alpha port
220:
1.75 miod 221: <dt><b>arm</b>
1.155 tj 222: <dd>OpenBSD/armv7 port and other ARM porting efforts
1.75 miod 223:
1.66 nick 224: <dt><b>hppa</b>
225: <dd>OpenBSD/hppa port
226:
1.98 miod 227: <dt><b>m88k</b>
1.144 tb 228: <dd>OpenBSD/luna88k port
1.98 miod 229:
1.66 nick 230: <dt><b>ppc</b>
1.81 nick 231: <dd>OpenBSD/macppc and other PowerPC porting efforts
1.66 nick 232:
1.109 jsing 233: <dt><b>sgi</b>
234: <dd>OpenBSD/sgi port
235:
1.66 nick 236: <dt><b>sparc</b>
1.150 tj 237: <dd>OpenBSD/sparc64 port
1.66 nick 238: </dl>
239:
1.151 tb 240: <h3>CVS changes mailing lists</h3>
1.139 tj 241:
242: Every time a developer commits a change to the OpenBSD CVS tree, a message
243: is mailed out to all the subscribers of these lists, containing the commit
244: comments.
1.66 nick 245:
246: <dl>
247: <dt><b>source-changes</b>
1.139 tj 248: <dd>Automated mail of CVS source tree changes in the src, xenocara and www
249: repositories.
1.66 nick 250:
251: <dt><b>ports-changes</b>
1.139 tj 252: <dd>Automated mail of CVS source tree changes in the ports repository.
1.1 deraadt 253: </dl>
254:
1.151 tb 255: <h2 id="Mirrors">Mirror-related lists</h2>
1.139 tj 256:
1.116 sthen 257: Announcements and discussion relating to mirrors of OpenBSD.
258:
259: <dl>
260: <dt><b>mirrors-announce</b>
261: <dd>This is a moderated list used solely for important announcements
262: to operators of OpenBSD mirrors.
263:
264: <dt><b>mirrors-discuss</b>
265: <dd>Discussion relating to OpenBSD mirrors.
266: </dl>
267:
1.151 tb 268: <h2 id="Majordomo">Managing list membership via Majordomo</h2>
1.139 tj 269:
1.57 horacio 270: If you want to be sent a complete list with all mailing lists available
1.139 tj 271: at openbsd.org, send the command <tt>lists</tt> in the body of
1.57 horacio 272: a message to
273: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>.
1.28 louis 274:
275: <p>
1.66 nick 276: To subscribe to a given list, send mail to
277: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
1.139 tj 278: with a message body of "subscribe <tt>mailing-list-name</tt>" (where
279: <tt>mailing-list-name</tt> is the name of your preferred list).
1.66 nick 280:
281: <p>
1.139 tj 282: For further assistance, send a message body of "help" to
283: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
284: and you will receive a reply outlining all your options.
1.151 tb 285: Your domain <b>must</b> resolve properly or the mail will not go through!
1.1 deraadt 286:
1.151 tb 287: <h2 id="Web">Managing list membership via the web</h2>
1.66 nick 288:
289: Your membership to the OpenBSD mailing lists can also be managed via
1.139 tj 290: a web interface at <a href="https://lists.openbsd.org">lists.openbsd.org</a>.
1.66 nick 291:
1.151 tb 292: <h2 id="Tricks">Mailing list tricks</h2>
1.66 nick 293:
294: There are a number of very useful options that can be selected, either
1.139 tj 295: by the <a href="https://lists.openbsd.org">web interface</a> or through
296: <a href="mailto:majordomo@openbsd.org">Majordomo</a>.
297: You can change your email address without having to unsubscribe and
298: resubscribe, temporarily disable your message delivery for a few days
299: while you go on vacation and much more.
300: The user is invited to spend some time reading through the options, available
301: by sending <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
302: containing "help" as the body text, or through the "Help" tab of the
303: <a href="https://lists.openbsd.org">web interface</a>.
1.66 nick 304:
305: <p>
306: As an example, if you were going on vacation for two weeks and didn't
1.139 tj 307: wish to come back to several thousand emails, you can disable message
308: delivery by the mail server for the time of your vacation and have
1.70 nick 309: delivery automatically resume upon your scheduled return using the command:
1.139 tj 310:
311: <blockquote><pre>
312: set ALL nomail-14d
313: </pre></blockquote>
314:
1.141 tj 315: This will suspend your subscription to all mailing lists for 14 days
1.139 tj 316: (<tt>-14d</tt>).
317: More details and options can be seen on the
318: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">
319: Majordomo overview page</a>.
1.68 nick 320:
1.139 tj 321: <h3>Digests</h3>
1.66 nick 322:
323: If you would prefer to see a "digest" (a consolidated listing of all the
324: messages for a time period), rather than getting messages individually
325: in "real-time" form, you can use the commands:
1.139 tj 326:
327: <blockquote><pre>
328: set misc digest-daily
329: set source-changes digest-weekly
330: </pre></blockquote>
331:
1.66 nick 332: for daily digests of the <b>misc</b> list, and weekly digests of the
1.139 tj 333: <b>source-changes</b> list.
334: Yes, multiple commands can be placed in one Majordomo email.
1.66 nick 335:
1.151 tb 336: <h2 id="OtherLists">Other Mailing Lists</h2>
1.66 nick 337:
1.151 tb 338: The fine folks at <a href="http://www.squish.net/openbsd/">squish.net</a> run
339: mailing lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
1.139 tj 340: and <b>ports-changes</b> mailing list.
1.151 tb 341: This is handy for those who don't like the typically high volume of these lists.
1.42 millert 342:
343: <p>
1.139 tj 344: The insomniac at <a href="http://www.benzedrine.ch/mailinglist.html">
345: benzedrine.ch</a> maintains the <b>pf</b> list for people using the
346: OpenBSD packet filter.
347: To subscribe, send an email with the message body of "subscribe" to
348: <a href="mailto:pf-request@benzedrine.ch">pf-request@benzedrine.ch</a>.
1.61 dhartmei 349:
1.151 tb 350: <h2 id="nonEnglish">Non-English lists</h2>
1.28 louis 351:
1.66 nick 352: Several non-English speaking mailing lists related to OpenBSD are available
1.139 tj 353: separately.
354: Here is a list of the currently known mailing lists:
1.59 miod 355:
356: <!--
357: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
358: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
359: -->
360:
361: <p>
1.114 syuu 362: Japanese:
1.139 tj 363: <b>openbsd-japan@googlegroups.com</b>
364: <br>To subscribe, visit the URL at:
1.114 syuu 365: <a href="http://groups.google.com/group/openbsd-japan">
366: http://groups.google.com/group/openbsd-japan</a>
367:
1.131 sthen 368: <p>
1.139 tj 369: Spanish:
370: <b>OpenBSD-Mexico@googlegroups.com</b>
1.59 miod 371: <br>To subscribe, visit the URL at:
1.91 grunk 372: <a href="http://groups.google.com.mx/group/OpenBSD-Mexico">
373: http://groups.google.com.mx/group/OpenBSD-Mexico</a>
1.49 horacio 374:
375: <p>
1.101 steven 376: Ukrainian:
377: <b>openbsd@uaoug.org.ua</b>
1.139 tj 378: <br>To subscribe, send an empty message to
1.101 steven 379: <a href="mailto:openbsd+subscribe@uaoug.org.ua">
380: openbsd+subscribe@uaoug.org.ua</a>
381:
1.151 tb 382: <h2 id="Archives">Mailing list archives</h2>
1.139 tj 383:
1.66 nick 384: These mailing list archives are not managed by the OpenBSD project.
385:
1.19 deraadt 386: <ul>
1.149 krw 387: <li>HTTP: <a href="https://marc.info">MARC</a>
388: <li>NNTP: <a href="nntp://news.gmane.org/">Gmane</a>
1.19 deraadt 389: </ul>
1.1 deraadt 390:
1.97 nick 391: <p>
1.139 tj 392: General search engines also prove very effective at finding answers to
393: OpenBSD questions.
1.97 nick 394:
1.103 reyk 395: <p>
1.1 deraadt 396: </body>
397: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to mail.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www