<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p> <br>
</p>
<div class="moz-cite-prefix">On 03.03.21 09:35, Kristijonas Lukas
Bukauskas wrote:<br>
</div>
<blockquote type="cite"
cite="mid:a8bae241e4f8714325d89c8eafb5d227@n0.lt">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Interestingly -- but not unexpectedly -- enough they may add you
to the uceprotect-level1 list if they see you attempted a payment
but haven't paid. So, for reasons not related to spamming. <br>
<p><br>
The whole autonomous system of my cloud provider got listed in
uceprotect-level3. I wanted to check how their whitelisting
works. They blacklisted the public IP of my home internet
connection, with a reason (<a
href="https://pasteboard.co/JQShns8.png"
moz-do-not-send="true">https://pasteboard.co/JQShns8.png</a>):</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">
<p>Payment attempts with invalid credit cards. </p>
</blockquote>
<p>Needless to say: my home ISP doesn't allow sending mail, has
port 25 blocked, and I haven't entered any card data to get my
IP of Cloud server whitelisted whatsoever, only initiated the
payment and closed the browser tab once I was routed to their
payment provider. <br>
<br>
</p>
</blockquote>
<p>This indeed puts the uceprotect in a different category in my
books. Please forget what I wrote earlier in this chain.</p>
<p><br>
</p>
<p>Yours</p>
<p>esa<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>-- </p>
<pre class="moz-signature" cols="72">Mr Esa Laitinen
IM: <a class="moz-txt-link-freetext" href="https://threema.id/2JP4Y33R">https://threema.id/2JP4Y33R</a> or <a class="moz-txt-link-freetext" href="https://signal.org/install">https://signal.org/install</a>
Skype: reunaesa
Mobile: +4178 838 57 77</pre>
</body>
</html>