From: Trevor Woerner <mips082-nospam@vtnet.ca>
To: linux-mips@linux-mips.org
Subject: mailing list spam
Date: Fri, 3 Oct 2003 16:09:07 -0400 [thread overview]
Message-ID: <200310031609.07289.mips082-nospam@vtnet.ca> (raw)
I appreciate microsoft *.exe updates by email just as much as the next
guy, however...
I create email aliases for the different mailing lists I join. I
noticed that I've been receiving a fair amount of spam to the email
address I setup for this list. I figured it was because I posted
something in the past, so I unsubscribed my old email address, created
a new one, and re-subscribed.
Without having made any postings since the change, I have just received
spam to the new address I've setup for this list, which means someone
has access to the membership list. Any chance this could be looked into
and turned off?
The humorous part being, of course, how stringently the the list
receiver is that the sender's email domain resolve properly. At least
we know it's dns-resolvable spam!
next reply other threads:[~2003-10-03 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 20:09 Trevor Woerner [this message]
2003-10-04 2:15 ` mailing list spam Keith Owens
2003-10-04 14:34 ` Ralf Baechle
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=200310031609.07289.mips082-nospam@vtnet.ca \
--to=mips082-nospam@vtnet.ca \
--cc=linux-mips@linux-mips.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