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