From: David Woodhouse <dwmw2@infradead.org>
To: Bzzzz <lazyvirus@gmx.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Can't seem to split tunnel using tables the way I can in OpenVPN
Date: Thu, 25 May 2017 20:50:14 +0100 [thread overview]
Message-ID: <1495741814.5454.22.camel@infradead.org> (raw)
In-Reply-To: <20170525214551.4b602d80@msi.defcon1>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Thu, 2017-05-25 at 21:45 +0200, Bzzzz wrote:
> On Thu, 25 May 2017 20:32:01 +0100
> David Woodhouse <dwmw2@infradead.org> wrote:
>
> > Why do you think that's strange? Your mail client will have two
> 'reply'
> > buttons — one for a private reply, and another for a public/group
> reply
> > or "reply-all".
>
> I use claws-mail, it has 3 answers possibilities: all/sender/ML,
> the strange thing is:
> if I hit 'all', it answer… all (quite normal until here),
> but if I hit 'ML', it only answers to your e-mail address !
>
> What is weird is the ML seems to be put in CC when it should stay the
> main receiver.
>
> I'm using Debian stable+backports, claws-mail is from backports, may
> be it has a bug, however answering every other ML has the right
> behavior.
The list doesn't have the RFC2369 List-Post: header which would allow
the 'Reply to List' option to work.
But that's OK because I just explained to you why it's anti-social and
shouldn't be used anyway.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
next prev parent reply other threads:[~2017-05-25 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 23:04 Text Editor
2017-05-25 17:13 ` Bzzzz
2017-05-25 17:58 ` Kalin KOZHUHAROV
2017-05-25 18:11 ` Bzzzz
2017-05-25 19:14 ` Kalin KOZHUHAROV
2017-05-25 19:28 ` Bzzzz
2017-05-25 19:32 ` David Woodhouse
2017-05-25 19:45 ` Bzzzz
2017-05-25 19:50 ` David Woodhouse [this message]
2017-05-25 20:03 ` Bzzzz
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=1495741814.5454.22.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=lazyvirus@gmx.com \
--cc=wireguard@lists.zx2c4.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).