Query: Patches break with Microsoft exchange server.
in [Kernel]
|
Prev: [RFC PATCH 1/2] debug_core: move all watch dog syncs to a single function
Next: x86: remove __phys_reloc_hide
From: David Woodhouse on 9 Aug 2010 06:10 On Mon, 2010-08-09 at 12:01 +0300, Matti Aarnio wrote: > It would probably be "against corporate policy" to use gmail for these > emails... If that's the case, then you really *do* need to get your boss to fix it. If the company provides a working email account, it makes a certain amount of sense for them to ask you to use it. But if all they provide is Microsoft Exchange, that's insane -- what Exchange provides is *like* email, but it is *not* email. Once you start trying to use it for real email, you find it's broken by design in a large number of ways. It makes no sense for them to require that you use Exchange for Internet email, because that's not what Exchange does. If my corporate overloads told me I had to use my Exchange "messaging" account for external email communication, they would get a quite clear 'no' in response. My response may also contain suggestions that they use certain other objects for purposes for which they were not designed. Seriously, just use an external email account and ignore the broken corporate policy. 'Policy' is just a euphemism for not having to think for yourself. -- dwmw2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Richard Cochran on 9 Aug 2010 10:20 On Mon, Aug 09, 2010 at 11:37:33AM +0530, viresh kumar wrote: > > Has anybody found a solution to this kind of issues? Are there any > workarounds possible? I have this same problem. The exchange server rewrites incoming and outgoing plain text emails as it sees fit, and our IT department seems unable to turn this "feature" off. One work around is to get an gmail account and use IMAP. Good luck, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Valeo de Vries on 9 Aug 2010 10:40 On 9 August 2010 15:19, Richard Cochran <richardcochran(a)gmail.com> wrote: > On Mon, Aug 09, 2010 at 11:37:33AM +0530, viresh kumar wrote: >> >> Has anybody found a solution to this kind of issues? Are there any >> workarounds possible? > > I have this same problem. The exchange server rewrites incoming and > outgoing plain text emails as it sees fit, and our IT department seems > unable to turn this "feature" off. > > One work around is to get an gmail account and use IMAP. The other solution is to kindly request that one's IS department upgrades Exchange so that this particular issue (of converting tabs to spaces) won't be a problem any longer... ;) You're right though, it's probably easier just to use another provider for e-mail, as this isn't the only way Exchange will mess with patches. Valeo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Mihai Donțu on 9 Aug 2010 10:40 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. -- Mihai Donțu -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin P. Mattock on 9 Aug 2010 14:00
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |