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