From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: From Gnus to mu4e
Date: Thu, 27 Aug 2015 14:58:16 +0200 [thread overview]
Message-ID: <20150827125816.GA30233@chitra.no-ip.org> (raw)
In-Reply-To: <87a8tezf7x.fsf@free.fr>
On Wed, Aug 26, 2015 at 09:22:26AM +0200, Julien Cubizolles wrote:
>
> I have a few questions about some details of your setup:
>
> + regarding filtering and spam detection, do you rely on the
> possibilities offered by you mail provider (Gmail or other)?
I don't know about Bastien, but for me, since I use Gmail I heavily rely
on both filtering and spam detection. I use Gmails filtering eventhough
it is a bit clunky to avoid setting up something on my end; I find it
simpler this way. And the spam detection, I find Gmail's spam detection
to be very good, specially when you have been training it for a few
years by reporting spam and phishing messages, as appropriate.
> + you said you're running Dovecot. Gnus could also directly access the
> local maildir without a local imap server the way mu4e does, couldn't
> it ? What's the benefit of running it ?
Probably Bastien has more up to date comments, but last time I looked, I
found Gnus's support for maildir rather poor. There were a few issues,
it didn't respect the usual maildir flags and stored its own flags
withing the maildir. So along with incorrect flag, the mail store took
about ~70% more disk space. It was also a bit slow, despite everything
being local. My impression is based on the status from about 2-3 years
back, so things might have improved a lot by now.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2015-08-27 12:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:23 From Gnus to mu4e Julien Cubizolles
2015-08-21 10:28 ` Julien Cubizolles
2015-08-21 10:49 ` Colin Yates
2015-08-21 13:06 ` Suvayu Ali
2015-08-26 6:53 ` Julien Cubizolles
2015-08-25 5:49 ` Bastien
2015-08-25 6:28 ` Ian Zimmerman
2015-08-25 6:56 ` Bastien Guerry
2015-08-26 7:22 ` Julien Cubizolles
2015-08-27 12:50 ` Rainer M Krug
2015-08-27 17:15 ` Bastien
2015-08-28 8:39 ` Rainer M Krug
2015-08-28 8:44 ` Bastien
2015-08-28 8:51 ` Rainer M Krug
2015-08-28 8:58 ` Rasmus
2015-08-28 9:15 ` Julien Cubizolles
2015-08-28 10:03 ` Rainer M Krug
2015-08-28 10:08 ` Rasmus
2015-08-28 10:41 ` Rainer M Krug
2015-08-28 10:04 ` Rasmus
2015-08-28 8:51 ` Bastien
2015-08-27 21:27 ` Julien Cubizolles
2015-08-27 23:34 ` Suvayu Ali
2015-08-27 23:50 ` Ian Zimmerman
2015-08-28 0:14 ` Suvayu Ali
2015-08-28 0:24 ` Ian Zimmerman
2015-08-28 8:25 ` Rainer M Krug
2015-08-28 9:06 ` Suvayu Ali
2015-08-28 15:31 ` Ian Zimmerman
2015-08-31 0:16 ` Suvayu Ali
2015-08-28 8:21 ` Rainer M Krug
2015-08-27 12:58 ` Suvayu Ali [this message]
2015-08-27 15:52 ` Glenn Morris
2015-08-27 17:32 ` Suvayu Ali
2015-08-27 17:11 ` Bastien
2015-08-27 17:08 ` Bastien
2015-08-27 17:30 ` Suvayu Ali
2015-08-27 21:52 ` Julien Cubizolles
2015-08-27 22:18 ` Bastien
2015-08-27 23:30 ` Julien Cubizolles
[not found] <mailman.14.1440105837.31004.help-gnu-emacs@gnu.org>
2015-08-24 11:19 ` Joost Kremers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150827125816.GA30233@chitra.no-ip.org \
--to=fatkasuvayu+linux@gmail.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).