I never knew about this...because i've never set qmail up for
nis/nfs.....which makes my situation even stranger....
I always check the permissions first....I have permissions set up correctly
in /etc/skel...so every user created automatically has the correct
permissions......permissions have always been what I look at first, because
as with you ...it always fixes 90% of my problems.......sucks to have one in
the other 10%
I'm almost stumped on this one......it has to be something simple....
I would rather not have to run that cron script...if I don't have to.
I concider it kind of a hack for now.
-----Original Message-----
From: Brett Randall [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 08, 2000 1:05 AM
To: qmail
Subject: RE: help with strange problem
> to add........
> I have discovered that the users that are working are in
> /var/control/users/assign
> what updates this file?
Unless RedHat 7.0 beta includes some automatic function, then you do. Read
the qmail FAQ on info for how to update this (specifically look for
information on NIS/NFS outages...this is included there.) I don't know if
this is covered in LWQ but I would guess so.
Also, most of the problems I have had with qmail like yours are to do with
Maildir permissions. Make sure in the actual home folder of the recipient
that they have at least read/write permissions (maybe a cd ~user; chmod -R
u+r *; chown -R user *; chown -R user .qmail; chgrp -R group *; chgrp -R
group .qmail) might help. This has 90% of the time caused the below problem.
BUT the assign file you asked about before probably caused the other 10%! If
in doubt, delete it :> (Or move it somewhere else and its associated
files...probably recommended).
Brett.
Manager
InterPlanetary Solutions
http://ipsware.com/
-----Original Message-----
From: Barry Smoke [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 08, 2000 1:11 PM
To: [EMAIL PROTECTED]
Subject: Re: help with strange problem
----- Original Message -----
From: Barry Smoke
To: [EMAIL PROTECTED]
Sent: Monday, August 07, 2000 9:45 PM
Subject: help with strange problem
I have been pulling my hair out on this one all day long. I am including
all my information so you guys can help keep my hair in.....
I have been running qmail on a mail machine at a k12 school for a year...no
real problems to speak of....
now I have upgraded this server to redhat 7.0 beta......I know...why on
earth would you use beta on a production machine....well, I tested it out on
several otehr machines...and all went well, and it's not the beta I'm having
problems with.
The machine in question is bryant.dsc.k12.ar.us
there is an alias to this machine...bryant.k12.ar.us
I have been running this machine aliased for our administrators for the
year...and now I'm moving all of our schools over to this machine.
That includes elementaries, the jr.high, high school, etc....
Mail is working perfectly for our administrators(thank goodness)...but not
for new users
I have /etc/skel setup to create a Maildir correctly(yes I used
maildirmake), and copy a .qmail file to everyone's home directory.
I checked permissions...they match our existing users that are working.....
you can send mail to [EMAIL PROTECTED] me at
[EMAIL PROTECTED]
but when you add a new user ....you can't send mail to them at either
address....I've tried restarting qmail...and restarting the machine(with
blind hopes)
I got this whe I added a user named testingthemail:
to local [EMAIL PROTECTED]
Aug 7 20:10:10 bryant qmail: 965697010.528031 status: local 2/10 remote
0/20
Aug 7 20:10:10 bryant qmail: 965697010.548143 delivery 24: success:
did_0+0+0/
Aug 7 20:10:10 bryant qmail: 965697010.566173 status: local 1/10 remote
0/20
Aug 7 20:10:10 bryant qmail: 965697010.567118 delivery 25: failure:
Sorry,_no_m
ailbox_here_by_that_name._(#5.1.1)/
I added another user just a while ago....and all of the sudden his is
working...I haven't done anything....
but this new one I just added isn't yet.......
is there a file I have to manually update if I want users to be accessible
right after being added?
#################/etc/skel##################
[root@bryant skel]# ls -al
total 20
drwxr-xr-x 6 root root 1024 Aug 3 17:51 .
drwxr-xr-x 48 root root 6144 Aug 7 19:20 ..
-rw-r--r-- 1 root root 24 Jul 17 09:56 .bash_logout
-rw-r--r-- 1 root root 230 Jul 17 09:56 .bash_profile
-rw-r--r-- 1 root root 124 Jul 17 09:56 .bashrc
-rw-r--r-- 1 root root 688 Jul 25 11:53 .emacs
drwxr-xr-x 4 root root 1024 Aug 3 17:34 .kde
-rw-rw-r-- 1 root root 11 May 10 12:55 .qmail
-rw-r--r-- 1 root root 3394 Jul 12 19:34 .screenrc
drwxr-xr-x 4 root root 1024 Aug 3 17:34 Desktop
drwx------ 5 root root 1024 Aug 3 15:48 Maildir
drwxrwxr-x 2 root root 1024 Dec 4 1999 web
[root@bryant skel]# cat .qmail
./Maildir/
[root@bryant skel]# cd Maildir
[root@bryant Maildir]# ls -al
total 5
drwx------ 5 root root 1024 Aug 3 15:48 .
drwxr-xr-x 6 root root 1024 Aug 3 17:51 ..
drwx------ 2 root root 1024 Aug 3 15:48 cur
drwx------ 2 root root 1024 Aug 3 15:48 new
drwx------ 2 root root 1024 Aug 3 15:48 tmp
##############control files#######################
[root@bryant control]# cat defaulthost
bryant.k12.ar.us
[root@bryant control]# cat defaultdomain
k12.ar.us
[root@bryant control]# cat locals
proxy.intranet.net
localhost
bryant.k12.ar.us
proxy.bryant.dsc.k12.ar.us
bryant.dsc.k12.ar.us
[root@bryant control]# cat me
bryant.k12.ar.us
##############nslookup on the ip##############
[root@bryant control]# nslookup 165.29.94.240
Server: achilles.k12.ar.us
Address: 165.29.1.1
Name: bryant.dsc.k12.ar.us
Address: 165.29.94.240
###########################################
##############nslookup on the aliased domain#######
[root@bryant control]# nslookup bryant.k12.ar.us
Server: achilles.k12.ar.us
Address: 165.29.1.1
Name: bryant.dsc.k12.ar.us
Address: 165.29.94.240
Aliases: bryant.k12.ar.us
#################################################
