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