* * * * *

    “I am sorry, we cannot allow you to view this innocuous text file. For
                                  reasons.”

I found a bug in “Project: Sippy-Cup [1]”. The nature of the bug is not
important, but QA (Quality Assurance) and I were able to reproduce locally
the issue seen in production. So I ask QA to send a copy of the SIPp [2]
script (an XML (eXtensible Markup Language) file) so I could fix the issue.

> From: QA <XXXXXXXXXXXXXXXXXXXXXXX>
> To: Sean Conner <XXXXXXXXXXXXXXXXXXX>
> Subject: Sipp command and xml for CP-209
> Date: Wednesday, February 1, 2017 4:27 PM
>
> Access to attachments has been blocked. Blocked attachments:
> sipptestCp209.xml.
>

Well then … okay. I have QA resend it, this time renamed to
sipptestCp209.txt. This time it shows up. I save it. Then …

> GenericUnixPrompt> more sipptestCp209.txt
> This attachment was removed because it contains data that could pose a
> security risk.
> GenericUnixPrmopt>
>

Seriously? Just to convince myself it wasn't Mac OS-X's version of more that
was doing the conversion:

> GenericUnixPrompt> cat sipptestCp209.txt
> This attachment was removed because it contains data that could pose a
> security risk.
> GenericUnixPrmopt>
>

So it's our overly paranoid email system's fault.

Gotcha.

[1] gopher://gopher.conman.org/0Phlog:2014/03/05.1
[2] http://sipp.sourceforge.net/

Email author at [email protected]

You are viewing proxied material from gopher.conman.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.