Re: [Evolution] Problem with the list?

[Patrick O'Callaghan <poc usb ve>]

A quick update: we looked at the server logs and headers. Two things
stand out:

1) The greylisting worked as it should. It applied to the first message
only and not subsequently, and in fact the MTA correctly retransmitted
the message after 20 minutes. There was no reason it should have
reported this back to the sender as an error. Why it happened in this
case is not under our control.

2) Here are the complete headers from Akhil's first message (note the
X-Greylist line):

Return-Path: <lakhil novell com>
Received: from skynet.usb.ve (cyrus [127.0.0.2]) by ilium.usb.ve (Cyrus
 v2.2.12-Invoca-RPM-2.2.12-3.RHEL4.1) with LMTPA; Thu, 02 Jun 2011 00:41:12
 -0430
X-Sieve: CMU Sieve 2.2
X-Greylist: delayed 00:20:09.444807 by SQLgrey-1.6.8
Received: from novprvoes0310.provo.novell.com
 (novprvoes0310.provo.novell.com [137.65.248.74]) by skynet.usb.ve (Postfix)
 with ESMTP id C82257709F3A6 for <poc usb ve>; Thu,  2 Jun 2011 00:41:11
 -0430 (VET)
Received: from INET-PRV-MTA by novprvoes0310.provo.novell.com with
 Novell_GroupWise; Wed, 01 Jun 2011 22:51:00 -0600
Subject: Re: Subscription problem
From: Akhil Laddha <lakhil novell com>
To: Patrick O'Callaghan <poc usb ve>
Cc: evolution-list-owner gnome org, pocallaghan gmail com
Date: Mon, 30 May 2011 13:48:19 +0530
In-Reply-To: <1306642091 2313 38 camel bree homelinux com>
References: <1306642091 2313 38 camel bree homelinux com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; 
boundary="=-6YKQUoW9WMOrtug8PUhs"
X-Mailer: Evolution 3.1.2
X-Evolution-Source-Folder: folder://1265690408.22587.3%40linux-r6qu/INBOX
X-Evolution-Source-Message: 42422
X-Evolution-Source-Flags: ANSWERED ANSWERED_ALL SEEN
X-Evolution-Account: 1265690408 22587 3 linux-r6qu
X-Evolution-Fcc: imapx://lakhil prv1-3 novell com/Sent%20Items
X-Evolution-Transport: 1265690408 22587 3 linux-r6qu-transport
X-Evolution-Format: text/plain, pgp-sign
X-Evolution-Source: 
Message-ID: <1306743499 3677 6 camel lakhil-kaboom labs blr novell com>
Mime-Version: 1.0

Looking at the various timestamps it's clear that the long delay is being caused by internal Novell servers.

poc