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