<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I agree, it is not for jnos to distribute that but for Winlink.</p>
<p><br>
</p>
<p>Boudewijn VE3TOK</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/10/26 12:33, David Lounsbury
wrote:<br>
</div>
<blockquote type="cite" cite="mid:0076RQ6W1gvf0k9py8@gmail.com">
<style type="text/css" sc-scope="required">p, div {
margin: 0.0em;
}</style>
<style type="text/css" sc-scope="rich-text">:root {
color-scheme: light dark;
}a {
color: blue;
}body {
font-family: Helvetica,sans-serif;
font-size: 13px;
color: light-dark(rgb(0,0,0), rgb(255,255,255));
text-align: natural;
background-color:rgb(255 255 255));
margin: 0px;
}</style>
<style type="text/css" sc-scope="sc-lists">ul, ol {
padding-inline-start: 30px;
margin-block: 0px;
}ul ul, ol ol {
padding-inline-start: 20px;
}ul, ul ul ul {
list-style-type: disc;
}ul ul, ul ul ul ul {
list-style-type: circle;
}ol {
list-style-type: decimal;
}ol ol {
list-style-type: lower-alpha;
}ol ol ol {
list-style-type: lower-roman;
}ol ol ol ol {
list-style-type: lower-greek;
}ul + p:has(+ ul) {
margin-block: 0px;
}</style>
<meta charset="utf-8" http-equiv="content-type"
content="text/html; charset=UTF-8">
<div sc-note="">I see no reason to process Winlink CCs in jnos
myself. The Winlink CC already implies a delivery path to the
intended recipient. I guess there might be a corner case in a
multi-user jnos node where people were fetching their Winlink
email. Even there, though, I believe every person would
receive a copy directly from Winlink - there's no need to repeat
the delivery via also handling the CCs in jnos.</div>
<div><br>
</div>
<div>Concur with Charles on making this an option. I don'e see the
use case myself, but I have relatively few users on my node and
haven't thought about all delivery paths. </div>
<div><br>
</div>
<div>Another downside to CC processing is that you end up with a
hidden area on your node for *every* CC. Cleaning this up is not
fun.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Dave Lounsbury</div>
<div>KC1UIX</div>
<hr id="sc-reply-separator">
<div style="color: #999;"><strong>On <span>Jul 10, 2026 at
10:03:07\u202fAM</span>, <span>Maiko Langelaar</span> wrote:</strong><br>
</div>
<blockquote>
<div id="original-content"><span>
<div id="" class="mvn-added-padding"
style="overflow: visible auto;">
<div style="white-space: pre-wrap;">That is an INSANE number of CC entries in the mail header.</div>
<br>
<div style="white-space: pre-wrap;">Can anyone give me a reason WHY we should not ignore CC entries.</div>
<br>
<div style="white-space: pre-wrap;">How many of you would actually be able to deliver to the CC entries within</div>
<div style="white-space: pre-wrap;">your own bbs setups ? I could add a flag something like :</div>
<br>
<div style="white-space: pre-wrap;"> mbox winlink ignoreCC *[from From: xxxx]</div>
<br>
<div style="white-space: pre-wrap;">But is there any point ? Opinion ? Comments ?</div>
<br>
<div style="white-space: pre-wrap;">I mean, really this can apply to ANY area, not just Wl2k</div>
<br>
<div style="white-space: pre-wrap;">Maiko / VE4KLM</div>
<br>
<div style="white-space: pre-wrap;">On 6/24/26 08:09, David Lounsbury wrote:</div>
<div style="white-space: pre-wrap;">> Problem: After receiving a Winlink email with a large number of CCs</div>
<br>
</div>
</span></div>
</blockquote>
<br>
<div><br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
nos-bbs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="0">--
There is nothing permanent except change
Heraclitus
</pre>
</body>
</html>