Any delivery block to freebsd-questions list?

Matthew Seaman m.seaman at infracaninophile.co.uk
Fri Jan 8 08:39:21 UTC 2010


Matthias Apitz wrote:
> El día Friday, January 08, 2010 a las 06:57:04AM +0100, Matthias Apitz escribió:
> 
>>> Sounds like that's just graylisting.  The delay will depend on how long
>>> it takes your MTA (or the smarthost you use) to retry the message.
>> In my case it seems not to be graylisting, but blacklisting; i.e. the
>> mail is not delivered at all :-(
> 
> Now, with the above reply, the mail of yesterday showed up in the list
> as well... what is this?

Well, looking at the headers, it spent about 11 hours sitting at ms4-1.1blu.de.
Once it was accepted at freebsd.org, it went out to the list in about 2 minutes.

Received: from ms4-1.1blu.de (ms4-1.1blu.de [89.202.0.34])
	by mx1.freebsd.org (Postfix) with ESMTP id EDF3F8FC1C
	for <freebsd-questions at freebsd.org>;
	Fri,  8 Jan 2010 05:57:09 +0000 (UTC)
Received: from [193.31.11.193] (helo=current.Sisis.de)
	by ms4-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32)
	(Exim 4.50) id 1NSuhI-0004mn-4D
	for freebsd-questions at freebsd.org; Thu, 07 Jan 2010 16:54:52 +0100
Received: from current.Sisis.de (current [127.0.0.1])
	by current.Sisis.de (8.14.3/8.14.3) with ESMTP id o07FspAW026325
	for <freebsd-questions at freebsd.org>;
	Thu, 7 Jan 2010 16:54:51 +0100 (CET) (envelope-from guru at unixarea.de)

Now, not knowing what the configuration of ms4-1.1blu.de is like,
I can only speculate that it tried to deliver to mx1.freebsd.org and, for
whatever reason, failed at the initial attempt.  [It's not greylisting by
the FreeBSD mailservers, because they don't use it.]  We can't see from this
trace how many times ms4-1.1blu.de retried sending the message during that
time -- typically it should try again after 15 or 30min and then keep trying
again at that sort of interval or longer for up to 5 days.  As they are using Exim, it's quite likely the message ended up in a stuck-message queue which would still keep retrying delivery, but at a much lower frequency.

Without looking at the mail logs on mx1.freebsd.org we can't know why the
message wasn't accepted.  We can tell that it was temp-failed -- ie. you
didn't get a bounce back with a permanent failure message.  There are several
mechanisms used with e-mail that might generate this sort of temp-fail response
(SPF, DKIM -- but there are no indications freebsd.org uses these in the
message headers) or else the problem might well have been a failure in the DNS
-- if mx1.freebsd.org couldn't look up ms4-1.1blu.de or sisis.de then it wouldn't accept the message.  This last scenario seems the most likely to me, especially since you say you've recently changed e-mail service provider.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100108/cb02035b/signature.pgp


More information about the freebsd-questions mailing list