From: Tommy Kelly <tommy.kelly@verilab.com>
To: Richard Riley <rileyrg@googlemail.com>
Cc: ding@gnus.org
Subject: Re: emacs 24 and gnus
Date: Sun, 9 Jan 2011 10:39:57 -0600 [thread overview]
Message-ID: <AANLkTi=5oiZRkbzuOrO8ncUSDCkJPCT8em5nynT-qnYD@mail.gmail.com> (raw)
In-Reply-To: <6daajaw324.fsf@news.eternal-september.org>
> Or do what I do : mark the mail with imap labels using gmail filters :
> they correspond to your gnus folders.
Yeah, I'm kinda doing that so I have less work to do when I have
another go with gnus. But gmail filters aren't up to much. For a
start, you can't control the order of execution. In fact I already
have an even better solution. We completely mirror our entire mail
setup in a regular IMAP (cyrus I think) server, complete with sieve
(and spamassassin). But something happened recently in gnus which
completely busted my access to it (I go via an ssh tunnel). It insists
on trying to go in via TLS and since I'm tunneling I need a plain
network connection. That's the only reason I've bothered messing with
gnus fancy splitting in the first place.
Anyway, I haven't given up -- just need to back off a bit so I can
actually *do* some work for a while. Ah'll be buck :-)
t
next prev parent reply other threads:[~2011-01-09 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 10:34 Richard Riley
2011-01-04 10:44 ` Tassilo Horn
2011-01-04 11:06 ` Richard Riley
2011-01-04 11:14 ` Adam Sjøgren
2011-01-04 11:58 ` Richard Riley
2011-01-04 12:04 ` Steinar Bang
2011-01-09 14:10 ` Tommy Kelly
2011-01-09 14:43 ` Richard Riley
2011-01-09 16:39 ` Tommy Kelly [this message]
2011-01-04 12:01 ` Tassilo Horn
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='AANLkTi=5oiZRkbzuOrO8ncUSDCkJPCT8em5nynT-qnYD@mail.gmail.com' \
--to=tommy.kelly@verilab.com \
--cc=ding@gnus.org \
--cc=rileyrg@googlemail.com \
/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).