From: Lute Kamstra <Lute.Kamstra.news@xs4all.nl>
Subject: Re: Status of bugs@gnus.org.
Date: Tue, 21 Jun 2005 10:11:44 +0200 [thread overview]
Message-ID: <87ll54b03j.fsf@xs4all.nl> (raw)
In-Reply-To: <877jgp5h0f.fsf@orebokech.com> (Romain Francoise's message of "Mon, 20 Jun 2005 14:50:40 +0200")
Romain Francoise <romain@orebokech.com> writes:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> Since then, the spam/ham ration even got worse and it's not good when
>> bug reports remain unprocessed because of this.
>
> If you have enough courage, you can cancel the spam in there. I used to
> do it but gave up after a few months when I realized that a default
> installation of SpamAssassin would have caught 99% of what I was
> expiring manually. My time is better spent elsewhere...
Plus, when you're removing so much spam manually, you tend to get
bored/tired and start to make mistakes. Once, a valid bug report of
mine got canceled.
Lute.
--
(spook) => "MD2 MDA Ceridian"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")
prev parent reply other threads:[~2005-06-21 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 9:03 Lute Kamstra
2005-06-20 12:38 ` Reiner Steib
2005-06-20 12:50 ` Romain Francoise
2005-06-21 8:11 ` Lute Kamstra [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=87ll54b03j.fsf@xs4all.nl \
--to=lute.kamstra.news@xs4all.nl \
/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).