Original Message
Subject: ESMTP Filtering by 46.166.163.163
Date: Wed, 30 Jan 2013 18:57:53 +0100
From: Moritz Bartl
To: ab...@santrex.net
Hi,
Your customer at 46.166.163.163 runs a Tor exit relay (hooray! great!).
The server should be configured in a way that does NOT tamper w
Moritz Bartl wrote
Tue, 29 Jan 2013 16:54:58 +0100:
| I finally deployed Munin across our exit nodes. The graphs are currently
| public, and I don't see an obvious reason for not doing that. Any
| objections?
|
| https://www.torservers.net/munin/
Thanks, that's interesting data.
FWIW, DFRI pub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 31 Jan 2013 13:34:13 +0100
Norman Rieß wrote:
> Hello,
>
> i have no suggestion, but i am seeing the same thing on my relay.
>
> https://atlas.torproject.org/#details/5A58FB3D0858148D4F4727AAC71B0D67F0903323
>
> Would be nice to know what
On Thu, 31 Jan 2013 10:21:42 +
Matthew Harrold wrote:
> I have ran a couple of Tor Relays now for a few months, one was steady and
> reliable, and providing about 2MB/s of bandwidth. Of late, its slowed down
> dramatically. A reboot resolved it temporarily, but its slowed right down
> again,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 31.01.2013 11:21, schrieb Matthew Harrold:
> Hello all.
>
> I have ran a couple of Tor Relays now for a few months, one was
> steady and reliable, and providing about 2MB/s of bandwidth. Of
> late, its slowed down dramatically. A reboot resolved it
Hello all.
This is my first time using a mailing list, so apologies if Im not doing it
right!
I have ran a couple of Tor Relays now for a few months, one was steady and
reliable, and providing about 2MB/s of bandwidth. Of late, its slowed down
dramatically. A reboot resolved it temporarily, but i
