Returned mail: see transcript for details (fwd)

why does this happen?

---------- Forwarded message ----------
Date: Thu, 8 Feb 2001 10:46:59 -0600 (CST)
From: Mail Delivery Subsystem <MAILER-DAEMON@minnesota.com>
To: tom@ns01.minnesota.com
Subject: Returned mail: see transcript for details

The original message was received at Thu, 8 Feb 2001 10:44:37 -0600 (CST)
from localhost [[UNIX: localhost]]

   ----- The following addresses had permanent fatal errors -----
<pgsql-general@postgresql.org>
    (reason: 550 5.7.1 <pgsql-general@postgresql.org>... Relaying denied)

   ----- Transcript of session follows -----
... while talking to mail.postgresql.org.:
>>> MAIL From:<tom@minnesota.com> SIZE=3641
<<< 451 4.1.8 <tom@minnesota.com>... Domain of sender address tom@minnesota.com does not resolve
... while talking to ftp.postgresql.org.:
>>> RCPT To:<pgsql-general@postgresql.org>
<<< 550 5.7.1 <pgsql-general@postgresql.org>... Relaying denied
550 5.1.1 <pgsql-general@postgresql.org>... User unknown

   ----- Original message follows -----

Return-Path: <tom@ns01.minnesota.com>
Received: from localhost (localhost [[UNIX: localhost]])
    by ns01.minnesota.com (8.11.0/8.11.0) with ESMTP id f18Giar18497
    for <pgsql-general@postgresql.org>; Thu, 8 Feb 2001 10:44:37 -0600 (CST)
Date: Thu, 8 Feb 2001 10:44:36 -0600 (CST)
From: "Thomas T. Thai" <tom@ns01.minnesota.com>
To: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Returned mail: see transcript for details (fwd)
Message-ID: <Pine.NEB.4.21.0102081043550.18439-100000@ns01.minnesota.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

why does this happen once in a while?

---------- Forwarded message ----------
Date: Thu, 8 Feb 2001 10:42:10 -0600 (CST)
From: Mail Delivery Subsystem <MAILER-DAEMON@minnesota.com>
To: tom@ns01.minnesota.com
Subject: Returned mail: see transcript for details

The original message was received at Thu, 8 Feb 2001 10:39:37 -0600 (CST)
from localhost [[UNIX: localhost]]

   ----- The following addresses had permanent fatal errors -----
<pgsql-general@postgresql.org>
    (reason: 550 5.7.1 <pgsql-general@postgresql.org>... Relaying denied)

   ----- Transcript of session follows -----
... while talking to mail.postgresql.org.:
>>> MAIL From:<tom@minnesota.com> SIZE=2078
<<< 451 4.1.8 <tom@minnesota.com>... Domain of sender address tom@minnesota.com does not resolve
... while talking to ftp.postgresql.org.:
>>> RCPT To:<pgsql-general@postgresql.org>
<<< 550 5.7.1 <pgsql-general@postgresql.org>... Relaying denied
550 5.1.1 <pgsql-general@postgresql.org>... User unknown

   ----- Original message follows -----

Return-Path: <tom@ns01.minnesota.com>
Received: from localhost (localhost [[UNIX: localhost]])
    by ns01.minnesota.com (8.11.0/8.11.0) with ESMTP id f18Gdbq18447;
    Thu, 8 Feb 2001 10:39:37 -0600 (CST)
Date: Thu, 8 Feb 2001 10:39:36 -0600 (CST)
From: "Thomas T. Thai" <tom@ns01.minnesota.com>
To: Lincoln Yeoh <lyeoh@pop.jaring.my>
cc: Gunnar R|nning <gunnar@candleweb.no>, Mitch Vincent <mitch@venux.net>,
       pgsql-general@postgresql.org
Subject: Re: full text searching
In-Reply-To: <3.0.5.32.20010208105456.0091a100@192.228.128.13>
Message-ID: <Pine.NEB.4.21.0102081039140.18439-100000@ns01.minnesota.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

yes it does get complicated. in the end i use mnogosearch. their
development is very active.

On Thu, 8 Feb 2001, Lincoln Yeoh wrote:

> Date: Thu, 08 Feb 2001 10:54:56 +0800
> From: Lincoln Yeoh <lyeoh@pop.jaring.my>
> To: Thomas T. Thai <tom@minnesota.com>, Gunnar R|nning <gunnar@candleweb.no>
> Cc: Mitch Vincent <mitch@venux.net>, pgsql-general@postgresql.org
> Subject: Re: full text searching
>
> At 11:40 AM 07-02-2001 -0600, Thomas T. Thai wrote:
> >On 7 Feb 2001, Gunnar R|nning wrote:
> >>
> >> Since we're only doing exact searches, the index is utilized. But the
> >> quality isn't good enough - I would love to have language sensitive
> >> searches. "car" should match "cars" but not cartography and "ship"
> >> should/could match "boat" etc.
> >
> >you can use ispell prefix/suffix for searching base words.
>
> Sometimes I want it literal too. e.g. I'm searching for car I want car and
> nothing else.
>
> What I figured first was to create yet another dictionary of meanings.
>
> Where ship is converted to meaning1 (verb), meaning2 (noun), etc.
> And boat is converted to meaning2 (noun).
>
> But then boat is not really the same as ship. So they should actually be
> separate meanings maybe linked by a weight.  Maybe we should make use of
> Postgresql's polygon stuff, and stick a boat polygon somewhere where it
> intersects a ship polygon and a canoe polygon.
>
> In the end it seems too complex. I'm starting to think it may be better to
> keep things literal but fast, and do the smart stuff at the client (do
> multiple searches if necessary).
>
> Cheerio,
> Link.
>
>