Thread: Fwd: Successful post to pgsql-hackers

<div dir="ltr">Recently I have started getting these confirmations for every email I send to the mailing lists. I think
it'srelated to the fact that I recently switched to using a new email address.<br /><br />How can I turn these
notificationsoff?<br /><br /><div class="gmail_quote">---------- Forwarded message ----------<br />From: <b
class="gmail_sendername"></b><span dir="ltr"><<a
href="mailto:pgsql-hackers-owner@postgresql.org">pgsql-hackers-owner@postgresql.org</a>></span><br/> Date: Sat, Feb
9,2013 at 10:13 AM<br />Subject: Successful post to pgsql-hackers<br />To: Gurjeet Singh <<a
href="mailto:gurjeet@singh.im">gurjeet@singh.im</a>><br/><br /><br />Your message to the pgsql-hackers list, posted
on<br/>   Sat, 9 Feb 2013 10:11:05 -0500<br /><br /> with subject<br />   Re: pg_prewarm<br /><br /> is currently being
delivered.<br/></div><br /><br clear="all" /><br />-- <br /><div dir="ltr">Gurjeet Singh<br /><br /><a
href="http://gurjeet.singh.im/"target="_blank">http://gurjeet.singh.im/</a></div></div> 

It's in your personal majordomo settings. I don't think it's related
to that at all, but it's a flag you set on your subscription, so
perhaps you set it by mistake.

You shold be able to set it from https://mail.postgresql.org. The
setting you're looking for is "ackpost", and you'll want to turn it
off.

//Magnus


On Sat, Feb 9, 2013 at 4:17 PM, Gurjeet Singh <gurjeet@singh.im> wrote:
> Recently I have started getting these confirmations for every email I send
> to the mailing lists. I think it's related to the fact that I recently
> switched to using a new email address.
>
> How can I turn these notifications off?
>
> ---------- Forwarded message ----------
> From: <pgsql-hackers-owner@postgresql.org>
> Date: Sat, Feb 9, 2013 at 10:13 AM
> Subject: Successful post to pgsql-hackers
> To: Gurjeet Singh <gurjeet@singh.im>
>
>
> Your message to the pgsql-hackers list, posted on
>   Sat, 9 Feb 2013 10:11:05 -0500
>
> with subject
>   Re: pg_prewarm
>
> is currently being delivered.
>
>
>
> --
> Gurjeet Singh
>
> http://gurjeet.singh.im/



--Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

On 9 February 2013 15:24, Magnus Hagander <magnus@hagander.net> wrote:
> It's in your personal majordomo settings. I don't think it's related
> to that at all, but it's a flag you set on your subscription, so
> perhaps you set it by mistake.

Then I must have set it by mistake too, when I recently changed e-mail
addresses.

-- 
Regards,
Peter Geoghegan

On Sat, Feb 9, 2013 at 4:31 PM, Peter Geoghegan
<peter.geoghegan86@gmail.com> wrote:
> On 9 February 2013 15:24, Magnus Hagander <magnus@hagander.net> wrote:
>> It's in your personal majordomo settings. I don't think it's related
>> to that at all, but it's a flag you set on your subscription, so
>> perhaps you set it by mistake.
>
> Then I must have set it by mistake too, when I recently changed e-mail
> addresses.

Hmm. I wonder if Alvaro may have accidentally switched the default, if
it happened to more than one person. Alvaro, can you check?


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

On 09-02-2013 13:45, Gurjeet Singh wrote:
> BTW, I hope I understand what selfcopy is: send a copy to yourself. Why would
> that be turned on by default?
> 
If you want to reply to yourself...


--   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/  PostgreSQL: Consultoria, Desenvolvimento,
Suporte24x7 e Treinamento
 

Magnus Hagander escribió:
> On Sat, Feb 9, 2013 at 4:31 PM, Peter Geoghegan
> <peter.geoghegan86@gmail.com> wrote:
> > On 9 February 2013 15:24, Magnus Hagander <magnus@hagander.net> wrote:
> >> It's in your personal majordomo settings. I don't think it's related
> >> to that at all, but it's a flag you set on your subscription, so
> >> perhaps you set it by mistake.
> >
> > Then I must have set it by mistake too, when I recently changed e-mail
> > addresses.
>
> Hmm. I wonder if Alvaro may have accidentally switched the default, if
> it happened to more than one person. Alvaro, can you check?

I hadn't touched this, but Andres Freund had already complained about
this before.  I just checked and yes, it seems that the flag to send a
confirmation for each post is set.  I have reset it.

I also took the opportunity to set the flags to send confirmation emails
when a posting is rejected or stalled for moderation.  We discussed this
previously (Pavel Stehule complained about it).

