From: Tomas Szepe <szepe@pinerecords.com>
To: David Woodhouse <postmaster@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw2100 wireless driver
Date: Thu, 12 Aug 2004 00:56:12 +0200 [thread overview]
Message-ID: <20040811225612.GB14073@louise.pinerecords.com> (raw)
In-Reply-To: <1092264200.1438.4347.camel@imladris.demon.co.uk>
On Aug-11 2004, Wed, 23:43 +0100
David Woodhouse <postmaster@infradead.org> wrote:
> On Wed, 2004-08-11 at 19:51 +0200, Tomas Szepe wrote:
> > 550-Verification failed for <szepe@pinerecords.com>
> > 550-(result of earlier verification reused).
> > 550 Sender verify failed
> >
> > I for one don't call this a properly configured mail system.
>
> Indeed it isn't. It doesn't accept mail to 'postmaster@pinerecords.com',
> which is in violation of RFC2821. Hence we don't accept mail from it.
>
> 2004-08-11 17:33:36 H=louise.pinerecords.com [213.168.176.16] sender
> verify fail for <kala@pinerecords.com>: response to "RCPT
> TO:<postmaster@pinerecords.com>" from louise.pinerecords.com
> [213.168.176.16] was: 553 5.3.0 <postmaster@pinerecords.com>... No such
> user
>
> 2004-08-11 17:33:36 H=louise.pinerecords.com [213.168.176.16]
> F=<kala@pinerecords.com> rejected RCPT <hch@infradead.org>: Sender
> verify failed
Ok, thanks for the warning. Is there any reason why you should
be trying to look up postmaster@ from the sender domain upon
RCPT TO?
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2004-08-11 23:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 11:41 Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55 ` Pavel Machek
2004-07-14 14:53 ` Éric Brunet
2004-07-14 15:24 ` Emiliano 'AlberT' Gabrielli
2004-08-09 20:15 ` Tomas Szepe
2004-08-10 5:02 ` Jeff Chua
2004-08-10 6:55 ` Christoph Hellwig
2004-08-10 10:16 ` Pavel Machek
2004-08-10 10:34 ` Christoph Hellwig
2004-08-11 12:17 ` Pavel Machek
2004-08-11 17:54 ` Jeff Garzik
2004-08-11 20:27 ` Pavel Machek
2004-08-11 22:01 ` Jeff Garzik
2004-08-11 10:16 ` James Ketrenos
2004-08-11 10:44 ` Christoph Hellwig
2004-08-11 10:53 ` Wichert Akkerman
2004-08-11 10:59 ` Christoph Hellwig
2004-08-11 16:21 ` James Ketrenos
2004-08-11 16:30 ` Stephen Hemminger
2004-08-11 16:33 ` Tomas Szepe
2004-08-11 16:51 ` Christoph Hellwig
2004-08-11 17:02 ` Tomas Szepe
2004-08-11 17:11 ` Christoph Hellwig
2004-08-11 17:22 ` Tomas Szepe
2004-08-11 17:41 ` Christoph Hellwig
2004-08-11 17:51 ` Tomas Szepe
2004-08-11 22:43 ` David Woodhouse
2004-08-11 22:56 ` Tomas Szepe [this message]
2004-08-11 23:06 ` David Woodhouse
2004-08-11 23:11 ` Tomas Szepe
2004-08-11 23:21 ` David Woodhouse
2004-08-11 18:55 ` John Stoffel
2004-08-11 23:55 ` Jeff Chua
2004-08-12 3:47 ` Luis R. Rodriguez
2004-08-11 17:51 ` Jeff Garzik
2004-07-14 12:30 ` Tomas Szepe
2004-07-14 12:27 ` Pavel Machek
2004-07-14 13:15 ` Vojtech Pavlik
2004-07-14 13:42 ` Pavel Machek
2004-07-14 17:00 ` Victor J. Orlikowski
[not found] <2hQr1-62p-23@gated-at.bofh.it>
[not found] ` <2hRQ5-7bn-9@gated-at.bofh.it>
2004-07-14 14:07 ` Andi Kleen
2004-07-14 14:59 ` Vojtech Pavlik
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=20040811225612.GB14073@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=postmaster@infradead.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
all inboxes | Powered by JetHome®