Thread: List moderation - need a break!
Hey Marc, I need to get a break from some of my list moderation chores, as part of a vain attempt to regain (some of) my sanity. Can you please remove me as moderator from the following lists: pgsql-bugs pgsql-hackers pgsql-committers Thanks! (volunteers for moderation duty are welcome of course!) -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > Hey Marc, > > I need to get a break from some of my list moderation chores, as part > of a vain attempt to regain (some of) my sanity. Can you please remove > me as moderator from the following lists: I have to say that the amount of spam is getting large and this is causing a lot more stress on the moderators. I urge for a temporary raise in stress on the antispam-measures-admin so that we moderators can feel more comfortable. (We still get a lot of Russian spam.) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Mon, 2009-06-15 at 10:37 -0400, Alvaro Herrera wrote: > Dave Page wrote: > > Hey Marc, > > > > I need to get a break from some of my list moderation chores, as part > > of a vain attempt to regain (some of) my sanity. Can you please remove > > me as moderator from the following lists: > > I have to say that the amount of spam is getting large and this is > causing a lot more stress on the moderators. I urge for a temporary > raise in stress on the antispam-measures-admin so that we moderators can > feel more comfortable. > > (We still get a lot of Russian spam.) I think spamassassin has a flag to not except anything that isn't certain character sets. Would that help in this case. Joshua D. Drake -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
On Mon, Jun 15, 2009 at 09:35:51AM -0700, Joshua D. Drake wrote: > On Mon, 2009-06-15 at 10:37 -0400, Alvaro Herrera wrote: > > Dave Page wrote: > > > Hey Marc, > > > > > > I need to get a break from some of my list moderation chores, as part > > > of a vain attempt to regain (some of) my sanity. Can you please remove > > > me as moderator from the following lists: > > > > I have to say that the amount of spam is getting large and this is > > causing a lot more stress on the moderators. I urge for a temporary > > raise in stress on the antispam-measures-admin so that we moderators can > > feel more comfortable. > > > > (We still get a lot of Russian spam.) > > I think spamassassin has a flag to not except anything that isn't I think you meant, "accept." > certain character sets. Would that help in this case. Cyrillic character sets are only legit on pgsql-ru-general. On other lists, they should bounce as spam. Similar with the Chinese, Japanese, Korean, etc. character sets. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
David Fetter wrote: > > I think spamassassin has a flag to not except anything that isn't > > I think you meant, "accept." > > > certain character sets. Would that help in this case. > > Cyrillic character sets are only legit on pgsql-ru-general. On other > lists, they should bounce as spam. Similar with the Chinese, > Japanese, Korean, etc. character sets. That is an excellent suggestion! -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Mon, Jun 15, 2009 at 5:54 PM, Bruce Momjian<bruce@momjian.us> wrote: > David Fetter wrote: >> > I think spamassassin has a flag to not except anything that isn't >> >> I think you meant, "accept." >> >> > certain character sets. Would that help in this case. >> >> Cyrillic character sets are only legit on pgsql-ru-general. On other >> lists, they should bounce as spam. Similar with the Chinese, >> Japanese, Korean, etc. character sets. > > That is an excellent suggestion! Except it prevents posters having their name or signature in their native character set. I can think of at least one contributor that does that. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > On Mon, Jun 15, 2009 at 5:54 PM, Bruce Momjian<bruce@momjian.us> wrote: > > David Fetter wrote: > >> > I think spamassassin has a flag to not except anything that isn't > >> > >> I think you meant, "accept." > >> > >> > certain character sets. ?Would that help in this case. > >> > >> Cyrillic character sets are only legit on pgsql-ru-general. ?On other > >> lists, they should bounce as spam. ?Similar with the Chinese, > >> Japanese, Korean, etc. character sets. > > > > That is an excellent suggestion! > > Except it prevents posters having their name or signature in their > native character set. I can think of at least one contributor that > does that. I was thinking of the "Subject" line. Also, we can let subscribed people have anything they want; this would only be for unsubscribed items that have to be moderated. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Mon, Jun 15, 2009 at 5:58 PM, Bruce Momjian<bruce@momjian.us> wrote: > I was thinking of the "Subject" line. What's Re: in russian? :-p > Also, we can let subscribed > people have anything they want; this would only be for unsubscribed > items that have to be moderated. I'd be happier with that if we allowed users of one list to post to another without subscription, as was recently discussed. That would at least prevent x-posted threads losing messages. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, 2009-06-15 at 09:51 -0700, David Fetter wrote: > > > (We still get a lot of Russian spam.) > > > > I think spamassassin has a flag to not except anything that isn't > > I think you meant, "accept." I did, I am exhausted sorry. > > > certain character sets. Would that help in this case. > > Cyrillic character sets are only legit on pgsql-ru-general. On other > lists, they should bounce as spam. Similar with the Chinese, > Japanese, Korean, etc. character sets. Seems reasonable. Joshua D. Drake -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
Dave Page wrote: > On Mon, Jun 15, 2009 at 5:58 PM, Bruce Momjian<bruce@momjian.us> wrote: > > > I was thinking of the "Subject" line. > > What's Re: in russian? :-p > > > Also, we can let subscribed > > people have anything they want; ?this would only be for unsubscribed > > items that have to be moderated. > > I'd be happier with that if we allowed users of one list to post to > another without subscription, as was recently discussed. That would at > least prevent x-posted threads losing messages. Yes, we should do that too. Right now obviously the moderation load is unsustainable; we can't keep going with our current system. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Dave Page wrote: > On Mon, Jun 15, 2009 at 5:54 PM, Bruce Momjian<bruce@momjian.us> wrote: > > David Fetter wrote: > >> Cyrillic character sets are only legit on pgsql-ru-general. On other > >> lists, they should bounce as spam. Similar with the Chinese, > >> Japanese, Korean, etc. character sets. > > > > That is an excellent suggestion! > > Except it prevents posters having their name or signature in their > native character set. I can think of at least one contributor that > does that. Nonsense. The header is escaped differently. (Of course, the sysadmin needs to ensure that this continues to work properly.) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Dave Page wrote: > On Mon, Jun 15, 2009 at 5:58 PM, Bruce Momjian<bruce@momjian.us> wrote: > > Also, we can let subscribed > > people have anything they want; this would only be for unsubscribed > > items that have to be moderated. > > I'd be happier with that if we allowed users of one list to post to > another without subscription, as was recently discussed. That would at > least prevent x-posted threads losing messages. +1. The only vote against was an hypothetical objection from Marc which seems baseless to me. (Also, pgsql-es-ayuda is configured that way, though of course crossposting to that list is not very common.) -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
On Mon, 15 Jun 2009, Bruce Momjian wrote: > I was thinking of the "Subject" line. Also, we can let subscribed > people have anything they want; this would only be for unsubscribed > items that have to be moderated. If someone has a regex to do this, we can easily set it up in Mj2 on a per list basis ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
I'm kinda curious as to which lists this 'unstustainable' is on ... I just checked pgsql-general ... out of 10 messages that are in the queue right now: 7 are subscribe / set requests 1 is spam from Jun 11th 2 are legit postings from Jun 11th (which I've just approved) pgsql-admin: 25 messages in queue 4 subscribe / set 20 spam 1 non-spam ... approved from the 10th Okay, so that one has a huge noise:signal ratio On Mon, 15 Jun 2009, Bruce Momjian wrote: > Dave Page wrote: >> On Mon, Jun 15, 2009 at 5:58 PM, Bruce Momjian<bruce@momjian.us> wrote: >> >>> I was thinking of the "Subject" line. >> >> What's Re: in russian? :-p >> >>> Also, we can let subscribed >>> people have anything they want; ?this would only be for unsubscribed >>> items that have to be moderated. >> >> I'd be happier with that if we allowed users of one list to post to >> another without subscription, as was recently discussed. That would at >> least prevent x-posted threads losing messages. > > Yes, we should do that too. Right now obviously the moderation load is > unsustainable; we can't keep going with our current system. > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, 15 Jun 2009, Joshua D. Drake wrote: > I think spamassassin has a flag to not except anything that isn't > certain character sets. Would that help in this case. No, as that would be 'list wide' ... better to cmoe up with some sort of regex that would trap things, say, by Subject, as Bruce suggested ... then we could easily add that to the per-list configuration file and reject it at that level ... I've tried unsucessfully in the past to do language based regex's and failed miserably though ... anyone out there good at this? ; ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, Jun 15, 2009 at 9:02 PM, Dave Page<dpage@pgadmin.org> wrote: > And as if mj2 wanted to prove the point, I had to approve this very message... Hah - twice at that, because it got cross-posted! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
And as if mj2 wanted to prove the point, I had to approve this very message... On Mon, Jun 15, 2009 at 8:55 PM, Marc G. Fournier<scrappy@hub.org> wrote: > > I'm kinda curious as to which lists this 'unstustainable' is on ... I just > checked pgsql-general ... out of 10 messages that are in the queue right > now: > > 7 are subscribe / set requests > 1 is spam from Jun 11th > 2 are legit postings from Jun 11th (which I've just approved) > > pgsql-admin: 25 messages in queue > > 4 subscribe / set > 20 spam > 1 non-spam ... approved from the 10th > > Okay, so that one has a huge noise:signal ratio > > > > On Mon, 15 Jun 2009, Bruce Momjian wrote: > >> Dave Page wrote: >>> >>> On Mon, Jun 15, 2009 at 5:58 PM, Bruce Momjian<bruce@momjian.us> wrote: >>> >>>> I was thinking of the "Subject" line. >>> >>> What's Re: in russian? :-p >>> >>>> Also, we can let subscribed >>>> people have anything they want; ?this would only be for unsubscribed >>>> items that have to be moderated. >>> >>> I'd be happier with that if we allowed users of one list to post to >>> another without subscription, as was recently discussed. That would at >>> least prevent x-posted threads losing messages. >> >> Yes, we should do that too. Right now obviously the moderation load is >> unsustainable; we can't keep going with our current system. >> >> -- >> Bruce Momjian <bruce@momjian.us> http://momjian.us >> EnterpriseDB http://enterprisedb.com >> >> + If your life is a hard drive, Christ can be your backup. + >> > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Marc G. Fournier wrote: > > I'm kinda curious as to which lists this 'unstustainable' is on ... I just > checked pgsql-general ... out of 10 messages that are in the queue right > now: > > 7 are subscribe / set requests > 1 is spam from Jun 11th > 2 are legit postings from Jun 11th (which I've just approved) > > pgsql-admin: 25 messages in queue > > 4 subscribe / set > 20 spam > 1 non-spam ... approved from the 10th > > Okay, so that one has a huge noise:signal ratio I really don't know which lists are a problem myself, but people are resigning from moderation duty, so something obviously has to be improved. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Mon, 15 Jun 2009, Alvaro Herrera wrote: > +1. The only vote against was an hypothetical objection from Marc which > seems baseless to me. (Also, pgsql-es-ayuda is configured that way, > though of course crossposting to that list is not very common.) This was done *ages* ago ... Does anyone know which lists it isn't configured on: configset DEFAULT restrict_post <<ENDAAB GLOBAL: ENDAAB ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, Jun 15, 2009 at 9:04 PM, Dave Page<dpage@pgadmin.org> wrote: > On Mon, Jun 15, 2009 at 9:02 PM, Dave Page<dpage@pgadmin.org> wrote: >> And as if mj2 wanted to prove the point, I had to approve this very message... > > Hah - twice at that, because it got cross-posted! Now 6 times, due to the followups to Marc's message which included the s word. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, 15 Jun 2009, Dave Page wrote: > And as if mj2 wanted to prove the point, I had to approve this very message... Based on ... ? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, Jun 15, 2009 at 9:07 PM, Marc G. Fournier<scrappy@hub.org> wrote: > On Mon, 15 Jun 2009, Dave Page wrote: > >> And as if mj2 wanted to prove the point, I had to approve this very >> message... > > Based on ... ? It, and every followup included the word s u b s c r i b e -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, Jun 15, 2009 at 9:09 PM, Marc G. Fournier<scrappy@hub.org> wrote: > On Mon, 15 Jun 2009, Dave Page wrote: > >> On Mon, Jun 15, 2009 at 9:02 PM, Dave Page<dpage@pgadmin.org> wrote: >>> >>> And as if mj2 wanted to prove the point, I had to approve this very >>> message... >> >> Hah - twice at that, because it got cross-posted! > > Okay, so, just to confirm ... you want *anyone* subscribe to *any* list to > be able to post without moderator approver to pgsql-www? Right now, this > one is setup as just those *on* pgsql-www can post through ... Yes - that was what I thought everyone agreed. Otherwise, I just end up having to approve potentially dozens of messages if a thread crosses over from somewhere else. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, 15 Jun 2009, Dave Page wrote: > On Mon, Jun 15, 2009 at 9:02 PM, Dave Page<dpage@pgadmin.org> wrote: >> And as if mj2 wanted to prove the point, I had to approve this very message... > > Hah - twice at that, because it got cross-posted! Okay, so, just to confirm ... you want *anyone* subscribe to *any* list to be able to post without moderator approver to pgsql-www? Right now, this one is setup as just those *on* pgsql-www can post through ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Marc G. Fournier wrote: > On Mon, 15 Jun 2009, Dave Page wrote: > > > On Mon, Jun 15, 2009 at 9:02 PM, Dave Page<dpage@pgadmin.org> wrote: > >> And as if mj2 wanted to prove the point, I had to approve this very message... > > > > Hah - twice at that, because it got cross-posted! > > Okay, so, just to confirm ... you want *anyone* subscribe to *any* list to > be able to post without moderator approver to pgsql-www? Right now, this > one is setup as just those *on* pgsql-www can post through ... Yep, if it becomes a problem, we can always revert it. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Mon, 15 Jun 2009, Dave Page wrote: > > Yes - that was what I thought everyone agreed. Otherwise, I just end > up having to approve potentially dozens of messages if a thread > crosses over from somewhere else. Done: configset pgsql-www restrict_post <<ENDAAB GLOBAL: ENDAAB > > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
I know I'm going to regret this one, but ... what regex pattern do you want me to change and to what? configset GLOBAL admin_headers <<ENDAAB /^subject:\s*subscribe\b/i /^subject:\s*unsubscribe\b/i /^subject:\s*uns\w*b/i /^subject:\s*.*un-sub/i /^subject:\s*help\b/i /^subject:\s.*\bchange\b.*\baddress\b/i /^subject:\s*request\b(.*\b)?addition\b/i /^subject:\s*cancel\b/i /^subject:\s*set\b/i /MSGRCPT/ ENDAAB On Mon, 15 Jun 2009, Dave Page wrote: > On Mon, Jun 15, 2009 at 9:07 PM, Marc G. Fournier<scrappy@hub.org> wrote: >> On Mon, 15 Jun 2009, Dave Page wrote: >> >>> And as if mj2 wanted to prove the point, I had to approve this very >>> message... >> >> Based on ... ? > > It, and every followup included the word s u b s c r i b e > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, Jun 15, 2009 at 9:12 PM, Marc G. Fournier<scrappy@hub.org> wrote: > > I know I'm going to regret this one, but ... what regex pattern do you want > me to change and to what? > > configset GLOBAL admin_headers <<ENDAAB > /^subject:\s*subscribe\b/i > /^subject:\s*unsubscribe\b/i > /^subject:\s*uns\w*b/i > /^subject:\s*.*un-sub/i > /^subject:\s*help\b/i > /^subject:\s.*\bchange\b.*\baddress\b/i > /^subject:\s*request\b(.*\b)?addition\b/i > /^subject:\s*cancel\b/i > /^subject:\s*set\b/i > /MSGRCPT/ > ENDAAB Afaics, none of those. You used the s word in the body, which seems to be the biggest problem. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, Jun 15, 2009 at 9:14 PM, Dave Page<dpage@pgadmin.org> wrote: > On Mon, Jun 15, 2009 at 9:12 PM, Marc G. Fournier<scrappy@hub.org> wrote: >> >> I know I'm going to regret this one, but ... what regex pattern do you want >> me to change and to what? >> >> configset GLOBAL admin_headers <<ENDAAB >> /^subject:\s*subscribe\b/i >> /^subject:\s*unsubscribe\b/i >> /^subject:\s*uns\w*b/i >> /^subject:\s*.*un-sub/i >> /^subject:\s*help\b/i >> /^subject:\s.*\bchange\b.*\baddress\b/i >> /^subject:\s*request\b(.*\b)?addition\b/i >> /^subject:\s*cancel\b/i >> /^subject:\s*set\b/i >> /MSGRCPT/ >> ENDAAB > > Afaics, none of those. You used the s word in the body, which seems to > be the biggest problem. If it helps: GLOBAL ADMIN BODY: /\bsubscribe\b/i matched "subscribe" at line number 6.GLOBAL ADMIN BODY: /\bunsubscribe\b/i matched"unsubscribe" at line number 7. And I'm now up to 15 approvals for this thread... -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
So you mean these ones: 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 /\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*index\s+\S+\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 ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > I'm kinda curious as to which lists this 'unstustainable' is on ... I just > checked pgsql-general ... out of 10 messages that are in the queue right > now: Check out -bugs. Right now it's > 60 messages, and I'm betting the amount of non-spam is 0,1, or 2 of those. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200906151736 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAko2vsUACgkQvJuQZxSWSsiC/wCfYJfbGE+fJUVOTYS+nqTs8qvr VLgAoL0avb3K9Pv2SRx6f393gaB+0tMR =kAzi -----END PGP SIGNATURE-----
On Mon, 2009-06-15 at 21:36 +0000, Greg Sabino Mullane wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > > > I'm kinda curious as to which lists this 'unstustainable' is on ... I just > > checked pgsql-general ... out of 10 messages that are in the queue right > > now: > > Check out -bugs. Right now it's > 60 messages, and I'm betting the amount > of non-spam is 0,1, or 2 of those. This is actually being pretty heavily discussed for solutions on sysadmins right now. > > - -- > Greg Sabino Mullane greg@turnstep.com > PGP Key: 0x14964AC8 200906151736 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > -----BEGIN PGP SIGNATURE----- > > iEYEAREDAAYFAko2vsUACgkQvJuQZxSWSsiC/wCfYJfbGE+fJUVOTYS+nqTs8qvr > VLgAoL0avb3K9Pv2SRx6f393gaB+0tMR > =kAzi > -----END PGP SIGNATURE----- > > > -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
Marc G. Fournier wrote: > This was done *ages* ago ... > > Does anyone know which lists it isn't configured on: > > configset DEFAULT restrict_post <<ENDAAB > GLOBAL: > ENDAAB Ah, great, thanks. You actually objected to the idea last week. Surprising how short ages have become, of late. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
On Mon, 15 Jun 2009, Marc G. Fournier wrote: > I've tried unsucessfully in the past to do language based regex's and failed > miserably though ... anyone out there good at this? ; I thought Josh was suggesting leaning on the SpamAssassin toolset here, you're certainly not going to write this yourself in any reasonable amount of time. The two rules you can use are: CHARSET_FARAWAY Character set indicates a foreign language UNWANTED_LANGUAGE_BODY Message written in an undesired language which both default to a relatively high score (around +3 points on the rev I just checked). The languages you're willing to accept goes into ok_languages, http://email.about.com/cs/spamassassintips/qt/et032504.htm has a reasonable primer here. That defaults to "all". Since tripping that rule alone isn't enough to pass a typical threshold, legit messages from people that just happen to have foreign stuff in their signature and such should typically survive. You might start by setting ok_languages and reducing the point value for the rules to something small in order to judge its impact, before using the higher default score. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
On Mon, 2009-06-15 at 19:08 -0400, Greg Smith wrote: > On Mon, 15 Jun 2009, Marc G. Fournier wrote: > > > I've tried unsucessfully in the past to do language based regex's and failed > > miserably though ... anyone out there good at this? ; > > I thought Josh was suggesting leaning on the SpamAssassin toolset here, > you're certainly not going to write this yourself in any reasonable amount > of time. Yes that is what I was suggesting. Joshua D. Drake -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
On Mon, 15 Jun 2009, Alvaro Herrera wrote: > Ah, great, thanks. You actually objected to the idea last week. > Surprising how short ages have become, of late. No, I did not object, I pointed out the potential ramifications of doing it ... :) ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Mon, Jun 15, 2009 at 4:14 PM, Marc G. Fournier<scrappy@hub.org> wrote: > On Mon, 15 Jun 2009, Dave Page wrote: > >> >> Yes - that was what I thought everyone agreed. Otherwise, I just end >> up having to approve potentially dozens of messages if a thread >> crosses over from somewhere else. > > Done: > > configset pgsql-www restrict_post <<ENDAAB > GLOBAL: > ENDAAB Forgive me for asking, but is this also set up this way for pgsql-hackers and pgsql-bugs? Threads are frequently cross-posted between the two, and ISTM I've had problems with stalled posts to -bugs in the not-too-distant past. ...Robert
>> I thought Josh was suggesting leaning on the SpamAssassin toolset here, >> you're certainly not going to write this yourself in any reasonable amount >> of time. > > Yes that is what I was suggesting. One worry, though ... will SA scale to the volume we need? My experience of SA is that it's a memory hog. We might need to figure out DSpam instead. -- Josh Berkus PostgreSQL Experts Inc. www.pgexperts.com
On Tue, Jun 16, 2009 at 12:08 AM, Greg Smith<gsmith@gregsmith.com> wrote: > On Mon, 15 Jun 2009, Marc G. Fournier wrote: > >> I've tried unsucessfully in the past to do language based regex's and >> failed miserably though ... anyone out there good at this? ; > > I thought Josh was suggesting leaning on the SpamAssassin toolset here, > you're certainly not going to write this yourself in any reasonable amount > of time. The two rules you can use are: > > CHARSET_FARAWAY Character set indicates a foreign language > UNWANTED_LANGUAGE_BODY Message written in an undesired language That doesn't help much because SA is configured globally, not per list. Unless Marc changed that. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Looks like it. Perhaps the mj2 commands we want to catch should be anchored to the beginning of the line. All the ones that look like: /\bsubscribe\b/i are completely forbidden, which seems look the root of my complaint. On Mon, Jun 15, 2009 at 9:57 PM, Marc G. Fournier<scrappy@hub.org> wrote: > > So you mean these ones: > > 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 > /\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*index\s+\S+\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 > > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mon, Jun 15, 2009 at 9:14 PM, Marc G. Fournier<scrappy@hub.org> wrote: > On Mon, 15 Jun 2009, Dave Page wrote: > >> >> Yes - that was what I thought everyone agreed. Otherwise, I just end >> up having to approve potentially dozens of messages if a thread >> crosses over from somewhere else. > > Done: > > configset pgsql-www restrict_post <<ENDAAB > GLOBAL: > ENDAAB I just realised you only did that for -www. The idea was to do it for all the lists. For example, I just had to deal with this: > The following request: > > "(post to webmaster)" > > was sent to postgresql.org > by Tom Lane <tgl@sss.pgh.pa.us>. > > The request requires your confirmation for the following reason(s): > > The author (Tom Lane <tgl@sss.pgh.pa.us>) > is not a member of any of the restrict_post groups. Thanks! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, 16 Jun 2009, Dave Page wrote: > That doesn't help much because SA is configured globally, not per > list. Unless Marc changed that. You might still be able to get some utility out of it just by including only the languages at least one list accepts traffic in. You'll still assign points to all the spam that doesn't match any list's native language. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
On 6/16/09, Greg Smith <gsmith@gregsmith.com> wrote: > On Tue, 16 Jun 2009, Dave Page wrote: > >> That doesn't help much because SA is configured globally, not per >> list. Unless Marc changed that. > > You might still be able to get some utility out of it just by including > only the languages at least one list accepts traffic in. You'll still > assign points to all the spam that doesn't match any list's native > language. We have a Russian list, so the majority of spam would still get through. However, it's a spam filter thats part of the hub.org mail system, which (unfortunately) means it's not just languages that we use that matter. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > On 6/16/09, Greg Smith <gsmith@gregsmith.com> wrote: > > On Tue, 16 Jun 2009, Dave Page wrote: > > > >> That doesn't help much because SA is configured globally, not per > >> list. Unless Marc changed that. > > > > You might still be able to get some utility out of it just by including > > only the languages at least one list accepts traffic in. You'll still > > assign points to all the spam that doesn't match any list's native > > language. > > We have a Russian list, so the majority of spam would still get > through. However, it's a spam filter thats part of the hub.org mail > system, which (unfortunately) means it's not just languages that we > use that matter. Is there really no way to say "if it's russian, and not in pgsql-ru-whatever, add 5 points to spam score"? If that's not possible, maybe we could have a rule "add 5 points if russian", and another "subtract 5 points if destined for pgsql-ru-blah" -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
On 6/16/09, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Dave Page wrote: >> On 6/16/09, Greg Smith <gsmith@gregsmith.com> wrote: >> > On Tue, 16 Jun 2009, Dave Page wrote: >> > >> >> That doesn't help much because SA is configured globally, not per >> >> list. Unless Marc changed that. >> > >> > You might still be able to get some utility out of it just by including >> > only the languages at least one list accepts traffic in. You'll still >> > assign points to all the spam that doesn't match any list's native >> > language. >> >> We have a Russian list, so the majority of spam would still get >> through. However, it's a spam filter thats part of the hub.org mail >> system, which (unfortunately) means it's not just languages that we >> use that matter. > > Is there really no way to say "if it's russian, and not in > pgsql-ru-whatever, add 5 points to spam score"? > > If that's not possible, maybe we could have a rule "add 5 points if > russian", and another "subtract 5 points if destined for pgsql-ru-blah" Its possible Marc can hack that in, but afaik, the SA instances are on dedicated VM's and are simple relays with no knowledge of postgresql.org, mj2 or any other servers or domains. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > Its possible Marc can hack that in, but afaik, the SA instances are on > dedicated VM's and are simple relays with no knowledge of > postgresql.org, mj2 or any other servers or domains. I don't see that they need to know about postgresql.org or mj2. They just need a fixed rule based on the headers (something based on "Cc: pgsql-ru-" or "To: pgsql-ru-" should do it.) Ultimately it seems the failure to fix this problem is just because Marc is the only one able to do it, and he's not around enough. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On 6/16/09, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Dave Page wrote: > >> Its possible Marc can hack that in, but afaik, the SA instances are on >> dedicated VM's and are simple relays with no knowledge of >> postgresql.org, mj2 or any other servers or domains. > > I don't see that they need to know about postgresql.org or mj2. They > just need a fixed rule based on the headers (something based on "Cc: > pgsql-ru-" or "To: pgsql-ru-" should do it.) That's what i meant by hack it in. > Ultimately it seems the failure to fix this problem is just because Marc > is the only one able to do it, and he's not around enough. No, the real problem is having our mail infrastructure tied into hub.org as a number of us have said before. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > On 6/16/09, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > Ultimately it seems the failure to fix this problem is just because Marc > > is the only one able to do it, and he's not around enough. > > No, the real problem is having our mail infrastructure tied into > hub.org as a number of us have said before. Yes. So what? There's not enough “political” pressure to fix that problem. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Was for pgsql-hackers, is now also for pgsql-bugs ... On Tue, 16 Jun 2009, Robert Haas wrote: > On Mon, Jun 15, 2009 at 4:14 PM, Marc G. Fournier<scrappy@hub.org> wrote: >> On Mon, 15 Jun 2009, Dave Page wrote: >> >>> >>> Yes - that was what I thought everyone agreed. Otherwise, I just end >>> up having to approve potentially dozens of messages if a thread >>> crosses over from somewhere else. >> >> Done: >> >> configset pgsql-www restrict_post <<ENDAAB >> GLOBAL: >> ENDAAB > > Forgive me for asking, but is this also set up this way for > pgsql-hackers and pgsql-bugs? Threads are frequently cross-posted > between the two, and ISTM I've had problems with stalled posts to > -bugs in the not-too-distant past. > > ...Robert > > ---------------------------(end of broadcast)--------------------------- > If the PostgreSQL.org mailing lists are down, use the auxillary list pgsysadmins@agliodbs.com > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Most should already be done .. not sure why they aren't all, but if you see something that still isn't (pgsql-bugs and webmaster are set now), let me know ... On Tue, 16 Jun 2009, Dave Page wrote: > On Mon, Jun 15, 2009 at 9:14 PM, Marc G. Fournier<scrappy@hub.org> wrote: >> On Mon, 15 Jun 2009, Dave Page wrote: >> >>> >>> Yes - that was what I thought everyone agreed. Otherwise, I just end >>> up having to approve potentially dozens of messages if a thread >>> crosses over from somewhere else. >> >> Done: >> >> configset pgsql-www restrict_post <<ENDAAB >> GLOBAL: >> ENDAAB > > I just realised you only did that for -www. The idea was to do it for > all the lists. For example, I just had to deal with this: > >> The following request: >> >> "(post to webmaster)" >> >> was sent to postgresql.org >> by Tom Lane <tgl@sss.pgh.pa.us>. >> >> The request requires your confirmation for the following reason(s): >> >> The author (Tom Lane <tgl@sss.pgh.pa.us>) >> is not a member of any of the restrict_post groups. > > Thanks! > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Tue, 16 Jun 2009, Dave Page wrote: >> Ultimately it seems the failure to fix this problem is just because >> Marc is the only one able to do it, and he's not around enough. > > No, the real problem is having our mail infrastructure tied into hub.org > as a number of us have said before. Now that I have those two new servers in place, if someone wants to setup spamassassin on that VPS itself to run instead of going through the global spamassassin daemon, I'm cool with that ... I haven't moved mail over to the new servers yet, but that just takes 15-20 minutes of downtime to make happen ... could do that tomorrow evening ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Marc G. Fournier wrote: > On Tue, 16 Jun 2009, Dave Page wrote: > >>> Ultimately it seems the failure to fix this problem is just because >>> Marc is the only one able to do it, and he's not around enough. >> >> No, the real problem is having our mail infrastructure tied into >> hub.org as a number of us have said before. > > Now that I have those two new servers in place, if someone wants to > setup spamassassin on that VPS itself to run instead of going through > the global spamassassin daemon, I'm cool with that ... I haven't moved > mail over to the new servers yet, but that just takes 15-20 minutes of > downtime to make happen ... could do that tomorrow evening ... Just to be absolutely clear on what you're saying here. Are you saying that you are now OK with de-coupling the postgresql.org mail from hub.org making it a community managed service? Or are you saying that you're ok with running a *second* instance of spamassassin, and still keep mail going through hub.org relays? -- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/
On Tue, 23 Jun 2009, Magnus Hagander wrote: > Marc G. Fournier wrote: >> On Tue, 16 Jun 2009, Dave Page wrote: >> >>>> Ultimately it seems the failure to fix this problem is just because >>>> Marc is the only one able to do it, and he's not around enough. >>> >>> No, the real problem is having our mail infrastructure tied into >>> hub.org as a number of us have said before. >> >> Now that I have those two new servers in place, if someone wants to >> setup spamassassin on that VPS itself to run instead of going through >> the global spamassassin daemon, I'm cool with that ... I haven't moved >> mail over to the new servers yet, but that just takes 15-20 minutes of >> downtime to make happen ... could do that tomorrow evening ... > > Just to be absolutely clear on what you're saying here. > > Are you saying that you are now OK with de-coupling the postgresql.org > mail from hub.org making it a community managed service? > > Or are you saying that you're ok with running a *second* instance of > spamassassin, and still keep mail going through hub.org relays? I'm okay with a dedicated instance of spamassassin running in mail.postgresql.org so that it can be more tailored / configured to mark spam going through to the moderators ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On 23 jun 2009, at 12.14, "Marc G. Fournier" <scrappy@hub.org> wrote: > On Tue, 23 Jun 2009, Magnus Hagander wrote: > >> Marc G. Fournier wrote: >>> On Tue, 16 Jun 2009, Dave Page wrote: >>> >>>>> Ultimately it seems the failure to fix this problem is just >>>>> because >>>>> Marc is the only one able to do it, and he's not around enough. >>>> >>>> No, the real problem is having our mail infrastructure tied into >>>> hub.org as a number of us have said before. >>> >>> Now that I have those two new servers in place, if someone wants to >>> setup spamassassin on that VPS itself to run instead of going >>> through >>> the global spamassassin daemon, I'm cool with that ... I haven't >>> moved >>> mail over to the new servers yet, but that just takes 15-20 >>> minutes of >>> downtime to make happen ... could do that tomorrow evening ... >> >> Just to be absolutely clear on what you're saying here. >> >> Are you saying that you are now OK with de-coupling the >> postgresql.org >> mail from hub.org making it a community managed service? >> >> Or are you saying that you're ok with running a *second* instance of >> spamassassin, and still keep mail going through hub.org relays? > > I'm okay with a dedicated instance of spamassassin running in mail.postgresql.org > so that it can be more tailored / configured to mark spam going > through to the moderators ... So you're still not accepting that the mail services are a community service and resource. Ok, sorry to hear that, but good to know. In that case, the the statement by Dave still stands - this does not fix the actual issue. It does paint over one crack a bit, but it does nothing to fix the structural problem. /Magnus
Marc G. Fournier wrote: > On Tue, 16 Jun 2009, Dave Page wrote: > >>> Ultimately it seems the failure to fix this problem is just because >>> Marc is the only one able to do it, and he's not around enough. >> >> No, the real problem is having our mail infrastructure tied into >> hub.org as a number of us have said before. > > Now that I have those two new servers in place, if someone wants to setup > spamassassin on that VPS itself to run instead of going through the > global spamassassin daemon, I'm cool with that ... I haven't moved mail > over to the new servers yet, but that just takes 15-20 minutes of > downtime to make happen ... could do that tomorrow evening ... By all means do *not* do it until 8.4 is well past release ... -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Tue, Jun 23, 2009 at 6:31 AM, Magnus Hagander<magnus@hagander.net> wrote: > > On 23 jun 2009, at 12.14, "Marc G. Fournier" <scrappy@hub.org> wrote: > >> On Tue, 23 Jun 2009, Magnus Hagander wrote: >> >>> Marc G. Fournier wrote: >>>> >>>> On Tue, 16 Jun 2009, Dave Page wrote: >>>> >>>>>> Ultimately it seems the failure to fix this problem is just because >>>>>> Marc is the only one able to do it, and he's not around enough. >>>>> >>>>> No, the real problem is having our mail infrastructure tied into >>>>> hub.org as a number of us have said before. >>>> >>>> Now that I have those two new servers in place, if someone wants to >>>> setup spamassassin on that VPS itself to run instead of going through >>>> the global spamassassin daemon, I'm cool with that ... I haven't moved >>>> mail over to the new servers yet, but that just takes 15-20 minutes of >>>> downtime to make happen ... could do that tomorrow evening ... >>> >>> Just to be absolutely clear on what you're saying here. >>> >>> Are you saying that you are now OK with de-coupling the postgresql.org >>> mail from hub.org making it a community managed service? >>> >>> Or are you saying that you're ok with running a *second* instance of >>> spamassassin, and still keep mail going through hub.org relays? >> >> I'm okay with a dedicated instance of spamassassin running in >> mail.postgresql.org so that it can be more tailored / configured to mark >> spam going through to the moderators ... > > So you're still not accepting that the mail services are a community service > and resource. Ok, sorry to hear that, but good to know. > > In that case, the the statement by Dave still stands - this does not fix the > actual issue. It does paint over one crack a bit, but it does nothing to fix > the structural problem. Since I'm new here, what is the structural problem? ...Robert
Robert Haas wrote: > On Tue, Jun 23, 2009 at 6:31 AM, Magnus Hagander<magnus@hagander.net> wrote: >> On 23 jun 2009, at 12.14, "Marc G. Fournier" <scrappy@hub.org> wrote: >> >>> On Tue, 23 Jun 2009, Magnus Hagander wrote: >>> >>>> Marc G. Fournier wrote: >>>>> On Tue, 16 Jun 2009, Dave Page wrote: >>>>> >>>>>>> Ultimately it seems the failure to fix this problem is just because >>>>>>> Marc is the only one able to do it, and he's not around enough. >>>>>> No, the real problem is having our mail infrastructure tied into >>>>>> hub.org as a number of us have said before. >>>>> Now that I have those two new servers in place, if someone wants to >>>>> setup spamassassin on that VPS itself to run instead of going through >>>>> the global spamassassin daemon, I'm cool with that ... I haven't moved >>>>> mail over to the new servers yet, but that just takes 15-20 minutes of >>>>> downtime to make happen ... could do that tomorrow evening ... >>>> Just to be absolutely clear on what you're saying here. >>>> >>>> Are you saying that you are now OK with de-coupling the postgresql.org >>>> mail from hub.org making it a community managed service? >>>> >>>> Or are you saying that you're ok with running a *second* instance of >>>> spamassassin, and still keep mail going through hub.org relays? >>> I'm okay with a dedicated instance of spamassassin running in >>> mail.postgresql.org so that it can be more tailored / configured to mark >>> spam going through to the moderators ... >> So you're still not accepting that the mail services are a community service >> and resource. Ok, sorry to hear that, but good to know. >> >> In that case, the the statement by Dave still stands - this does not fix the >> actual issue. It does paint over one crack a bit, but it does nothing to fix >> the structural problem. > > Since I'm new here, what is the structural problem? Well, as Dave said earlier: everything about the email handling is deeply integrated in the hub.org systems. Which are not maintained by the community (they're maintained by hub.org == Marc (who is a member of the community of course, but that doesn't make it a community service)), not documented (at least not in a way that is available and useful to the community), designed with all of hub.org in mind and not focused on the needs of postgresql.org etc. The only part that is running on a community managed VM is the majordomo install. Relay in *and* out of it, spamfilter, graylisting, etc, etc, is all hub.org. Feel free to browse the archives for previous discussions on this topic :-P -- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/
On Tue, 23 Jun 2009, Magnus Hagander wrote: > > Well, as Dave said earlier: everything about the email handling is > deeply integrated in the hub.org systems. No it isn't ... when the VPS was first setup, the agreement was that someone was going to setup spamassassin on it as a failback mechanism in case of any problems with the central spamassassin ... to the best of my knowledge, nobody has done that ... Mail going out from Majordomo is set to go out three different MX servers so that they are spread across three postfix queues instead of bottlenecking into one ... there is nothing 'deeply integrated' there, its a performance thing that can be simply removed by doing: mj_shell -p XXXX configedit DEFAULT delivery_rules A command there there are several admins on the list capable of doing ... Even the spamassassin stuff is easily disabled by a simple modification to the postfix main.cf file to remove the content_filter and sqlgrey lines .. nothing "deeply integrated" there either, the processing is just offloaded to a different physical server ... If you don't *understand* how things are setup, don't jump to the falsely represented it as 'deeply integrated', as there is nothing integrated with anything Hub related, only stuff piggy backing off of, and those things are be very easily detached ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Tue, 23 Jun 2009, Alvaro Herrera wrote: > By all means do *not* do it until 8.4 is well past release ... Why not? I'm not making any changes, other then rsync'ng files between physical servers ... both are running same kernel, 64bit, etc ... the new machine just has ~6x the RAM on it, and 3x the drives ... I'm not upgrading the VPS, or changing config files ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Tue, 16 Jun 2009, Dave Page wrote: > Looks like it. Perhaps the mj2 commands we want to catch should be > anchored to the beginning of the line. All the ones that look like: > > /\bsubscribe\b/i > > are completely forbidden, which seems look the root of my complaint. So, change: /\bsubscribe\b/i to /^subscribe\b/i ? I can do that, just want to make sure we're on the same page before I do ... > > On Mon, Jun 15, 2009 at 9:57 PM, Marc G. Fournier<scrappy@hub.org> wrote: >> >> So you mean these ones: >> >> 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 >> /\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*index\s+\S+\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 >> >> >> ---- >> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) >> Email . scrappy@hub.org MSN . scrappy@hub.org >> Yahoo . yscrappy Skype: hub.org ICQ . 7615664 >> > > > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > > ---------------------------(end of broadcast)--------------------------- > If the PostgreSQL.org mailing lists are down, use the auxillary list pgsysadmins@agliodbs.com > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On Tue, Jun 23, 2009 at 4:57 PM, Marc G. Fournier<scrappy@hub.org> wrote: > On Tue, 16 Jun 2009, Dave Page wrote: > >> Looks like it. Perhaps the mj2 commands we want to catch should be >> anchored to the beginning of the line. All the ones that look like: >> >> /\bsubscribe\b/i >> >> are completely forbidden, which seems look the root of my complaint. > > So, change: > > /\bsubscribe\b/i > > to > > /^subscribe\b/i > > ? > > I can do that, just want to make sure we're on the same page before I do ... That seems reasonable to me. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Marc G. Fournier wrote: > On Tue, 23 Jun 2009, Magnus Hagander wrote: > >> >> Well, as Dave said earlier: everything about the email handling is >> deeply integrated in the hub.org systems. > > No it isn't ... when the VPS was first setup, the agreement was that > someone was going to setup spamassassin on it as a failback mechanism in > case of any problems with the central spamassassin ... to the best of my > knowledge, nobody has done that ... That's not what we're talking about. > Mail going out from Majordomo is set to go out three different MX > servers so that they are spread across three postfix queues instead of > bottlenecking into one ... there is nothing 'deeply integrated' there, > its a performance thing that can be simply removed by doing: Again, that's not what people are talking about. That is the one part of the system that usually works. Even if it would've been nice to have the thing documented, as has been requested for years, rather than to have to go to the list archives. It's the incoming mail, an the maia integration, that is the reason for almost every single instance of our lists not working every now and then. It may very well be that a community maintained system would have the exact same issues, but it would have more people who could look at it. > mj_shell -p XXXX configedit DEFAULT delivery_rules > > A command there there are several admins on the list capable of doing ... > > Even the spamassassin stuff is easily disabled by a simple modification > to the postfix main.cf file to remove the content_filter and sqlgrey > lines .. nothing "deeply integrated" there either, the processing is > just offloaded to a different physical server ... > > If you don't *understand* how things are setup, don't jump to the > falsely represented it as 'deeply integrated', as there is nothing > integrated with anything Hub related, only stuff piggy backing off of, > and those things are be very easily detached ... Then why has this not happened since it has been requested for *years*? But you're now saying you're Ok to decouple it? Rather than the usual "never going to happen"? That's good news, indeed. Is the same true for DNS? //Magnus
Marc G. Fournier escribió: > If you don't *understand* how things are setup, don't jump to the falsely > represented it as 'deeply integrated', as there is nothing integrated > with anything Hub related, only stuff piggy backing off of, and those > things are be very easily detached ... How is anybody going to understand anything, given that you haven't documented it as has been requested dozens of times? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Tue, Jun 23, 2009 at 12:40 PM, Magnus Hagander<magnus@hagander.net> wrote: > Marc G. Fournier wrote: >> On Tue, 23 Jun 2009, Magnus Hagander wrote: >> >>> >>> Well, as Dave said earlier: everything about the email handling is >>> deeply integrated in the hub.org systems. >> >> No it isn't ... when the VPS was first setup, the agreement was that >> someone was going to setup spamassassin on it as a failback mechanism in >> case of any problems with the central spamassassin ... to the best of my >> knowledge, nobody has done that ... > > That's not what we're talking about. > > >> Mail going out from Majordomo is set to go out three different MX >> servers so that they are spread across three postfix queues instead of >> bottlenecking into one ... there is nothing 'deeply integrated' there, >> its a performance thing that can be simply removed by doing: > > Again, that's not what people are talking about. That is the one part of > the system that usually works. Even if it would've been nice to have the > thing documented, as has been requested for years, rather than to have > to go to the list archives. > > It's the incoming mail, an the maia integration, that is the reason for > almost every single instance of our lists not working every now and > then. It may very well be that a community maintained system would have > the exact same issues, but it would have more people who could look at it. > > >> mj_shell -p XXXX configedit DEFAULT delivery_rules >> >> A command there there are several admins on the list capable of doing ... >> >> Even the spamassassin stuff is easily disabled by a simple modification >> to the postfix main.cf file to remove the content_filter and sqlgrey >> lines .. nothing "deeply integrated" there either, the processing is >> just offloaded to a different physical server ... >> >> If you don't *understand* how things are setup, don't jump to the >> falsely represented it as 'deeply integrated', as there is nothing >> integrated with anything Hub related, only stuff piggy backing off of, >> and those things are be very easily detached ... > > Then why has this not happened since it has been requested for *years*? > > But you're now saying you're Ok to decouple it? Rather than the usual > "never going to happen"? That's good news, indeed. > > Is the same true for DNS? I notice that this thread seems to have died an abrupt death, but without really resolving any of the issues. ...Robert
On Fri, Jun 26, 2009 at 4:04 PM, Robert Haas<robertmhaas@gmail.com> wrote: > I notice that this thread seems to have died an abrupt death, but > without really resolving any of the issues. The original issue is resolved. I figured out how to relieve myself of duty. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Fri, Jun 26, 2009 at 17:04, Robert Haas<robertmhaas@gmail.com> wrote: > On Tue, Jun 23, 2009 at 12:40 PM, Magnus Hagander<magnus@hagander.net> wrote: >> Marc G. Fournier wrote: >>> On Tue, 23 Jun 2009, Magnus Hagander wrote: >>> >>>> >>>> Well, as Dave said earlier: everything about the email handling is >>>> deeply integrated in the hub.org systems. >>> >>> No it isn't ... when the VPS was first setup, the agreement was that >>> someone was going to setup spamassassin on it as a failback mechanism in >>> case of any problems with the central spamassassin ... to the best of my >>> knowledge, nobody has done that ... >> >> That's not what we're talking about. >> >> >>> Mail going out from Majordomo is set to go out three different MX >>> servers so that they are spread across three postfix queues instead of >>> bottlenecking into one ... there is nothing 'deeply integrated' there, >>> its a performance thing that can be simply removed by doing: >> >> Again, that's not what people are talking about. That is the one part of >> the system that usually works. Even if it would've been nice to have the >> thing documented, as has been requested for years, rather than to have >> to go to the list archives. >> >> It's the incoming mail, an the maia integration, that is the reason for >> almost every single instance of our lists not working every now and >> then. It may very well be that a community maintained system would have >> the exact same issues, but it would have more people who could look at it. >> >> >>> mj_shell -p XXXX configedit DEFAULT delivery_rules >>> >>> A command there there are several admins on the list capable of doing ... >>> >>> Even the spamassassin stuff is easily disabled by a simple modification >>> to the postfix main.cf file to remove the content_filter and sqlgrey >>> lines .. nothing "deeply integrated" there either, the processing is >>> just offloaded to a different physical server ... >>> >>> If you don't *understand* how things are setup, don't jump to the >>> falsely represented it as 'deeply integrated', as there is nothing >>> integrated with anything Hub related, only stuff piggy backing off of, >>> and those things are be very easily detached ... >> >> Then why has this not happened since it has been requested for *years*? >> >> But you're now saying you're Ok to decouple it? Rather than the usual >> "never going to happen"? That's good news, indeed. >> >> Is the same true for DNS? > > I notice that this thread seems to have died an abrupt death, but > without really resolving any of the issues. > > ...Robert > Yes. This is pretty much standard. -- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/