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