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