"Thomas T. Thai" <[EMAIL PROTECTED]> writes: > why does this happen? > > ---------- Forwarded message ---------- > Date: Thu, 8 Feb 2001 10:46:59 -0600 (CST) > From: Mail Delivery Subsystem <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > 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 ----- > <[EMAIL PROTECTED]> > (reason: 550 5.7.1 <[EMAIL PROTECTED]>... Relaying denied) > > ----- Transcript of session follows ----- > ... while talking to mail.postgresql.org.: > >>> MAIL From:<[EMAIL PROTECTED]> SIZE=3641 > <<< 451 4.1.8 <[EMAIL PROTECTED]>... Domain of sender address [EMAIL PROTECTED] does >not resolve > ... while talking to ftp.postgresql.org.: > >>> RCPT To:<[EMAIL PROTECTED]> > <<< 550 5.7.1 <[EMAIL PROTECTED]>... Relaying denied > 550 5.1.1 <[EMAIL PROTECTED]>... User unknown There are two problems here. The first one is with the mailer configuration at postgresql.org. postgresql.org lists to MX records. The first is for mail.postgresql.org, the second is for ftp.postgresql.org. Unfortunately, ftp.postgresql.org rejects mail for the postgresql.org domain, reporting ``Relaying denied''. This is definitely bad. If postgresql.org is going to have a secondary MX, the secondary system must accept mail for postgresql.org. I am CC'ing Marc Fournier think I think he is responsible for the postgresql.org mail system. The second problem may be caused by the fact that there is a problem with the minnesota.com domain. The root name servers report that the name servers for minnesota.com are ns01.minnesota.com and ns02.minnesota.com. ns02.minnesota.com appears to be down at the moment. ns01.minnesota.com reports an additional name server: ns1.uswest.net. That ns1.uswest.net server is lame: it gives nonauthoritative replies for minnesota.com. Whoever is responsible for the minnesota.com name servers should fix them to not report ns1.uswest.net as an authoritative name server for minnesota.com. Alternatively, get ns1.uswest.net to actually be authoritative. Ian