On Wed, Jun 13, 2012 at 08:03:46PM +0300, Maxim Kammerer wrote:
On Wed, Jun 13, 2012 at 4:46 PM, anonym ano...@lavabit.com wrote:
Yup. I've opened bugs/claws_with_torsocks_leaks_hostname to track this
issue.
This is possibly not a bug with torsocks, but a result of its extended
We have a regression here. EHLO/HELO messages leaks the hostname
('amnesia'), resulting in '*@amnesia' Message IDs, and 'amnesia' in
the last Received field. I managed to track down the culprit: torsocks.
We start claws-mail with torify, which uses torsocks over tsocks.
Switching back to
06/13/2012 03:01 PM, intrigeri:
We have a regression here. EHLO/HELO messages leaks the hostname
('amnesia'), resulting in '*@amnesia' Message IDs, and 'amnesia' in
the last Received field. I managed to track down the culprit: torsocks.
We start claws-mail with torify, which uses torsocks over
Hi,
Today I've been testing (what I thought was) the final 0.12 build, but
beyond the usual minor annoyances that I've been reporting for a few
releases now there's a regression with Claws Mail (see below). I suppose
this could be called a blocker, but I'd like input on it. No matter what
this
On Tue, Jun 12, 2012 at 07:21:36PM +0200, anonym wrote:
# Claws
* Check that the profile works and is torified (specifically the
EHLO/HELO SMTP messages it sends). Send an email using Claws and a
non-anonymizing SMTP relay. Then check that email's headers once
received,
