Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Dmitrii Kashin <freehck@freehck.ru>
To: info-gnus-english@gnu.org
Subject: Re: Spam despite spam header
Date: Thu, 12 Dec 2013 11:27:50 +0400	[thread overview]
Message-ID: <87k3fao7ex.fsf@lpt00.freehck.ru> (raw)
In-Reply-To: <871u1jhvb2.fsf@nl106-137-194.student.uu.se>


[-- Attachment #1.1: Type: text/plain, Size: 1723 bytes --]

Emanuel Berg <embe8573@student.uu.se> writes:

> Dmitrii Kashin <freehck@freehck.ru> writes:
>
>>> You mean like this?
>>>
>>> (setq nnmail-split-methods
>>>       '(("spam" "^X-Spam-Flag: YES")
>>>         ("mail.misc" "") ))
>>>
>>> I hope I won't get them in a directory called "spam",
>>> now!
>>
>> Can't you have it unsubscribed?
>
> I don't know. How would I do that, and what would it do?

By pressing 'u' in the group buffer.

>> Certainly, you can solve this problem another
>> way. What do you think about scoring?
>
> I never understood scoring. I know there is an entire
> chapter on that in the Gnus manual so I should probably
> look into it. But the groups I'm on: gnu.emacs.help,
> gnu.emacs.gnus, and some others - they don't carry that
> much traffic anyway. So I thought it would be overkill
> to implement scoring. But I don't know. I use a KILL
> file to get rid of trolls.

Gnus prefers to hide articles that doesn't seem to be
interesting. There's no difference between nntp groups and 'mail
groups'. You can use scoring in both. Score is a number you add to the
article to show its 'importance level'. If score is high article will be
bold. If it's low article will be marked as read automatically. If it's
too low then article will expire (will be hided at all).

>> And of course this is not a good practice to use gnus
>> for sorting your mail. It is very slow and
>> local-only.
>
> Like I said, I don't have those kinds of volumes so
> speed isn't an issue. I prefer to have my mails local
> on the disk - one mail per file, so I can search them
> with the Unix batch tools.

You decide. As I've already written: if I've foreseen such a pile of
correspondence I would not reorganize it later.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2013-12-12  7:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 16:13 Emanuel Berg
2013-12-11 18:11 ` Adam Sjøgren
     [not found] ` <mailman.8951.1386785526.10748.info-gnus-english@gnu.org>
2013-12-11 19:21   ` Emanuel Berg
2013-12-11 20:04     ` Dmitrii Kashin
2013-12-11 20:26       ` Adam Sjøgren
2013-12-12  7:14         ` Dmitrii Kashin
2013-12-12  9:22           ` Peter Münster
2013-12-12 15:27             ` Dmitrii Kashin
2013-12-23 17:03           ` Adam Sjøgren
     [not found]           ` <mailman.10164.1387818251.10748.info-gnus-english@gnu.org>
2013-12-24 19:58             ` Emanuel Berg
     [not found]       ` <mailman.8965.1386793822.10748.info-gnus-english@gnu.org>
2013-12-11 22:42         ` Emanuel Berg
2013-12-11 20:22     ` Adam Sjøgren
     [not found]     ` <mailman.8961.1386792309.10748.info-gnus-english@gnu.org>
2013-12-11 22:33       ` Emanuel Berg
2013-12-12  7:27         ` Dmitrii Kashin [this message]
     [not found]         ` <mailman.8994.1386833301.10748.info-gnus-english@gnu.org>
2013-12-12 20:03           ` Emanuel Berg
     [not found]     ` <mailman.8964.1386793377.10748.info-gnus-english@gnu.org>
2013-12-11 22:40       ` Emanuel Berg
2013-12-12 23:35       ` Emanuel Berg
2013-12-13  9:13         ` Adam Sjøgren

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=87k3fao7ex.fsf@lpt00.freehck.ru \
    --to=freehck@freehck.ru \
    --cc=info-gnus-english@gnu.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).