public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Creating a valid bmp file
Date: Tue, 06 Nov 2007 07:37:46 -0500	[thread overview]
Message-ID: <4730601A.7080101@ge.com> (raw)
In-Reply-To: <20071106063727.7729B249E7@gemini.denx.de>

Wolfgang Denk wrote:
> In message <OF870B63B5.7D50724B-ON8525738A.00768F45-8525738A.00770EE3@orbital.com> you wrote:
>> NOTE: just disregard the legalese attached to this message, if you are
>> reading this... odds are you should be reading this.
> 
> No, we cannot ignore this. By posting such a  message  to  a  mailing
> list  which gets internationally distributed without restrictions you
> are violating your own company's regulations, and we are supposed  to
> report you for that to your managemen.
> 
> Please turn this off. If necessary, use a different mail account  for
> posting to mailing lists.
> 
> Best regards,
> Wolfgang Denk

Dear Wolfgang,

While I agree with you in principle and believe that those disclaimers 
are a bunch of worthless drivel (and I cannot see how they possibly 
could be useful from a legal standpoint), I have to empathize with Roger.

In big companies those disclaimers are auto-attached to all email 
(!!!inside!!! as well as outside).  Not only that, but many companies 
(my own included) block access to all of the common "free" email 
services (gmail, yahoo, juno, etc.).  The only alternative is to not 
subscribe to the list at work, which would hurt information flow on the 
u-boot list.

In my case, it is only an oversight by the IT department that this email 
doesn't have a stupid pseudo-legal disclaimer on it - the mail handling 
path I use bypasses the primary corporate Exchange servers.  I would not 
be surprised if this bypass goes away in a matter of months as a side 
effect of our cutover of our IT resources to our new overlords.

By the way, the disclaimer drivel is very likely part of the Microsoft 
conspiracy to allow self-important idiots to control vital company 
resources - I suspect Exchange is involved in most, if not all, of the 
disclaimer attachment crimes.  Note that the people that control these 
disclaimers are the same ones that habitually send 500KB-2.2MB Word 
documents as attachments... said 500KB document containing *one page* of 
actual text.

Best regards,
gvb

P.S. Years ago, when the stupid disclaimers became the rage and one was 
implemented locally, I noticed that IT was smart enough to not put 
second and third disclaimers on email replies (we've since lost even 
that minimal level of intelligence).  I experimented and found that they 
implemented keyword matching to trigger the disclaimer or not.  As a 
result, I was able to put my own cut down version that was about half 
the size of the original (and made twice as much sense ;-). 
Unfortunately, eventually the IT department caught on, probably as a 
result of bounces, and switched to a full match, making my subterfuge 
ineffective. :-/

  reply	other threads:[~2007-11-06 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 21:19 [U-Boot-Users] Creating a valid bmp file Roger Williamson
2007-10-25 23:38 ` Detlev Zundel
2007-11-05 21:40   ` Roger Williamson
2007-11-05 22:15     ` Jerry Van Baren
2007-11-06  6:37     ` Wolfgang Denk
2007-11-06 12:37       ` Jerry Van Baren [this message]
2007-11-06 12:08     ` Clemens Koller

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=4730601A.7080101@ge.com \
    --to=gerald.vanbaren@ge.com \
    --cc=u-boot@lists.denx.de \
    /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