From: Jonathan Larmour <jifl@jifvik.org>
To: overseers@sourceware.org
Subject: Re: questions about blocking disclaimers
Date: Sun, 05 Aug 2007 22:16:00 -0000 [thread overview]
Message-ID: <46B64C27.102@jifvik.org> (raw)
In-Reply-To: <20070805184604.GA14471@ednor.casa.cgf.cx>
Christopher Faylor wrote:
> On Sun, Aug 05, 2007 at 01:34:29AM -0400, Christopher Faylor wrote:
>> As many people know, I'm working on modifying the spam filter software
>> so that it will block email which contains unenforceable company
>> disclaimers. I've been surveying the archives for samples of
>> disclaimers to seed the spam blocking regex. I'd like to be able to
>> include the match that triggered the disclaimer bounce so that people
>> can see what is causing the problem but that may increase the size
>> of the bounce. Is that ok, though?
>>
>> Here's what I have for the bounce message right now:
My only thought is that this might be sudden and dramatic for some people,
who may find it difficult to remove them. Can it temporarily accept the
message (with a warning that they will be rejected entirely soon), and
after a month, we change it so we do reject them?
Out of interest I have had long arguments in my workplace about such
disclaimers, and it has been alleged that EU Data Protection law (as
applied in the UK at least) pretty much requires that any mail sent from a
business (including any employees) has to include them. It was a hard fight
to prevent them being added to all our email, and allegedly omitting them
is being done at some risk to the company directors. I doubt this should
change the policy, but it does show that the only solution people may have
is not to post from their work at all, so giving them time to arrange an
alternative would some reasonable.
I think the text of the bounce is fine (for when things do get dropped).
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2007-08-05 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 5:34 Christopher Faylor
2007-08-05 18:45 ` Christopher Faylor
2007-08-05 22:16 ` Jonathan Larmour [this message]
2007-08-05 23:54 ` Christopher Faylor
2007-08-06 10:34 ` Jonathan Larmour
2007-08-06 13:28 ` Ian Lance Taylor
2007-08-06 13:38 ` Daniel Berlin
2007-08-06 14:33 ` Gerald Pfeifer
2007-08-06 14:36 ` Jonathan Larmour
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=46B64C27.102@jifvik.org \
--to=jifl@jifvik.org \
--cc=overseers@sourceware.org \
/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).