Re: Problems with pgsql-announce
От | Greg Sabino Mullane |
---|---|
Тема | Re: Problems with pgsql-announce |
Дата | |
Msg-id | 4631b26ee4ea6df564f0d8689a377f9d@biglumber.com обсуждение исходный текст |
Ответ на | Re: Problems with pgsql-announce (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Problems with pgsql-announce
|
Список | pgsql-www |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Josh Berkus replied: >> Yeah, something weird is going on there. From looking at the moderation >> queue, it seems everyone is getting three or four duplicates. Maybe >> we can simply turn that off, Marc? > > ... not if duplicates are actually being received; we don't want 3-4 or > each message. I'm not sure what's going on, but it was working before, and now is not, so the recent "cure" may be worse than the disease. I'm pretty sure these are not people *sending* duplicate messages: for example, yesterday's Weekly News appeared three times in the moderation queue, which it never has before. Perhaps it was getting flagged as a duplicate before but not sent to the moderation queue? Somehow I doubt that everyone's mail clients are misconfigured to be sending duplicate mails, so the problem is on our end. Hm...just checked the -announce queue...their are three identical messages from Josh Berkus about the new releases, all claiming the checksum errors. Josh, did you ever get those checksum errors bounced back to you before the change when you posted previously to announce? ISTR this change started with someone complaining about getting those sent back to them? - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200701081540 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFFoq1ivJuQZxSWSsgRAmRyAJ9me1wnE1yHnsNS4abijAA4e4joMwCg7R94 y9T3a1gwpGyxBbDixo2snww= =P3zI -----END PGP SIGNATURE-----
В списке pgsql-www по дате отправления: