Mailing List Archive

JAmes Atwill writes:
> I recall seeing this a while back, but alas the archive's
> aren't grepable so it's difficult to find the discussion.
>
> I've recently installed qmail on a BSDi 2.0 box, and in the
> INSTALL docs, it says to attempt a test of:
>
> % echo to: james | /var/qmail/bin/qmail-inject
^
>
> After taking a look at the maillog, I'm getting the error
> 5.1.1 (Sorry, there is no mailbox here by that name.). I do
> have a ~/Mailbox file, I've followed all the directions to that
> point by the book.
>
> I've probably overlooked something, any help is appreciated.

Maybe a little "a"?

--
......................................
Arnaldo Mandel
Computer Science Dept.
Universidade de S\~{a}o Paulo, Brazil
am@ime.usp.br

On Tue, 18 Feb 1997, JAmes Atwill wrote:

> I recall seeing this a while back, but alas the archive's
> aren't grepable so it's difficult to find the discussion.
>
> I've recently installed qmail on a BSDi 2.0 box, and in the
> INSTALL docs, it says to attempt a test of:
>
> % echo to: james | /var/qmail/bin/qmail-inject
>
> After taking a look at the maillog, I'm getting the error
> 5.1.1 (Sorry, there is no mailbox here by that name.). I do
> have a ~/Mailbox file, I've followed all the directions to that
> point by the book.
>
> I've probably overlooked something, any help is appreciated.

Try the obvious first. 1) look in the log and 2) what are the permissions
on not only the Mailbox file, the ~ directory and its parent?

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================

I recall seeing this a while back, but alas the archive's
aren't grepable so it's difficult to find the discussion.

I've recently installed qmail on a BSDi 2.0 box, and in the
INSTALL docs, it says to attempt a test of:

% echo to: james | /var/qmail/bin/qmail-inject

After taking a look at the maillog, I'm getting the error
5.1.1 (Sorry, there is no mailbox here by that name.). I do
have a ~/Mailbox file, I've followed all the directions to that
point by the book.

It seems your username is `jamesa' not `james'.

Mate
Mate Wierdl
mw@moni.msci.memphis.edu
University of Memphis

I've looked around.

My account on the host that I'm setting this up
on is "james", not "jamesa", so as observant as
it is to note the difference, that isn't the issue. 8(

As far as directory/file permissions, my home directory
is 700, and after doing another test with my Mailbox at 777,
the same error occurs.

A group of users (developers, such as myself), all have their
home directories in /usr/home/devils/<userid>, of which one
needs to be in the group "devils" to get into.

I was told that qmail delivers as the user receiving mail,
so that this is not an issue.

JAmes

At 09:39 PM 2/19/97 -0500, you wrote:
>Michael R. Gile wrote:
>james:*:100:102:JAmes Atwill:/usr/home/devils/james:/bin/bash
>
>[Does having a shadow passwd file matter?] That is infact my
>correct home directory.
>
>> the permission on the ~james/Mailbox file are only writeable by james
>
>-rwx------ 1 james devils 0 Feb 18 11:46 Mailbox

James:

I'm a *recent* convert, so I dunno much, but I did check my test system,
and the mailbox that I have set up (almost everything default) the
executable bit is _not_ set... It's a shot in the dark, I assure you... but
did you try changing that?

I do know that with qlist, it's *really* finiky about the permissions on
the files, especially where the executable bit is concerned.

Hope this helps!
"Merch"

--
Roger Merchberger | On the first day of Christmas my True Love
Programmer, NorthernWay | gave to me: A Beer. -- Bob & Doug McKenzie
zmerch@northernway.net | ====> Like, take off, eh hoser!!!! <====

On Wed, 19 Feb 1997, Roger Merchberger wrote:

> At 09:39 PM 2/19/97 -0500, you wrote:
> >Michael R. Gile wrote:
> >james:*:100:102:JAmes Atwill:/usr/home/devils/james:/bin/bash
> >
> >[Does having a shadow passwd file matter?] That is infact my
> >correct home directory.
> >
> >> the permission on the ~james/Mailbox file are only writeable by james
> >
> >-rwx------ 1 james devils 0 Feb 18 11:46 Mailbox
>
> James:
>
> I'm a *recent* convert, so I dunno much, but I did check my test system,
> and the mailbox that I have set up (almost everything default) the
> executable bit is _not_ set... It's a shot in the dark, I assure you... but
> did you try changing that?

Go one step farther. Delete the file since it's empty anyway and let
qmail re-create it.

>
> I do know that with qlist, it's *really* finiky about the permissions on
> the files, especially where the executable bit is concerned.

Also check the permissions on both /usr/home/devils/james and on
/usr/home/devils. Someone else had a problem when there was a permission
problem on the directory one up from the user's dir.

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================

> A group of users (developers, such as myself), all have their
> home directories in /usr/home/devils/<userid>, of which one
> needs to be in the group "devils" to get into.

That explains it. qmail-getpw hits a permanent error when it tries to
stat your home directory.

You can override qmail-getpw with the qmail-users mechanism; feed
/etc/passwd through qmail-pw2u to create /var/qmail/users/assign, and
then run qmail-newu.

> I was told that qmail delivers as the user receiving mail,
> so that this is not an issue.

It's not up to that stage yet. The decision of which user receives mail
is made by qmail-getpw, running as qmailp.

