Annotation of www/mail.html, Revision 1.164
1.164 ! bentley 1: <!doctype html>
! 2: <html lang=en>
! 3: <meta charset=utf-8>
! 4:
1.147 tj 5: <title>OpenBSD: Mailing Lists</title>
1.144 tb 6: <meta name="viewport" content="width=device-width, initial-scale=1">
7: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.148 tb 8: <link rel="canonical" href="https://www.openbsd.org/mail.html">
1.164 ! bentley 9: <style>
! 10: h2 {
! 11: color: var(--red);
! 12: }
1.151 tb 13: </style>
1.1 deraadt 14:
1.164 ! bentley 15: <h2 id=OpenBSD>
1.145 tb 16: <a href="index.html">
1.164 ! bentley 17: <i>Open</i><b>BSD</b></a>
! 18: Mailing Lists
1.144 tb 19: </h2>
1.164 ! bentley 20:
1.57 horacio 21: <hr>
1.164 ! bentley 22:
1.144 tb 23: <p>
1.66 nick 24: Mailing lists are an important means of communication among users and
1.139 tj 25: developers of OpenBSD.
26: With the exception of <b>announce</b>, the lists are not moderated.
27: We deliberately restrict the number of different mailing lists.
28: This helps reduce the amount of cross-posting and makes sure that
29: the information gets distributed to a wide audience.
30:
1.151 tb 31: <h2 id="Netiquette">Netiquette</h2>
1.66 nick 32:
1.164 ! bentley 33: <p>
1.28 louis 34: Be considerate of other subscribers on the mailing lists.
1.139 tj 35:
1.28 louis 36: <dl>
1.66 nick 37: <dt><b>Plain text, 72 characters per line</b>
38: <dd>Many subscribers and developers read their mail on text-based mailers
1.161 tb 39: like <a href="https://man.openbsd.org/mail">mail(1)</a>,
1.139 tj 40: emacs or mutt, and they often find HTML-formatted messages (or lines that
41: stretch beyond 72 characters) unreadable.
42: Most OpenBSD mailing lists strip messages of MIME content before sending
43: them out to the rest of the list.
1.163 tj 44: If you don't use plain text, your messages will be reformatted.
45: If they cannot be reformatted, they will be summarily rejected.
1.139 tj 46: The only mailing lists that allow file attachments are the <b>bugs</b>,
47: <b>ports</b> and <b>tech</b> lists.
48: They will be removed from messages on the others.
1.163 tj 49: <p>
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.164 ! bentley 53: the relevant documents, such as the <code>INSTALL.*</code> 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.161 tb 56: <a href= "https://man.openbsd.org/afterboot">afterboot(8)</a>).
1.163 tj 57: Also check the mailing list archives.
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.
1.163 tj 61: <p>
1.66 nick 62:
63: <dt><b>Include a useful Subject line</b>
1.45 millert 64: <dd>Messages with an empty Subject will get bounced to the list manager and
1.139 tj 65: will take longer to show up.
1.163 tj 66: Including a relevant Subject in the message will ensure that more people
67: actually read what you've written.
1.45 millert 68: Also, avoid Subject lines with excessive capitalization.
1.96 jmc 69: "Help!" or "I can't get it to work!" are not useful subject lines.
1.139 tj 70: Do not change the subject line while on the same topic.
71: YOU may know what it is regarding, the rest of us who get several hundred
72: messages a day will have no idea.
1.163 tj 73: <p>
1.66 nick 74:
75: <dt><b>Trim your signature</b>
1.163 tj 76: <dd>Keep the signature lines at the bottom of your mail to a reasonable length.
1.139 tj 77: PGP signatures and those automatic address cards are merely annoying and
78: are stripped out.
79: Legal disclaimers and advisories are also very annoying, and inappropriate
80: for public mailing lists.
1.163 tj 81: <p>
1.66 nick 82:
83: <dt><b>Stay on topic</b>
1.28 louis 84: <dd>Please keep the subject of the post relevant to users of OpenBSD.
1.163 tj 85: <p>
1.66 nick 86:
87: <dt><b>Include important information</b>
88: <dd>Don't waste everyone's time with a hopelessly incomplete question.
89: No one other than you has the information needed to resolve your
1.139 tj 90: problem, it is better to provide more information than needed than not
91: enough detail.
92: All questions should include at least the <a href="faq/faq5.html#Flavors">
93: version</a> of OpenBSD.
94: Any hardware-related questions should mention the platform (i386, amd64,
1.163 tj 95: etc.) and provide a full <a href="https://man.openbsd.org/dmesg">dmesg(8)</a>.
1.66 nick 96: Hardware model numbers, unfortunately, don't indicate much about the
97: actual content of a particular machine or accessory, and are useless to
98: anyone who doesn't have that exact machine sitting where they can easily
1.139 tj 99: recognize it.
1.163 tj 100: The dmesg output tells us exactly what is IN your machine, not what
1.139 tj 101: stickers are on the outside.
1.163 tj 102: <p>
1.66 nick 103:
104: <dt><b>Respect differences in opinion and philosophy</b>
1.139 tj 105: <dd>Intelligent people may look at the same set of facts and come to very
106: different conclusions.
107: Repeating the same points that didn't convince someone previously rarely
108: changes their mind, and irritates all the other readers.
1.28 louis 109: </dl>
1.1 deraadt 110:
1.151 tb 111: <h2 id="spam">Spam</h2>
1.139 tj 112:
1.164 ! bentley 113: <p>
1.161 tb 114: The OpenBSD lists use <a href="https://man.openbsd.org/spamd">spamd(8)</a>
1.163 tj 115: and <a href="https://spamassassin.apache.org">SpamAssassin</a> to keep down the
1.164 ! bentley 116: spam volume, but things do sneak through from time to time — deal with it.
1.139 tj 117: In addition, the list server also has regex-based rules to reject emails
1.87 millert 118: based on some common spam and virus telltales.
119: If you get spam through one of the OpenBSD mailing lists, you don't need to
1.164 ! bentley 120: send a copy to the list owner — chances are he's already seen it.
1.87 millert 121: Also, please do <b>not</b> submit spam received through the
1.139 tj 122: mailing lists to <a href="http://spamcop.net">spamcop</a>,
1.87 millert 123: as this will result in the list server being added to their RBL.
1.139 tj 124: Complaining about and commenting upon spam on the list proper is
125: counter-productive, as it generates more traffic than the spam itself.
126:
1.87 millert 127: <p>
1.139 tj 128: Note that if you are sending mail from a dynamic IP address, you
1.77 millert 129: will probably <b>not</b> be able to post to the mailing lists.
1.136 tb 130: In this case, you should use a <em>smart host</em> mail configuration
1.139 tj 131: that utilizes your ISP's mail server.
132: See the examples in
1.161 tb 133: <a href="https://man.openbsd.org/smtpd.conf">smtpd.conf(5)</a> for how
1.151 tb 134: to do this.
1.66 nick 135:
1.151 tb 136: <h2 id="Lists">General interest lists</h2>
1.33 millert 137:
1.164 ! bentley 138: <p>
1.66 nick 139: These lists are of interest to most users of OpenBSD.
1.163 tj 140:
1.1 deraadt 141: <dl>
1.163 tj 142: <dt><b>announce@openbsd.org</b>
143: <dd>Announcements and security advisories.
144: <br>
145: (<a href="https://marc.info/?l=openbsd-announce">Archive</a>)
146: <p>
1.66 nick 147:
1.163 tj 148: <dt><b>misc@openbsd.org</b>
1.139 tj 149: <dd>User questions and answers, general questions.
150: This is the most active list.
1.163 tj 151: Please read <a href="faq/index.html">the FAQ</a> and the installation
1.139 tj 152: documents, and see <a href="report.html">how to report a problem</a>
153: before posting.
1.163 tj 154: <br>
155: (<a href="https://marc.info/?l=openbsd-misc">Archive</a>)
156: <p>
1.66 nick 157:
1.163 tj 158: <dt><b>advocacy@openbsd.org</b>
1.139 tj 159: <dd>Promoting the use of OpenBSD.
1.163 tj 160: <br>
161: (<a href="https://marc.info/?l=openbsd-advocacy">Archive</a>)
162: <p>
163:
164: <dt><b>ports@openbsd.org</b>
165: <dd>Discussions about using and contributing to the ports tree.
166: <br>
167: (<a href="https://marc.info/?l=openbsd-ports">Archive</a>)
168: <p>
1.66 nick 169:
1.163 tj 170: <dt><b>misc@opensmtpd.org</b>
171: <dd>General discussions, issues and ideas about native and portable OpenSMTPD.
172: Patches for the portable bits should be pull requests on
173: <a href="https://github.com/OpenSMTPD/OpenSMTPD">Github</a>.
174: <br>
175: (<a href="https://www.mail-archive.com/misc@opensmtpd.org">Archive</a>)
176: <p>
1.66 nick 177:
1.163 tj 178: <dt><b>users@openbgpd.org</b>
179: <!-- XXX need archive link -->
180: <dd>General discussions, issues and ideas about native and portable OpenBGPD.
181: Patches for the portable bits should be pull requests on
182: <a href="https://github.com/openbgpd-portable/openbgpd-portable">Github</a>.
183: </dl>
1.66 nick 184:
1.151 tb 185: <h3>Developer lists</h3>
1.139 tj 186:
1.164 ! bentley 187: <p>
1.139 tj 188: These lists are for technical discussions of aspects of OpenBSD.
1.163 tj 189: They are NOT for beginners or average users, they are not for problem
1.139 tj 190: reporting (unless you are including a good fix) and they are not for
191: installation problems.
192: If you have any question about if a message should be posted to any of
193: these lists, it probably should not.
194: Use <b>misc</b> instead.
1.66 nick 195:
196: <dl>
1.163 tj 197: <dt><b>bugs@openbsd.org</b>
198: <dd>Bug reports as sent in via
199: <a href="https://man.openbsd.org/sendbug">sendbug(1)</a> and follow-up discussion.
200: <br>
201: (<a href="https://marc.info/?l=openbsd-bugs">Archive</a>)
202: <p>
203:
204: <dt><b>tech@openbsd.org</b>
205: <dd>Discussion of technical topics for OpenBSD developers and advanced users.
1.164 ! bentley 206: This is <b>not</b> a "tech support" forum — do not use it as such.
1.86 nick 207: OpenBSD developers will often make patches to implement new features
1.163 tj 208: and other important changes available for public testing through this list.
209: <br>
210: (<a href="https://marc.info/?l=openbsd-tech">Archive</a>)
211: <p>
1.134 doug 212:
1.163 tj 213: <dt><b>libressl@openbsd.org</b>
1.134 doug 214: <dd>Technical discussion about native and portable LibreSSL.
215: Patches for the portable bits should be pull requests on
1.163 tj 216: <a href="https://github.com/libressl-portable/portable">Github</a>.
217: <br>
218: (<a href="https://marc.info/?l=libressl">Archive</a>)
1.134 doug 219: </dl>
220:
1.162 tj 221: <h3>Reporting security issues</h3>
1.139 tj 222:
1.162 tj 223: These private addresses are for reporting vulnerabilities to the OpenBSD team.
1.134 doug 224:
225: <dl>
1.163 tj 226: <dt><b>security@openbsd.org</b>
227: <dd>Report vulnerabilities related to OpenBSD.
228: <p>
229: <dt><b>openssh@openssh.com</b>
230: <dd>Report vulnerabilities related to OpenSSH.
231: <p>
1.162 tj 232: <dt><b>libressl-security@openbsd.org</b>
233: <dd>Report vulnerabilities related to LibreSSL.
1.163 tj 234: <p>
235: <dt><b>security@opensmtpd.org</b>
236: <dd>Report vulnerabilities related to OpenSMTPD.
1.123 deraadt 237: </dl>
1.66 nick 238:
1.151 tb 239: <h3>Platform-specific lists</h3>
1.139 tj 240:
1.164 ! bentley 241: <p>
1.66 nick 242: These lists are focused on user issues and development on individual
243: platforms.
1.139 tj 244:
1.66 nick 245: <dl>
1.163 tj 246: <dt><b>alpha@openbsd.org</b>
247: <dd>OpenBSD/alpha port.
248: <br>
249: (<a href="https://marc.info/?l=openbsd-alpha">Archive</a>)
250: <p>
251:
252: <dt><b>arm@openbsd.org</b>
253: <dd>OpenBSD/armv7 and OpenBSD/arm64 ports.
254: <br>
255: (<a href="https://marc.info/?l=openbsd-arm">Archive</a>)
256: <p>
1.66 nick 257:
1.163 tj 258: <dt><b>hppa@openbsd.org</b>
259: <dd>OpenBSD/hppa port.
260: <br>
261: (<a href="https://marc.info/?l=openbsd-hppa">Archive</a>)
262: <p>
1.75 miod 263:
1.163 tj 264: <dt><b>m88k@openbsd.org</b>
265: <dd>OpenBSD/luna88k port.
266: <br>
267: (<a href="https://marc.info/?l=openbsd-m88k">Archive</a>)
268: <p>
1.66 nick 269:
1.163 tj 270: <dt><b>ppc@openbsd.org</b>
271: <dd>OpenBSD/macppc and other PowerPC porting efforts.
272: <br>
273: (<a href="https://marc.info/?l=openbsd-ppc">Archive</a>)
274: <p>
1.98 miod 275:
1.163 tj 276: <dt><b>sgi@openbsd.org</b>
277: <dd>OpenBSD/sgi port.
278: <br>
279: (<a href="https://marc.info/?l=openbsd-sgi">Archive</a>)
280: <p>
1.66 nick 281:
1.163 tj 282: <dt><b>sparc@openbsd.org</b>
283: <dd>OpenBSD/sparc64 port.
284: <br>
285: (<a href="https://marc.info/?l=openbsd-sparc">Archive</a>)
1.109 jsing 286:
1.66 nick 287: </dl>
288:
1.163 tj 289: <h2>CVS changes mailing lists</h2>
1.139 tj 290:
291: Every time a developer commits a change to the OpenBSD CVS tree, a message
292: is mailed out to all the subscribers of these lists, containing the commit
293: comments.
1.66 nick 294:
295: <dl>
1.163 tj 296: <dt><b>source-changes@openbsd.org</b>
1.139 tj 297: <dd>Automated mail of CVS source tree changes in the src, xenocara and www
298: repositories.
1.163 tj 299: <br>
300: (<a href="https://marc.info/?l=openbsd-cvs">Archive</a>)
301: <p>
1.66 nick 302:
1.163 tj 303: <dt><b>ports-changes@openbsd.org</b>
1.139 tj 304: <dd>Automated mail of CVS source tree changes in the ports repository.
1.163 tj 305: <br>
306: (<a href="https://marc.info/?l=openbsd-ports-cvs">Archive</a>)
307:
1.1 deraadt 308: </dl>
309:
1.151 tb 310: <h2 id="Mirrors">Mirror-related lists</h2>
1.139 tj 311:
1.163 tj 312: Announcements and discussion relating to <a href="ftp.html">mirrors</a>
313: of OpenBSD.
1.116 sthen 314:
315: <dl>
1.163 tj 316: <dt><b>mirrors-announce@openbsd.org</b>
1.116 sthen 317: <dd>This is a moderated list used solely for important announcements
318: to operators of OpenBSD mirrors.
1.163 tj 319: <!-- XXX need archive link -->
320: <p>
1.116 sthen 321:
1.163 tj 322: <dt><b>mirrors-discuss@openbsd.org</b>
1.116 sthen 323: <dd>Discussion relating to OpenBSD mirrors.
1.163 tj 324: <!-- XXX need archive link -->
325:
1.116 sthen 326: </dl>
327:
1.151 tb 328: <h2 id="Majordomo">Managing list membership via Majordomo</h2>
1.139 tj 329:
1.164 ! bentley 330: <p>
1.57 horacio 331: If you want to be sent a complete list with all mailing lists available
1.164 ! bentley 332: at openbsd.org, send the command <code>lists</code> in the body of
1.57 horacio 333: a message to
1.163 tj 334: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>.
1.28 louis 335:
336: <p>
1.66 nick 337: To subscribe to a given list, send mail to
1.163 tj 338: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>
1.164 ! bentley 339: with a message body of "subscribe <code>mailing-list-name</code>" (where
! 340: <code>mailing-list-name</code> is the name of your preferred list).
1.66 nick 341:
342: <p>
1.139 tj 343: For further assistance, send a message body of "help" to
1.163 tj 344: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>
1.139 tj 345: and you will receive a reply outlining all your options.
1.151 tb 346: Your domain <b>must</b> resolve properly or the mail will not go through!
1.1 deraadt 347:
1.151 tb 348: <h2 id="Web">Managing list membership via the web</h2>
1.66 nick 349:
1.164 ! bentley 350: <p>
1.66 nick 351: Your membership to the OpenBSD mailing lists can also be managed via
1.139 tj 352: a web interface at <a href="https://lists.openbsd.org">lists.openbsd.org</a>.
1.66 nick 353:
1.151 tb 354: <h2 id="Tricks">Mailing list tricks</h2>
1.66 nick 355:
1.164 ! bentley 356: <p>
1.66 nick 357: There are a number of very useful options that can be selected, either
1.139 tj 358: by the <a href="https://lists.openbsd.org">web interface</a> or through
359: <a href="mailto:majordomo@openbsd.org">Majordomo</a>.
360: You can change your email address without having to unsubscribe and
361: resubscribe, temporarily disable your message delivery for a few days
1.163 tj 362: while you go on vacation, and much more.
1.139 tj 363: The user is invited to spend some time reading through the options, available
364: by sending <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
365: containing "help" as the body text, or through the "Help" tab of the
366: <a href="https://lists.openbsd.org">web interface</a>.
1.66 nick 367:
368: <p>
369: As an example, if you were going on vacation for two weeks and didn't
1.139 tj 370: wish to come back to several thousand emails, you can disable message
371: delivery by the mail server for the time of your vacation and have
1.70 nick 372: delivery automatically resume upon your scheduled return using the command:
1.139 tj 373:
1.164 ! bentley 374: <blockquote><kbd>
1.139 tj 375: set ALL nomail-14d
1.164 ! bentley 376: </kbd></blockquote>
1.139 tj 377:
1.164 ! bentley 378: <p>
1.141 tj 379: This will suspend your subscription to all mailing lists for 14 days
1.164 ! bentley 380: (<code>-14d</code>).
1.139 tj 381: More details and options can be seen on the
382: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">
383: Majordomo overview page</a>.
1.68 nick 384:
1.139 tj 385: <h3>Digests</h3>
1.66 nick 386:
1.164 ! bentley 387: <p>
1.66 nick 388: If you would prefer to see a "digest" (a consolidated listing of all the
389: messages for a time period), rather than getting messages individually
390: in "real-time" form, you can use the commands:
1.139 tj 391:
1.164 ! bentley 392: <blockquote><kbd>
! 393: set misc digest-daily<br>
1.139 tj 394: set source-changes digest-weekly
1.164 ! bentley 395: </kbd></blockquote>
1.139 tj 396:
1.66 nick 397: for daily digests of the <b>misc</b> list, and weekly digests of the
1.139 tj 398: <b>source-changes</b> list.
399: Yes, multiple commands can be placed in one Majordomo email.
1.66 nick 400:
1.162 tj 401: <h2 id="OtherLists">Other mailing lists</h2>
1.66 nick 402:
1.164 ! bentley 403: <p>
1.151 tb 404: The fine folks at <a href="http://www.squish.net/openbsd/">squish.net</a> run
405: mailing lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
1.139 tj 406: and <b>ports-changes</b> mailing list.
1.151 tb 407: This is handy for those who don't like the typically high volume of these lists.
1.42 millert 408:
409: <p>
1.163 tj 410: The insomniac at <a href="https://www.benzedrine.ch/mailinglist.html">
1.139 tj 411: benzedrine.ch</a> maintains the <b>pf</b> list for people using the
412: OpenBSD packet filter.
413: To subscribe, send an email with the message body of "subscribe" to
414: <a href="mailto:pf-request@benzedrine.ch">pf-request@benzedrine.ch</a>.
1.61 dhartmei 415:
1.151 tb 416: <h2 id="nonEnglish">Non-English lists</h2>
1.28 louis 417:
1.164 ! bentley 418: <p>
1.66 nick 419: Several non-English speaking mailing lists related to OpenBSD are available
1.139 tj 420: separately.
421: Here is a list of the currently known mailing lists:
1.59 miod 422:
423: <!--
424: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
425: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
426: -->
427:
428: <p>
1.114 syuu 429: Japanese:
1.139 tj 430: <b>openbsd-japan@googlegroups.com</b>
431: <br>To subscribe, visit the URL at:
1.163 tj 432: <a href="https://groups.google.com/group/openbsd-japan">
433: https://groups.google.com/group/openbsd-japan</a>
1.114 syuu 434:
1.131 sthen 435: <p>
1.139 tj 436: Spanish:
437: <b>OpenBSD-Mexico@googlegroups.com</b>
1.59 miod 438: <br>To subscribe, visit the URL at:
1.163 tj 439: <a href="https://groups.google.com/group/OpenBSD-Mexico">
440: https://groups.google.com/group/OpenBSD-Mexico</a>
1.49 horacio 441:
442: <p>
1.101 steven 443: Ukrainian:
444: <b>openbsd@uaoug.org.ua</b>
1.139 tj 445: <br>To subscribe, send an empty message to
1.101 steven 446: <a href="mailto:openbsd+subscribe@uaoug.org.ua">
447: openbsd+subscribe@uaoug.org.ua</a>
![[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