From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Administrivia: (was Re: [linux-lvm] shit on the ml [was: fwd: hey its me again])
Date: Mon Aug 11 10:02:01 2003 [thread overview]
Message-ID: <20030811160123.L31325@uk.sistina.com> (raw)
In-Reply-To: <1060606467.3f3792035576a@secure.st-peter.stw.uni-erlangen.de>; from galia@st-peter.stw.uni-erlangen.de on Mon, Aug 11, 2003 at 02:54:27PM +0200
> > >>can we now please close the ml for public posts???
> well i don't like the spam too,
> but i think i dislike closed lists even more.
Same here - it would increase the 'nuisance factor' for list members
and increase the amount of work for the list admins.
The amount of spam sent to the list vastly exceeds the genuine email -
luckily for you, almost all the spam gets trapped and you don't see
it:-)
Unluckily for AJ and me, we *do* see it and have to look out for any
genuine messages that got trapped - such messages *do* get delayed.
We review the filters every so often - I've tightened them again today,
trying to take into account the spam that got through recently.
We don't get many false positives, but you can reduce the risk if you:
- Use properly-formatted headers
- Use meaningful and specific subject lines - words common in spam,
such as 'urgent' get trapped
- Avoid posting HTML
- Avoid attachments: post URLs instead; send patches in the main
message body, one patch per email
Also, make sure any vacation or anti-virus program you decide to use
is set up properly so it doesn't respond to mailing lists (e.g.
ignore messages with bulk 'Precedence' headers). Addresses that
generate automated messages back to the list/list owner/list admin
addresses get silently dropped from the list (short grace period).
[This includes MTA messages saying a message has been in some queue for
X hours and not yet delivered - turn these off for messages with bulk
precedence.]
Alasdair
--
agk@uk.sistina.com
prev parent reply other threads:[~2003-08-11 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 12:28 [linux-lvm] fwd: hey its me again bpac-proj
2003-08-09 2:01 ` [linux-lvm] shit on the ml [was: fwd: hey its me again] Steffen Koch
2003-08-11 7:36 ` Brian J. Murrell
2003-08-11 7:42 ` Jeff Layton
2003-08-11 7:55 ` Svetoslav Slavtchev
2003-08-11 10:02 ` Alasdair G Kergon [this message]
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=20030811160123.L31325@uk.sistina.com \
--to=agk@uk.sistina.com \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.