|
|
@@ -3,7 +3,7 @@
|
|
3
|
3
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
4
|
4
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
5
|
5
|
<head>
|
|
6
|
|
-<!-- 2016-01-15 Fri 10:06 -->
|
|
|
6
|
+<!-- 2016-01-17 Sun 13:21 -->
|
|
7
|
7
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
|
8
|
8
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
9
|
9
|
<title></title>
|
|
|
@@ -175,67 +175,71 @@ for the JavaScript code in this tag.
|
|
175
|
175
|
</tr>
|
|
176
|
176
|
|
|
177
|
177
|
<tr>
|
|
178
|
|
-<td class="org-left"><a href="#orgheadline2">Why can't I access my .onion site with a Tor browser?</a></td>
|
|
|
178
|
+<td class="org-left"><a href="#orgheadline2">Why use Github?</a></td>
|
|
179
|
179
|
</tr>
|
|
180
|
180
|
|
|
181
|
181
|
<tr>
|
|
182
|
|
-<td class="org-left"><a href="#orgheadline3">What is the best hardware to run this system on?</a></td>
|
|
|
182
|
+<td class="org-left"><a href="#orgheadline3">Why can't I access my .onion site with a Tor browser?</a></td>
|
|
183
|
183
|
</tr>
|
|
184
|
184
|
|
|
185
|
185
|
<tr>
|
|
186
|
|
-<td class="org-left"><a href="#orgheadline4">Can I add more users to the system?</a></td>
|
|
|
186
|
+<td class="org-left"><a href="#orgheadline4">What is the best hardware to run this system on?</a></td>
|
|
187
|
187
|
</tr>
|
|
188
|
188
|
|
|
189
|
189
|
<tr>
|
|
190
|
|
-<td class="org-left"><a href="#orgheadline5">How do I remove a user from the system?</a></td>
|
|
|
190
|
+<td class="org-left"><a href="#orgheadline5">Can I add more users to the system?</a></td>
|
|
191
|
191
|
</tr>
|
|
192
|
192
|
|
|
193
|
193
|
<tr>
|
|
194
|
|
-<td class="org-left"><a href="#orgheadline6">How do I reset the tripwire?</a></td>
|
|
|
194
|
+<td class="org-left"><a href="#orgheadline6">How do I remove a user from the system?</a></td>
|
|
195
|
195
|
</tr>
|
|
196
|
196
|
|
|
197
|
197
|
<tr>
|
|
198
|
|
-<td class="org-left"><a href="#orgheadline7">Is metadata protected?</a></td>
|
|
|
198
|
+<td class="org-left"><a href="#orgheadline7">How do I reset the tripwire?</a></td>
|
|
199
|
199
|
</tr>
|
|
200
|
200
|
|
|
201
|
201
|
<tr>
|
|
202
|
|
-<td class="org-left"><a href="#orgheadline8">How do I create email processing rules?</a></td>
|
|
|
202
|
+<td class="org-left"><a href="#orgheadline8">Is metadata protected?</a></td>
|
|
203
|
203
|
</tr>
|
|
204
|
204
|
|
|
205
|
205
|
<tr>
|
|
206
|
|
-<td class="org-left"><a href="#orgheadline9">Why isn't dynamic DNS working?</a></td>
|
|
|
206
|
+<td class="org-left"><a href="#orgheadline9">How do I create email processing rules?</a></td>
|
|
207
|
207
|
</tr>
|
|
208
|
208
|
|
|
209
|
209
|
<tr>
|
|
210
|
|
-<td class="org-left"><a href="#orgheadline10">How do I change my encryption settings?</a></td>
|
|
|
210
|
+<td class="org-left"><a href="#orgheadline10">Why isn't dynamic DNS working?</a></td>
|
|
211
|
211
|
</tr>
|
|
212
|
212
|
|
|
213
|
213
|
<tr>
|
|
214
|
|
-<td class="org-left"><a href="#orgheadline11">How do I get a domain name?</a></td>
|
|
|
214
|
+<td class="org-left"><a href="#orgheadline11">How do I change my encryption settings?</a></td>
|
|
215
|
215
|
</tr>
|
|
216
|
216
|
|
|
217
|
217
|
<tr>
|
|
218
|
|
-<td class="org-left"><a href="#orgheadline12">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
|
|
218
|
+<td class="org-left"><a href="#orgheadline12">How do I get a domain name?</a></td>
|
|
219
|
219
|
</tr>
|
|
220
|
220
|
|
|
221
|
221
|
<tr>
|
|
222
|
|
-<td class="org-left"><a href="#orgheadline13">How do I renew a Let's Encrypt certificate?</a></td>
|
|
|
222
|
+<td class="org-left"><a href="#orgheadline13">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
|
223
|
223
|
</tr>
|
|
224
|
224
|
|
|
225
|
225
|
<tr>
|
|
226
|
|
-<td class="org-left"><a href="#orgheadline14">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
|
|
226
|
+<td class="org-left"><a href="#orgheadline14">How do I renew a Let's Encrypt certificate?</a></td>
|
|
227
|
227
|
</tr>
|
|
228
|
228
|
|
|
229
|
229
|
<tr>
|
|
230
|
|
-<td class="org-left"><a href="#orgheadline15">Why use self-signed certificates?</a></td>
|
|
|
230
|
+<td class="org-left"><a href="#orgheadline15">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
|
231
|
231
|
</tr>
|
|
232
|
232
|
|
|
233
|
233
|
<tr>
|
|
234
|
|
-<td class="org-left"><a href="#orgheadline16">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
|
|
234
|
+<td class="org-left"><a href="#orgheadline16">Why use self-signed certificates?</a></td>
|
|
235
|
235
|
</tr>
|
|
236
|
236
|
|
|
237
|
237
|
<tr>
|
|
238
|
|
-<td class="org-left"><a href="#orgheadline17">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
|
|
238
|
+<td class="org-left"><a href="#orgheadline17">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
|
|
239
|
+</tr>
|
|
|
240
|
+
|
|
|
241
|
+<tr>
|
|
|
242
|
+<td class="org-left"><a href="#orgheadline18">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
|
239
|
243
|
</tr>
|
|
240
|
244
|
</tbody>
|
|
241
|
245
|
</table>
|
|
|
@@ -254,17 +258,33 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
|
|
254
|
258
|
</div>
|
|
255
|
259
|
</div>
|
|
256
|
260
|
<div id="outline-container-orgheadline2" class="outline-2">
|
|
257
|
|
-<h2 id="orgheadline2">Why can't I access my .onion site with a Tor browser?</h2>
|
|
|
261
|
+<h2 id="orgheadline2">Why use Github?</h2>
|
|
258
|
262
|
<div class="outline-text-2" id="text-orgheadline2">
|
|
259
|
263
|
<p>
|
|
260
|
|
-By default the Tor browser has <a href="https://www.eff.org/HTTPS-everywhere">https everywhere</a> enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key).
|
|
|
264
|
+Github is paradoxically a centralized, closed and proprietary system which happens to mostly host free and open source projects. Up until now it has been relatively benign, but at some point in the name of "growth" it will likely start becoming more evil, or just become like SourceForge - which was also once much loved by FOSS developers, but turned into a den of malvertizing.
|
|
|
265
|
+</p>
|
|
|
266
|
+
|
|
|
267
|
+<p>
|
|
|
268
|
+At present Github is useful just because of the sheer number of eyeballs and the easy discoverability of projects via search.
|
|
|
269
|
+</p>
|
|
|
270
|
+
|
|
|
271
|
+<p>
|
|
|
272
|
+The source code for this project is experimentally independently hosted, and it is expected that in future the main development will shift over to an independent site, maybe with mirrors on Github if it still exists in a viable form.
|
|
261
|
273
|
</p>
|
|
262
|
274
|
</div>
|
|
263
|
275
|
</div>
|
|
264
|
276
|
<div id="outline-container-orgheadline3" class="outline-2">
|
|
265
|
|
-<h2 id="orgheadline3">What is the best hardware to run this system on?</h2>
|
|
|
277
|
+<h2 id="orgheadline3">Why can't I access my .onion site with a Tor browser?</h2>
|
|
266
|
278
|
<div class="outline-text-2" id="text-orgheadline3">
|
|
267
|
279
|
<p>
|
|
|
280
|
+By default the Tor browser has <a href="https://www.eff.org/HTTPS-everywhere">https everywhere</a> enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key).
|
|
|
281
|
+</p>
|
|
|
282
|
+</div>
|
|
|
283
|
+</div>
|
|
|
284
|
+<div id="outline-container-orgheadline4" class="outline-2">
|
|
|
285
|
+<h2 id="orgheadline4">What is the best hardware to run this system on?</h2>
|
|
|
286
|
+<div class="outline-text-2" id="text-orgheadline4">
|
|
|
287
|
+<p>
|
|
268
|
288
|
It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you <a href="https://en.wikipedia.org/wiki/Uninterruptible_power_supply">UPS capability</a> to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical.
|
|
269
|
289
|
</p>
|
|
270
|
290
|
|
|
|
@@ -273,9 +293,9 @@ It was originally designed to run on the Beaglebone Black, but that should be re
|
|
273
|
293
|
</p>
|
|
274
|
294
|
</div>
|
|
275
|
295
|
</div>
|
|
276
|
|
-<div id="outline-container-orgheadline4" class="outline-2">
|
|
277
|
|
-<h2 id="orgheadline4">Can I add more users to the system?</h2>
|
|
278
|
|
-<div class="outline-text-2" id="text-orgheadline4">
|
|
|
296
|
+<div id="outline-container-orgheadline5" class="outline-2">
|
|
|
297
|
+<h2 id="orgheadline5">Can I add more users to the system?</h2>
|
|
|
298
|
+<div class="outline-text-2" id="text-orgheadline5">
|
|
279
|
299
|
<p>
|
|
280
|
300
|
Yes. Freedombone can support a small number of users, for a "<i>friends and family</i>" type of home installation. This gives them access to an email account, XMPP, SIP phone and the blog (depending on whether the variant which you installed includes those).
|
|
281
|
301
|
</p>
|
|
|
@@ -300,9 +320,9 @@ Another point is that Freedombone installations are not intended to support many
|
|
300
|
320
|
</p>
|
|
301
|
321
|
</div>
|
|
302
|
322
|
</div>
|
|
303
|
|
-<div id="outline-container-orgheadline5" class="outline-2">
|
|
304
|
|
-<h2 id="orgheadline5">How do I remove a user from the system?</h2>
|
|
305
|
|
-<div class="outline-text-2" id="text-orgheadline5">
|
|
|
323
|
+<div id="outline-container-orgheadline6" class="outline-2">
|
|
|
324
|
+<h2 id="orgheadline6">How do I remove a user from the system?</h2>
|
|
|
325
|
+<div class="outline-text-2" id="text-orgheadline6">
|
|
306
|
326
|
<p>
|
|
307
|
327
|
To remove a user:
|
|
308
|
328
|
</p>
|
|
|
@@ -319,9 +339,9 @@ Select <i>Manage Users</i> and then <i>Delete a user</i>. Note that this will de
|
|
319
|
339
|
</p>
|
|
320
|
340
|
</div>
|
|
321
|
341
|
</div>
|
|
322
|
|
-<div id="outline-container-orgheadline6" class="outline-2">
|
|
323
|
|
-<h2 id="orgheadline6">How do I reset the tripwire?</h2>
|
|
324
|
|
-<div class="outline-text-2" id="text-orgheadline6">
|
|
|
342
|
+<div id="outline-container-orgheadline7" class="outline-2">
|
|
|
343
|
+<h2 id="orgheadline7">How do I reset the tripwire?</h2>
|
|
|
344
|
+<div class="outline-text-2" id="text-orgheadline7">
|
|
325
|
345
|
<p>
|
|
326
|
346
|
The tripwire will be automatically reset once per week. If you want to reset it earlier then do the following:
|
|
327
|
347
|
</p>
|
|
|
@@ -338,17 +358,17 @@ Select "reset tripwire" using cursors and space bar then enter.
|
|
338
|
358
|
</p>
|
|
339
|
359
|
</div>
|
|
340
|
360
|
</div>
|
|
341
|
|
-<div id="outline-container-orgheadline7" class="outline-2">
|
|
342
|
|
-<h2 id="orgheadline7">Is metadata protected?</h2>
|
|
343
|
|
-<div class="outline-text-2" id="text-orgheadline7">
|
|
|
361
|
+<div id="outline-container-orgheadline8" class="outline-2">
|
|
|
362
|
+<h2 id="orgheadline8">Is metadata protected?</h2>
|
|
|
363
|
+<div class="outline-text-2" id="text-orgheadline8">
|
|
344
|
364
|
<p>
|
|
345
|
365
|
Even when using Freedombone metadata analysis by third parties is still possible. This can be mitigated by accessing your blog, or other web services, via their <i>onion addresses</i>, rather than via more conventional domain names. In that case your ISP and any government which they might be compelled to report back to will know when your system is being accessed, but not necessarily <i>which</i> services are being accessed <i>or by whom</i>. So for instance using a Tor browser and the onion address people may be able to safely read your blog or wiki and be reasonably confident that metadata isn't being gathered about what they read (or more concisely the metadata which can be gathered by a third party may just not be very useful or personally identifiable). On the other hand if you access the system via conventional domain names and dynamic DNS then it's safe to assume that metadata can and will be collected by third parties.
|
|
346
|
366
|
</p>
|
|
347
|
367
|
</div>
|
|
348
|
368
|
</div>
|
|
349
|
|
-<div id="outline-container-orgheadline8" class="outline-2">
|
|
350
|
|
-<h2 id="orgheadline8">How do I create email processing rules?</h2>
|
|
351
|
|
-<div class="outline-text-2" id="text-orgheadline8">
|
|
|
369
|
+<div id="outline-container-orgheadline9" class="outline-2">
|
|
|
370
|
+<h2 id="orgheadline9">How do I create email processing rules?</h2>
|
|
|
371
|
+<div class="outline-text-2" id="text-orgheadline9">
|
|
352
|
372
|
<div class="org-src-container">
|
|
353
|
373
|
|
|
354
|
374
|
<pre class="src src-bash">ssh username@domainname -p 2222
|
|
|
@@ -406,9 +426,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
|
|
406
|
426
|
</p>
|
|
407
|
427
|
</div>
|
|
408
|
428
|
</div>
|
|
409
|
|
-<div id="outline-container-orgheadline9" class="outline-2">
|
|
410
|
|
-<h2 id="orgheadline9">Why isn't dynamic DNS working?</h2>
|
|
411
|
|
-<div class="outline-text-2" id="text-orgheadline9">
|
|
|
429
|
+<div id="outline-container-orgheadline10" class="outline-2">
|
|
|
430
|
+<h2 id="orgheadline10">Why isn't dynamic DNS working?</h2>
|
|
|
431
|
+<div class="outline-text-2" id="text-orgheadline10">
|
|
412
|
432
|
<p>
|
|
413
|
433
|
If you run the command:
|
|
414
|
434
|
</p>
|
|
|
@@ -476,9 +496,9 @@ http://httpbin.org/ip
|
|
476
|
496
|
</div>
|
|
477
|
497
|
</div>
|
|
478
|
498
|
|
|
479
|
|
-<div id="outline-container-orgheadline10" class="outline-2">
|
|
480
|
|
-<h2 id="orgheadline10">How do I change my encryption settings?</h2>
|
|
481
|
|
-<div class="outline-text-2" id="text-orgheadline10">
|
|
|
499
|
+<div id="outline-container-orgheadline11" class="outline-2">
|
|
|
500
|
+<h2 id="orgheadline11">How do I change my encryption settings?</h2>
|
|
|
501
|
+<div class="outline-text-2" id="text-orgheadline11">
|
|
482
|
502
|
<p>
|
|
483
|
503
|
Suppose that some new encryption vulnerability has been announced and that you need to change your encryption settings. Maybe an algorithm thought to be secure is now no longer so and you need to remove it. You can change your settings by doing the following:
|
|
484
|
504
|
</p>
|
|
|
@@ -495,9 +515,9 @@ Then select <i>Security Settings</i>. You will then be able to edit the crypto s
|
|
495
|
515
|
</p>
|
|
496
|
516
|
</div>
|
|
497
|
517
|
</div>
|
|
498
|
|
-<div id="outline-container-orgheadline11" class="outline-2">
|
|
499
|
|
-<h2 id="orgheadline11">How do I get a domain name?</h2>
|
|
500
|
|
-<div class="outline-text-2" id="text-orgheadline11">
|
|
|
518
|
+<div id="outline-container-orgheadline12" class="outline-2">
|
|
|
519
|
+<h2 id="orgheadline12">How do I get a domain name?</h2>
|
|
|
520
|
+<div class="outline-text-2" id="text-orgheadline12">
|
|
501
|
521
|
<p>
|
|
502
|
522
|
Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
|
|
503
|
523
|
</p>
|
|
|
@@ -565,9 +585,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
|
|
565
|
585
|
</div>
|
|
566
|
586
|
</div>
|
|
567
|
587
|
|
|
568
|
|
-<div id="outline-container-orgheadline12" class="outline-2">
|
|
569
|
|
-<h2 id="orgheadline12">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
|
570
|
|
-<div class="outline-text-2" id="text-orgheadline12">
|
|
|
588
|
+<div id="outline-container-orgheadline13" class="outline-2">
|
|
|
589
|
+<h2 id="orgheadline13">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
|
|
590
|
+<div class="outline-text-2" id="text-orgheadline13">
|
|
571
|
591
|
<p>
|
|
572
|
592
|
If you did the full install or selected the social variant then the system will have tried to obtain a Let's Encrypt certificate automatically during the install process. If this failed for any reason, or if you have created a new site which you need a certificate for then do the following:
|
|
573
|
593
|
</p>
|
|
|
@@ -588,9 +608,9 @@ One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS
|
|
588
|
608
|
</p>
|
|
589
|
609
|
</div>
|
|
590
|
610
|
</div>
|
|
591
|
|
-<div id="outline-container-orgheadline13" class="outline-2">
|
|
592
|
|
-<h2 id="orgheadline13">How do I renew a Let's Encrypt certificate?</h2>
|
|
593
|
|
-<div class="outline-text-2" id="text-orgheadline13">
|
|
|
611
|
+<div id="outline-container-orgheadline14" class="outline-2">
|
|
|
612
|
+<h2 id="orgheadline14">How do I renew a Let's Encrypt certificate?</h2>
|
|
|
613
|
+<div class="outline-text-2" id="text-orgheadline14">
|
|
594
|
614
|
<p>
|
|
595
|
615
|
Normally certificates will be automatically renewed once per month, so you don't need to be concerned about it. If anything goes wrong with the automatic renewal then you should receive a warning email.
|
|
596
|
616
|
</p>
|
|
|
@@ -611,9 +631,9 @@ Select <b>Security settings</b> then <b>Renew Let's Encrypt certificate</b>.
|
|
611
|
631
|
</p>
|
|
612
|
632
|
</div>
|
|
613
|
633
|
</div>
|
|
614
|
|
-<div id="outline-container-orgheadline14" class="outline-2">
|
|
615
|
|
-<h2 id="orgheadline14">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
|
616
|
|
-<div class="outline-text-2" id="text-orgheadline14">
|
|
|
634
|
+<div id="outline-container-orgheadline15" class="outline-2">
|
|
|
635
|
+<h2 id="orgheadline15">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
|
|
636
|
+<div class="outline-text-2" id="text-orgheadline15">
|
|
617
|
637
|
<p>
|
|
618
|
638
|
Most likely it's because Let's Encrypt doesn't support your particular domain or subdomain. Currently free subdomains tend not to work. You'll need to buy a domain name, link it to your dynamic DNS account and then do:
|
|
619
|
639
|
</p>
|
|
|
@@ -630,9 +650,9 @@ Select <b>Security settings</b> then <b>Create a new Let's Encrypt certificate</
|
|
630
|
650
|
</p>
|
|
631
|
651
|
</div>
|
|
632
|
652
|
</div>
|
|
633
|
|
-<div id="outline-container-orgheadline15" class="outline-2">
|
|
634
|
|
-<h2 id="orgheadline15">Why use self-signed certificates?</h2>
|
|
635
|
|
-<div class="outline-text-2" id="text-orgheadline15">
|
|
|
653
|
+<div id="outline-container-orgheadline16" class="outline-2">
|
|
|
654
|
+<h2 id="orgheadline16">Why use self-signed certificates?</h2>
|
|
|
655
|
+<div class="outline-text-2" id="text-orgheadline16">
|
|
636
|
656
|
<p>
|
|
637
|
657
|
Almost everywhere on the web you will read that self-signed certificates are worthless. They bring up <i>scary-scary looking</i> browser warnings and gurus will advise you not to use them. Self-signed certificates are quite useful though. What the scary warnings mean - and it would be good if they explained this more clearly - is that you have an encrypted connection established but there is <i>no certainty about who that connection is with</i>.
|
|
638
|
658
|
</p>
|
|
|
@@ -654,17 +674,17 @@ For now a self-signed certificate will probably in most cases protect your commu
|
|
654
|
674
|
</p>
|
|
655
|
675
|
</div>
|
|
656
|
676
|
</div>
|
|
657
|
|
-<div id="outline-container-orgheadline16" class="outline-2">
|
|
658
|
|
-<h2 id="orgheadline16">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
|
659
|
|
-<div class="outline-text-2" id="text-orgheadline16">
|
|
|
677
|
+<div id="outline-container-orgheadline17" class="outline-2">
|
|
|
678
|
+<h2 id="orgheadline17">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
|
|
679
|
+<div class="outline-text-2" id="text-orgheadline17">
|
|
660
|
680
|
<p>
|
|
661
|
681
|
<a href="http://seppuku.cryptostorm.org/">That pledge</a> is utterly worthless. Years ago people trusted Google in the same sort of way, because they promised not be be evil and because a lot of the engineers working for them seemed like honest types who were "<i>on our side</i>". Post-<a href="https://en.wikipedia.org/wiki/Nymwars">nymwars</a> and post-<a href="https://en.wikipedia.org/wiki/PRISM_(surveillance_program)">PRISM</a> we know exactly how much Google cared about the privacy and security of its users. But Google is only one particular example. In general don't trust pledges made by companies, even if the people running them seem really sincere.
|
|
662
|
682
|
</p>
|
|
663
|
683
|
</div>
|
|
664
|
684
|
</div>
|
|
665
|
|
-<div id="outline-container-orgheadline17" class="outline-2">
|
|
666
|
|
-<h2 id="orgheadline17">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
|
667
|
|
-<div class="outline-text-2" id="text-orgheadline17">
|
|
|
685
|
+<div id="outline-container-orgheadline18" class="outline-2">
|
|
|
686
|
+<h2 id="orgheadline18">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
|
|
687
|
+<div class="outline-text-2" id="text-orgheadline18">
|
|
668
|
688
|
<p>
|
|
669
|
689
|
Welcome to the world of email. Email is really the archetypal decentralized service, developed during the early days of the internet. In principle anyone can run an email server, and that's exactly what you're doing with Freedombone. Email is very useful, but it has a big problem, and that's that the protocols are totally insecure. That made it easy for spammers to do their thing, and in response highly elaborate spam filtering and blocking systems were developed. Chances are that your emails are being blocked in this way. Sometimes the blocking is so indisciminate that entire countries are excluded. What can you do about it? Unless you control the block list at the receiving end probably you can't do anything. There is zero accountability for such blocking, and you can't just contact someone and say "hey, I'm not a spammer". This system works well for the big internet companies because it effectively centralises email to a few well-known brand names and keeps any independent servers out.
|
|
670
|
690
|
</p>
|
Bob Mottram
9 年之前