On Wed, 2005-11-30 at 14:12 -0500, Tom Lane wrote: > Joshua Drake <[EMAIL PROTECTED]> writes: > >> Anyway, next time you're seeing a delay take a look at the headers and > >> see if you can pin down what the bottleneck is. > > > Thank you for that... except that, I was talking about HOUR[n] delays not 13 > > minutes. > > Yeah, so ... where's the blockage according to your Received: headers? > > Personally I've been seeing list turnaround on the order of one minute, > across all the lists, since Marc fixed whatever he fixed about a week > ago (that was before the server changeover). It would seem that the > problem is with a forwarder upstream of you ...
I actually think I might know one part of it at least. Which is I only whitelist the hub (and my own) relays... Which means if it hits any other relay, then that message will get greylisted. I have asked marc for the other relay ips so I can whitelist them and see if the problem persists. Joshua D. Drake > > regards, tom lane -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl, ODBCng - http://www.commandprompt.com/ ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
