Apache OpenOffice (AOO) Bugzilla – Issue 680
dev@website.openoffice.org not working
Last modified: 2003-12-06 14:52:32 UTC
We need to get this list up ASAP When i tried to send a testmail, i got the following error: *********************************************************** Date: 10 Apr 2001 21:16:49 -0000 From: MAILER-DAEMON@openoffice.org To: goolie@collab.net Subject: failure notice Hi. This is the qmail-send program at openoffice.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <dev@website.openoffice.org>: Sorry. Although I'm listed as a best-preference MX or A for that host, it isn't in my control/locals file, so I don't treat it as local. (#5.4.6) --- Below this line is a copy of the message. Return-Path: <goolie@collab.net> Received: (qmail 21754 invoked from network); 10 Apr 2001 21:16:49 -0000 Received: from laswell.sp.collab.net (64.211.228.55) by h12.sny.collab.net with SMTP; 10 Apr 2001 21:16:49 -0000 Received: (qmail 25081 invoked from network); 10 Apr 2001 21:15:56 -0000 Received: from gate.sp.collab.net (HELO goolie) (64.211.228.36) by laswell.sp.collab.net with SMTP; 10 Apr 2001 21:15:56 -0000 Date: Tue, 10 Apr 2001 14:14:29 -0700 (PDT) From: Adam Gould <goolie@collab.net> To: <dev@website.openoffice.org> Subject: test Message-ID: <Pine.WNT.4.33.0104101414150.1292-100000@goolie> X-X-Sender: goolie@laswell.sp.collab.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII testmsg --goolie
I added website to the qmail virtual domains file and restarted the process. Things should be all right now. Let me know if you are still having problems.
just go a failure - sorry will try some more things.
Thanks for taking this Kathy. The change you did had one typo, but was otherwise totally correct. I fixed the typo and send a SIGHUP to qmail-send ... I can now send subscribe requests to dev@website.openoffice.org.
OK then, it's fixed.
As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue.