From: Larry Hynes <larry@larryhynes.com>
To: zsh-workers@zsh.org
Subject: zsh mailing list spam
Date: Fri, 22 Jan 2016 00:05:33 +0000 (UTC) [thread overview]
Message-ID: <n7rrod$ghp$1@ger.gmane.org> (raw)
Hullo
Does anyone else find that the levels of spam on zsh users/devel
lists are kinda high? I think so, in comparison to other lists.
I'm assuming that ezmlm is being used to manage the lists. If it
is, maybe ezmlm-reject[1] could be deployed to - at a minimum -
remove messages whose "Subject:" lines include the likes of "You
have a new fax" and "Goodbye from our newsletter" and some other
notable repeat offenders.
Is there any appetite among those 'in charge' here to tackle
this?
I'm very happy to help, either by compiling data for
ezmlm-reject to use based on list spam or looking into other
solutions. (I just found mention of ezmlm-reject during a search
for 'ezmlm spam', maybe it's not part of a 'default', or the
zsh, installation?)
[1] http://untroubled.org/ezmlm/man/man1/ezmlm-reject.1.html
reply other threads:[~2016-01-22 0:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='n7rrod$ghp$1@ger.gmane.org' \
--to=larry@larryhynes.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).