Annotation of www/mail.html, Revision 1.68
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.66 nick 11: <meta name= "copyright" content= "This document copyright 1996-2003 by OpenBSD.">
1.1 deraadt 12: </head>
13:
1.66 nick 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
23: <b>security-anounce</b>, the lists are not moderated. We deliberately
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
82: questions should also include mentioning the platform (i.e., sparc,
83: alpha, etc.), and provide a full
84: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dmesg&sektion=8">dmesg(8)</a>).
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
112: <a href="http://www.spamassassin.org">SpamAssassin</a> to keep down the
1.67 nick 113: spam volume but sometimes things sneak through.
1.66 nick 114: In addition, the list server also has regex-based rules to reject
115: based on some common spam telltales.
116: If you get spam through one of the OpenBSD mailing lists,
1.33 millert 117: you might want to submit it to <a href="http://spamcop.net">spamcop</a>.
118: In general, you don't have to send a copy to the list owner--chances
1.42 millert 119: are he's already seen it. Please note that complaining about
1.66 nick 120: and commenting upon
1.42 millert 121: spam on the list proper is counter-productive as it generates more
1.66 nick 122: traffic than the spam itself.
123:
124:
125: <a name="Lists"></a>
126: <h2><font color="#e00000">The Mailing Lists</font></h2>
1.33 millert 127:
1.66 nick 128: <h3>General Interest Lists</h3>
129: These lists are of interest to most users of OpenBSD.
1.1 deraadt 130: <dl>
1.66 nick 131:
132: <dt><b>misc</b>
133: <dd>User questions and answers, general questions. This is the most
134: active list. Please, <a href="faq/index.html">read the FAQ</a> and the
135: installation documents, and see <a href="report.html">How to report a
136: Problem</a> before posting.
137:
138: <dt><b>advocacy</b>
139: <dd>Promoting the use of OpenBSD. Non-technical discussions in
140: <i>misc</i> often get shunted here.
141:
142: <dt><b>announce</b>
143: <dd>Important announcements. This low volume list is excellent for
144: people who just want occasional news about the project.
145:
146: <dt><b>security-announce</b>
1.31 millert 147: <dd>Security announcements. This low volume list receives OpenBSD
148: security advisories and pointers to security patches as they become
149: available.
1.66 nick 150:
151: <dt><b>ports</b>
152: <dd>Discussions about using and contributing to the 'ports' source tree.
153:
154: <dt><b>www</b>
155: <dd>Discussion of the OpenBSD Website.</dd>
156: </dl>
157:
158: <h3>Developer's Lists</h3>
159: These lists are for technical discussions of aspects of OpenBSD. They
160: are NOT for beginning or average users, they are not for problem
161: reporting (unless you are including a good fix), and they are not for
162: installation problems. If you have any question about if a message
163: should be posted to any of these lists, almost invariably, it should not
164: be. Use <b>misc</b>, above, instead. <b>Please</b> do not cross post
165: to multiple lists.
166:
167: <dl>
168: <dt><b>bugs</b>
1.57 horacio 169: <dd><a href="report.html">Bug reports</a> as sent in via
1.66 nick 170: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1">sendbug(1)</a>
171: and follow-up discussions. If you wish to have your message logged
172: by the <a href="query-pr.html">GNATS</a> bug tracking system, reply
173: to <i>gnats@openbsd.org</i>, gnats@ will then forward to <i>bugs@</i>.
174:
175: <dt><b>ipv6</b>
176: <dd>Discussion of IPv6 and IPsec in OpenBSD
177:
178: <dt><b>ports-bugs</b>
179: <dd>Discussion regarding bugs within the OpenBSD ports tree
180:
181: <dt><b>smp</b>
182: <dd>Development of <a href="faq/faq8.html#SMP">multiprocessor</a>
183: support in OpenBSD. Offers to "help test" and complaints about it not
184: being completed yet are not appreciated. Code, however, is welcome.
185:
186: <dt><b>tech</b>
187: <dd>Discussion of technical topics for OpenBSD developers and advanced
188: users. This is <b>not</b> a "tech support" forum, do not use it as
189: such.
190:
191: <dt><b>x11</b>
192: <dd>Discussion of X11 development within OpenBSD
193: </dl>
194:
195: <h3>Platform Specific Lists</h3>
196: These lists are focused on user issues and development on individual
197: platforms.
198: <dl>
199: <dt><b>alpha</b>
200: <dd>OpenBSD/alpha port
201:
202: <dt><b>hppa</b>
203: <dd>OpenBSD/hppa port
204:
205: <dt><b>mac68k</b>
206: <dd>OpenBSD/mac68k port (not PowerPC Macintosh systems)
207:
208: <dt><b>ppc</b>
209: <dd>OpenBSD/macppc port and other PowerPC porting efforts
210:
211: <dt><b>sparc</b>
212: <dd>OpenBSD/sparc and OpenBSD/sparc64 ports
213:
214: <dt><b>vax</b>
215: <dd>OpenBSD/vax port
216: </dl>
217:
218: <h3>CVS Changes Mailing Lists</h3>
219: Every time a developer commits a change to the OpenBSD
220: <a href="">CVS tree</a>, a message is mailed out to all the subscribers
221: of these lists, containing the commit comments.
222:
223: <dl>
224: <dt><b>source-changes</b>
225: <dd>Automated mail-out of CVS source tree changes in all the repositories
226: other than <i>ports</i>.
227:
228: <dt><b>ports-changes</b>
229: <dd>Automated mail-out of ports-specific CVS source tree changes.
1.1 deraadt 230: </dl>
231:
1.66 nick 232: <h3>CTM Lists</h3>
233: A number of mailing lists are used by the <a href="ctm.html">CTM</a>,
234: an alternative source change distribution system. See the
235: <a href="ctm.html">CTM page</a> for details.
236:
237:
238: <a name="Majordomo"></a>
239: <h2><font color="#e00000">Managing Mailing List Membership via
240: Majordomo</font></h2>
1.1 deraadt 241: <p>
1.57 horacio 242: If you want to be sent a complete list with all mailing lists available
1.66 nick 243: at openbsd.org, send the command "<tt>lists</tt>" on the body of
1.57 horacio 244: a message to
245: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>.
1.28 louis 246:
247: <p>
1.66 nick 248: To subscribe to a given list, send mail to
249: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
250: with a message body of "<b>subscribe mailing-list-name</b>".
251:
252: <p>
253: For further assistance, send a message body of "<b>help</b>"
1.57 horacio 254: to <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
1.13 deraadt 255: and you will receive a reply outlining all your options. Your domain
1.66 nick 256: <b>MUST</b> resolve properly or the mail will not go through!
1.1 deraadt 257:
1.66 nick 258:
259: <a name="Web"></a>
260: <h2><font color="#e00000">Managing Mailing List Membership via
261: Web</font></h2>
262: Your membership to the OpenBSD mailing lists can also be managed via
263: a web interface at:
264: <blockquote>
265: <a href="http://lists.openbsd.org/">http://lists.openbsd.org/</a>
266: </blockquote>
267:
268:
269: <a name="Tricks"></a>
270: <h2><font color="#e00000">Mailing Lists Tricks</font></h2>
271: There are a number of very useful options that can be selected, either
272: by the <a href="http://lists.openbsd.org">web interface</a> or through
273: <a href="mailto:majordomo@openbsd.org">Majordomo</a>. You can change
274: your email address without having to unsubscribe and resubscribe, you
275: can temporarily disable your message for a few days while you go on
276: vacation, and much more. The user is invited to spend some time reading
277: through the options, available by sending
278: <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
279: containing "<tt>help</tt>" as the body text, or through the
280: "<tt>Help</tt>" tab of the <a href="http://lists.openbsd.org">web
281: interface</a>.
282:
283: <p>
284: As an example, if you were going on vacation for two weeks and didn't
285: wish to come back to several thousand e-mails, you can disable the
286: messages from the mail server for the time of your vacation and have
287: them automaticly resume upon your scheduled return using the command:
288: <pre>
289: set all nomail-14d
290: </pre>
1.68 ! nick 291: This will suspend your subscription to all mail lists for 14 days
! 292: (<tt>-14d</tt>). More details and options can be seen on the
! 293: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">Majordomo
! 294: overview page</a>.
! 295:
1.66 nick 296:
297: <h3>Digests</h3>
298: If you would prefer to see a "digest" (a consolidated listing of all the
299: messages for a time period), rather than getting messages individually
300: in "real-time" form, you can use the commands:
301: <pre>
302: set misc digest-daily
303: set source-changes digest-weekly
304: </pre>
305: for daily digests of the <b>misc</b> list, and weekly digests of the
306: <b>source-changes</b> list. Yes, multiple commands can be placed in one
307: Majordomo email.
308:
309:
310: <a name="OtherLists"></a>
311: <h2><font color="#e00000">Other Mailing Lists</font></h2>
312: <p>
313: The fine folks at
314: <a href="http://www.squish.net/openbsd/">squish.net</a> run mailing
315: lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
316: and <b>ports-changes</b> mailing list. This is handy for those who
317: don't like the typically high volume of that list.
1.42 millert 318:
319: <p>
1.39 horacio 320: The clever monkeys at <a href="http://www.monkey.org/openbsd-mobile/">monkey.org</a>
1.66 nick 321: maintain the <b>openbsd-mobile</b> list for people using OpenBSD
1.29 louis 322: on mobile and laptop computers. To subscribe:
323: <br>
324: echo subscribe | mail openbsd-mobile-request@monkey.org
325:
1.50 jufi 326: <p>
1.61 dhartmei 327: The insomniac at <a href="http://www.benzedrine.cx/pf/">benzedrine.cx</a>
1.66 nick 328: maintains the <b>pf</b> list for people using the OpenBSD
1.61 dhartmei 329: packet filter. To subscribe:
330: <br>
331: echo subscribe | mail pf-request@benzedrine.cx
332:
333: <p>
1.50 jufi 334: A mailing list for OpenBSD FTP, Web, AnonCVS and CVSup mirror maintainers is
335: available at <a href="http://rt.fm/openbsd-mirrors/">rt.fm</a>.
336:
1.66 nick 337: <a name="nonEnglish"></a>
338: <h2><font color="#e00000">Non-English Lists</font></h2>
1.28 louis 339:
1.66 nick 340: Several non-English speaking mailing lists related to OpenBSD are available
1.59 miod 341: separately. Here is a list of the currently known mailing lists:
342:
343: <!--
344: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
345: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
346: -->
1.63 nick 347: <!--
1.59 miod 348: <p>
349: Chinese:
1.66 nick 350: <b>openbsd@shellhung.org</b>
1.59 miod 351: <br>To subscribe, visit the URL at:
352: <a href="http://www.shellhung.org/mailman/listinfo/openbsd/">http://www.shellhung.org/mailman/listinfo/openbsd/</a>.
1.63 nick 353: -->
1.59 miod 354:
355: <p>
356: Czech:
1.66 nick 357: <b>users@openbsd.cz</b>
1.59 miod 358: <br>To subscribe, visit the URL at:
359: <a href="http://openbsd.cz/mailman/listinfo/users/">http://openbsd.cz/mailman/listinfo/users/</a>.
360:
361: <p>
1.64 nick 362: German:
363: <strong>liste@openbsd.de</strong>
364: <br>To subscribe, please visit the URL at:
365: <a href="https://www.openbsd.de/listen/listinfo/liste">https://www.openbsd.de/listen/listinfo/liste</a>.
366:
367: <p>
1.59 miod 368: Greek:
1.66 nick 369: <b>openbsd@bsd.gr</b>
1.59 miod 370: <br>To subscribe send a mail to
371: <a href="mailto:majordomo@bsd.gr">majordomo@bsd.gr</a> with a message
1.66 nick 372: body of "<b>subscribe openbsd</b>".
1.18 deraadt 373:
374: <p>
1.59 miod 375: Italian:
1.66 nick 376: <a href="http://www.sikurezza.org/">sikurezza.org</a>, an Italian language
377: non-commercial security portal hosts <b>openbsd@sikurezza.org</b>.
1.59 miod 378: <br>To subscribe just send an empty message to <a
379: href="mailto:openbsd-subscribe@sikurezza.org">openbsd-subscribe@sikurezza.org</a>.
380:
381: <p>
382: Japanese: Please visit the URL at:
383: <a href="http://www.openbsd.ics.nara-wu.ac.jp/wakakusa">http://www.openbsd.ics.nara-wu.ac.jp/wakakus</a>
384: for more information.
385:
386: <p>
387: Polish: to subscribe, send mail to
1.55 miod 388: <a href="mailto:OpenBSD-request@bsdzine.org">OpenBSD-request@bsdzine.org</a>.
1.24 deraadt 389:
390: <p>
1.59 miod 391: Portuguese:
1.66 nick 392: <b>openbsd@neei.uevora.pt</b>
1.59 miod 393: <br>To subscribe, visit the URL at:
394: <a href="http://neei.uevora.pt/mailman/listinfo/openbsd/">http://neei.uevora.pt/mailman/listinfo/openbsd/</a>.
395:
396: <p>
1.60 miod 397: Russian:
1.66 nick 398: <b>openbsd@openbsd.ru</b>
1.47 form 399: <br>To subscribe, send mail to
400: <a href="mailto:minimalist@openbsd.ru">minimalist@openbsd.ru</a> with
1.66 nick 401: subject "<b>subscribe openbsd</b>".
1.34 form 402:
403: <p>
1.62 fgsch 404: Spanish:
1.66 nick 405: <b>misc@openbsd.org.mx</b>, run from Mexico.
1.43 horacio 406: <br>To subscribe, send an empty mail to
1.65 nick 407: <a href="mailto:misc-subscribe@openbsd.org.mx">misc-subscribe@openbsd.org.mx</a>.
1.49 horacio 408:
409: <p>
1.66 nick 410: <a name="Archives"></a>
411: <h2><font color="#e00000">Mailing List Archives:</font></h2>
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,
414: and has different search abilities. If you don't find an answer in
415: one, check another.
416:
417: <p>
418: General search engines, such as
419: <a href="http://www.google.com">Google</a> also prove very effective at
420: finding answers to OpenBSD questions.
421:
1.19 deraadt 422: <ul>
1.57 horacio 423: <li><a href="http://www.sigmasoft.com/~openbsd/">USA</a>
1.66 nick 424: <!-- seemingly not working any longer
1.27 ericj 425: <li><a href="http://www.geocrawler.com/lists/4/OpenBSD">Geocrawler Archive</a>
1.66 nick 426: -->
1.39 horacio 427: <li><a href="http://www.monkey.org/openbsd/">The primates at monkey.org</a>
1.41 avsm 428: <li><a href="http://marc.theaimsgroup.com/">MARC</a>
1.51 heko 429: <li><a href="http://bsdsearch.com/eao/phorum/index.php?f=2">BSDSearch.com</a>
430: <li><a href="http://www.netsys.com/archives.html">@netsys.com</a>
1.57 horacio 431: <li>Neohapsis has a
432: <a href="http://archives.neohapsis.com/archives/openbsd/">mixed archive
433: for tech@, misc@ and ports@</a> and a
434: <a href="http://archives.neohapsis.com/archives/openbsd/cvs/">mixed
435: archive for CVS commits</a>
1.19 deraadt 436: </ul>
1.1 deraadt 437:
438: <hr>
1.57 horacio 439: <a href="index.html"><img height=24 width=24 src="back.gif" border=0 alt="OpenBSD"></a>
440: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.68 ! nick 441: <br><small>$OpenBSD: mail.html,v 1.67 2003/08/05 18:47:06 nick Exp $</small>
1.1 deraadt 442:
443: </body>
444: </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