[nos-bbs] Winlink CC headers opinions ? comments ?

[David Lounsbury]

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.

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. 

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.

Regards,
Dave Lounsbury
KC1UIX


----
On Jul 10, 2026 at 10:03:07 AM, Maiko Langelaar wrote:
That is an INSANE number of CC entries in the mail header.

Can anyone give me a reason WHY we should not ignore CC entries.

How many of you would actually be able to deliver to the CC entries within
your own bbs setups ? I could add a flag something like :

    mbox winlink ignoreCC *[from From: xxxx]

But is there any point ? Opinion ? Comments ?

I mean, really this can apply to ANY area, not just Wl2k

Maiko / VE4KLM

On 6/24/26 08:09, David Lounsbury wrote:
> Problem: After receiving a Winlink email with a large number of CCs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20260710/b2628615/attachment.htm>