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:14:59 +0400	[thread overview]
Message-ID: <87ob4mo80c.fsf@lpt00.freehck.ru> (raw)
In-Reply-To: <8738lzt9r5.fsf@topper.koldfront.dk>


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

asjo@koldfront.dk (Adam Sjøgren) writes:

> Dmitrii Kashin <freehck@freehck.ru> writes:
>
>> And of course this is not a good practice to use gnus for sorting your
>> mail. It is very slow and local-only.
>
> What works horribly for you may very well work great for the next guy.

This was not emotions. I've specifically got rather definite claims. 2
years ago I got and spitted mail by gnus. And... First of all, this was
very slow while downloading big attachments. And I needed to wait for a
very long time in order to continue reading mail. Secondly, it was good
to me only until I bought a second computer (laptop). How would you
manage mail if you could do it only with one of you computers? And what
did I need the second computer for in this case? For all except
communication?

Now I get mail via imap sorting it on server side by sieve. For most
mailing lists I use gmane transport, and for all of my rss I use gwene.
In comparison with nnmail and nnrss this works supersonic and in
background, by the way.

If I did everything right in the beginning, I would not spend so much
time for reorganization of my mailing system.

> Using Gnus to split my email has served me great for the past 15+ years,
> and I think it is a perfectly fine practice.

I would like to know how you solved the problems with speed described
above.

[-- 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:14 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 [this message]
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
     [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=87ob4mo80c.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).