Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.018 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'subject:Python': 0.06; 'problem?': 0.07; 'http': 0.09; 'moderation': 0.09; 'subject:posting': 0.09; 'python': 0.11; 'posted': 0.15; '6:30': 0.16; 'effect.': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'headers,': 0.16; 'missing?': 0.16; 'moderation,': 0.16; 'python-dev,': 0.16; 'through,': 0.16; 'timestamp': 0.16; 'wrote:': 0.18; 'everyone,': 0.19; 'possible,': 0.19; 'server,': 0.19; 'thu,': 0.19; 'all:': 0.24; "i've": 0.25; '+0200': 0.26; 'somewhere': 0.26; 'header:In-Reply-To:1': 0.27; 'idea': 0.28; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'usually': 0.31; '(cest)': 0.31; 'obscure': 0.31; 'python.org.': 0.31; 'though.': 0.31; 'lists': 0.32; 'python.org': 0.32; 'fri,': 0.33; 'trouble': 0.34; 'date:': 0.34; 'problem.': 0.35; 'something': 0.35; 'anybody': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'subject:List': 0.36; 'half': 0.37; 'requirements': 0.37; 'list': 0.37; 'list.': 0.37; 'gmail': 0.38; 'to:addr:python-list': 0.38; 'issue': 0.38; 'does': 0.39; 'moving': 0.39; 'to:addr:python.org': 0.39; 'mailing': 0.39; 'most': 0.60; 'ago.': 0.61; 'length': 0.61; 'first': 0.61; 'address': 0.63; 'happen': 0.63; 'reached': 0.63; 'within': 0.65; 'hours': 0.66; 'reverse': 0.68; 'jul': 0.74; 'day': 0.76; 'order:': 0.84; '(pdt)': 0.91; '2013': 0.98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9rmicNacu+sPl+he/09Ho+1cAaE9mcWq5X4erU4yGy8=; b=NRBqn0aQYSbZP2SRh4sQ/Jal1UJbxHi5wQaphFVn9U6PleHH2wlRLqozJOPXJR1lln ULegcHkNdlyNDvEbaF3E3dXHMvsRm/Br1I0tL7Kr2z0ZYazfKj0U0/1hY1ti2Ds9ZEuS ehCN7eJIOGEWaudk55TYz6imT9fnj0ZyYpmHT8kDzi+pswxALyVzxDEJB1QS2PWeL1WG 0CNxzn5Llh2AaiY/mBL25emZfTTNB7G4QFZJyb7f1WDRBTMmpQXUKIa4Wwioqj3MraWd p0uhG39dYF8+aeX+3rr2jdIieGgurG9WjEEDTwTBBRNqHTnEmkGL5jAz59lib141ZYqp so5A== MIME-Version: 1.0 X-Received: by 10.220.43.19 with SMTP id u19mr340396vce.3.1374221123496; Fri, 19 Jul 2013 01:05:23 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jul 2013 18:05:23 +1000 Subject: Re: Messages to Python-List aren't posting From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 33 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1374221126 news.xs4all.nl 15900 [2001:888:2000:d::a6]:56597 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:50895 On Fri, Jul 19, 2013 at 6:30 AM, Matthew Lefavor wrote: > All: > > I've been having trouble with all three Python mailing lists (python-list, > python-dev, python-ideas). This has been going on for about a month. > Whenever I post, it takes hours for my messages to be posted on the list. I > first thought it was an issue with my work email server, but moving to gmail > has had no effect. > > Is there some obscure setting I am missing? Has anybody else had this > problem? This just came through, timestamped 11.5 hours ago. I don't usually have this problem. Looking at your Received headers, in reverse order: Date: Thu, 18 Jul 2013 16:30:51 -0400 - timestamp of your mail Thu, 18 Jul 2013 13:30:51 -0700 (PDT) - you posted it via HTTP Thu, 18 Jul 2013 22:31:39 +0200 (CEST) - it reached python.org Fri, 19 Jul 2013 09:56:14 +0200 (CEST) - it began delivery to my address Fri, 19 Jul 2013 00:56:15 -0700 (PDT) - it reached gmail and me. So the big delay is somewhere within python.org. Since this does NOT happen to everyone, I would be looking for something like: * Moderation requirements (does your message not comply with spec?) * Spam greylisting * Slow/glitchy DNS when attempting to verify your message Most likely I think is moderation, given the extreme length of time. Something would have to be pretty glitchy to lag your mail out for half a day in spam filtering. It's possible, I guess, though. I've no idea what anti-spam features the list is using. ChrisA