tcpserver daemon tools and xinetd

2000-10-15 Thread John Chronakis




Hi,
 
I am a new (and happy) qmail user.
After spending days on reading various documents, 
man pages, how to pages, FAQ ...
some things about daemon tools are still not 
so clear to me.
 
qmail.org and qmail's author clearlly suggest to 
use tcpserver for qmail-smtpd and this is 
enough for me.
 
But there is not any clear suggestion for using 
daemon tools instead of a superserver like xinetd 
(inetd is out of the question).
In addition, the "install" file from the qmail 
source destribution has an example for using inetd to launch qmail-smtpd and 
pop3d.
 
On the other hand qmail-howto, and allmost every 
othe document about qmail, are suggesting using daemon tools.
 
Friends of mine working as administrators in medium 
size ISPs, are suggesting to use qmail-smtpd and qmail-pop3d
with xinetd like they do.
 
All these different oppinions confused 
me.
 
I just want to know the best way to 
control qmail since I am expecting a high 
number of mail users.
What I am concerned is a reliable, stable and 
efficient mail delivery.
 
Only :)
 
 
John
 


Whrere are my log files?

2000-10-18 Thread John Chronakis

Hello,

I have configured qmail-send & qmail-smtp to run under the daemon tools,
according to qmail howto.

For example I use the two following run script under
/service/qmail-send/log/


#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t
s250 /var/log/qmail/qmail-send


/var/log/qmail /var/log/qmail/qmail-send are owned by qmaill

My problem is that ther is nothing inside the log directories





Re: Whrere are my log files?

2000-10-18 Thread John Chronakis

Hello again,

>Is multilog running? Is the sticky bit set on /service/qmail-send?

There are two instances of multilog running, one for qmai-send and one for
qmail-smtpd.

The sticky bit is set for /var/qmail/supervice/qmail-send
(/service/qmail-send is a sim link to the former).
I just worry if the /var/qmail/rc file is correct, because man qmail-start
sais that default logger is splogger.

Here it is.

#!/bin/sh
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start './Maildir/'

John





Re: "Whrere are my log files?" The blind man said.

2000-10-18 Thread John Chronakis



I was blind !!!
 
The cause off all these was a missing backslash in 
the /service/qmail-send/log/run file.
 
Thanks for your help.
 
John
 


How to ignore .qmail-* files for given users?

2000-10-23 Thread John Chronakis

Hello,

I would like to prevent users with ftp access to change the
delivery instructions for qmail.

To be more specific, I want some users not to be able to receive mail at all
(they all bellong to the same group) and others not be able to change
delivery instruction by creating their own dot-qmail files via ftp
(they all belong to another group).

I suppose that this is controled by QMAILHOME/users/assign,
but the man page is not very helpful.

Can anyone help?

John





Re: How to ignore .qmail-* files for given users?

2000-10-24 Thread John Chronakis

You are right. wu.ftpd can restrict actions to files or directories
matching a pattern.

I am going to use it for now, but I would prefer to control all mail
relative
stuff from within qmail. I am going to experiment with qmail/users/assign
file and see what I can do.

Thanks

John


> I don't know that this is the most efficient way, but you should be able
> to prevent all access to any file that starts with .qmail via your ftp
> daemon setup.
>
> - T
>
> --
> Tyler J. Frederick
> Systems Administrator
> Sportsline.com, Inc.
>
> On Tue, 24 Oct 2000, John Chronakis wrote:
>
> > Hello,
> >
> > I would like to prevent users with ftp access to change the
> > delivery instructions for qmail.
> >
> > To be more specific, I want some users not to be able to receive mail at
all
> > (they all bellong to the same group) and others not be able to change
> > delivery instruction by creating their own dot-qmail files via ftp
> > (they all belong to another group).
> >
> > I suppose that this is controled by QMAILHOME/users/assign,
> > but the man page is not very helpful.
> >
> > Can anyone help?
> >
> > John
> >
> >
>
>