From: justinmattock@gmail•com (Justin P. Mattock)
To: linux-arm-kernel@lists•infradead.org
Subject: Query: Patches break with Microsoft exchange server.
Date: Mon, 09 Aug 2010 10:55:08 -0700 [thread overview]
Message-ID: <4C6040FC.2020702@gmail.com> (raw)
In-Reply-To: <201008091735.11105.mihai.dontu@gmail.com>
On 08/09/2010 07:35 AM, Mihai Don?u wrote:
> On Monday 09 August 2010 12:43:16 Justin P. Mattock wrote:
>> On 08/09/2010 02:35 AM, viresh kumar wrote:
>>> On 8/9/2010 2:31 PM, Matti Aarnio wrote:
>>>> On Mon, Aug 09, 2010 at 12:26:24PM +0530, viresh kumar wrote:
>>>>>> I missed this information in my last mail. We are using git send-email
>>>>>> for sending patches. As patches will go through Microsoft exchange
>>>>>> server only, so they are broken.
>>>>
>>>> Let your boss complain to your IT keepers.
>>>> "These are Machine-to-Machine messages, they must not be modified!"
>>>>
>>>>
>>>> It would probably be "against corporate policy" to use gmail for these
>>>> emails...
>>>
>>> We got one solution: Upgrade Exchange server to SP2.
>>> Lets see if our IT department does this upgradation.
>>
>> that or just blast them with some cryptology..i.e. pretty sure if your
>> message was encapsulated(AH/ESP) they couldn't tweak it.. but then
>> sending such encryption to a public list would require a _key_ on the
>> other side.. wishful thinking...
>> (just a thought)...
>
> Shouldn't just signing the message be enough? The server (normally) would not
> alter it, otherwise it will break the signature (which is a too obvious bug
> even for Microsoft). Or am I missing something here?
>
> PS: A local SMTP with DKIM signing capabilities could be another possibility,
> assuming Exchange does not break such signatures.
>
yeah that would probably be just enough to get through without Microsoft
mucking around with the font etc.., but the biggest problem(I see) with
the encryption is having the key on the other end of the line.
Justin P. Mattock
next prev parent reply other threads:[~2010-08-09 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:23 Query: Patches break with Microsoft exchange server viresh kumar
2010-08-09 14:19 ` Richard Cochran
2010-08-10 22:04 ` Felipe Contreras
2010-08-11 7:01 ` viresh kumar
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 0:32 ` Gururaja Hebbar K R
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` Uwe Kleine-König
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:26 ` Matti Aarnio
2018-06-19 20:26 ` viresh kumar
2010-08-10 9:22 ` Gadiyar, Anand
2010-08-10 9:26 ` viresh kumar
2018-06-19 20:26 ` Justin P. Mattock
2010-08-09 14:35 ` Mihai Donțu
2010-08-09 17:55 ` Justin P. Mattock [this message]
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
2010-08-11 14:05 ` Geert Uytterhoeven
2018-06-19 20:26 ` David Woodhouse
2018-06-19 20:42 ` Willy Tarreau
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=4C6040FC.2020702@gmail.com \
--to=justinmattock@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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