---Dan
Put an end to unauthorized mail relaying. http://pobox.com/~djb/qmail.html

On 19 Feb 1997, D. J. Bernstein wrote:

> > A group of users (developers, such as myself), all have their
> > home directories in /usr/home/devils/<userid>, of which one
> > needs to be in the group "devils" to get into.
>
> That explains it. qmail-getpw hits a permanent error when it tries to
> stat your home directory.
>
> You can override qmail-getpw with the qmail-users mechanism; feed
> /etc/passwd through qmail-pw2u to create /var/qmail/users/assign, and
> then run qmail-newu.
>
> > I was told that qmail delivers as the user receiving mail,
> > so that this is not an issue.
>
> It's not up to that stage yet. The decision of which user receives mail
> is made by qmail-getpw, running as qmailp.

I'm wondering if by putting qmailp into group devils that would also
work - or is that openning a security hole that I'm not seeing right
off?

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================

Michael R. Gile wrote:

> the only other things to check are:
> james entry in the passwd file has the proper home dir specified

james:*:100:102:JAmes Atwill:/usr/home/devils/james:/bin/bash

[Does having a shadow passwd file matter?] That is infact my
correct home directory.

> the permission on the ~james/Mailbox file are only writeable by james

-rwx------ 1 james devils 0 Feb 18 11:46 Mailbox

> check the conf-unusual.h and make sure ALIAS_EMPTY is set to what
> you think it is (in this case ./Mailbox)

% grep "ALIAS_EMPTY" *.h

conf-unusual.h:#define ALIAS_EMPTY "./Mailbox"

> make sure that /var/qmail/control/defaulthost entry is listed in
> /var/qmail/control/locals

It is.

Here is the snipit of doing:

% echo to: james | /var/qmail/bin/qmail-inject

..from /var/log/maillog, apologise to everyone for it being so
long.. 8(

--------->

Feb 19 16:09:27 topaz qmail: 856386567.274096 new msg 374
Feb 19 16:09:27 topaz qmail: 856386567.457271 info msg 374:
bytes 214 from <rootja@topaz.wonder.ca> qp 25411 uid 0
Feb 19 16:09:27 topaz qmail: 856386567.511548 starting
delivery 22: msg 374 to local james@topaz.wonder.ca
Feb 19 16:09:27 topaz qmail: 856386567.988710 delivery
22: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
Feb 19 16:09:28 topaz qmail: 856386568.346489 bounce msg 374 qp 25414
Feb 19 16:09:28 topaz qmail: 856386568.380106 end msg 374
Feb 19 16:09:28 topaz qmail: 856386568.583941 new msg 375
Feb 19 16:09:28 topaz qmail: 856386568.589399 info msg 375:
bytes 764 from <> qp 25414 uid 192
Feb 19 16:09:28 topaz qmail: 856386568.723819 starting delivery
23: msg 375 to local rootja@topaz.wonder.ca
Feb 19 16:09:28 topaz qmail: 856386568.816309 delivery 23:
failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
Feb 19 16:09:29 topaz qmail: 856386569.118879 bounce msg 375 qp 25417
Feb 19 16:09:29 topaz qmail: 856386569.153580 end msg 375
Feb 19 16:09:29 topaz qmail: 856386569.244028 new msg 374
Feb 19 16:09:29 topaz qmail: 856386569.249101 info msg 374: bytes
1227 from <#@[]> qp 25417 uid 192
Feb 19 16:09:29 topaz qmail: 856386569.444037 starting
delivery 24: msg 374 to local postmaster@topaz.wonder.ca
Feb 19 16:09:29 topaz qmail: 856386569.770685 new msg 375
Feb 19 16:09:29 topaz qmail: 856386569.776252 info msg 375:
bytes 1337 from <#@[]> qp 25420 uid 186
Feb 19 16:09:29 topaz qmail: 856386569.966079 starting
delivery 25: msg 375 to local james@wonder.ca
Feb 19 16:09:30 topaz qmail: 856386570.001147 delivery 24:
success: did_0+1+0/qp_25420/
Feb 19 16:09:30 topaz qmail: 856386570.044274 delivery 25:
failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
Feb 19 16:09:30 topaz qmail: 856386570.128124 end msg 374
Feb 19 16:09:30 topaz qmail: 856386570.189751 triple bounce:
discarding bounce/375
Feb 19 16:09:30 topaz qmail: 856386570.233298 end msg 375

<---------

I have ~alias/.qmail-root -postmaster and -mailer-daemon to be
sent to "james@wonder.ca". (which is me).

Help! 8)

JAmes

Roger Merchberger wrote:

> and the mailbox that I have set up (almost everything default) the
> executable bit is _not_ set... It's a shot in the dark, I assure

Tried that just now, same error. I've recently discovered
that my qmail-alias program core dumps when testing it with:

% /var/qmail/bin/qmail-alias -n james $HOME james "" ""
topaz.wonder.ca james@topaz.wonder.ca
8(

JAmes

D. J. Bernstein wrote:

> You can override qmail-getpw with the qmail-users mechanism; feed
> /etc/passwd through qmail-pw2u to create /var/qmail/users/assign, and
> then run qmail-newu.

This has fixed my problem! The qmail-alias core dumping
was a mistake on my part. All appears to be working well!

I'll go back to lurking now.. 8)

Cheers!

JAmes