From: Flavio Visentin <THe_ZiPMaN@zipman.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu-devel digest getting wrongly marked as spam
Date: Mon, 24 Oct 2005 23:48:28 +0200 [thread overview]
Message-ID: <435D56AC.5080203@zipman.it> (raw)
In-Reply-To: <c10dbf450510241417u4899da8g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Phil Krylov wrote:
> Probably the digest includes real spam messages (which occur on the
> list regularly, especially from a spammer named "info" - could list
> administrator do something to stop it?)
Admin should stop posts from not subscribed people.
- --
Flavio Visentin
| \|||/
| @/0.0\@
| \ - /
+------------------oOOo---oOOo------------------
There are only 10 types of people in this world:
those who understand binary, and those who don't.
GPG Key: http://www.zipman.it/gpgkey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDXVasusUmHkh1cnoRAvUGAJ9Ji5qYOMGcB3iAakAER107jI8XBQCeP5i5
quIHD3pZi879P0+4FGeH3x0=
=zYGM
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-10-24 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 21:04 [Qemu-devel] Qemu-devel digest getting wrongly marked as spam Richard Neill
2005-10-24 21:17 ` Phil Krylov
2005-10-24 21:48 ` Flavio Visentin [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=435D56AC.5080203@zipman.it \
--to=the_zipman@zipman.it \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).