Обсуждение: Email filter problem with 'index'
I have found that some of my emails are being blocked by our email filter. I turns out that the word 'index' at the start of a line in my git patches is causing this. Now that most git patches have a line starting with the word 'index', e.g. index acd2514..b2da1cf, can we remove this limitation? Thanks. I assume the rule is there to prevent people from sending Majordomo 'index' commands to the public list. Magnus says this is the rule: GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Bruce Momjian wrote: > I have found that some of my emails are being blocked by our email > filter. I turns out that the word 'index' at the start of a line in my > git patches is causing this. Now that most git patches have a line > starting with the word 'index', e.g. index acd2514..b2da1cf, can we > remove this limitation? Thanks. > > I assume the rule is there to prevent people from sending Majordomo > 'index' commands to the public list. Magnus says this is the rule: > > GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i Ah, this email got right through because I didn't use the word index at the start of a line. inde... Live dangerously! -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
'k, try that ... I did it globally, but if we do find that the other lists are getting a bunch of admin garbage as a result, I can restrict it down to just h ecommitters list that it is removed from ... On Mon, 14 Mar 2011, Bruce Momjian wrote: > I have found that some of my emails are being blocked by our email > filter. I turns out that the word 'index' at the start of a line in my > git patches is causing this. Now that most git patches have a line > starting with the word 'index', e.g. index acd2514..b2da1cf, can we > remove this limitation? Thanks. > > I assume the rule is there to prevent people from sending Majordomo > 'index' commands to the public list. Magnus says this is the rule: > > GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + It's impossible for everything to be true. + > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
Marc G. Fournier wrote: > > 'k, try that ... I did it globally, but if we do find that the other lists > are getting a bunch of admin garbage as a result, I can restrict it down > to just h ecommitters list that it is removed from ... Thanks. I think globally is the right solution now that everyone is using git. > > I have found that some of my emails are being blocked by our email > > filter. I turns out that the word 'index' at the start of a line in my > > git patches is causing this. Now that most git patches have a line > > starting with the word 'index', e.g. index acd2514..b2da1cf, can we > > remove this limitation? Thanks. > > > > I assume the rule is there to prevent people from sending Majordomo > > 'index' commands to the public list. Magnus says this is the rule: > > > > GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i OK, "index" test: index -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Bruce Momjian wrote: > Marc G. Fournier wrote: > > > > 'k, try that ... I did it globally, but if we do find that the other lists > > are getting a bunch of admin garbage as a result, I can restrict it down > > to just h ecommitters list that it is removed from ... > > Thanks. I think globally is the right solution now that everyone is > using git. > > > > I have found that some of my emails are being blocked by our email > > > filter. I turns out that the word 'index' at the start of a line in my > > > git patches is causing this. Now that most git patches have a line > > > starting with the word 'index', e.g. index acd2514..b2da1cf, can we > > > remove this limitation? Thanks. > > > > > > I assume the rule is there to prevent people from sending Majordomo > > > 'index' commands to the public list. Magnus says this is the rule: > > > > > > GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i > > OK, "index" test: > > index Bingo! Success! Thanks. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Excerpts from Bruce Momjian's message of lun mar 14 13:45:03 -0300 2011: > Bruce Momjian wrote: > > Marc G. Fournier wrote: > > > > > > 'k, try that ... I did it globally, but if we do find that the other lists > > > are getting a bunch of admin garbage as a result, I can restrict it down > > > to just h ecommitters list that it is removed from ... > > > > Thanks. I think globally is the right solution now that everyone is > > using git. > > > > > > I have found that some of my emails are being blocked by our email > > > > filter. I turns out that the word 'index' at the start of a line in my > > > > git patches is causing this. Now that most git patches have a line > > > > starting with the word 'index', e.g. index acd2514..b2da1cf, can we > > > > remove this limitation? Thanks. > > > > > > > > I assume the rule is there to prevent people from sending Majordomo > > > > 'index' commands to the public list. Magnus says this is the rule: > > > > > > > > GLOBAL ADMIN BODY: /^\s*index\s+\S+\s*$/i > > > > OK, "index" test: > > > > index > > Bingo! Success! Thanks. Well that doesn't qualify because you need a word after it. This does: index the -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Bruce Momjian <bruce@momjian.us> writes:
> I have found that some of my emails are being blocked by our email
> filter. I turns out that the word 'index' at the start of a line in my
> git patches is causing this. Now that most git patches have a line
> starting with the word 'index', e.g. index acd2514..b2da1cf, can we
> remove this limitation? Thanks.
Hm, is that a recently added rule? It seems like a pretty bad idea for
database-related lists, because the word "index" is not exactly
infrequently used around here. I had a message disappear into the ether
just yesterday, and I didn't know why, but now I wonder if ...
regards, tom lane
That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to the leftside ... I believe all admin rules are anchored that why ... Sent from my iPhone On 2011-03-14, at 13:00, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Bruce Momjian <bruce@momjian.us> writes: >> I have found that some of my emails are being blocked by our email >> filter. I turns out that the word 'index' at the start of a line in my >> git patches is causing this. Now that most git patches have a line >> starting with the word 'index', e.g. index acd2514..b2da1cf, can we >> remove this limitation? Thanks. > > Hm, is that a recently added rule? It seems like a pretty bad idea for > database-related lists, because the word "index" is not exactly > infrequently used around here. I had a message disappear into the ether > just yesterday, and I didn't know why, but now I wonder if ... > > regards, tom lane
On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: > That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to the leftside ... I believe all admin rules are anchored that why ... > Uhm, what other bad words will get our emails trashed? -- greg
On Tue, Mar 15, 2011 at 16:50, Greg Stark <gsstark@mit.edu> wrote: > On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: >> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to the leftside ... I believe all admin rules are anchored that why ... >> > > Uhm, what other bad words will get our emails trashed? FWIW, they should never be *trashed*. If they match that regex, they get *moderated*, not deleted. Right, marc? Or are there some regex's that will actually delete them? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Nothing gets 'trashed', only put into the moderation cue for manual approval ... That said, the current 'taboo' list looks like: configset GLOBAL admin_body <<ENDAAB /^accept$/i /^reject$/i /\badd me\b/i /\bdelete me\b/i /\bremove\s+me\b/i /\bchange\b.*\baddress\b/ /\bsignoff\b/i /\bsubscribe\b/i /^sub\b/i /\bunsubscribe\b/i /^unsub\b/i /^\s*help\s*$/i /^\s*info\s*$/i /^\s*info\s+\S+\s*$/i /^\s*lists\s*$/i /^\s*which\s*$/i /^\s*which\s+\S+\s*$/i /^\s*index\s*$/i /^\s*who\s*$/i /^\s*who\s+\S+\s*$/i /^\s*get\s+\S+\s*$/i /^\s*get\s+\S+\s+\S+\s*$/i /^\s*approve\b/i /^\s*passwd\b/i /^\s*newinfo\b/i /^\s*newconfig\b/i /^\s*writeconfig\b/i /^\s*mkdigest\b/i ENDAAB On Tue, 15 Mar 2011, Greg Stark wrote: > On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: >> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to the leftside ... I believe all admin rules are anchored that why ... >> > > Uhm, what other bad words will get our emails trashed? > > -- > greg > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
Does anyone even know how to use the majordomo commands? I think subscribe and unsubscribe are the only one we need to worry about. --------------------------------------------------------------------------- Marc G. Fournier wrote: > > Nothing gets 'trashed', only put into the moderation cue for manual > approval ... > > That said, the current 'taboo' list looks like: > > configset GLOBAL admin_body <<ENDAAB > /^accept$/i > /^reject$/i > /\badd me\b/i > /\bdelete me\b/i > /\bremove\s+me\b/i > /\bchange\b.*\baddress\b/ > /\bsignoff\b/i > /\bsubscribe\b/i > /^sub\b/i > /\bunsubscribe\b/i > /^unsub\b/i > /^\s*help\s*$/i > /^\s*info\s*$/i > /^\s*info\s+\S+\s*$/i > /^\s*lists\s*$/i > /^\s*which\s*$/i > /^\s*which\s+\S+\s*$/i > /^\s*index\s*$/i > /^\s*who\s*$/i > /^\s*who\s+\S+\s*$/i > /^\s*get\s+\S+\s*$/i > /^\s*get\s+\S+\s+\S+\s*$/i > /^\s*approve\b/i > /^\s*passwd\b/i > /^\s*newinfo\b/i > /^\s*newconfig\b/i > /^\s*writeconfig\b/i > /^\s*mkdigest\b/i > ENDAAB > > > On Tue, 15 Mar 2011, Greg Stark wrote: > > > On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: > >> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to theleft side ... I believe all admin rules are anchored that why ... > >> > > > > Uhm, what other bad words will get our emails trashed? > > > > -- > > greg > > > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > scrappy@hub.org http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
On Tue, 15 Mar 2011, Bruce Momjian wrote: > > Does anyone even know how to use the majordomo commands? I think > subscribe and unsubscribe are the only one we need to worry about. Anyone that sends a 'help' to majordomo@postgresql.org will get a full list of all admin commands ... just because you haven't gone past subscribe/unsubscribe doesn't mean nobody has :) > > --------------------------------------------------------------------------- > > Marc G. Fournier wrote: >> >> Nothing gets 'trashed', only put into the moderation cue for manual >> approval ... >> >> That said, the current 'taboo' list looks like: >> >> configset GLOBAL admin_body <<ENDAAB >> /^accept$/i >> /^reject$/i >> /\badd me\b/i >> /\bdelete me\b/i >> /\bremove\s+me\b/i >> /\bchange\b.*\baddress\b/ >> /\bsignoff\b/i >> /\bsubscribe\b/i >> /^sub\b/i >> /\bunsubscribe\b/i >> /^unsub\b/i >> /^\s*help\s*$/i >> /^\s*info\s*$/i >> /^\s*info\s+\S+\s*$/i >> /^\s*lists\s*$/i >> /^\s*which\s*$/i >> /^\s*which\s+\S+\s*$/i >> /^\s*index\s*$/i >> /^\s*who\s*$/i >> /^\s*who\s+\S+\s*$/i >> /^\s*get\s+\S+\s*$/i >> /^\s*get\s+\S+\s+\S+\s*$/i >> /^\s*approve\b/i >> /^\s*passwd\b/i >> /^\s*newinfo\b/i >> /^\s*newconfig\b/i >> /^\s*writeconfig\b/i >> /^\s*mkdigest\b/i >> ENDAAB >> >> >> On Tue, 15 Mar 2011, Greg Stark wrote: >> >>> On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: >>>> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to theleft side ... I believe all admin rules are anchored that why ... >>>> >>> >>> Uhm, what other bad words will get our emails trashed? >>> >>> -- >>> greg >>> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> scrappy@hub.org http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + It's impossible for everything to be true. + > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
Marc G. Fournier wrote: > On Tue, 15 Mar 2011, Bruce Momjian wrote: > > > > > Does anyone even know how to use the majordomo commands? I think > > subscribe and unsubscribe are the only one we need to worry about. > > Anyone that sends a 'help' to majordomo@postgresql.org will get a full > list of all admin commands ... just because you haven't gone past > subscribe/unsubscribe doesn't mean nobody has :) True. The question is how many people are doing that vs. how many people accidentally have these words in their email text. We know "index" was one of them, so it was removed. Any others? --------------------------------------------------------------------------- > > Marc G. Fournier wrote: > >> > >> Nothing gets 'trashed', only put into the moderation cue for manual > >> approval ... > >> > >> That said, the current 'taboo' list looks like: > >> > >> configset GLOBAL admin_body <<ENDAAB > >> /^accept$/i > >> /^reject$/i > >> /\badd me\b/i > >> /\bdelete me\b/i > >> /\bremove\s+me\b/i > >> /\bchange\b.*\baddress\b/ > >> /\bsignoff\b/i > >> /\bsubscribe\b/i > >> /^sub\b/i > >> /\bunsubscribe\b/i > >> /^unsub\b/i > >> /^\s*help\s*$/i > >> /^\s*info\s*$/i > >> /^\s*info\s+\S+\s*$/i > >> /^\s*lists\s*$/i > >> /^\s*which\s*$/i > >> /^\s*which\s+\S+\s*$/i > >> /^\s*index\s*$/i > >> /^\s*who\s*$/i > >> /^\s*who\s+\S+\s*$/i > >> /^\s*get\s+\S+\s*$/i > >> /^\s*get\s+\S+\s+\S+\s*$/i > >> /^\s*approve\b/i > >> /^\s*passwd\b/i > >> /^\s*newinfo\b/i > >> /^\s*newconfig\b/i > >> /^\s*writeconfig\b/i > >> /^\s*mkdigest\b/i > >> ENDAAB > >> > >> > >> On Tue, 15 Mar 2011, Greg Stark wrote: > >> > >>> On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: > >>>> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to theleft side ... I believe all admin rules are anchored that why ... > >>>> > >>> > >>> Uhm, what other bad words will get our emails trashed? > >>> > >>> -- > >>> greg > >>> > >> > >> ---- > >> Marc G. Fournier Hub.Org Hosting Solutions S.A. > >> scrappy@hub.org http://www.hub.org > >> > >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > > > -- > > Bruce Momjian <bruce@momjian.us> http://momjian.us > > EnterpriseDB http://enterprisedb.com > > > > + It's impossible for everything to be true. + > > > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > scrappy@hub.org http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
On Wed, 16 Mar 2011, Bruce Momjian wrote: > Marc G. Fournier wrote: >> On Tue, 15 Mar 2011, Bruce Momjian wrote: >> >>> >>> Does anyone even know how to use the majordomo commands? I think >>> subscribe and unsubscribe are the only one we need to worry about. >> >> Anyone that sends a 'help' to majordomo@postgresql.org will get a full >> list of all admin commands ... just because you haven't gone past >> subscribe/unsubscribe doesn't mean nobody has :) > > True. The question is how many people are doing that vs. how many > people accidentally have these words in their email text. We know > "index" was one of them, so it was removed. Any others? Few ppl would know, since their messsages would still get to the lists, and, generally, with very little delay, except on some of the fringe lists where we dont' have redundant moderators ... > > --------------------------------------------------------------------------- > > >>> Marc G. Fournier wrote: >>>> >>>> Nothing gets 'trashed', only put into the moderation cue for manual >>>> approval ... >>>> >>>> That said, the current 'taboo' list looks like: >>>> >>>> configset GLOBAL admin_body <<ENDAAB >>>> /^accept$/i >>>> /^reject$/i >>>> /\badd me\b/i >>>> /\bdelete me\b/i >>>> /\bremove\s+me\b/i >>>> /\bchange\b.*\baddress\b/ >>>> /\bsignoff\b/i >>>> /\bsubscribe\b/i >>>> /^sub\b/i >>>> /\bunsubscribe\b/i >>>> /^unsub\b/i >>>> /^\s*help\s*$/i >>>> /^\s*info\s*$/i >>>> /^\s*info\s+\S+\s*$/i >>>> /^\s*lists\s*$/i >>>> /^\s*which\s*$/i >>>> /^\s*which\s+\S+\s*$/i >>>> /^\s*index\s*$/i >>>> /^\s*who\s*$/i >>>> /^\s*who\s+\S+\s*$/i >>>> /^\s*get\s+\S+\s*$/i >>>> /^\s*get\s+\S+\s+\S+\s*$/i >>>> /^\s*approve\b/i >>>> /^\s*passwd\b/i >>>> /^\s*newinfo\b/i >>>> /^\s*newconfig\b/i >>>> /^\s*writeconfig\b/i >>>> /^\s*mkdigest\b/i >>>> ENDAAB >>>> >>>> >>>> On Tue, 15 Mar 2011, Greg Stark wrote: >>>> >>>>> On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: >>>>>> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored to theleft side ... I believe all admin rules are anchored that why ... >>>>>> >>>>> >>>>> Uhm, what other bad words will get our emails trashed? >>>>> >>>>> -- >>>>> greg >>>>> >>>> >>>> ---- >>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>> scrappy@hub.org http://www.hub.org >>>> >>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org >>> >>> -- >>> Bruce Momjian <bruce@momjian.us> http://momjian.us >>> EnterpriseDB http://enterprisedb.com >>> >>> + It's impossible for everything to be true. + >>> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> scrappy@hub.org http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + It's impossible for everything to be true. + > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
Marc G. Fournier wrote: > On Wed, 16 Mar 2011, Bruce Momjian wrote: > > > Marc G. Fournier wrote: > >> On Tue, 15 Mar 2011, Bruce Momjian wrote: > >> > >>> > >>> Does anyone even know how to use the majordomo commands? I think > >>> subscribe and unsubscribe are the only one we need to worry about. > >> > >> Anyone that sends a 'help' to majordomo@postgresql.org will get a full > >> list of all admin commands ... just because you haven't gone past > >> subscribe/unsubscribe doesn't mean nobody has :) > > > > True. The question is how many people are doing that vs. how many > > people accidentally have these words in their email text. We know > > "index" was one of them, so it was removed. Any others? > > Few ppl would know, since their messsages would still get to the lists, > and, generally, with very little delay, except on some of the fringe lists > where we dont' have redundant moderators ... I think only the moderators would know how many of the majordomo emails are being caught by the filters below. My guess is that there are very few aside from subscribe/unsubscribe. "who", "which", and "info" seem like they are likely to be caught in normal emails. What if we disable most of these and see how many get through to our list, again keeping subscribe/unsubscribe and "remove me"? --------------------------------------------------------------------------- > > > > > >>> Marc G. Fournier wrote: > >>>> > >>>> Nothing gets 'trashed', only put into the moderation cue for manual > >>>> approval ... > >>>> > >>>> That said, the current 'taboo' list looks like: > >>>> > >>>> configset GLOBAL admin_body <<ENDAAB > >>>> /^accept$/i > >>>> /^reject$/i > >>>> /\badd me\b/i > >>>> /\bdelete me\b/i > >>>> /\bremove\s+me\b/i > >>>> /\bchange\b.*\baddress\b/ > >>>> /\bsignoff\b/i > >>>> /\bsubscribe\b/i > >>>> /^sub\b/i > >>>> /\bunsubscribe\b/i > >>>> /^unsub\b/i > >>>> /^\s*help\s*$/i > >>>> /^\s*info\s*$/i > >>>> /^\s*info\s+\S+\s*$/i > >>>> /^\s*lists\s*$/i > >>>> /^\s*which\s*$/i > >>>> /^\s*which\s+\S+\s*$/i > >>>> /^\s*index\s*$/i > >>>> /^\s*who\s*$/i > >>>> /^\s*who\s+\S+\s*$/i > >>>> /^\s*get\s+\S+\s*$/i > >>>> /^\s*get\s+\S+\s+\S+\s*$/i > >>>> /^\s*approve\b/i > >>>> /^\s*passwd\b/i > >>>> /^\s*newinfo\b/i > >>>> /^\s*newconfig\b/i > >>>> /^\s*writeconfig\b/i > >>>> /^\s*mkdigest\b/i > >>>> ENDAAB > >>>> > >>>> > >>>> On Tue, 15 Mar 2011, Greg Stark wrote: > >>>> > >>>>> On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: > >>>>>> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchored tothe left side ... I believe all admin rules are anchored that why ... > >>>>>> > >>>>> > >>>>> Uhm, what other bad words will get our emails trashed? > >>>>> > >>>>> -- > >>>>> greg > >>>>> > >>>> > >>>> ---- > >>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. > >>>> scrappy@hub.org http://www.hub.org > >>>> > >>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > >>> > >>> -- > >>> Bruce Momjian <bruce@momjian.us> http://momjian.us > >>> EnterpriseDB http://enterprisedb.com > >>> > >>> + It's impossible for everything to be true. + > >>> > >> > >> ---- > >> Marc G. Fournier Hub.Org Hosting Solutions S.A. > >> scrappy@hub.org http://www.hub.org > >> > >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > > > -- > > Bruce Momjian <bruce@momjian.us> http://momjian.us > > EnterpriseDB http://enterprisedb.com > > > > + It's impossible for everything to be true. + > > > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > scrappy@hub.org http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Wow, any idea why these were so delayed in appearing? I assume it was the keywords quoted below. --------------------------------------------------------------------------- Bruce Momjian wrote: > Marc G. Fournier wrote: > > On Wed, 16 Mar 2011, Bruce Momjian wrote: > > > > > Marc G. Fournier wrote: > > >> On Tue, 15 Mar 2011, Bruce Momjian wrote: > > >> > > >>> > > >>> Does anyone even know how to use the majordomo commands? I think > > >>> subscribe and unsubscribe are the only one we need to worry about. > > >> > > >> Anyone that sends a 'help' to majordomo@postgresql.org will get a full > > >> list of all admin commands ... just because you haven't gone past > > >> subscribe/unsubscribe doesn't mean nobody has :) > > > > > > True. The question is how many people are doing that vs. how many > > > people accidentally have these words in their email text. We know > > > "index" was one of them, so it was removed. Any others? > > > > Few ppl would know, since their messsages would still get to the lists, > > and, generally, with very little delay, except on some of the fringe lists > > where we dont' have redundant moderators ... > > I think only the moderators would know how many of the majordomo emails > are being caught by the filters below. My guess is that there are very > few aside from subscribe/unsubscribe. "who", "which", and "info" seem > like they are likely to be caught in normal emails. > > What if we disable most of these and see how many get through to our > list, again keeping subscribe/unsubscribe and "remove me"? > > --------------------------------------------------------------------------- > > > > > > > > >>> Marc G. Fournier wrote: > > >>>> > > >>>> Nothing gets 'trashed', only put into the moderation cue for manual > > >>>> approval ... > > >>>> > > >>>> That said, the current 'taboo' list looks like: > > >>>> > > >>>> configset GLOBAL admin_body <<ENDAAB > > >>>> /^accept$/i > > >>>> /^reject$/i > > >>>> /\badd me\b/i > > >>>> /\bdelete me\b/i > > >>>> /\bremove\s+me\b/i > > >>>> /\bchange\b.*\baddress\b/ > > >>>> /\bsignoff\b/i > > >>>> /\bsubscribe\b/i > > >>>> /^sub\b/i > > >>>> /\bunsubscribe\b/i > > >>>> /^unsub\b/i > > >>>> /^\s*help\s*$/i > > >>>> /^\s*info\s*$/i > > >>>> /^\s*info\s+\S+\s*$/i > > >>>> /^\s*lists\s*$/i > > >>>> /^\s*which\s*$/i > > >>>> /^\s*which\s+\S+\s*$/i > > >>>> /^\s*index\s*$/i > > >>>> /^\s*who\s*$/i > > >>>> /^\s*who\s+\S+\s*$/i > > >>>> /^\s*get\s+\S+\s*$/i > > >>>> /^\s*get\s+\S+\s+\S+\s*$/i > > >>>> /^\s*approve\b/i > > >>>> /^\s*passwd\b/i > > >>>> /^\s*newinfo\b/i > > >>>> /^\s*newconfig\b/i > > >>>> /^\s*writeconfig\b/i > > >>>> /^\s*mkdigest\b/i > > >>>> ENDAAB > > >>>> > > >>>> > > >>>> On Tue, 15 Mar 2011, Greg Stark wrote: > > >>>> > > >>>>> On Mon, Mar 14, 2011 at 5:42 PM, Marc <scrappy@hub.org> wrote: > > >>>>>> That rule has been there since the lists were originally setup ... The rule should have been ^index, anchoredto the left side ... I believe all admin rules are anchored that why ... > > >>>>>> > > >>>>> > > >>>>> Uhm, what other bad words will get our emails trashed? > > >>>>> > > >>>>> -- > > >>>>> greg > > >>>>> > > >>>> > > >>>> ---- > > >>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. > > >>>> scrappy@hub.org http://www.hub.org > > >>>> > > >>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > >>> > > >>> -- > > >>> Bruce Momjian <bruce@momjian.us> http://momjian.us > > >>> EnterpriseDB http://enterprisedb.com > > >>> > > >>> + It's impossible for everything to be true. + > > >>> > > >> > > >> ---- > > >> Marc G. Fournier Hub.Org Hosting Solutions S.A. > > >> scrappy@hub.org http://www.hub.org > > >> > > >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > > > > > -- > > > Bruce Momjian <bruce@momjian.us> http://momjian.us > > > EnterpriseDB http://enterprisedb.com > > > > > > + It's impossible for everything to be true. + > > > > > > > ---- > > Marc G. Fournier Hub.Org Hosting Solutions S.A. > > scrappy@hub.org http://www.hub.org > > > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + It's impossible for everything to be true. + > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
On Wed, Mar 16, 2011 at 17:31, Bruce Momjian <bruce@momjian.us> wrote: > > Wow, any idea why these were so delayed in appearing? I assume it was > the keywords quoted below. They were caught in the moderation queue, which I checked when I got back off my flight. clearly whomever else is moderating -www was also not available for 2 days or however long it was before it got released. I didn't check *why* they were backed up, I just released them. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Excerpts from Bruce Momjian's message of mié mar 16 11:36:58 -0300 2011: > I think only the moderators would know how many of the majordomo emails > are being caught by the filters below. My guess is that there are very > few aside from subscribe/unsubscribe. "who", "which", and "info" seem > like they are likely to be caught in normal emails. I know. Very few messages are being caught in the filters. Note that most patterns are anchored to start and end of line (allowing only for some intervening whitespace), so just having them in a message does not trigger the filter. The "index" pattern was special because it matches a common pattern of certain git diffs, so it was rightly removed. I don't think the others merit the same treatment. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Alvaro Herrera wrote: > Excerpts from Bruce Momjian's message of mié mar 16 11:36:58 -0300 2011: > > > I think only the moderators would know how many of the majordomo emails > > are being caught by the filters below. My guess is that there are very > > few aside from subscribe/unsubscribe. "who", "which", and "info" seem > > like they are likely to be caught in normal emails. > > I know. Very few messages are being caught in the filters. Note that > most patterns are anchored to start and end of line (allowing only for > some intervening whitespace), so just having them in a message > does not trigger the filter. > > The "index" pattern was special because it matches a common pattern of > certain git diffs, so it was rightly removed. I don't think the others > merit the same treatment. Thanks for the analysis. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +