Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: [nnimap] nnimap-split vs SIEVE script ?
Date: Fri, 27 Nov 2015 09:46:47 +0800	[thread overview]
Message-ID: <87y4dk1aew.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m0fuzsbwct.fsf@kcals.intra.maillard.im>

Xavier Maillard <lists.emacs.gnus@xavier.maillard.im> writes:

> Hello,
>
> same player, shoot again.
>
> This is a 2-questions-in-one message:
>
> * do you use both methods (and if so, why) ?
>
> * is there any possibility to connect to a remote SIEVE server from Gnus ?

When I switched from Google to self-hosted email, I switched from
client-side split to server-side SIEVE. It just seemed a bit silly to be
creating all that extra network traffic. The only thing I regret a tiny
bit is automatic splitting based on BBDB "imap" fields. Everything else
I had to write by hand anyway, and while it's definitely more of a pain
to do it in SIEVE, it's usually a one-time pain.

Emacs comes with a sieve.el package that can interact with a dovecot
sieve server. I tried it once without reading the documentation, screwed
it up, and didn't bother going back and doing it right. I'm sure it
works just fine, if you actually learn to use it :)

E




  reply	other threads:[~2015-11-27  1:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 15:42 Xavier Maillard
2015-11-27  1:46 ` Eric Abrahamsen [this message]
2015-11-27  5:18   ` Julien Cubizolles
2015-11-27  5:39     ` Eric Abrahamsen
2015-11-27 14:04       ` Julien Cubizolles
2015-11-28  3:15         ` Eric Abrahamsen
2015-11-28  8:47           ` Julien Cubizolles
2015-11-28 10:26           ` Adam Sjøgren
2015-11-28 14:46             ` Eric Abrahamsen
2015-12-03 12:38   ` Simon Josefsson
2015-12-04  7:02     ` Eric Abrahamsen

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=87y4dk1aew.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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).