netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: schwab@redhat.com
Cc: plaes@plaes.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IMAP through SSH tunnels stopped working in 2.6.35
Date: Wed, 16 Jun 2010 12:04:39 -0700 (PDT)	[thread overview]
Message-ID: <20100616.120439.104063332.davem@davemloft.net> (raw)
In-Reply-To: <m3ocfbjle2.fsf@hase.home>

From: Andreas Schwab <schwab@redhat.com>
Date: Wed, 16 Jun 2010 12:56:53 +0200

> Priit Laes <plaes@plaes.org> writes:
> 
>> I recently tried out 2.6.35-rc3 kernel (latest Linus's tree), where I
>> noticed that I couldn't access my IMAP accounts through ssh tunnel
>> anymore because connection timeouts. Things used to work in 2.6.34-rc7+.
> 
> See <https://bugzilla.kernel.org/show_bug.cgi?id=16188>.

Also "linux-netdev" does not exist, it's just plain "netdev" :-)

           reply	other threads:[~2010-06-16 19:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m3ocfbjle2.fsf@hase.home>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100616.120439.104063332.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=plaes@plaes.org \
    --cc=schwab@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).