On 09/27/2015 09:34 PM, Jeff Janes wrote:
> On Sun, Sep 27, 2015 at 11:07 AM, Alvaro Herrera
> <alvherre@2ndquadrant.com <mailto:alvherre@2ndquadrant.com>> wrote:
>
> Tom Lane wrote:
> > Amir Rohan <amir.rohan@mail.com <mailto:amir.rohan@mail.com>> writes:
> > > I've read elsewhere that a possible solution is to provide a
> > > mail address associated with a message (displayed on the web interface)
> > > that routes your mail message to the thread.
> >
> > Seems awfully like a here-please-spam-us button.
>


a captcha would be the usual way to solve that problem.

> Yeah, that doesn't sound good. What I think would be workable is to
> create a feature that emails you an archived message, and requires that
> you're logged in with your community account. That sounds hard enough
> to abuse by spammers and convenient enough for actual users.
>
> I think majordomo already has a command to do that. It was discussed
> somewhere on one
> of these lists in the last few months, but I can't seem to find the
> discussion now.
>


> I thought someone was going to create a link on the maillist archive
> page that would provide some visibility to this buried gem.


Isn't there a ticket on the bug tracker? ;)

> Maybe this vague recollection can jog someone's memory.
>


Not my memory, but my urge to read documentation:

|To: majordomo@postgresql.org
|
| approve mypassword archive-get pgsql-www 20150927


Will get you the email(s), but:

1) You need to subscribe first (and unsubsribe again later). Defeating the purpose.
2) Find out how to do this was not trivial and took (relativly) a lot of time. Hiding instructions on this somewhere on the website wouldn't
be much better in practice.
3) The selection granularity is crap. Asking for a day from -hackers
got me 120 messages to sift through. Majordomo offers alternative
filters, but none is much better.

So as a user-facing solution, it sucks, but if it helps to implement
a click handler on the website that gets me a particular message,
that'll work.

Amir