Annotation of www/mail.html, Revision 1.86
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.22 wvdputte 5: <link rev="made" href= "mailto:www@openbsd.org">
1.57 horacio 6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.22 wvdputte 7: <meta name= "resource-type" content= "document">
1.28 louis 8: <meta name= "description" content= "the OpenBSD mailing list page">
1.22 wvdputte 9: <meta name= "keywords" content= "openbsd,mail">
10: <meta name= "distribution" content= "global">
1.74 jose 11: <meta name= "copyright" content= "This document copyright 1996-2004 by OpenBSD.">
1.1 deraadt 12: </head>
13:
1.76 david 14: <body bgcolor="#ffffff" text="#000000">
1.1 deraadt 15:
1.58 jsyn 16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.25 deraadt 17: <p>
1.66 nick 18: <h1><font color="#e00000">Mailing Lists</font></h1>
1.57 horacio 19: <hr>
1.7 downsj 20:
1.66 nick 21: Mailing lists are an important means of communication among users and
22: developers of OpenBSD. With the exceptions of <b>announce</b> and
1.70 nick 23: <b>security-announce</b>, the lists are not moderated. We deliberately
1.66 nick 24: restrict the number of different mailing lists.
25: This helps reduce the amount of cross-posting and makes sure that the
26: information gets distributed to a wide audience.
27:
1.28 louis 28: <p>
1.66 nick 29: <a name="Netiquette"></a>
30: <h2><font color="#e00000">Netiquette</font></h2>
1.28 louis 31: <p>
32: Be considerate of other subscribers on the mailing lists.
33: <dl>
1.66 nick 34: <dt><b>Plain text, 72 characters per line</b>
35: <dd>Many subscribers and developers read their mail on text-based mailers
36: (mail(1), emacs, Mutt)
1.45 millert 37: and they find HTML-formatted messages, or lines that stretch beyond 72
38: characters often unreadable.
39: Most OpenBSD mailing lists strip messages of MIME content before
40: sending them out to the rest of the list.
41: If you don't use plain text your messages will be reformatted or,
42: if they cannot be reformatted, summarily rejected.
1.66 nick 43: The only mailing list that allows attachments is the <b>ports</b> list,
1.45 millert 44: they will be removed from messages on the other mailing lists.
1.66 nick 45:
46: <dt><b>Do your homework before you post</b>
1.28 louis 47: <dd>If you have an installation question, make sure that you have read the relevant
48: documents such as the INSTALL.* text files in the FTP installation directories, the
1.57 horacio 49: <a href="faq/index.html">FAQ</a> and the relevant man pages (start with
1.66 nick 50: <a href= "http://www.openbsd.org/cgi-bin/man.cgi?query=afterboot&sektion=8">afterboot(8)</a>),
51: and check the mailing list <a href="#Archives">archives</a>.
52: We want to help, but we wouldn't want to deprive you of a valuable
53: learning experience, and no one wants to see the same question on the
54: lists for the fifth time in a month.
55:
56: <dt><b>Include a useful Subject line</b>
1.45 millert 57: <dd>Messages with an empty Subject will get bounced to the list manager and
1.57 horacio 58: so they will take longer to show up. Including a relevant Subject in the message
1.45 millert 59: will ensure that more people actually read what you've written.
60: Also, avoid Subject lines with excessive capitalization.
1.66 nick 61: "Help!" or "I can't get it to work!" are not a useful subject lines.
62: Do not change the subject line while on the same topic. YOU may know
63: what it is regarding, the rest of us who get several hundred messages a
64: day will have no idea.
65:
66: <dt><b>Trim your signature</b>
67: <dd>Keep the signature lines at the bottom of your mail to a reasonable
68: length. PGP signatures, and those automatic address cards are merely
69: annoying and are stripped out. Legal disclaimers and advisories are
70: very annoying, and inappropriate to public mailing lists.
71:
72: <dt><b>Stay on topic</b>
1.28 louis 73: <dd>Please keep the subject of the post relevant to users of OpenBSD.
1.66 nick 74:
75: <dt><b>Include important information</b>
76: <dd>Don't waste everyone's time with a hopelessly incomplete question.
77: No one other than you has the information needed to resolve your
78: problem, it is better to provide more information than needed than one
79: detail too little. Any question should include at least the
80: <a href="faq/faq5.html#Flavors">version</a> of OpenBSD (i.e.,
81: "3.2-stable", "3.3-current as of July 20, 2003"). Any hardware related
1.69 nick 82: questions should mention the platform (i.e., sparc,
1.66 nick 83: alpha, etc.), and provide a full
1.70 nick 84: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dmesg&sektion=8">dmesg(8)</a>.
1.66 nick 85: Hardware model numbers, unfortunately, don't indicate much about the
86: actual content of a particular machine or accessory, and are useless to
87: anyone who doesn't have that exact machine sitting where they can easily
88: recognize it. The dmesg(8) tells us exactly what is IN your machine,
89: not what stickers are on the outside.
90:
91: <dt><b>Respect differences in opinion and philosophy</b>
92: <dd>Intelligent people may look at the same set of facts and come to
93: very different conclusions. Repeating the same points that didn't
94: convince someone previously rarely changes their mind and irritates all
95: the other readers.
96:
97: <dt><b>Do not cross-post or repeat post</b>
98: <dd>Posting the same message to multiple lists and/or multiple times
99: does not increase the likelihood of getting a useful response, but is
100: likely to irritate the people you want to help you. If you didn't get a
101: satisfactory response the first time you posted to an appropriate list,
102: it is usually because you provided insufficient or unclear information.
103: Don't simply repost the same message.
104:
1.28 louis 105: </dl>
1.1 deraadt 106:
1.33 millert 107: <p>
1.66 nick 108: <a name="spam"></a>
109: <h2><font color="#e00000">Spam</font></h2>
1.33 millert 110: <p>
1.66 nick 111: The OpenBSD mailing lists use
1.78 millert 112: <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 113: <a href="http://www.spamassassin.org">SpamAssassin</a> to keep down the
1.67 nick 114: spam volume but sometimes things sneak through.
1.66 nick 115: In addition, the list server also has regex-based rules to reject
116: based on some common spam telltales.
117: If you get spam through one of the OpenBSD mailing lists,
1.33 millert 118: you might want to submit it to <a href="http://spamcop.net">spamcop</a>.
119: In general, you don't have to send a copy to the list owner--chances
1.42 millert 120: are he's already seen it. Please note that complaining about
1.66 nick 121: and commenting upon
1.42 millert 122: spam on the list proper is counter-productive as it generates more
1.66 nick 123: traffic than the spam itself.
1.77 millert 124: Note that if you are sending mail from a dynamic IP address you
125: will probably <b>not</b> be able to post to the mailing lists.
126: In this case you should use a <em>smart host</em> sendmail configuration
127: that utilizes your ISP's mail server. See the comments in
128: <tt>/usr/share/sendmail/cf/openbsd-proto.mc</tt> for how to do this.
1.66 nick 129:
130:
131: <a name="Lists"></a>
132: <h2><font color="#e00000">The Mailing Lists</font></h2>
1.33 millert 133:
1.66 nick 134: <h3>General Interest Lists</h3>
135: These lists are of interest to most users of OpenBSD.
1.1 deraadt 136: <dl>
1.66 nick 137:
138: <dt><b>misc</b>
139: <dd>User questions and answers, general questions. This is the most
140: active list. Please, <a href="faq/index.html">read the FAQ</a> and the
141: installation documents, and see <a href="report.html">How to report a
142: Problem</a> before posting.
143:
144: <dt><b>advocacy</b>
145: <dd>Promoting the use of OpenBSD. Non-technical discussions in
146: <i>misc</i> often get shunted here.
147:
148: <dt><b>announce</b>
149: <dd>Important announcements. This low volume list is excellent for
150: people who just want occasional news about the project.
151:
152: <dt><b>security-announce</b>
1.31 millert 153: <dd>Security announcements. This low volume list receives OpenBSD
154: security advisories and pointers to security patches as they become
155: available.
1.66 nick 156:
157: <dt><b>ports</b>
158: <dd>Discussions about using and contributing to the 'ports' source tree.
159:
1.80 pvalchev 160: <dt><b>ports-security</b>
161: <dd>Security announcements for ports and packages. This low volume
162: list receives OpenBSD security advisories concerning the ports tree
163: and packages with more information about the vulnerabilities and
164: patches.
165:
1.66 nick 166: <dt><b>www</b>
167: <dd>Discussion of the OpenBSD Website.</dd>
168: </dl>
169:
170: <h3>Developer's Lists</h3>
171: These lists are for technical discussions of aspects of OpenBSD. They
172: 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. If you have any question about if a message
175: should be posted to any of these lists, almost invariably, it should not
176: be. Use <b>misc</b>, above, instead. <b>Please</b> do not cross post
177: to multiple lists.
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.66 nick 182: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1">sendbug(1)</a>
183: and follow-up discussions. If you wish to have your message logged
184: by the <a href="query-pr.html">GNATS</a> bug tracking system, reply
185: to <i>gnats@openbsd.org</i>, gnats@ will then forward to <i>bugs@</i>.
186:
187: <dt><b>ipv6</b>
188: <dd>Discussion of IPv6 and IPsec in OpenBSD
189:
190: <dt><b>ports-bugs</b>
191: <dd>Discussion regarding bugs within the OpenBSD ports tree
192:
193: <dt><b>smp</b>
194: <dd>Development of <a href="faq/faq8.html#SMP">multiprocessor</a>
195: support in OpenBSD. Offers to "help test" and complaints about it not
196: being completed yet are not appreciated. Code, however, is welcome.
197:
198: <dt><b>tech</b>
199: <dd>Discussion of technical topics for OpenBSD developers and advanced
200: users. This is <b>not</b> a "tech support" forum, do not use it as
201: such.
1.86 ! nick 202: OpenBSD developers will often make patches to implement new features
! 203: and other important changes available for public testing through this
! 204: list.
1.66 nick 205:
206: <dt><b>x11</b>
207: <dd>Discussion of X11 development within OpenBSD
208: </dl>
209:
210: <h3>Platform Specific Lists</h3>
211: These lists are focused on user issues and development on individual
212: platforms.
213: <dl>
214: <dt><b>alpha</b>
215: <dd>OpenBSD/alpha port
216:
1.75 miod 217: <dt><b>arm</b>
218: <dd>OpenBSD/cats port and other ARM porting efforts
219:
1.66 nick 220: <dt><b>hppa</b>
221: <dd>OpenBSD/hppa port
222:
223: <dt><b>mac68k</b>
224: <dd>OpenBSD/mac68k port (not PowerPC Macintosh systems)
225:
226: <dt><b>ppc</b>
1.81 nick 227: <dd>OpenBSD/macppc and other PowerPC porting efforts
1.66 nick 228:
229: <dt><b>sparc</b>
230: <dd>OpenBSD/sparc and OpenBSD/sparc64 ports
231:
232: <dt><b>vax</b>
233: <dd>OpenBSD/vax port
234: </dl>
235:
236: <h3>CVS Changes Mailing Lists</h3>
237: Every time a developer commits a change to the OpenBSD
1.69 nick 238: <a href="why-cvs.html">CVS tree</a>, a message is mailed out to all the subscribers
1.66 nick 239: of these lists, containing the commit comments.
240:
241: <dl>
242: <dt><b>source-changes</b>
243: <dd>Automated mail-out of CVS source tree changes in all the repositories
244: other than <i>ports</i>.
245:
246: <dt><b>ports-changes</b>
247: <dd>Automated mail-out of ports-specific CVS source tree changes.
1.1 deraadt 248: </dl>
249:
1.66 nick 250: <h3>CTM Lists</h3>
251: A number of mailing lists are used by the <a href="ctm.html">CTM</a>,
252: an alternative source change distribution system. See the
253: <a href="ctm.html">CTM page</a> for details.
254:
255:
256: <a name="Majordomo"></a>
257: <h2><font color="#e00000">Managing Mailing List Membership via
258: Majordomo</font></h2>
1.1 deraadt 259: <p>
1.57 horacio 260: If you want to be sent a complete list with all mailing lists available
1.66 nick 261: at openbsd.org, send the command "<tt>lists</tt>" on the body of
1.57 horacio 262: a message to
263: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>.
1.28 louis 264:
265: <p>
1.66 nick 266: To subscribe to a given list, send mail to
267: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
268: with a message body of "<b>subscribe mailing-list-name</b>".
269:
270: <p>
271: For further assistance, send a message body of "<b>help</b>"
1.57 horacio 272: to <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
1.13 deraadt 273: and you will receive a reply outlining all your options. Your domain
1.66 nick 274: <b>MUST</b> resolve properly or the mail will not go through!
1.1 deraadt 275:
1.66 nick 276:
277: <a name="Web"></a>
278: <h2><font color="#e00000">Managing Mailing List Membership via
279: Web</font></h2>
280: Your membership to the OpenBSD mailing lists can also be managed via
281: a web interface at:
282: <blockquote>
283: <a href="http://lists.openbsd.org/">http://lists.openbsd.org/</a>
284: </blockquote>
285:
286:
287: <a name="Tricks"></a>
288: <h2><font color="#e00000">Mailing Lists Tricks</font></h2>
289: There are a number of very useful options that can be selected, either
290: by the <a href="http://lists.openbsd.org">web interface</a> or through
291: <a href="mailto:majordomo@openbsd.org">Majordomo</a>. You can change
292: your email address without having to unsubscribe and resubscribe, you
1.69 nick 293: can temporarily disable your message delivery for a few days while you go on
1.66 nick 294: vacation, and much more. The user is invited to spend some time reading
295: through the options, available by sending
296: <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
297: containing "<tt>help</tt>" as the body text, or through the
298: "<tt>Help</tt>" tab of the <a href="http://lists.openbsd.org">web
299: interface</a>.
300:
301: <p>
302: As an example, if you were going on vacation for two weeks and didn't
1.69 nick 303: wish to come back to several thousand e-mails, you can disable
1.70 nick 304: message delivery by the mail server for the time of your vacation and have
305: delivery automatically resume upon your scheduled return using the command:
1.66 nick 306: <pre>
1.82 nick 307: set ALL nomail-14d
1.66 nick 308: </pre>
1.68 nick 309: This will suspend your subscription to all mail lists for 14 days
310: (<tt>-14d</tt>). More details and options can be seen on the
311: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">Majordomo
312: overview page</a>.
313:
1.66 nick 314:
315: <h3>Digests</h3>
316: If you would prefer to see a "digest" (a consolidated listing of all the
317: messages for a time period), rather than getting messages individually
318: in "real-time" form, you can use the commands:
319: <pre>
320: set misc digest-daily
321: set source-changes digest-weekly
322: </pre>
323: for daily digests of the <b>misc</b> list, and weekly digests of the
324: <b>source-changes</b> list. Yes, multiple commands can be placed in one
325: Majordomo email.
326:
327:
328: <a name="OtherLists"></a>
329: <h2><font color="#e00000">Other Mailing Lists</font></h2>
330: <p>
331: The fine folks at
332: <a href="http://www.squish.net/openbsd/">squish.net</a> run mailing
333: lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
334: and <b>ports-changes</b> mailing list. This is handy for those who
1.72 nick 335: don't like the typically high volume of these lists.
1.42 millert 336:
337: <p>
1.39 horacio 338: The clever monkeys at <a href="http://www.monkey.org/openbsd-mobile/">monkey.org</a>
1.66 nick 339: maintain the <b>openbsd-mobile</b> list for people using OpenBSD
1.29 louis 340: on mobile and laptop computers. To subscribe:
341: <br>
342: echo subscribe | mail openbsd-mobile-request@monkey.org
343:
1.50 jufi 344: <p>
1.61 dhartmei 345: The insomniac at <a href="http://www.benzedrine.cx/pf/">benzedrine.cx</a>
1.66 nick 346: maintains the <b>pf</b> list for people using the OpenBSD
1.61 dhartmei 347: packet filter. To subscribe:
348: <br>
349: echo subscribe | mail pf-request@benzedrine.cx
350:
351: <p>
1.50 jufi 352: A mailing list for OpenBSD FTP, Web, AnonCVS and CVSup mirror maintainers is
353: available at <a href="http://rt.fm/openbsd-mirrors/">rt.fm</a>.
354:
1.66 nick 355: <a name="nonEnglish"></a>
356: <h2><font color="#e00000">Non-English Lists</font></h2>
1.28 louis 357:
1.66 nick 358: Several non-English speaking mailing lists related to OpenBSD are available
1.59 miod 359: separately. Here is a list of the currently known mailing lists:
360:
361: <!--
362: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
363: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
364: -->
1.63 nick 365: <!--
1.59 miod 366: <p>
367: Chinese:
1.66 nick 368: <b>openbsd@shellhung.org</b>
1.59 miod 369: <br>To subscribe, visit the URL at:
370: <a href="http://www.shellhung.org/mailman/listinfo/openbsd/">http://www.shellhung.org/mailman/listinfo/openbsd/</a>.
1.63 nick 371: -->
1.59 miod 372:
373: <p>
374: Czech:
1.66 nick 375: <b>users@openbsd.cz</b>
1.59 miod 376: <br>To subscribe, visit the URL at:
377: <a href="http://openbsd.cz/mailman/listinfo/users/">http://openbsd.cz/mailman/listinfo/users/</a>.
378:
379: <p>
1.84 otto 380: Dutch:
381: <b>openbsd@list.ii.nl</b>
382: <br>To subscribe, visit the URL at:
383: <a href="http://list.ii.nl/listinfo/openbsd">http://list.ii.nl/listinfo/openbsd</a>.
384:
385: <p>
1.71 todd 386: French:
387: <b>openbsd-france-misc@openbsd-france.org</b>
388: <br>To subscribe, visit the URL at:
389: <a href="http://www.openbsd-france.org/mailing-list.php">http://www.openbsd-france.org/mailing-list.php</a>.
390:
391: <p>
1.64 nick 392: German:
1.69 nick 393: <b>liste@openbsd.de</b>
1.64 nick 394: <br>To subscribe, please visit the URL at:
1.85 nick 395: <a href="https://www.openbsd.de/mailing_lists">https://www.openbsd.de/mailing_lists</a>.
1.64 nick 396:
397: <p>
1.59 miod 398: Greek:
1.66 nick 399: <b>openbsd@bsd.gr</b>
1.83 saad 400: <br>To subscribe, please visit the URL at:
401: <a href="http://www.bsd.gr/mailman/listinfo/openbsd/">http://www.bsd.gr/mailman/listinfo/openbsd/</a>.
1.18 deraadt 402:
403: <p>
1.59 miod 404: Italian:
1.66 nick 405: <a href="http://www.sikurezza.org/">sikurezza.org</a>, an Italian language
406: non-commercial security portal hosts <b>openbsd@sikurezza.org</b>.
1.59 miod 407: <br>To subscribe just send an empty message to <a
408: href="mailto:openbsd-subscribe@sikurezza.org">openbsd-subscribe@sikurezza.org</a>.
409:
410: <p>
411: Japanese: Please visit the URL at:
412: <a href="http://www.openbsd.ics.nara-wu.ac.jp/wakakusa">http://www.openbsd.ics.nara-wu.ac.jp/wakakus</a>
413: for more information.
414:
415: <p>
416: Polish: to subscribe, send mail to
1.55 miod 417: <a href="mailto:OpenBSD-request@bsdzine.org">OpenBSD-request@bsdzine.org</a>.
1.24 deraadt 418:
419: <p>
1.59 miod 420: Portuguese:
1.66 nick 421: <b>openbsd@neei.uevora.pt</b>
1.59 miod 422: <br>To subscribe, visit the URL at:
423: <a href="http://neei.uevora.pt/mailman/listinfo/openbsd/">http://neei.uevora.pt/mailman/listinfo/openbsd/</a>.
424:
425: <p>
1.60 miod 426: Russian:
1.66 nick 427: <b>openbsd@openbsd.ru</b>
1.47 form 428: <br>To subscribe, send mail to
429: <a href="mailto:minimalist@openbsd.ru">minimalist@openbsd.ru</a> with
1.66 nick 430: subject "<b>subscribe openbsd</b>".
1.34 form 431:
432: <p>
1.73 nick 433: Slovenian:
434: to subscribe please visit the URL at
435: <a href="http://obsd.17slon.org/mailinglist.php"
436: >http://obsd.17slon.org/mailinglist.php</a>
437:
438: <p>
1.62 fgsch 439: Spanish:
1.66 nick 440: <b>misc@openbsd.org.mx</b>, run from Mexico.
1.79 nick 441: <br>To subscribe, send mail to
442: <a href="mailto:misc-request@openbsd.org.mx?body=subscribe">misc-request@openbsd.org.mx</a>.
1.49 horacio 443:
444: <p>
1.66 nick 445: <a name="Archives"></a>
446: <h2><font color="#e00000">Mailing List Archives:</font></h2>
447: These mailing list archives are not managed by the OpenBSD project.
448: Take the time to look at more than one -- each is a little different,
449: and has different search abilities. If you don't find an answer in
450: one, check another.
451:
452: <p>
453: General search engines, such as
454: <a href="http://www.google.com">Google</a> also prove very effective at
455: finding answers to OpenBSD questions.
456:
1.19 deraadt 457: <ul>
1.57 horacio 458: <li><a href="http://www.sigmasoft.com/~openbsd/">USA</a>
1.66 nick 459: <!-- seemingly not working any longer
1.27 ericj 460: <li><a href="http://www.geocrawler.com/lists/4/OpenBSD">Geocrawler Archive</a>
1.66 nick 461: -->
1.39 horacio 462: <li><a href="http://www.monkey.org/openbsd/">The primates at monkey.org</a>
1.41 avsm 463: <li><a href="http://marc.theaimsgroup.com/">MARC</a>
1.51 heko 464: <li><a href="http://bsdsearch.com/eao/phorum/index.php?f=2">BSDSearch.com</a>
465: <li><a href="http://www.netsys.com/archives.html">@netsys.com</a>
1.57 horacio 466: <li>Neohapsis has a
467: <a href="http://archives.neohapsis.com/archives/openbsd/">mixed archive
468: for tech@, misc@ and ports@</a> and a
469: <a href="http://archives.neohapsis.com/archives/openbsd/cvs/">mixed
470: archive for CVS commits</a>
1.19 deraadt 471: </ul>
1.1 deraadt 472:
473: <hr>
1.57 horacio 474: <a href="index.html"><img height=24 width=24 src="back.gif" border=0 alt="OpenBSD"></a>
475: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.86 ! nick 476: <br><small>$OpenBSD: mail.html,v 1.85 2004/12/08 16:28:47 nick Exp $</small>
1.1 deraadt 477:
478: </body>
479: </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