Annotation of www/mail.html, Revision 1.173
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.173 ! tj 37: <dt><b>Plain text, 72 characters per line.</b>
1.66 nick 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:
1.173 ! tj 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:
1.173 ! tj 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:
1.173 ! tj 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:
1.173 ! tj 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:
1.173 ! tj 87: <dt><b>Include important information.</b>
1.66 nick 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:
1.173 ! tj 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.165 deraadt 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.173 ! tj 122: mailing lists to <a href="https://www.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.173 ! tj 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>
1.173 ! tj 143: (<a href="https://marc.info/?l=openbsd-announce">Archive</a>)
1.163 tj 144: <dd>Announcements and security advisories.
145: <p>
1.66 nick 146:
1.163 tj 147: <dt><b>misc@openbsd.org</b>
1.173 ! tj 148: (<a href="https://marc.info/?l=openbsd-misc">Archive</a>)
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: <p>
1.66 nick 155:
1.163 tj 156: <dt><b>advocacy@openbsd.org</b>
1.173 ! tj 157: (<a href="https://marc.info/?l=openbsd-advocacy">Archive</a>)
1.139 tj 158: <dd>Promoting the use of OpenBSD.
1.163 tj 159: <p>
160:
161: <dt><b>ports@openbsd.org</b>
1.173 ! tj 162: (<a href="https://marc.info/?l=openbsd-ports">Archive</a>)
1.163 tj 163: <dd>Discussions about using and contributing to the ports tree.
164: <p>
1.66 nick 165:
1.163 tj 166: <dt><b>misc@opensmtpd.org</b>
1.173 ! tj 167: (<a href="https://www.mail-archive.com/misc@opensmtpd.org">Archive</a>)
1.163 tj 168: <dd>General discussions, issues and ideas about native and portable OpenSMTPD.
169: Patches for the portable bits should be pull requests on
170: <a href="https://github.com/OpenSMTPD/OpenSMTPD">Github</a>.
1.167 gilles 171: To subscribe there,
172: follow instructions from <a href="https://opensmtpd.org/list.html">the OpenSMTPD website</a>.
1.163 tj 173: <p>
1.66 nick 174:
1.163 tj 175: <dt><b>users@openbgpd.org</b>
1.173 ! tj 176: (<a href="https://marc.info/?l=openbgpd-users">Archive</a>)
1.163 tj 177: <dd>General discussions, issues and ideas about native and portable OpenBGPD.
178: Patches for the portable bits should be pull requests on
179: <a href="https://github.com/openbgpd-portable/openbgpd-portable">Github</a>.
180: </dl>
1.66 nick 181:
1.173 ! tj 182: <h2>Developer Lists</h2>
1.139 tj 183:
1.164 bentley 184: <p>
1.139 tj 185: These lists are for technical discussions of aspects of OpenBSD.
1.163 tj 186: They are NOT for beginners or average users, they are not for problem
1.139 tj 187: reporting (unless you are including a good fix) and they are not for
188: installation problems.
189: If you have any question about if a message should be posted to any of
190: these lists, it probably should not.
191: Use <b>misc</b> instead.
1.66 nick 192:
193: <dl>
1.163 tj 194: <dt><b>bugs@openbsd.org</b>
1.173 ! tj 195: (<a href="https://marc.info/?l=openbsd-bugs">Archive</a>)
1.163 tj 196: <dd>Bug reports as sent in via
197: <a href="https://man.openbsd.org/sendbug">sendbug(1)</a> and follow-up discussion.
198: <p>
199:
200: <dt><b>tech@openbsd.org</b>
1.173 ! tj 201: (<a href="https://marc.info/?l=openbsd-tech">Archive</a>)
1.163 tj 202: <dd>Discussion of technical topics for OpenBSD developers and advanced users.
1.164 bentley 203: This is <b>not</b> a "tech support" forum — do not use it as such.
1.86 nick 204: OpenBSD developers will often make patches to implement new features
1.163 tj 205: and other important changes available for public testing through this list.
206: <p>
1.134 doug 207:
1.163 tj 208: <dt><b>libressl@openbsd.org</b>
1.173 ! tj 209: (<a href="https://marc.info/?l=libressl">Archive</a>)
1.134 doug 210: <dd>Technical discussion about native and portable LibreSSL.
211: Patches for the portable bits should be pull requests on
1.163 tj 212: <a href="https://github.com/libressl-portable/portable">Github</a>.
1.134 doug 213: </dl>
214:
1.173 ! tj 215: <h2>Reporting Security Issues</h2>
1.139 tj 216:
1.162 tj 217: These private addresses are for reporting vulnerabilities to the OpenBSD team.
1.134 doug 218:
219: <dl>
1.163 tj 220: <dt><b>security@openbsd.org</b>
221: <dd>Report vulnerabilities related to OpenBSD.
222: <p>
223: <dt><b>openssh@openssh.com</b>
224: <dd>Report vulnerabilities related to OpenSSH.
225: <p>
1.162 tj 226: <dt><b>libressl-security@openbsd.org</b>
227: <dd>Report vulnerabilities related to LibreSSL.
1.163 tj 228: <p>
1.168 millert 229: <dt><b>opensmtpd-security@openbsd.org</b>
1.163 tj 230: <dd>Report vulnerabilities related to OpenSMTPD.
1.123 deraadt 231: </dl>
1.66 nick 232:
1.173 ! tj 233: <h2>Platform-Specific Lists</h2>
1.139 tj 234:
1.164 bentley 235: <p>
1.66 nick 236: These lists are focused on user issues and development on individual
1.166 deraadt 237: <a href=plat.html>platforms</a>.
1.139 tj 238:
1.66 nick 239: <dl>
1.163 tj 240: <dt><b>alpha@openbsd.org</b>
1.173 ! tj 241: (<a href="https://marc.info/?l=openbsd-alpha">Archive</a>)
1.163 tj 242: <dd>OpenBSD/alpha port.
243: <p>
244:
245: <dt><b>arm@openbsd.org</b>
1.173 ! tj 246: (<a href="https://marc.info/?l=openbsd-arm">Archive</a>)
1.163 tj 247: <dd>OpenBSD/armv7 and OpenBSD/arm64 ports.
248: <p>
1.66 nick 249:
1.163 tj 250: <dt><b>hppa@openbsd.org</b>
1.173 ! tj 251: (<a href="https://marc.info/?l=openbsd-hppa">Archive</a>)
1.163 tj 252: <dd>OpenBSD/hppa port.
253: <p>
1.75 miod 254:
1.163 tj 255: <dt><b>m88k@openbsd.org</b>
1.173 ! tj 256: (<a href="https://marc.info/?l=openbsd-m88k">Archive</a>)
1.163 tj 257: <dd>OpenBSD/luna88k port.
258: <p>
1.66 nick 259:
1.163 tj 260: <dt><b>ppc@openbsd.org</b>
1.173 ! tj 261: (<a href="https://marc.info/?l=openbsd-ppc">Archive</a>)
1.163 tj 262: <dd>OpenBSD/macppc and other PowerPC porting efforts.
263: <p>
1.66 nick 264:
1.163 tj 265: <dt><b>sparc@openbsd.org</b>
1.173 ! tj 266: (<a href="https://marc.info/?l=openbsd-sparc">Archive</a>)
1.163 tj 267: <dd>OpenBSD/sparc64 port.
1.109 jsing 268:
1.66 nick 269: </dl>
270:
1.173 ! tj 271: <h2>CVS Changes Mailing Lists</h2>
1.139 tj 272:
273: Every time a developer commits a change to the OpenBSD CVS tree, a message
274: is mailed out to all the subscribers of these lists, containing the commit
1.165 deraadt 275: comments.
1.66 nick 276:
277: <dl>
1.163 tj 278: <dt><b>source-changes@openbsd.org</b>
1.173 ! tj 279: (<a href="https://marc.info/?l=openbsd-cvs">Archive</a>)
1.166 deraadt 280: <dd>Automated mail of CVS source tree changes in the <code>src</code>,
281: <code>xenocara</code> and <code>www</code> repositories.
1.163 tj 282: <p>
1.66 nick 283:
1.163 tj 284: <dt><b>ports-changes@openbsd.org</b>
1.173 ! tj 285: (<a href="https://marc.info/?l=openbsd-ports-cvs">Archive</a>)
1.166 deraadt 286: <dd>Automated mail of CVS source tree changes in the <code>ports</code>
287: repository.
1.163 tj 288:
1.1 deraadt 289: </dl>
290:
1.173 ! tj 291: <h2 id="Mirrors">Mirror-Related Lists</h2>
1.139 tj 292:
1.163 tj 293: Announcements and discussion relating to <a href="ftp.html">mirrors</a>
294: of OpenBSD.
1.116 sthen 295:
296: <dl>
1.163 tj 297: <dt><b>mirrors-announce@openbsd.org</b>
1.116 sthen 298: <dd>This is a moderated list used solely for important announcements
299: to operators of OpenBSD mirrors.
1.163 tj 300: <!-- XXX need archive link -->
301: <p>
1.116 sthen 302:
1.163 tj 303: <dt><b>mirrors-discuss@openbsd.org</b>
1.116 sthen 304: <dd>Discussion relating to OpenBSD mirrors.
1.170 schwarze 305: <!-- Do not create a web archive of this list.
306: There is no benefit in looking up old posts,
307: so the only effect would be helping spammers
308: to collect mail addresses of mirror admins. -->
1.116 sthen 309: </dl>
310:
1.173 ! tj 311: <h2 id="Majordomo">Managing List Membership via Majordomo</h2>
1.139 tj 312:
1.164 bentley 313: <p>
1.57 horacio 314: If you want to be sent a complete list with all mailing lists available
1.164 bentley 315: at openbsd.org, send the command <code>lists</code> in the body of
1.57 horacio 316: a message to
1.163 tj 317: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>.
1.28 louis 318:
319: <p>
1.66 nick 320: To subscribe to a given list, send mail to
1.163 tj 321: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>
1.164 bentley 322: with a message body of "subscribe <code>mailing-list-name</code>" (where
323: <code>mailing-list-name</code> is the name of your preferred list).
1.66 nick 324:
325: <p>
1.139 tj 326: For further assistance, send a message body of "help" to
1.163 tj 327: <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>
1.139 tj 328: and you will receive a reply outlining all your options.
1.151 tb 329: Your domain <b>must</b> resolve properly or the mail will not go through!
1.1 deraadt 330:
1.173 ! tj 331: <h2 id="Web">Managing List Membership via the Web</h2>
1.66 nick 332:
1.164 bentley 333: <p>
1.66 nick 334: Your membership to the OpenBSD mailing lists can also be managed via
1.139 tj 335: a web interface at <a href="https://lists.openbsd.org">lists.openbsd.org</a>.
1.66 nick 336:
1.173 ! tj 337: <h2 id="Tricks">Mailing List Tricks</h2>
1.66 nick 338:
1.164 bentley 339: <p>
1.66 nick 340: There are a number of very useful options that can be selected, either
1.139 tj 341: by the <a href="https://lists.openbsd.org">web interface</a> or through
342: <a href="mailto:majordomo@openbsd.org">Majordomo</a>.
343: You can change your email address without having to unsubscribe and
344: resubscribe, temporarily disable your message delivery for a few days
1.163 tj 345: while you go on vacation, and much more.
1.139 tj 346: The user is invited to spend some time reading through the options, available
347: by sending <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
348: containing "help" as the body text, or through the "Help" tab of the
349: <a href="https://lists.openbsd.org">web interface</a>.
1.66 nick 350:
351: <p>
352: As an example, if you were going on vacation for two weeks and didn't
1.139 tj 353: wish to come back to several thousand emails, you can disable message
354: delivery by the mail server for the time of your vacation and have
1.70 nick 355: delivery automatically resume upon your scheduled return using the command:
1.139 tj 356:
1.164 bentley 357: <blockquote><kbd>
1.139 tj 358: set ALL nomail-14d
1.164 bentley 359: </kbd></blockquote>
1.139 tj 360:
1.164 bentley 361: <p>
1.141 tj 362: This will suspend your subscription to all mailing lists for 14 days
1.164 bentley 363: (<code>-14d</code>).
1.165 deraadt 364: More details and options can be seen on the
1.139 tj 365: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">
366: Majordomo overview page</a>.
1.68 nick 367:
1.173 ! tj 368: <h2>Digests</h2>
1.66 nick 369:
1.164 bentley 370: <p>
1.66 nick 371: If you would prefer to see a "digest" (a consolidated listing of all the
372: messages for a time period), rather than getting messages individually
373: in "real-time" form, you can use the commands:
1.139 tj 374:
1.164 bentley 375: <blockquote><kbd>
376: set misc digest-daily<br>
1.139 tj 377: set source-changes digest-weekly
1.164 bentley 378: </kbd></blockquote>
1.139 tj 379:
1.66 nick 380: for daily digests of the <b>misc</b> list, and weekly digests of the
1.139 tj 381: <b>source-changes</b> list.
382: Yes, multiple commands can be placed in one Majordomo email.
1.66 nick 383:
1.173 ! tj 384: <h2 id="OtherLists">Other Mailing Lists</h2>
1.66 nick 385:
1.173 ! tj 386: <dt><b>pf@benzedrine.ch</b>
! 387: (<a href="https://marc.info/?l=openbsd-pf">Archive</a>)
! 388: <dd>Discussions about the <a href=faq/pf/index.html>OpenBSD packet filter</a>.
! 389: To subscribe, send an email with a message body of "subscribe" to
1.139 tj 390: <a href="mailto:pf-request@benzedrine.ch">pf-request@benzedrine.ch</a>.
1.173 ! tj 391: More info <a href="https://www.benzedrine.ch/mailinglist.html">here</a>.
! 392: </dd>
1.61 dhartmei 393:
1.173 ! tj 394: <h2 id="nonEnglish">Non-English Lists</h2>
1.28 louis 395:
1.164 bentley 396: <p>
1.66 nick 397: Several non-English speaking mailing lists related to OpenBSD are available
1.139 tj 398: separately.
399: Here is a list of the currently known mailing lists:
1.59 miod 400:
1.165 deraadt 401: <!--
1.59 miod 402: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
403: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
404: -->
1.114 syuu 405:
1.131 sthen 406: <p>
1.171 schwarze 407: French:
408: <b>blabla@openbsd.fr.eu.org</b>
1.173 ! tj 409: (<a href="https://openbsd.fr.eu.org/blabla/">Archive</a>)
1.171 schwarze 410: <br>To subscribe, send a message to
411: <a href="mailto:blabla+subscribe@openbsd.fr.eu.org">
412: blabla+subscribe@openbsd.fr.eu.org</a>
413:
414: <p>
1.139 tj 415: Spanish:
416: <b>OpenBSD-Mexico@googlegroups.com</b>
1.59 miod 417: <br>To subscribe, visit the URL at:
1.163 tj 418: <a href="https://groups.google.com/group/OpenBSD-Mexico">
419: https://groups.google.com/group/OpenBSD-Mexico</a>
1.49 horacio 420:
421: <p>
1.101 steven 422: Ukrainian:
423: <b>openbsd@uaoug.org.ua</b>
1.139 tj 424: <br>To subscribe, send an empty message to
1.101 steven 425: <a href="mailto:openbsd+subscribe@uaoug.org.ua">
426: 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