Dave,

Earlier, you asked me for the data from the logfiles showing the event of
sending a message to [EMAIL PROTECTED]

After some study, I found this information.  Here it is:

<from file /var/log/message>

*** BEGINNING OF TRANSACTION ***

Sep  5 04:01:36 mpmail smtpd: 968122896.088214 tcpserver: status: 1/32
Sep  5 04:01:36 mpmail smtpd: 968122896.089696 tcpserver: pid 3755 from
158.95.210.54
Sep  5 04:01:36 mpmail smtpd: 968122896.094373 tcpserver: ok 3755
mpmail.inside.missionprinting.org:158.95.210.7:25 :158.95.210.54::1069
Sep  5 04:01:36 mpmail smtpd: 968122896.143675 tcpserver: end 3755 status 0
Sep  5 04:01:36 mpmail smtpd: 968122896.143814 tcpserver: status: 0/32

*** END OF TRANSACTION ***

Is this what you asked for?

Thank you for any assistance you can send my way on this.

Regards,
Tom

-----Original Message-----
From: tom.sarratt.jr [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 04, 2000 9:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Alias Support Question


Tim,

Thanks for the suggestion, however, after changing ownership and acces
params, it still would not work.

Therefore, this is how the .qmail-postmaster file looks now:

Filename:               /var/qmail/alias/.qmail-postmaster
access params:  0644
owner:          root
group:          qmail
File Contents:

START OF FILE

[EMAIL PROTECTED]

END OF FILE

Exact contents of the error message:

*** START OF CONTENTS ***

Hi. This is the qmail-send program at mpmail.inside.missionprinting.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.

<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 3525 invoked by uid 508); 5 Sep 2000 02:24:40 -0000
Received: from unknown (HELO sarrtport1) (158.95.210.54)
  by mpmail.inside.missionprinting.org with SMTP; 5 Sep 2000 02:24:40 -0000
Reply-To: <[EMAIL PROTECTED]>
From: "tom.sarratt.jr" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: FW: TEST
Date: Mon, 4 Sep 2000 21:23:35 -0500
Message-ID: <001901c016e0$4b73cea0$36d25f9e@sarrtport1>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

ANOTHER TEST

 -----Original Message-----
From:   tom.sarratt.jr [mailto:[EMAIL PROTECTED]]
Sent:   Monday, September 04, 2000 9:22 PM
To:     '[EMAIL PROTECTED]'
Subject:        TEST

*** END OF CONTENTS ***

Do anyone have any suggestions as to why the ALIAS support feature does not
work?

Thanks!
Tom Sarratt


-----Original Message-----
From: Timothy Legant [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 01, 2000 8:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Alias Support Question


On Fri, Sep 01, 2000 at 11:04:10AM -0500, tom.sarratt.jr wrote:
>
[snip...]
> Rights to the .qmail-postmaster file:
>
> access params:        0664
> owner:                alias
> group:                qmail
[snip...]

According to INSTALL.alias, you should create the ~alias/.qmail-XXX
files by touching them. Presumably you *wouldn't* be logged in as alias,
so the owner wouldn't be alias. Maybe that doesn't matter, but upon
inspection, I find all my ~alias/.qmail-XXX files are owned by
root:qmail.

Also, and more importantly, the dot-qmail man page says:

       If .qmail is world-writable or group-writable, qmail-local
       stops and indicates a temporary failure.

Your permissions are group writable. chmod 644 .qmail-postmaster and see
if the delivery works.

Tim
--
Tim Legant
[EMAIL PROTECTED]


Reply via email to