Annotation of www/mail.html, Revision 1.157
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.157 ! tj 114: If you believe a diff you sent was overlooked, requesting follow-up with
! 115: a "ping" email is fine once a week or so.
1.28 louis 116: </dl>
1.1 deraadt 117:
1.151 tb 118: <h2 id="spam">Spam</h2>
1.139 tj 119:
1.151 tb 120: The OpenBSD lists use <a href="http://man.openbsd.org/spamd">spamd(8)</a>
121: and <a href="http://www.spamassassin.org">SpamAssassin</a> to keep down the
122: spam volume, but things do sneak through from time to time -- deal with it.
1.139 tj 123: In addition, the list server also has regex-based rules to reject emails
1.87 millert 124: based on some common spam and virus telltales.
125: If you get spam through one of the OpenBSD mailing lists, you don't need to
1.139 tj 126: send a copy to the list owner -- chances are he's already seen it.
1.87 millert 127: Also, please do <b>not</b> submit spam received through the
1.139 tj 128: mailing lists to <a href="http://spamcop.net">spamcop</a>,
1.87 millert 129: as this will result in the list server being added to their RBL.
1.139 tj 130: Complaining about and commenting upon spam on the list proper is
131: counter-productive, as it generates more traffic than the spam itself.
132:
1.87 millert 133: <p>
1.139 tj 134: Note that if you are sending mail from a dynamic IP address, you
1.77 millert 135: will probably <b>not</b> be able to post to the mailing lists.
1.136 tb 136: In this case, you should use a <em>smart host</em> mail configuration
1.139 tj 137: that utilizes your ISP's mail server.
138: See the examples in
1.151 tb 139: <a href="http://man.openbsd.org/smtpd.conf">smtpd.conf(5)</a> for how
140: to do this.
1.66 nick 141:
1.151 tb 142: <h2 id="Lists">General interest lists</h2>
1.33 millert 143:
1.66 nick 144: These lists are of interest to most users of OpenBSD.
1.1 deraadt 145: <dl>
1.66 nick 146:
147: <dt><b>misc</b>
1.139 tj 148: <dd>User questions and answers, general questions.
149: This is the most active list.
150: Please, <a href="faq/index.html">read the FAQ</a> and the installation
151: documents, and see <a href="report.html">how to report a problem</a>
152: before posting.
1.66 nick 153:
154: <dt><b>advocacy</b>
1.139 tj 155: <dd>Promoting the use of OpenBSD.
1.66 nick 156:
157: <dt><b>announce</b>
1.139 tj 158: <dd>Important announcements.
159: This low volume list is excellent for people who just want occasional news
1.154 tj 160: about the project.
1.66 nick 161:
162: <dt><b>ports</b>
1.156 tj 163: <dd>Discussions about using and contributing to the ports tree.
1.66 nick 164:
1.127 tedu 165: </dl>
166:
1.151 tb 167: <h3>Developer lists</h3>
1.139 tj 168:
169: These lists are for technical discussions of aspects of OpenBSD.
170: They are NOT for beginning or average users, they are not for problem
171: reporting (unless you are including a good fix) and they are not for
172: installation problems.
173: If you have any question about if a message should be posted to any of
174: these lists, it probably should not.
175: Use <b>misc</b> instead.
176: Again, <b>do not cross post to multiple lists</b>.
1.66 nick 177:
178: <dl>
179: <dt><b>bugs</b>
1.57 horacio 180: <dd><a href="report.html">Bug reports</a> as sent in via
1.151 tb 181: <a href="http://man.openbsd.org/sendbug">sendbug(1)</a>
1.139 tj 182: and follow-up discussions.
1.66 nick 183:
184: <dt><b>tech</b>
185: <dd>Discussion of technical topics for OpenBSD developers and advanced
1.139 tj 186: users.
187: This is <b>not</b> a "tech support" forum; do not use it as such.
1.86 nick 188: OpenBSD developers will often make patches to implement new features
189: and other important changes available for public testing through this
190: list.
1.134 doug 191:
192: <dt><b>libressl</b>
193: <dd>Technical discussion about native and portable LibreSSL.
194: Users of LibreSSL on any operating system are welcome to participate.
195: Patches for the native LibreSSL should be sent to this list and use
196: OpenBSD's CVS tree or a git mirror of it.
197: Patches for the portable bits should be pull requests on
198: <a href="https://github.com/libressl-portable">github</a>.
199: </dl>
200:
1.151 tb 201: <h3>Security lists</h3>
1.139 tj 202:
1.134 doug 203: These private lists are for reporting vulnerabilities to the OpenBSD team.
204:
205: <dl>
206: <dt><b>libressl-security</b>
207: <dd>Report vulnerabilities related to OpenSSL or LibreSSL to the core
208: LibreSSL team.
1.151 tb 209: <dt><b>security</b>
210: <dd>Report vulnerabilities related to OpenBSD.
1.123 deraadt 211: </dl>
1.66 nick 212:
1.151 tb 213: <h3>Platform-specific lists</h3>
1.139 tj 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.155 tj 223: <dd>OpenBSD/armv7 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>
1.150 tj 238: <dd>OpenBSD/sparc64 port
1.66 nick 239: </dl>
240:
1.151 tb 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.151 tb 256: <h2 id="Mirrors">Mirror-related lists</h2>
1.139 tj 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.151 tb 269: <h2 id="Majordomo">Managing list membership via Majordomo</h2>
1.139 tj 270:
1.57 horacio 271: If you want to be sent a complete list with all mailing lists available
1.139 tj 272: at openbsd.org, send the command <tt>lists</tt> in the body of
1.57 horacio 273: a message to
274: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>.
1.28 louis 275:
276: <p>
1.66 nick 277: To subscribe to a given list, send mail to
278: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
1.139 tj 279: with a message body of "subscribe <tt>mailing-list-name</tt>" (where
280: <tt>mailing-list-name</tt> is the name of your preferred list).
1.66 nick 281:
282: <p>
1.139 tj 283: For further assistance, send a message body of "help" to
284: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
285: and you will receive a reply outlining all your options.
1.151 tb 286: Your domain <b>must</b> resolve properly or the mail will not go through!
1.1 deraadt 287:
1.151 tb 288: <h2 id="Web">Managing list membership via the web</h2>
1.66 nick 289:
290: Your membership to the OpenBSD mailing lists can also be managed via
1.139 tj 291: a web interface at <a href="https://lists.openbsd.org">lists.openbsd.org</a>.
1.66 nick 292:
1.151 tb 293: <h2 id="Tricks">Mailing list tricks</h2>
1.66 nick 294:
295: There are a number of very useful options that can be selected, either
1.139 tj 296: by the <a href="https://lists.openbsd.org">web interface</a> or through
297: <a href="mailto:majordomo@openbsd.org">Majordomo</a>.
298: You can change your email address without having to unsubscribe and
299: resubscribe, temporarily disable your message delivery for a few days
300: while you go on vacation and much more.
301: The user is invited to spend some time reading through the options, available
302: by sending <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
303: containing "help" as the body text, or through the "Help" tab of the
304: <a href="https://lists.openbsd.org">web interface</a>.
1.66 nick 305:
306: <p>
307: As an example, if you were going on vacation for two weeks and didn't
1.139 tj 308: wish to come back to several thousand emails, you can disable message
309: delivery by the mail server for the time of your vacation and have
1.70 nick 310: delivery automatically resume upon your scheduled return using the command:
1.139 tj 311:
312: <blockquote><pre>
313: set ALL nomail-14d
314: </pre></blockquote>
315:
1.141 tj 316: This will suspend your subscription to all mailing lists for 14 days
1.139 tj 317: (<tt>-14d</tt>).
318: More details and options can be seen on the
319: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">
320: Majordomo overview page</a>.
1.68 nick 321:
1.139 tj 322: <h3>Digests</h3>
1.66 nick 323:
324: If you would prefer to see a "digest" (a consolidated listing of all the
325: messages for a time period), rather than getting messages individually
326: in "real-time" form, you can use the commands:
1.139 tj 327:
328: <blockquote><pre>
329: set misc digest-daily
330: set source-changes digest-weekly
331: </pre></blockquote>
332:
1.66 nick 333: for daily digests of the <b>misc</b> list, and weekly digests of the
1.139 tj 334: <b>source-changes</b> list.
335: Yes, multiple commands can be placed in one Majordomo email.
1.66 nick 336:
1.151 tb 337: <h2 id="OtherLists">Other Mailing Lists</h2>
1.66 nick 338:
1.151 tb 339: The fine folks at <a href="http://www.squish.net/openbsd/">squish.net</a> run
340: mailing lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
1.139 tj 341: and <b>ports-changes</b> mailing list.
1.151 tb 342: This is handy for those who don't like the typically high volume of these lists.
1.42 millert 343:
344: <p>
1.139 tj 345: The insomniac at <a href="http://www.benzedrine.ch/mailinglist.html">
346: benzedrine.ch</a> maintains the <b>pf</b> list for people using the
347: OpenBSD packet filter.
348: To subscribe, send an email with the message body of "subscribe" to
349: <a href="mailto:pf-request@benzedrine.ch">pf-request@benzedrine.ch</a>.
1.61 dhartmei 350:
1.151 tb 351: <h2 id="nonEnglish">Non-English lists</h2>
1.28 louis 352:
1.66 nick 353: Several non-English speaking mailing lists related to OpenBSD are available
1.139 tj 354: separately.
355: Here is a list of the currently known mailing lists:
1.59 miod 356:
357: <!--
358: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
359: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
360: -->
361:
362: <p>
1.114 syuu 363: Japanese:
1.139 tj 364: <b>openbsd-japan@googlegroups.com</b>
365: <br>To subscribe, visit the URL at:
1.114 syuu 366: <a href="http://groups.google.com/group/openbsd-japan">
367: http://groups.google.com/group/openbsd-japan</a>
368:
1.131 sthen 369: <p>
1.139 tj 370: Spanish:
371: <b>OpenBSD-Mexico@googlegroups.com</b>
1.59 miod 372: <br>To subscribe, visit the URL at:
1.91 grunk 373: <a href="http://groups.google.com.mx/group/OpenBSD-Mexico">
374: http://groups.google.com.mx/group/OpenBSD-Mexico</a>
1.49 horacio 375:
376: <p>
1.101 steven 377: Ukrainian:
378: <b>openbsd@uaoug.org.ua</b>
1.139 tj 379: <br>To subscribe, send an empty message to
1.101 steven 380: <a href="mailto:openbsd+subscribe@uaoug.org.ua">
381: openbsd+subscribe@uaoug.org.ua</a>
382:
1.151 tb 383: <h2 id="Archives">Mailing list archives</h2>
1.139 tj 384:
1.66 nick 385: These mailing list archives are not managed by the OpenBSD project.
386:
1.19 deraadt 387: <ul>
1.149 krw 388: <li>HTTP: <a href="https://marc.info">MARC</a>
389: <li>NNTP: <a href="nntp://news.gmane.org/">Gmane</a>
1.19 deraadt 390: </ul>
1.1 deraadt 391:
1.97 nick 392: <p>
1.139 tj 393: General search engines also prove very effective at finding answers to
394: OpenBSD questions.
1.97 nick 395:
1.103 reyk 396: <p>
1.1 deraadt 397: </body>
398: </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