public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kenneth Wolcott <kennethwolcott@gmail.com>
To: cygwin@cygwin.com
Subject: Re: trouble posting to cygwin-apps
Date: Fri, 08 Oct 2010 19:27:00 -0000	[thread overview]
Message-ID: <AANLkTi=BG-i6kKPUZQwYNMkTjNJGU2nfaoB0f=3n2=km@mail.gmail.com> (raw)
In-Reply-To: <1286518842.1832.42.camel@OG3>

2010/10/7 SZABÓ Gergely <szg@subogero.com>:
> Hello,
>
> The mailing list does not accept html email, that's fair enough.
>
> The real problem is, it also bounces every email with a company
> disclaimer about intentions and original addressees.
>
> Well, the original addressee is cygwin at cygwin dot com, which is a public
> mailing list, readable even from Alpha Centauri (with 4 years delay).
>
> This policy is OK for most FOSS projects, but Cygwin should be an
> exception. I think Cygwin is used most by 3PPs within big companies
> where everybody _must_ use Windows and those disclaimers are always attached to
> outgoing mail. If you are a free and sane person, attracted to unixy stuff,
> you'd probably use Linux.
>
> Yes, I've read the posting instructions, and I know I should convince my
> employer to remove the disclaimers. What chance do you think I have to
> convince a 20000-employee company, where central IT is not even in my
> country? They also restrict access to private email from the office.
>
> I know, I should leave them and/or buy a smartphone for emailing. :-)
>
> But my point is: the mailing list is cut off from its most important
> audience.
>
> Best regards
> Gergely

IMNSHO:  Solution: Subscribe to the list and post to the list using a
non-company email address.

  The only downside I can think of is where the management does not
allow you to use non-company email or application to access a
non-company email address.

Ken Wolcott

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2010-10-08 19:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  6:20 SZABÓ Gergely
2010-10-08 13:52 ` Eric Blake
2010-10-08 15:41 ` Christopher Faylor
2010-10-08 19:27 ` Kenneth Wolcott [this message]
2010-10-11  8:01   ` Csaba Raduly
2010-10-11  8:12     ` SZABO Gergely
  -- strict thread matches above, loose matches on Subject: below --
2010-10-08 14:20 SZABO Gergely
2010-10-07 21:57 Gregg Levine
2010-10-07 22:16 ` Christopher Faylor
2010-10-08 13:05   ` Bill Hoffman
2010-10-04 20:33 Bill Hoffman
2010-10-05  8:07 ` Corinna Vinschen
2010-10-05 12:29   ` Bill Hoffman
2010-10-05 15:32     ` Corinna Vinschen
2010-10-05 20:46 ` Charles Wilson
2010-10-05 21:29   ` Bill Hoffman
2010-10-05 21:47     ` Marco Atzeri
2010-10-05 21:51     ` Yaakov (Cygwin/X)
2010-10-05 22:13       ` Bill Hoffman
2010-10-07  6:21         ` Yaakov (Cygwin/X)
2010-10-07 12:54           ` Bill Hoffman
2010-10-07 21:45 ` Christopher Faylor

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='AANLkTi=BG-i6kKPUZQwYNMkTjNJGU2nfaoB0f=3n2=km@mail.gmail.com' \
    --to=kennethwolcott@gmail.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).