public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: linux-kernel@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [e-mail problems] with infradead.org recipients
Date: Sun, 19 Nov 2006 13:04:25 -0500	[thread overview]
Message-ID: <45609CA9.8030806@garzik.org> (raw)
In-Reply-To: <slrnem0qco.fp5.olecom@flower.upol.cz>

Oleg Verych wrote:
> Hi, guys. I have problems with you.
> 
> Is some special NS or route needed? I can add, no problem (ISP problems
> are very unlikely, but possible ;).
> 
> Final-Recipient: RFC822; arjan infradead.org
> Action: failed
> Status: 4.4.7
> Remote-MTA: DNS; canuck.infradead.org
> Last-Attempt-Date: Sun, 19 Nov 2006 14:27:52 +0100
> 
> Final-Recipient: RFC822; matthew wil.cx
> Action: delayed
> Status: 4.4.1
> Remote-MTA: DNS; canuck.infradead.org
> Last-Attempt-Date: Sun, 19 Nov 2006 12:49:26 +0100
> Will-Retry-Until: Fri, 24 Nov 2006 08:43:49 +0100


I bet this is greylisting on infradead.org.  Greylisting will put 
unknown IPs into a database, and /temporarily/ reject the mail, asking 
for the remote mail server to queue it.  Once $GREYLIST_TIME has passed, 
infradead.org will accept the email.  This successfully filters out a 
lot of spammers, and broken SMTP servers that have broken retransmit 
[rules].

You probably need to fix the mail server delivering the mails to 
properly retransmit...

	Jeff




  reply	other threads:[~2006-11-19 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 14:19 [e-mail problems] with infradead.org recipients Oleg Verych
2006-11-19 18:04 ` Jeff Garzik [this message]
2006-11-19 18:49   ` David Woodhouse
2006-11-20  0:26     ` Oleg Verych
2006-11-20  6:10       ` Oleg Verych
2006-11-20  7:57         ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45609CA9.8030806@garzik.org \
    --to=jeff@garzik.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox