[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [Interoperability] Tor and GNU Anubis

To: "Daniel S. Haischt" <or-talk@xxxxxxxxxxxxx>
Subject: Re: [Interoperability] Tor and GNU Anubis
From: Roman Mamedov <rm@xxxxxxxxxxxxxxxxxx>
Date: Fri, 7 Jan 2005 23:08:50 +0500
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Fri, 07 Jan 2005 13:09:46 -0500
In-reply-to: <41DECC87.2030300@daniel.stefan.haischt.name>
Organization: http://www.distributed.org.ru/
References: <41DECC87.2030300@daniel.stefan.haischt.name>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Daniel!

> remote-mta 217.9.16.16:25 # -> Mail server of my ISP
> socks-proxy 127.0.0.1:9050 # -> Tor instance
socks-v4 no # ->> GNU Anubis should talk SOCKS 5

Your ISP's mail server probably denies all connections which are from
outside its own network (and rightly so). And guess where the
Torrified connection to the provider's SMTP server comes from? Right,
from one of the Tor exit nodes, which of course is not within your
provider's smtp server's allowed IP range.

With respect,
 Roman

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0.2
Comment: ""

iQA/AwUBQd7QNzYPVt5xCkCcEQK5swCfSv+zWSPCbfjOzZ4nU7MIaofZir8Anjn1
6NJKLWdzWBEEFapVLRLtAEYd
=GVuH
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: [Interoperability] Tor and GNU Anubis
  - From: Daniel S. Haischt

References:
- [Interoperability] Tor and GNU Anubis
  - From: Daniel S. Haischt

Prev by Author: Re: http status 403 (unapproved server) response from dirserver
Next by Author: Re: Hardware requirements for a tor server
Previous by thread: [Interoperability] Tor and GNU Anubis
Next by thread: Re: [Interoperability] Tor and GNU Anubis
Index(es):
- Author
- Thread