Thread: Listmail disappearing: bad spam filters?
Marc, WWW: I moderate three of the main PostgreSQL lists. For the last month or so, we've been having chronic issues with e-mails from certain users getting blocked. That is, they don't show up in the moderation queue. They may show up in the spam trap, but it's hard for me to tell: Maia does NOT provide a search interface, so I can't find them amount the 500+ e-mails in the trap. Blocked e-mails include even ones from regular PostgreSQL contributors like Gevik. Can someone please help troubleshoot this? People's mails are not getting through to the list, and they're getting very frustrated. Below is one such blocked user. He's tried to send this post multiple times since he subscribed. --Josh Berkus ---------- Forwarded Message ---------- Subject: Postgres v MySQL 5.0 Date: Monday 16 October 2006 09:33 From: "Duncan Garland" <duncan.garland@ntlworld.com> To: pgsql-advocacy@postgresql.org Cc: "Josh Berkus" <josh@agliodbs.com> How do you position Postgres against MySQL 5.0? MySQL is more popular but I've always regarded it as a bit lightweight. I'm told that this is no longer the case with 5.0. Why choose Postgres over MySQL 5.0? Thanks. ------------------------------------------------------- -- Josh Berkus PostgreSQL @ Sun San Francisco
All, HEY! This is the second time I've brought up list mail mysteriously vanishing, and it's like my reports of the problem are vanishing too. Can I *please* have some attention from someone with access to the mail servers? > I moderate three of the main PostgreSQL lists. For the last month or so, > we've been having chronic issues with e-mails from certain users getting > blocked. That is, they don't show up in the moderation queue. They may > show up in the spam trap, but it's hard for me to tell: Maia does NOT > provide a search interface, so I can't find them amount the 500+ e-mails in > the trap. > > Blocked e-mails include even ones from regular PostgreSQL contributors like > Gevik. > > Can someone please help troubleshoot this? People's mails are not getting > through to the list, and they're getting very frustrated. > > Below is one such blocked user. He's tried to send this post multiple > times since he subscribed. > > --Josh Berkus > > ---------- Forwarded Message ---------- > > Subject: Postgres v MySQL 5.0 > Date: Monday 16 October 2006 09:33 > From: "Duncan Garland" <duncan.garland@ntlworld.com> > To: pgsql-advocacy@postgresql.org > Cc: "Josh Berkus" <josh@agliodbs.com> > > How do you position Postgres against MySQL 5.0? > > MySQL is more popular but I've always regarded it as a bit lightweight. I'm > told that this is no longer the case with 5.0. Why choose Postgres over > MySQL 5.0? > > Thanks. > > ------------------------------------------------------- -- Josh Berkus PostgreSQL @ Sun San Francisco
Josh Berkus wrote: > All, > > HEY! This is the second time I've brought up list mail mysteriously > vanishing, and it's like my reports of the problem are vanishing too. Can I > *please* have some attention from someone with access to the mail servers? well there is also the issue with some of my posts to -hackers getting lost still open - Marc promised to look into it a while ago ... Stefan
I know I'm sooooo going to regret this, but, there is a setting (you can do it per list also) that I've just added to the default ones: configset DEFAULT inform <<ENDAAB connect | fail | inform reject | succeed | inform tokenbounce | succeed | inform subscribe | succeed | inform unsubscribe | succeed | inform post | fail | inform ENDAAB Any post that fails will now (or is supposed to) generate a message informing *why* it failed ... This goes to the list owner, so most of it will hit my mailbox, but if you want to disable it, just modify inform for your particular lists to turn it off ... And yes, if I'm reading right, if you get rid of any of those lines, it defaults to no-inform, so, for instance, tired of getting subscribe/unsubscribe requests? remove those lines ... --On Tuesday, October 17, 2006 09:14:56 -0700 Josh Berkus <josh@agliodbs.com> wrote: > All, > > HEY! This is the second time I've brought up list mail mysteriously > vanishing, and it's like my reports of the problem are vanishing too. Can I > *please* have some attention from someone with access to the mail servers? > >> I moderate three of the main PostgreSQL lists. For the last month or so, >> we've been having chronic issues with e-mails from certain users getting >> blocked. That is, they don't show up in the moderation queue. They may >> show up in the spam trap, but it's hard for me to tell: Maia does NOT >> provide a search interface, so I can't find them amount the 500+ e-mails in >> the trap. >> >> Blocked e-mails include even ones from regular PostgreSQL contributors like >> Gevik. >> >> Can someone please help troubleshoot this? People's mails are not getting >> through to the list, and they're getting very frustrated. >> >> Below is one such blocked user. He's tried to send this post multiple >> times since he subscribed. >> >> --Josh Berkus >> >> ---------- Forwarded Message ---------- >> >> Subject: Postgres v MySQL 5.0 >> Date: Monday 16 October 2006 09:33 >> From: "Duncan Garland" <duncan.garland@ntlworld.com> >> To: pgsql-advocacy@postgresql.org >> Cc: "Josh Berkus" <josh@agliodbs.com> >> >> How do you position Postgres against MySQL 5.0? >> >> MySQL is more popular but I've always regarded it as a bit lightweight. I'm >> told that this is no longer the case with 5.0. Why choose Postgres over >> MySQL 5.0? >> >> Thanks. >> >> ------------------------------------------------------- > > -- > Josh Berkus > PostgreSQL @ Sun > San Francisco ---- 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
Attachment
The changes I just made to the lists will hopeflly allow us to identify that as well ... --On Tuesday, October 17, 2006 19:37:55 +0200 Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote: > Josh Berkus wrote: >> All, >> >> HEY! This is the second time I've brought up list mail mysteriously >> vanishing, and it's like my reports of the problem are vanishing too. Can I >> *please* have some attention from someone with access to the mail servers? > > well there is also the issue with some of my posts to -hackers getting > lost still open - Marc promised to look into it a while ago ... > > > Stefan ---- 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
Attachment
Marc, Thing is, these people are bona fide subscribers. But their mail is not showing up in the moderation queue, at all. In fact, in the example user whose message I sent, his message hit the moderation queue, I told him to subscribe, he subscribed and re-submitted ... and now the message isn't going through, but it isn't showing up in the moderation queue, either. --Josh Berkus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yup, that are somehow failing to be posted, most probably due to one of the access_rules that are in place, and that the added inform setting should help us to determine ... But ... if he "re-submitted" the same article a second time, then most likely it got rejected for exactly the right reason: it was a duplicate posting. Why didn't you approve the one that actually *was* in the moderation queue? :( - --On Wednesday, October 18, 2006 00:16:34 -0400 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > > Thing is, these people are bona fide subscribers. But their mail is not > showing up in the moderation queue, at all. > > In fact, in the example user whose message I sent, his message hit the > moderation queue, I told him to subscribe, he subscribed and re-submitted ... > and now the message isn't going through, but it isn't showing up in the > moderation queue, either. > > --Josh Berkus - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFNhuC4QvfyHIvDvMRApB4AKDHo1CVHDAu/4Oe2JhyIrZiqOm0HACg3uw/ 2GY7zgrk/TuVUYdYFPaIk9w= =V6eN -----END PGP SIGNATURE-----
Marc, > But ... if he "re-submitted" the same article a second time, then most likely > it got rejected for exactly the right reason: it was a duplicate posting. Why > didn't you approve the one that actually *was* in the moderation queue? :( Because this is the first time I've ever heard of that filter? And by now the moderation hold has expired? --Josh Berkus
Marc, > But ... if he "re-submitted" the same article a second time, then most likely > it got rejected for exactly the right reason: it was a duplicate posting. Why > didn't you approve the one that actually *was* in the moderation queue? :( Actually, that's a buggy filter. It really should not be filtering out "duplicate" messages with timestamps hours apart. The post-bounce-subscribe-repost cycle happens *all the time* and that filter makes a subscriber wait for me to get to them in the hold queue (which sometimes I don't, due to 100+ spams per list per day) even though they resoved the "problem" themselves. So please correct that filter so that it behaves intelligently. Thanks! --Josh Berkus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Friday, October 20, 2006 19:11:33 -0400 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > >> But ... if he "re-submitted" the same article a second time, then most >> likely it got rejected for exactly the right reason: it was a duplicate >> posting. Why didn't you approve the one that actually *was* in the >> moderation queue? :( > > Actually, that's a buggy filter. It really should not be filtering out > "duplicate" messages with timestamps hours apart. The > post-bounce-subscribe-repost cycle happens *all the time* and that filter > makes a subscriber wait for me to get to them in the hold queue (which > sometimes I don't, due to 100+ spams per list per day) even though they > resoved the "problem" themselves. > > So please correct that filter so that it behaves intelligently. Thanks! You are most welcome to modify the access_rules for those lists you moderate if you feel they are broken ... there is no way for the system to know you *didn't* approve what was in the moderation queue (it kinda assumes that, as moderator, you approved any legit postings, not rejected them because the poster wasn't subscribed) ... - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFOV7X4QvfyHIvDvMRAseFAKCrCycXgRt+1Wr+lojU88VK8m9clQCglSa8 3WBQGUZIkJ7NVzM1ofg+EHo= =7caF -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Friday, October 20, 2006 19:09:10 -0400 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > >> But ... if he "re-submitted" the same article a second time, then most >> likely it got rejected for exactly the right reason: it was a duplicate >> posting. Why didn't you approve the one that actually *was* in the >> moderation queue? :( > > Because this is the first time I've ever heard of that filter? And by now > the moderation hold has expired? 'k, sorry, but its *always* been there ... you wouldn't believe the amount of duplicate posts you'd see on the list(s) without it ... Anyone that is listed as 'unsubscribed' as reason for a posting making it to the moderation queue should be approved, even if you get them to subscribe later, since there is a good chance its coming from the news gateway as well ... - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFOV5O4QvfyHIvDvMRAs7TAKC2ii7tTIUGBqyc2BcaMcQNMDwFIACgqnw9 laWrpfMWc4lF5cTNoWhRKd4= =vDpz -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just want to confirm that you are now receiving the POST messages from majordomo whenever a message auto-rejected? I know I'm getting them here, and all look legit, *but* I'm not looking for anyone in particular either ... - --On Monday, October 16, 2006 09:52:42 -0700 Josh Berkus <josh@agliodbs.com> wrote: > Marc, WWW: > > I moderate three of the main PostgreSQL lists. For the last month or so, > we've been having chronic issues with e-mails from certain users getting > blocked. That is, they don't show up in the moderation queue. They may show > up in the spam trap, but it's hard for me to tell: Maia does NOT provide a > search interface, so I can't find them amount the 500+ e-mails in the trap. > > Blocked e-mails include even ones from regular PostgreSQL contributors like > Gevik. > > Can someone please help troubleshoot this? People's mails are not getting > through to the list, and they're getting very frustrated. > > Below is one such blocked user. He's tried to send this post multiple times > since he subscribed. > > --Josh Berkus > > ---------- Forwarded Message ---------- > > Subject: Postgres v MySQL 5.0 > Date: Monday 16 October 2006 09:33 > From: "Duncan Garland" <duncan.garland@ntlworld.com> > To: pgsql-advocacy@postgresql.org > Cc: "Josh Berkus" <josh@agliodbs.com> > > How do you position Postgres against MySQL 5.0? > > MySQL is more popular but I've always regarded it as a bit lightweight. I'm > told that this is no longer the case with 5.0. Why choose Postgres over > MySQL 5.0? > > Thanks. > > ------------------------------------------------------- > > -- > Josh Berkus > PostgreSQL @ Sun > San Francisco - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFQGU+4QvfyHIvDvMRAi1FAKC9j9lqEgOjSak+d9EhdB/zIYrzYQCfeFb8 8z6fJ97ceupVHSH8ymEld1c= =8cM8 -----END PGP SIGNATURE-----
Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Just want to confirm that you are now receiving the POST messages from > majordomo whenever a message auto-rejected? I know I'm getting them here, and > all look legit, *but* I'm not looking for anyone in particular either ... Would these look different from the regular list moderation traffic? Mind you, the no duplicates rule explained a lot of the issues I was seeing ... I guess I'll know the next time a problem crops up. --Josh Berkus
Marc, > Just want to confirm that you are now receiving the POST messages from > majordomo whenever a message auto-rejected? I know I'm getting them > here, and all look legit, *but* I'm not looking for anyone in particular > either ... OK, I just had a test case. I AM getting the POST messages, but their content is not at all informative. For example: ---------- The command: "(post to pgsql-performance)" issued by: "Tom Darci" <tom@nuws.com> was executed with status: 0 (failure) in session: 0f93dc9192214f4cf0cf3e54f35ac77d5bd4cfb2 from the resend interface, taking 0.264 seconds. ------------ This doesn't tell me anything about why Tom's post was rejected, just that it was (duplicate, in this case). -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 'k, let me look into this ... I thought I had fixed the "blank ones", but apparently must have missed a case :( - --On Thursday, October 26, 2006 14:43:20 -0700 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > >> Just want to confirm that you are now receiving the POST messages from >> majordomo whenever a message auto-rejected? I know I'm getting them >> here, and all look legit, *but* I'm not looking for anyone in particular >> either ... > > OK, I just had a test case. I AM getting the POST messages, but their > content is not at all informative. For example: > > ---------- > The command: > "(post to pgsql-performance)" > > issued by: > "Tom Darci" <tom@nuws.com> > > was executed with status: > 0 (failure) > > in session: > 0f93dc9192214f4cf0cf3e54f35ac77d5bd4cfb2 > > from the resend interface, taking 0.264 seconds. > ------------ > > This doesn't tell me anything about why Tom's post was rejected, just that > it was (duplicate, in this case). > > -- > --Josh > > Josh Berkus > PostgreSQL @ Sun > San Francisco - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFQU8k4QvfyHIvDvMRArxZAKDEZBYiR2SrWrfo+s425mU6JDsllgCfT2Lw bYYSaH73E/oVQNaRhDj+nZk= =x8Qs -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 'k, I just went in and changed all of the access_rules so that they have a 'reason=' attached to them ... I'm watching mine for the next one that doesn't give a reason and will hit Michael (one of the Mj2 developers) about it, since, if no reasons are coming up, then the reject is happening outside of hte normal access_rules :( - --On Thursday, October 26, 2006 14:43:20 -0700 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > >> Just want to confirm that you are now receiving the POST messages from >> majordomo whenever a message auto-rejected? I know I'm getting them >> here, and all look legit, *but* I'm not looking for anyone in particular >> either ... > > OK, I just had a test case. I AM getting the POST messages, but their > content is not at all informative. For example: > > ---------- > The command: > "(post to pgsql-performance)" > > issued by: > "Tom Darci" <tom@nuws.com> > > was executed with status: > 0 (failure) > > in session: > 0f93dc9192214f4cf0cf3e54f35ac77d5bd4cfb2 > > from the resend interface, taking 0.264 seconds. > ------------ > > This doesn't tell me anything about why Tom's post was rejected, just that > it was (duplicate, in this case). > > -- > --Josh > > Josh Berkus > PostgreSQL @ Sun > San Francisco - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFRC2U4QvfyHIvDvMRAnUpAKCHW5pfKFosZIxPLnIbQ1kQglbW5ACgyr3f vvQDN2P+XgX5y7zcRhM8eOQ= =27dt -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Thursday, October 26, 2006 09:47:44 -0700 Josh Berkus <josh@agliodbs.com> wrote: > Marc G. Fournier wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Just want to confirm that you are now receiving the POST messages from >> majordomo whenever a message auto-rejected? I know I'm getting them here, >> and all look legit, *but* I'm not looking for anyone in particular either >> ... > > Would these look different from the regular list moderation traffic? Yes, the Subject's should be "POST ..." vs the usual "CONSULT / REMINDER" messages ... - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFRC044QvfyHIvDvMRArVIAJ9Scug/fM09ZxBXpfajIKmR5XLWUQCgzdgo KzwZDUhmmHZDsZi9/xxwUSQ= =NxG5 -----END PGP SIGNATURE-----
Marc, Right now, whenever someone posts to pgsql-announce, they get a flood of "Please remove me" and bounce messages. This is quite startling for vendors who post announcements for the first time, and quite annoying for the rest of us. And I think it's fixable. What if we: 1) set pgsql-announce to be "reply to pgsql-announce-reply@postgreSQL.org". 2) set up pgsql-announce-reply with a set of filters which looks for "remove", "unsubscribe" and typical bounce messages in the body or subject of the reply, and unsubscibes the sender. If you can't use one list to unsubscribe another, then you can reverse it; have them reply to pgsql-announce, but have a seperate address (pgsql-announce-submit) for submitting new announcements. Thoughts? --Josh Berkus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 'k, the reply-to is easy ... the auto-unsubscribe *alot* harder ... there is an 'interface' for Mj2 that might allow for this, if someone feels up to writing the perl hook to do it ... I've CC'd Michael Yount into this, as he's whom I generally talk to concerning Mj2 problems, and might have an idea of how to do this cleanly ... Of course, this would potentially open this up to a load of attack, since its very easy to forge an email to come from a third party ... but, setting a Reply-To to the list-owner would make sense ... - --On Sunday, October 29, 2006 11:53:26 -0800 Josh Berkus <josh@agliodbs.com> wrote: > Marc, > > Right now, whenever someone posts to pgsql-announce, they get a flood of > "Please remove me" and bounce messages. This is quite startling for vendors > who post announcements for the first time, and quite annoying for the rest of > us. And I think it's fixable. > > What if we: > > 1) set pgsql-announce to be "reply to pgsql-announce-reply@postgreSQL.org". > 2) set up pgsql-announce-reply with a set of filters which looks for > "remove", "unsubscribe" and typical bounce messages in the body or subject of > the reply, and unsubscibes the sender. > > If you can't use one list to unsubscribe another, then you can reverse it; > have them reply to pgsql-announce, but have a seperate address > (pgsql-announce-submit) for submitting new announcements. > > Thoughts? > > --Josh Berkus - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFRRo44QvfyHIvDvMRAhEMAKCW/3f/J0J+qNR1wQTfUK0UN31VZACeNrJz Vj+B+FuGPb6BAVQO61INZJ8= =Dn7D -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > 'k, the reply-to is easy ... the auto-unsubscribe *alot* harder ... there is an > 'interface' for Mj2 that might allow for this, if someone feels up to writing > the perl hook to do it ... I think the reply-to is enough for now. The list already gets its fair share of "please unsubscribe" messages requiring manual intervention. A few more, going to the mods instead of the sender, probably won't matter much. Of course, I'll be the first to let you know if I'm wrong and suddenly have to unsubscribe hundreds of people, but my own postings to announce usually produce 0-handful of unsubscribe requests. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200610292032 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFFRVZXvJuQZxSWSsgRAtRMAKD6LuFRYVfZHxF9CHbdoCAXzDDrJgCgrk2o CjNm5i1Hjo3RY9iCZGztm7s= =LOpi -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, October 30, 2006 01:35:41 +0000 Greg Sabino Mullane <greg@turnstep.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> 'k, the reply-to is easy ... the auto-unsubscribe *alot* harder ... there is >> an 'interface' for Mj2 that might allow for this, if someone feels up to >> writing the perl hook to do it ... > > I think the reply-to is enough for now. The list already gets its fair share > of "please unsubscribe" messages requiring manual intervention. A few more, > going to the mods instead of the sender, probably won't matter much. Of > course, I'll be the first to let you know if I'm wrong and suddenly have to > unsubscribe hundreds of people, but my own postings to announce usually > produce 0-handful of unsubscribe requests. 'k, try that ... I've set teh reply_to to be the $OWNER of the list ... - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFRoet4QvfyHIvDvMRAqA0AJ9mFe2pORTp3AD2j1H8puKSYR5g8gCgsDm3 v4jRT5TUb6HHOJJ2CTkQnls= =33Z2 -----END PGP SIGNATURE-----
Greg, Marc, One more change we can make to pgsql-announce to make life better: can we put the unsubscribe message in the footer of *every* pgsql-announce message? That is, no message rotation for that list, only the unsub instructions. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Friday, November 10, 2006 11:55:29 -0800 Josh Berkus <josh@agliodbs.com> wrote: > Greg, Marc, > > One more change we can make to pgsql-announce to make life better: can we > put the unsubscribe message in the footer of *every* pgsql-announce > message? That is, no message rotation for that list, only the unsub > instructions. Done ... if you can suggest better wording, please feel free .. configset pgsql-announce message_footer <<ENDAAB - - - ----------------------------(end of broadcast)--------------------------- - -To unsubscribe from this list, send an email to: - - - - pgsql-announce-unsubscribe@postgresql.org 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFVgLH4QvfyHIvDvMRAv4NAJsE2S+B9fpkBvhGU46ky08LBPWcOQCgnEVN a7xWm9utRjC5zmKqpoh7MO0= =3247 -----END PGP SIGNATURE-----
On Sat, 2006-11-11 at 13:05 -0400, Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > - --On Friday, November 10, 2006 11:55:29 -0800 Josh Berkus <josh@agliodbs.com> > wrote: > > > Greg, Marc, > > > > One more change we can make to pgsql-announce to make life better: can we > > put the unsubscribe message in the footer of *every* pgsql-announce > > message? That is, no message rotation for that list, only the unsub > > instructions. > > Done ... if you can suggest better wording, please feel free .. To unsubscribe from this list, please send an email to: pgsql-announce-unsubscribe@postgresql.org With the words Unsubscribe as the subject. > > configset pgsql-announce message_footer <<ENDAAB > - - > - ----------------------------(end of broadcast)--------------------------- > - -To unsubscribe from this list, send an email to: > - - > - - pgsql-announce-unsubscribe@postgresql.org > 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 SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFVgLH4QvfyHIvDvMRAv4NAJsE2S+B9fpkBvhGU46ky08LBPWcOQCgnEVN > a7xWm9utRjC5zmKqpoh7MO0= > =3247 > -----END PGP SIGNATURE----- > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> >> > >> Done ... if you can suggest better wording, please feel free .. > > > > > > To unsubscribe from this list, please send an email to: > > > > pgsql-announce-unsubscribe@postgresql.org > > > > With the words Unsubscribe as the subject. > > Are you sure? The point of the -unsubscribe is to avoid having to use > 'unsubscribe' in the body ... Oh :). I didn't know that. Cool, yeah leave it as is. J > > - ---- > 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 SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFVo8G4QvfyHIvDvMRAkMQAJ9ekJh4Jl5qxBykbl7NowTr6oRu+QCfb5+r > lKQjWXwF0zgD/32GA5sIzLw= > =H1Au > -----END PGP SIGNATURE----- > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Saturday, November 11, 2006 18:44:02 -0800 "Joshua D. Drake" <jd@commandprompt.com> wrote: > On Sat, 2006-11-11 at 13:05 -0400, Marc G. Fournier wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> >> - --On Friday, November 10, 2006 11:55:29 -0800 Josh Berkus >> <josh@agliodbs.com> wrote: >> >> > Greg, Marc, >> > >> > One more change we can make to pgsql-announce to make life better: can we >> > put the unsubscribe message in the footer of *every* pgsql-announce >> > message? That is, no message rotation for that list, only the unsub >> > instructions. >> >> Done ... if you can suggest better wording, please feel free .. > > > To unsubscribe from this list, please send an email to: > > pgsql-announce-unsubscribe@postgresql.org > > With the words Unsubscribe as the subject. Are you sure? The point of the -unsubscribe is to avoid having to use 'unsubscribe' in the body ... - ---- 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 SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFVo8G4QvfyHIvDvMRAkMQAJ9ekJh4Jl5qxBykbl7NowTr6oRu+QCfb5+r lKQjWXwF0zgD/32GA5sIzLw= =H1Au -----END PGP SIGNATURE-----
On Oct 29, 2006, at 12:53 PM, Josh Berkus wrote: > If you can't use one list to unsubscribe another, then you can > reverse it; have them reply to pgsql-announce, but have a seperate > address (pgsql-announce-submit) for submitting new announcements. Another benefit to that is it would probably cut down on the amount of spam flowing in... -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)