Yes, that is a simple question. When a 3rd party non-ham user opens up his or her email account and hammers out (initiates) a message to a Winlink domain, there isn't anything on his or her email page that warns them that the email they are about to send will be essentially broadcast to anyone monitoring over the air or via the Winlink Viewer. Sure if the non-ham Internet emailer is responding to a Winlink domain email in his or her in basket, that might be different. If, and only if there's a disclaimer warning anyone that replies to the message will be unprotected and considered broadcast to anyone listening. I find it hilarious that you went to moderators to complain about something quite relevant to the Winlink service. Not just in my opinion, but someone else who is I think employed by law enforcement was also thinking the same way. And, then there's Peter's warning on his PMON page to not take monitored content and use it to one's personal advantage..... Didn't you read that, or did you forget already? It's good that you apparently saved someone's life, thanks to your medical knowledge. And, congrats on your son's accomplishment. Quite a catch 22 for Winlink. All I can say is that if I were an ARSFI principal with attendant liability, I'd only allow incoming Internet sourced content to be stored and forwarded via amateur radio where I had proof that the sender was aware at the time he or she authored the content, that it would be as good as broadcast for anyone to read. A checkoff box acknowledgement. I'm pretty sure we would not have seen what the group of us saw on the Viewer had such a system been in use. Would someone drop sensitive account numbers, credit card numbers, personal relationship intimate details had they known that? Most likely not...... How convenient it would have been for Waterman and Sherrod and the gang to have gotten the "official" OK to encrypt content. Then, they wouldn't have to worry about the ECPA now would they? And, you've proven that Winlink isn't seriously obscured by borrowing a C program for Linux, showed us you can decompress a page of hex content from an SCS modem and read it, if conditions are ideal and no lost data. Peter, of course, has taken that even further. Much further. 73.