Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwtWb-00008a-4L for pgsql-www@arkaria.postgresql.org; Thu, 21 Feb 2019 18:56:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gwtWZ-0001UT-S3 for pgsql-www@arkaria.postgresql.org; Thu, 21 Feb 2019 18:56:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwtWZ-0001D9-Gw for pgsql-www@lists.postgresql.org; Thu, 21 Feb 2019 18:56:47 +0000 Received: from mail-io1-xd43.google.com ([2607:f8b0:4864:20::d43]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwtWW-0004Op-Kz for pgsql-www@postgresql.org; Thu, 21 Feb 2019 18:56:46 +0000 Received: by mail-io1-xd43.google.com with SMTP id y6so3082588ioq.10 for ; Thu, 21 Feb 2019 10:56:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=Oo9CJUQgKHntwMGorDnl776LMIVW0tTbp0vxliF1UZU=; b=e1vu+DSJt+heT4aW5nfxYrJD/xSE4TJtz3kW7kPMBHJUsb3/BlPjiMZ0vOfwoNvCI4 toSGMUcfJhPXcCfKBenaQw6NpLY0PA0Q7TGA0iTQYzI6+653ov+B7O6fZcUUKldm2crr k1frTrtHjfnF5HDGpUuT6rUU4IAtMt0M6zAGSzfXBGPj7tsHF/H31VmfI3E/0jbAZcs3 n9+P3V5Qa31557PpulT+rLpFOvx7OeJwtgHuD4EPA/e43687urIBjCDop3PRpICYrt16 hywoOIirCw5WOFGjEq5QgAvvYW+zX1QvGbuMmA/EDIy6dCN5nJ+pfRSLNCpJqoHrvM1D /Wig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=Oo9CJUQgKHntwMGorDnl776LMIVW0tTbp0vxliF1UZU=; b=PnCrD09xMtb9gN6HQyqNB8A3XHz4IGuZZ3SNylt4JZ8ZLNsPFykccT9LK/ao8ON+yh cNnUIF0swmhIN5HWzoKPXkUtKNauCw/Sd413mU0+d7CuetuE8aj7uliEavfekp1OmudQ pIqjeaF7N+3mV2hCp/9g35CiPrDmxbQKcXjf8GaD8HQBz6ubVm7oAx8KYxIh4u6gC82Y ZwCmlz+KraCBrYzgk0OtwON+t+U0hsAxWMzmDXKKa90F6jy1hve43xycrXqCmLiVwjFP UIVRqsqk4Wkxgp8lHFfRpw3Vh9PJjdGWkJqwZytJ6XleoNymq8BVm4v/PWbGp3LVcVMm w+uQ== X-Gm-Message-State: AHQUAua2sEy4FKiVmD42YRa8WFqKwPbdOXIzdR/mh4XqEQ3ATccQqEk5 bVEspmmlcDDzO8ndgPqb//vAa9ZMVNg= X-Google-Smtp-Source: AHgI3IbvGNkQhvWHHeAwjtRXwsOcH6RfJfrfGxCH9CxojjeqlPtH/OUfI7PlegYEPrGB+RKfYs4/2w== X-Received: by 2002:a6b:710e:: with SMTP id q14mr3010iog.210.1550775403388; Thu, 21 Feb 2019 10:56:43 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o9sm4480627itb.23.2019.02.21.10.56.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Feb 2019 10:56:42 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 8C66A800B9A; Thu, 21 Feb 2019 12:56:41 -0600 (CST) Date: Thu, 21 Feb 2019 12:56:41 -0600 From: Justin Pryzby To: pgsql-www@postgresql.org Subject: order of messages on www.p.o/list Message-ID: <20190221185641.GB24667@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, I'm interested to follow PG development but -hackers is too noisy for me to subscribe. I tried following the list on www page few times per day. However, sometimes I refresh the page, and I see that new mails have arrived somewhere in the middle (above the bottom mail), and I don't know which. So I either lose time rereading list of mails (and mails themselves) or otherwise I miss mails which showed up somehere in the middle.. I'm refering to a page like this: https://www.postgresql.org/list/pgsql-hackers/since/201902210000/ Is that list ordered by time accounting for timezone ? For example if someone in -11:00 sends a message at 14:00 UTC, does their message show up above somone else in -04:00 who mails at 13:00 UTC ? Because their "Date:" header says 03:00. Or perhaps it's an issue of the RFC822 "Date:" header vs. the received date? All the headers are just annotations, and so I suggest the page should be ordered not by the "date:" header set by the remote MUA but by the date in the most recent "Received:" header, added by the local MTA. That avoids issue of wrong time setting on remote side. Thanks, Justin