From: Leonidas Tsampros <ltsampros@upnet.gr>
To: ding@gnus.org
Subject: Re: reading groups.google.com with gnus?
Date: Sat, 07 Jan 2012 15:55:33 +0200 [thread overview]
Message-ID: <87boqfmxbe.fsf@kepler.lan> (raw)
In-Reply-To: <87vcooth4u.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 06 Jan 2012 20:50:57 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Wed, 14 Dec 2011 16:51:46 +0000 Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> ESF> Robert Epprecht <epprecht@solnet.ch> writes:
>>> The newsserver I've been using has been shut down.
>>> There is at least one usenet group (comp.lang.forth) I'm still interested in.
>>> Can Gnus read groups from groups.google.com? How?
>
> ESF> I don't think it can but I'm sure somebody will correct me if I am
> ESF> wrong. If it cannot, it's not gnus's fault; I believe that google
> ESF> doesn't support nttp access to its groups.
>
> Right. It's intentionally inaccessible, like the vast majority of web
> forums.
>
> Ted
Actually, using the old google groups web interface there was a very
nice UI where you could subscribe to groups and receive all the new
mails in your inbox. You could even subscribe to receive the mails in an
address other than your @gmail.com one.
In order to get them fancy-split, I'm still using this rule here:
("list-id" ".*<\\(.+\\)\\.googlegroups\\.com>.*" "mail.gg.\\1")
That's the method I used to subscribe to some google groups, however I
remember some difficulty on how to subscribe by mail to groups using
there new UI blabla.
Leonidas
prev parent reply other threads:[~2012-01-07 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87borbtlwe.fsf@e901.home>
2011-12-14 16:51 ` Eric S Fraga
2012-01-07 1:50 ` Ted Zlatanov
2012-01-07 11:17 ` James Cloos
2012-01-07 13:55 ` Leonidas Tsampros [this message]
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=87boqfmxbe.fsf@kepler.lan \
--to=ltsampros@upnet.gr \
--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).