public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: James Antill <james@and.org>
Cc: Benjamin LaHaise <bcrl@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Tue, 15 Jan 2002 17:28:13 -0500	[thread overview]
Message-ID: <20020115172813.A10210@thyrsus.com> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com> <20020114173542.C30639@redhat.com> <20020114173854.C23081@thyrsus.com> <20020114180007.D30639@redhat.com> <20020114180522.A24120@thyrsus.com> <20020114183820.G30639@redhat.com> <20020114205307.E24120@thyrsus.com> <nn1ygrw8h1.fsf@code.and.org>
In-Reply-To: <nn1ygrw8h1.fsf@code.and.org>; from james@and.org on Tue, Jan 15, 2002 at 05:32:58PM -0500

James Antill <james@and.org>:
> . User runs fetchmail
> . fetchmail feeds email to exim
> . exim does callback verification, and refuses email.
> . fetchmail pretends it has delivered email, so _even if_ you hack your
>   MTA to say don't verify from localhost lost emails will never be
>   delivered by fetchmail (even though they are still on the server,
>   and fetchmail knew they didn't get sent).

If you tell fetchmail's config about exim's antispam responses 
correctly, this should not happen.

I have a lot of happy exim users on my development list.  Perhaps
you should try asking questions there?
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety."
	-- Benjamin Franklin, Historical Review of Pennsylvania, 1759.

  reply	other threads:[~2002-01-15 22:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 21:59 Penelope builds a kernel Eric S. Raymond
2002-01-14 22:24 ` Jeff Garzik
2002-01-14 22:28 ` Lars Marowsky-Bree
2002-01-14 22:32 ` Davide Libenzi
2002-01-14 22:32 ` Chris Friesen
2002-01-14 22:35 ` Benjamin LaHaise
2002-01-14 22:38   ` Eric S. Raymond
2002-01-14 23:00     ` Benjamin LaHaise
2002-01-14 23:05       ` Eric S. Raymond
2002-01-14 23:38         ` Benjamin LaHaise
2002-01-15  1:53           ` Eric S. Raymond
2002-01-15  2:36             ` Benjamin LaHaise
2002-01-15 11:53               ` Matthias Andree
2002-01-15 22:32             ` James Antill
2002-01-15 22:28               ` Eric S. Raymond [this message]
2002-01-16  1:29                 ` Alan Cox
2002-01-15 23:00               ` Diego Calleja
2002-01-14 22:37 ` Bruce Harada
2002-01-15  0:56   ` Thomas Duffy
2002-02-01 20:46   ` Pavel Zaitsev
2002-01-14 22:44 ` Richard Gooch
2002-01-14 22:45   ` Eric S. Raymond
2002-01-14 23:15     ` Richard Gooch
2002-01-15 15:53     ` salvador
2002-01-14 23:08 ` Chris Ricker
2002-01-14 23:14 ` Tom Gilbert
2002-01-15  0:50 ` Nathan Walp
2002-01-15  1:24   ` John Levon
2002-01-15  1:39 ` Tom Rini
2002-01-15  2:07   ` John Levon
2002-01-15  3:59     ` Tom Rini
2002-01-15 13:28 ` David Woodhouse
2002-01-15 19:53   ` Ingo Oeser
2002-01-15 20:37   ` David Woodhouse
2002-01-15 21:00 ` Matthew M
2002-01-16 21:31 ` Felix von Leitner
     [not found] <d7.11a4a260.2974c807@aol.com>
2002-01-14 23:51 ` Jeff Garzik

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=20020115172813.A10210@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=bcrl@redhat.com \
    --cc=james@and.org \
    --cc=linux-kernel@vger.kernel.org \
    /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