I changed the defaults for new subscribers, and also the flags values
for all existing subscribers, note.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Magnus Hagander escribió:
>> On Sat, Feb 9, 2013 at 4:31 PM, Peter Geoghegan
>> <peter.geoghegan86@gmail.com> wrote:
>> > On 9 February 2013 15:24, Magnus Hagander <magnus@hagander.net> wrote:
>> >> It's in your personal majordomo settings. I don't think it's related
>> >> to that at all, but it's a flag you set on your subscription, so
>> >> perhaps you set it by mistake.
>> >
>> > Then I must have set it by mistake too, when I recently changed e-mail
>> > addresses.
>>
>> Hmm. I wonder if Alvaro may have accidentally switched the default, if
>> it happened to more than one person. Alvaro, can you check?
>
> I hadn't touched this, but Andres Freund had already complained about
> this before.  I just checked and yes, it seems that the flag to send a
> confirmation for each post is set.  I have reset it.
>
> I also took the opportunity to set the flags to send confirmation emails
> when a posting is rejected or stalled for moderation.  We discussed this
> previously (Pavel Stehule complained about it).
>
> I changed the defaults for new subscribers, and also the flags values
> for all existing subscribers, note.

For *all* existing subscribers, or those that had not changed their
defaults? And did you change just those flags, or for all flags?


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

Magnus Hagander escribió:
> On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:

> > I changed the defaults for new subscribers, and also the flags values
> > for all existing subscribers, note.
>
> For *all* existing subscribers, or those that had not changed their
> defaults? And did you change just those flags, or for all flags?

For all existing subscribers, I changed the ackpost (to off), ackreject
(to on), ackstall (to on) flags.  Other flags were untouched.  There's
no way to distinguish "unchanged" from "set to the same as the default"
in mj2, I'm afraid.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Magnus Hagander escribió:
>> On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
>> <alvherre@2ndquadrant.com> wrote:
>
>> > I changed the defaults for new subscribers, and also the flags values
>> > for all existing subscribers, note.
>>
>> For *all* existing subscribers, or those that had not changed their
>> defaults? And did you change just those flags, or for all flags?
>
> For all existing subscribers, I changed the ackpost (to off), ackreject
> (to on), ackstall (to on) flags.  Other flags were untouched.  There's
> no way to distinguish "unchanged" from "set to the same as the default"
> in mj2, I'm afraid.

Yeah, it seems you at least broke some cronjobs that relied on the old
default...

That said, I think that was pretty darn unfriendly to those who
potentially changed their own configuration. E.g. all those who
potentially set their ackpost to on intentionally years ago, have now
lost that one... But it's clearly too late to do anything about that
one now.

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

Magnus Hagander escribió:
> On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:
> > Magnus Hagander escribió:
> >> On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
> >> <alvherre@2ndquadrant.com> wrote:
> >
> >> > I changed the defaults for new subscribers, and also the flags values
> >> > for all existing subscribers, note.
> >>
> >> For *all* existing subscribers, or those that had not changed their
> >> defaults? And did you change just those flags, or for all flags?
> >
> > For all existing subscribers, I changed the ackpost (to off), ackreject
> > (to on), ackstall (to on) flags.  Other flags were untouched.  There's
> > no way to distinguish "unchanged" from "set to the same as the default"
> > in mj2, I'm afraid.
>
> Yeah, it seems you at least broke some cronjobs that relied on the old
> default...

Huh?  We had cronjobs that relied on ackpost being set?  Please elaborate.

> That said, I think that was pretty darn unfriendly to those who
> potentially changed their own configuration. E.g. all those who
> potentially set their ackpost to on intentionally years ago, have now
> lost that one... But it's clearly too late to do anything about that
> one now.

Yes, that true.  Sorry about that.  As I said, there was no way to
figure that out.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

On Mon, Feb 11, 2013 at 2:44 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Magnus Hagander escribió:
>> On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera
>> <alvherre@2ndquadrant.com> wrote:
>> > Magnus Hagander escribió:
>> >> On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
>> >> <alvherre@2ndquadrant.com> wrote:
>> >
>> >> > I changed the defaults for new subscribers, and also the flags values
>> >> > for all existing subscribers, note.
>> >>
>> >> For *all* existing subscribers, or those that had not changed their
>> >> defaults? And did you change just those flags, or for all flags?
>> >
>> > For all existing subscribers, I changed the ackpost (to off), ackreject
>> > (to on), ackstall (to on) flags.  Other flags were untouched.  There's
>> > no way to distinguish "unchanged" from "set to the same as the default"
>> > in mj2, I'm afraid.
>>
>> Yeah, it seems you at least broke some cronjobs that relied on the old
>> default...
>
> Huh?  We had cronjobs that relied on ackpost being set?  Please elaborate.

Nah, cronjobs that synchronized the flags for certain subscribers.
Didn't you receive a copy of the error message? :) It didn't actually
beak it, but it's spewing warnings.

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

Magnus Hagander <magnus@hagander.net> writes:
> That said, I think that was pretty darn unfriendly to those who
> potentially changed their own configuration. E.g. all those who
> potentially set their ackpost to on intentionally years ago, have now
> lost that one... But it's clearly too late to do anything about that
> one now.

The new defaults are clearly saner.  But maybe it's worth a post on
pgsql-announce to let people know this was done?  If there is anybody
out there who's expecting ackpost, that would cue them to fix it.
        regards, tom lane