From: "Justin P. Mattock" <justinmattock@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Mihai Donțu" <mihai.dontu@gmail.com>,
"viresh kumar" <viresh.kumar@st.com>,
"Matti Aarnio" <matti.aarnio@zmailer.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Query: Patches break with Microsoft exchange server.
Date: Mon, 09 Aug 2010 14:56:40 -0700 [thread overview]
Message-ID: <4C607998.90509@gmail.com> (raw)
In-Reply-To: <1281389338.7143.32.camel@localhost>
On 08/09/2010 02:28 PM, David Woodhouse wrote:
> On Mon, 2010-08-09 at 21:15 +0300, Mihai Donțu wrote:
>>
>> Wait. I don't think we're on the same page here. I'm talking about message
>> signing (which does not require the receiving end to have any key - it's the
>> same plain text e-mail with a blob after it) while you refer to actually
>> encrypting the message. Mm? Or am I being extremely slow today? :-)
>
> Only when you assume that Exchange would pass signed messages without
> corrupting them. It really is that broken.
>
figured the encryption would be kind of a last resort situation..but if
it's that broken to where it wont pass it along without corrupting, then
the best solution is to figure out what Microsoft needs in terms of
encoding, i.e. is there a way to have the scanner scan but not throw
everything around after it scans.(if this is what it's doing)
Justin P. Mattock
next prev parent reply other threads:[~2010-08-09 21:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 6:07 Query: Patches break with Microsoft exchange server viresh kumar
2010-08-09 6:42 ` Justin P. Mattock
2010-08-09 6:55 ` viresh kumar
2010-08-09 7:32 ` Justin P. Mattock
2010-08-09 6:49 ` Uwe Kleine-König
2010-08-09 6:56 ` viresh kumar
2010-08-09 7:19 ` Valeo de Vries
2010-08-09 7:47 ` viresh kumar
2010-08-09 9:00 ` Valeo de Vries
2010-08-09 9:01 ` Matti Aarnio
2010-08-09 9:35 ` viresh kumar
2010-08-09 9:43 ` Justin P. Mattock
2010-08-09 14:35 ` Mihai Donțu
2010-08-09 17:55 ` Justin P. Mattock
2010-08-09 18:15 ` Mihai Donțu
2010-08-09 18:53 ` Justin P. Mattock
2010-08-09 21:28 ` David Woodhouse
2010-08-09 21:56 ` Justin P. Mattock [this message]
2010-08-09 22:12 ` Valeo de Vries
2010-08-09 22:24 ` Justin P. Mattock
2010-08-11 14:05 ` Geert Uytterhoeven
2010-08-10 9:22 ` Gadiyar, Anand
2010-08-10 9:26 ` viresh kumar
2010-08-09 10:02 ` David Woodhouse
2018-06-19 20:42 ` Willy Tarreau
2010-08-09 14:19 ` Richard Cochran
2010-08-09 14:34 ` Valeo de Vries
2010-08-10 22:04 ` Felipe Contreras
2010-08-11 7:01 ` viresh kumar
2010-08-11 10:11 ` Valeo de Vries
2010-08-11 10:53 ` viresh kumar
2010-08-11 11:38 ` Wouter Simons
2010-08-11 13:33 ` Justin P. Mattock
2010-08-11 15:46 ` Jeffrey Hundstad
2010-08-11 15:58 ` David Woodhouse
2010-08-11 16:16 ` Jeffrey Hundstad
2010-08-11 16:18 ` Avery Pennarun
2010-08-11 16:30 ` David Woodhouse
2010-08-11 16:39 ` Avery Pennarun
2010-08-12 4:41 ` viresh kumar
2010-08-16 1:02 ` Gururaja Hebbar K R
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=4C607998.90509@gmail.com \
--to=justinmattock@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=mihai.dontu@gmail.com \
--cc=viresh.kumar@st.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).