Re: Migration to PGLister - After

2017-12-21 Thread Magnus Hagander 
On Mon, Nov 20, 2017 at 10:09 PM, Magnus Hagander 
wrote:

> On Mon, Nov 20, 2017 at 9:31 PM, Michael Nolan  wrote:
>
>>
>>
>> On Mon, Nov 20, 2017 at 9:45 AM, Stephen Frost 
>> wrote:
>>
>>>
>>> This list has now been migrated to new mailing list software known as
>>> 'PGLister'.  This migration will impact all users of this mailing list
>>> in one way or another.
>>>
>>
>> Is there more information available about PGLister somewhere, ie, is this
>> a list package that other people running mailing lists might be able to
>> use?  A net search for "PGLister" doesn't find much yet.
>>
>>
> Hi!
>
> Please track the thread at https://www.postgresql.org/
> message-id/CABUevEw7Vs9Hpe-9dRWPwXDa4sPuE71BDNk2X8_UOQ%
> 3Dhvf1tnA%40mail.gmail.com for information on that. TL/DR version is that
> right now it's in a closed repo, but it's scheduled to be opened as soon as
> somebody has had the time to go through it and make sure we're not
> accidentally leaking something that shouldn't be leaked.
>
>
That took a lot longer than expected, but at least we've had someone go
through it now. And hopefully nothing was missed :)

For now, there's a mirror pushed to https://gitlab.com/pglister/pglister.
We're happy to take comments and improvements!


-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/

Re: Migration to PGLister - After

2017-11-20 Thread Stephen Frost 
Mike,

* Michael Nolan (htf...@gmail.com) wrote:
> On Mon, Nov 20, 2017 at 9:45 AM, Stephen Frost  wrote:
> > This list has now been migrated to new mailing list software known as
> > 'PGLister'.  This migration will impact all users of this mailing list
> > in one way or another.
> 
> Is there more information available about PGLister somewhere, ie, is this a
> list package that other people running mailing lists might be able to use?
> A net search for "PGLister" doesn't find much yet.

It's open source and we'll open the git tree for it soon, but it's tied
into our community authentication system, so it's not like it's
something that would be easy to plug-n-play elsewhere.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: Migration to PGLister - After

2017-11-20 Thread Rob Sargent 
Kinda looking like you should have unsubscribed everybody and those of 
us that would miss the feed would re-connect.



On 11/20/2017 02:09 PM, Magnus Hagander wrote:
On Mon, Nov 20, 2017 at 9:31 PM, Michael Nolan > wrote:




On Mon, Nov 20, 2017 at 9:45 AM, Stephen Frost > wrote:


This list has now been migrated to new mailing list software
known as
'PGLister'.  This migration will impact all users of this
mailing list
in one way or another.


Is there more information available about PGLister somewhere, ie,
is this a list package that other people running mailing lists
might be able to use?  A net search for "PGLister" doesn't find
much yet.


Hi!

Please track the thread at 
https://www.postgresql.org/message-id/CABUevEw7Vs9Hpe-9dRWPwXDa4sPuE71BDNk2X8_UOQ%3Dhvf1tnA%40mail.gmail.com 
for information on that. TL/DR version is that right now it's in a 
closed repo, but it's scheduled to be opened as soon as somebody has 
had the time to go through it and make sure we're not accidentally 
leaking something that shouldn't be leaked.


--
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/

Re: Migration to PGLister - After

2017-11-20 Thread Tom Lane 
Ben Coleman  writes:
> On 11/20/2017 09:45 AM, Stephen Frost wrote:
>> This list has now been migrated to new mailing list software known as
>> 'PGLister'.  This migration will impact all users of this mailing list
>> in one way or another.

> I note the conspicuous absence of pgsql-annou...@postgresql.org in the
> lists the Before email was sent to.  Can I assume that that list
> continues under the old regime?

It's scheduled to be migrated next week.

regards, tom lane

Re: Migration to PGLister - After

2017-11-20 Thread Ben Coleman 
On 11/20/2017 09:45 AM, Stephen Frost wrote:
> Greetings!
> 
> This list has now been migrated to new mailing list software known as
> 'PGLister'.  This migration will impact all users of this mailing list
> in one way or another.

I note the conspicuous absence of pgsql-annou...@postgresql.org in the
lists the Before email was sent to.  Can I assume that that list
continues under the old regime?

Ben
-- 
Ben Coleman  
CTO, Accelerated Design, Inc.
(678) 337-8899



signature.asc
Description: OpenPGP digital signature

Re: Migration to PGLister - After

2017-11-20 Thread Rich Shepard 

On Mon, 20 Nov 2017, Joshua D. Drake wrote:


Yep, but that is why the list-id filter is bad advice (at least for me). I
filter on the list email address and it works flawlessly.


Joshua,

  This does not work if the procmail recipe is for pgsql-gene...@postgresql.org
and the source includes the server; e.g, pgsql-general@lists.postgresql.org.
Perhaps adding '.*' in front of postgresql.org will fix this.

Rich

Re: Migration to PGLister - After

2017-11-20 Thread Stephen Frost 
Josh,

* Joshua D. Drake (j...@commandprompt.com) wrote:
> Yep, but that is why the list-id filter is bad advice (at least for
> me). I filter on the list email address and it works flawlessly.

Indeed, this depends on what you're looking to do.  Filtering on
addresses listed in the To/CC is another approach and might work for
some, but it really depends on what you want.

If you do filter on the addresses listed in the To/CC, then it would
probably make sense to turn off the 'extra copy' option in the PGLister
configuration to avoid having duplicates.

If, as I do, you'd prefer to have both and to have the emails sent
through the list end up in a specific folder with the emails sent
directly to you going to your inbox, then using List-Id is the better
approach.

As mentioned up-thread, this isn't something we're able to really
control on the PGLister side, however.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: Migration to PGLister - After

2017-11-20 Thread Joshua D. Drake 

On 11/20/2017 09:32 AM, John R Pierce wrote:

On 11/20/2017 6:45 AM, Stephen Frost wrote:

The changes which we expect to be most significant to users can be found
on the wiki here:https://wiki.postgresql.org/wiki/PGLister_Announce  the
current version of which is also included below.



A peeve on this new configuration:    if someone does a reply-all and 
sends both direct and list responses, the direct response ends up in 
my regular inbox because it doesn't have the List-ID... Previously, 
the direct reply would still have the Subject: [listname] that I 
filtered on, so it too would end up in my 'postgres' folder, where I 
want it.


I realize why this was done, and yada yada, what a mess.



Yep, but that is why the list-id filter is bad advice (at least for me). 
I filter on the list email address and it works flawlessly.


JD



--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
* Unless otherwise stated, opinions are my own.   *