Re: Problems with pgsql-announce

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Friday, January 12, 2007 10:08:51 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:

> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> most of what gets 'falsely stuck' tend to be
>>> subscribe/unsubscribe requests though ... if you see one that has been
>>> 'spending 48 hours', please forward it to me with full headers, as something
>>> else is wrong ...
>
>> I've definitly seen that happen and more than once. DOn't have one
>> around, but I'll eb sure to collect the headers next time it happens.
>
> Something else I've noticed saveral times in the last week is getting a
> delayed copy of something that already came through. These weren't the
> usual newbie-sends-another-copy-after-subscribing deal because they came
> from established subscribers. I didn't save copies but will next time.

Which is why I'm hesitant to remove the duplicate checks ...

Just curious though, next time you see this, if you notice it on time, could
you send me the full headers? I know this will be a hard one, since I imagine
the second comes through as almost a 'deja vu' kind of experience, not
simultaneously, but if you get 'lucky' enough to have them both at the same
time, be interseting to see the complete message with full headers to compare
...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFp8TG4QvfyHIvDvMRAlpDAJ9brwpCOjOBDrrY8zQ+bK0F3o10EACglwVh
0RCqqNj0RUJidxLmt8mMYRg=
=4fIm
-----END PGP SIGNATURE-----