qmail Digest 26 Jul 1999 10:00:01 -0000 Issue 709
Topics (messages 28171 through 28188):
Personal name & qmail's sendmail replacement
28171 by: [EMAIL PROTECTED]
28177 by: Keith Burdis <[EMAIL PROTECTED]>
supervision of tcpserver qmptd
28172 by: "Alex Miller" <[EMAIL PROTECTED]>
28173 by: Chris Johnson <[EMAIL PROTECTED]>
28174 by: "Alex Miller" <[EMAIL PROTECTED]>
28175 by: Chris Johnson <[EMAIL PROTECTED]>
Maildir quotas.
28176 by: "Sam" <[EMAIL PROTECTED]>
Brought to you by www.privacyx.com -- ReDate: Sun, 25 Jul 1999 15:07:27 -0700
28178 by: "Wil Boucher" <[EMAIL PROTECTED]>
Qmail::Queue
28179 by: Russell Nelson <[EMAIL PROTECTED]>
28181 by: Russ Allbery <[EMAIL PROTECTED]>
28184 by: [EMAIL PROTECTED]
Logging Failed POP attempts
28180 by: Doug Lumpkin <[EMAIL PROTECTED]>
newbie on qmail
28182 by: Joel Gatdula Pira <[EMAIL PROTECTED]>
28183 by: Scott Schwartz <[EMAIL PROTECTED]>
Recipientmap dead?
28185 by: Ira Abramov <[EMAIL PROTECTED]>
28186 by: Martijn Koster <[EMAIL PROTECTED]>
relaying redundancy
28187 by: torben fjerdingstad <[EMAIL PROTECTED]>
28188 by: Ira Abramov <[EMAIL PROTECTED]>
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Hello!
What is the proper environment variable to use for setting
the personal name in the From: field when sending mail by
invoking qmail's sendmail replacement?
I'm getting a lite tired of "[EMAIL PROTECTED]" being the only
thing showing up in the From: field in people's mail clients :)
Thanks!
/ Peter Schuller
--
PGP userID: 0x5584BD98 or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrival: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://hem.passagen.se/petersch
PGP signature
On Sun 1999-07-25 (17:09), [EMAIL PROTECTED] wrote:
> Hello!
>
> What is the proper environment variable to use for setting
> the personal name in the From: field when sending mail by
> invoking qmail's sendmail replacement?
>
> I'm getting a lite tired of "[EMAIL PROTECTED]" being the only
> thing showing up in the From: field in people's mail clients :)
I use:
export NAME=`perl -e 'print ((split(/,/,(getpwnam($ENV{USER}))[6]))[0]);'`
in my /etc/profile.
It sets the name to the first part of the gecos field.
- Keith
> / Peter Schuller
--
Keith Burdis - MSc (Com Sci) - Rhodes University, South Africa
Email : [EMAIL PROTECTED]
WWW : http://www.rucus.ru.ac.za/~keith/
IRC : Panthras JAPH
"Any technology sufficiently advanced is indistinguishable from a perl script"
Standard disclaimer.
---
I have noticed that my hard disk light clicks on every 2/3 second or so.
It seems that a new process that supervises the tcpserver is created, then
destroyed and created again with a new process number.
the "status" file in /var/lock/qmail-qmtpd keeps getting recreated, even if
I delete it.
The "solution", for lack of a better term, maybe "diagnostic cure", is to
delete the stable process that seems to be spawning the flashing process.
ps -axw yielded 2 processes almost identical.
I kill the one that is stable (and earlier)
it'll be something like where 12345 is the PID
12345 supervise /var/lock/qmail-qmtpd tcpserver -u -c40 -u81 -g80 0 qmtp
qmail-qmtpd
I then execute
kill 12345
This stops the flashing (supervision has been terminated)
I am using Mate's memphis RPM.
Has anyone else seen this? Should supervision be so disk intensive to create
and destroy a file 60+ times a minute?
When I kill that process my disk is mostly silent, unless I am doing
something.
Alex Miller
On Sun, Jul 25, 1999 at 12:13:48PM -0400, Alex Miller wrote:
> I have noticed that my hard disk light clicks on every 2/3 second or so.
>
> It seems that a new process that supervises the tcpserver is created, then
> destroyed and created again with a new process number.
>
> the "status" file in /var/lock/qmail-qmtpd keeps getting recreated, even if
> I delete it.
>
> The "solution", for lack of a better term, maybe "diagnostic cure", is to
> delete the stable process that seems to be spawning the flashing process.
>
> ps -axw yielded 2 processes almost identical.
>
> I kill the one that is stable (and earlier)
> it'll be something like where 12345 is the PID
>
> 12345 supervise /var/lock/qmail-qmtpd tcpserver -u -c40 -u81 -g80 0 qmtp
> qmail-qmtpd
Look at how you're calling tcpserver: you're not providing an argument to the
-u (the first one), so tcpserver prints an error message (which you're not
seeing) and exits. supervise notices tcpserver's death and starts it again,
which is what it's supposed to do.
Fix your tcpserver invocation and everything will be okay.
Chris
> -----Original Message-----
> From: Chris Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, July 25, 1999 12:24 PM
> To: Alex Miller
> Cc: Qmail
> Subject: Re: supervision of tcpserver qmptd
>
>
> On Sun, Jul 25, 1999 at 12:13:48PM -0400, Alex Miller wrote:
> > I have noticed that my hard disk light clicks on every 2/3 second or so.
> >
> > It seems that a new process that supervises the tcpserver is
> created, then
> > destroyed and created again with a new process number.
> >
> > the "status" file in /var/lock/qmail-qmtpd keeps getting
> recreated, even if
> > I delete it.
> >
> > The "solution", for lack of a better term, maybe "diagnostic
> cure", is to
> > delete the stable process that seems to be spawning the
> flashing process.
> >
> > ps -axw yielded 2 processes almost identical.
> >
> > I kill the one that is stable (and earlier)
> > it'll be something like where 12345 is the PID
> >
> > 12345 supervise /var/lock/qmail-qmtpd tcpserver -u -c40 -u81 -g80 0 qmtp
> > qmail-qmtpd
>
> Look at how you're calling tcpserver: you're not providing an
> argument to the
> -u (the first one), so tcpserver prints an error message (which you're not
> seeing) and exits. supervise notices tcpserver's death and starts
> it again,
> which is what it's supposed to do.
>
> Fix your tcpserver invocation and everything will be okay.
>
> Chris
>
Having installed the memphis rpm the invocation of the tcpserver is
controlled by the following file /etc/rc.d/init.d/qmail-qmtpd.init which is
as follows:
#! /bin/sh -
# $INITDIR/qmail-qmqpd.init
# INITDIR is defined below
# Sun Dec 14 1997 XZ <[EMAIL PROTECTED]> v2.3
# chkconfig: 345 84 49
# description: Start, stop, restart, reload, and otherwise \
# signal qmail-qmqpd. \
# Makes heavy use of parts of DJB's daemontools package \
# It also relies upon daemontools.functions for 91.04982% \
# of the grunt work.
#
# [EMAIL PROTECTED]:
# small fixes and modifications
# customize
QMAILHOME=/var/qmail # ~qmail
USERID=`id -u qmaild` # UID to run with
GROUPID=`id -g qmaild` # GID to run with
PROG=qmail-qmqpd # what program?
COMMAND=$PROG # command to start $PROG
DIR=/var/lock/$PROG # directory for supervise
LOGDIR=/var/log/$PROG # directory to log to
LOGUSER=qmaill # user to own logs
LOGSIZE="-s 1000000" # size of logfile
CDB=/etc/tcprules.d/$PROG.cdb # rules file
CONCURRENT=40 # number of concurrent connections
# (40 is the default of tcpserver)
PORT=628 # port to watch
VERBOSE=-v # use verbose option to tcpserver
INITDIR=/etc/rc.d/init.d # location of initscripts
# Grab the daemontools init functions
. $INITDIR/daemontools.functions
export PATH=$QMAILHOME/bin:$PATH
start() {
if check; then
echo "$PROG is already running"
else
echo -n "Starting $PROG..."
if [ -e $CDB ]; then
supervise $DIR \
tcpserver $VERBOSE -c$CONCURRENT -x $CDB -u$USERID -g$GROUPID 0 $PORT
$COMMAND \
2>&1| setuser $LOGUSER accustamp \
| setuser $LOGUSER cyclog $LOGSIZE $LOGDIR &
else
supervise $DIR \
tcpserver $VERBOSE -c$CONCURRENT -u$USERID -g$GROUPID 0 $PORT $COMMAND
\
2>&1 | setuser $LOGUSER accustamp \
| setuser $LOGUSER cyclog $LOGSIZE $LOGDIR &
fi
echo "done"
fi
}
case "$1" in
start)
start
;;
stop)
stop
;;
restart)
restart
;;
status)
status
;;
help)
help
;;
*)
signal $1
;;
esac
I think I might be able to figure out how to fix this file so it doesn't
launch a supervised tcpserver with incorrect parameters but it would be
useful to start off with a working one, and then I can try to translate that
into the script.
What does your invocation look like?
It seems to me though that since this script is unmodified from the memphis
rpm that everyone who uses the memphis rpm should have the identical
symptom, or am I missing something?
Alex Miller
On Sun, Jul 25, 1999 at 12:47:05PM -0400, Alex Miller wrote:
[Quoted text which has been butchered beyond recognition by MS Outlook omitted]
> Having installed the memphis rpm the invocation of the tcpserver is
> controlled by the following file /etc/rc.d/init.d/qmail-qmtpd.init which is
> as follows:
>
> #! /bin/sh -
> # $INITDIR/qmail-qmqpd.init
> # INITDIR is defined below
> # Sun Dec 14 1997 XZ <[EMAIL PROTECTED]> v2.3
>
> # chkconfig: 345 84 49
> # description: Start, stop, restart, reload, and otherwise \
> # signal qmail-qmqpd. \
> # Makes heavy use of parts of DJB's daemontools package \
> # It also relies upon daemontools.functions for 91.04982% \
> # of the grunt work.
> #
> # [EMAIL PROTECTED]:
> # small fixes and modifications
>
> # customize
> QMAILHOME=/var/qmail # ~qmail
> USERID=`id -u qmaild` # UID to run with
> GROUPID=`id -g qmaild` # GID to run with
> PROG=qmail-qmqpd # what program?
> COMMAND=$PROG # command to start $PROG
> DIR=/var/lock/$PROG # directory for supervise
> LOGDIR=/var/log/$PROG # directory to log to
> LOGUSER=qmaill # user to own logs
> LOGSIZE="-s 1000000" # size of logfile
> CDB=/etc/tcprules.d/$PROG.cdb # rules file
> CONCURRENT=40 # number of concurrent connections
> # (40 is the default of tcpserver)
> PORT=628 # port to watch
> VERBOSE=-v # use verbose option to tcpserver
> INITDIR=/etc/rc.d/init.d # location of initscripts
>
> # Grab the daemontools init functions
> . $INITDIR/daemontools.functions
> export PATH=$QMAILHOME/bin:$PATH
>
> start() {
> if check; then
> echo "$PROG is already running"
> else
> echo -n "Starting $PROG..."
> if [ -e $CDB ]; then
> supervise $DIR \
> tcpserver $VERBOSE -c$CONCURRENT -x $CDB -u$USERID -g$GROUPID 0 $PORT
> $COMMAND \
> 2>&1| setuser $LOGUSER accustamp \
> | setuser $LOGUSER cyclog $LOGSIZE $LOGDIR &
> else
> supervise $DIR \
> tcpserver $VERBOSE -c$CONCURRENT -u$USERID -g$GROUPID 0 $PORT $COMMAND
> \
> 2>&1 | setuser $LOGUSER accustamp \
> | setuser $LOGUSER cyclog $LOGSIZE $LOGDIR &
> fi
> echo "done"
> fi
> }
>
> case "$1" in
> start)
> start
> ;;
> stop)
> stop
> ;;
> restart)
> restart
> ;;
> status)
> status
> ;;
> help)
> help
> ;;
> *)
> signal $1
> ;;
> esac
>
> I think I might be able to figure out how to fix this file so it doesn't
> launch a supervised tcpserver with incorrect parameters but it would be
> useful to start off with a working one, and then I can try to translate that
> into the script.
>
> What does your invocation look like?
Mine looks mostly like yours, except that mine doesn't have the extraneous -u.
> It seems to me though that since this script is unmodified from the memphis
> rpm that everyone who uses the memphis rpm should have the identical symptom,
> or am I missing something?
Hell if I can see where that -u is coming from, but if you see it in your
process list, it's coming from somewhere. It doesn't look like that script
should be producing it though; it looks like your -u wants to be a -v.
I've said it before: Redhat packages are wonderful things, but if you want to
understand how things work and not get caught by surprise by things like this,
install qmail and the related programs directly from the sources and write your
own scripts to start them up. Otherwise lots of stuff is going to remain
mysterious and will be much harder to troubleshoot.
Chris
About a month ago I was thinking about various possible ways to implement
quotas on Maildir mailboxes without using filesystem-based quotas. In some
situations, like virtual domains, filesystem quotas will not work.
I've played with my original idea, and came up with a slightly different
way to potentially implement something like this. This one should be much
simpler to implement and use. Many thanks to the few who provided
feedback the first time around:
http://www.concentric.net/~mrsam/maildirpp.html
Never Mind,
I figured it out and got it all working beautifully!
----- Original Message -----
From: Wil Boucher <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 1999 2:15 PM
Subject: Qmail / Ldap / and a seperate outgoing Queue...
Hi there.
I am using qmail-1.03 with the LDAP patches, I have it all up and runnig
nicely, load balanced on several machines and things are just zooming, I am
very happy with Qmail.
What I want to do is add a tag to all messages not destined for local users,
so I want to set up another instance on qmail in a different directory with
a seperate queue etc... (I have the 'taggin' program all ready, I just need
to know how to get the messages to it)
To do this with out the LDAP patches, it was a matter of setting up a
':remote' entry in my virtualdomains file and then setting up
.qmail-remote-default to execute the message parser and then inject the
message into the second queue...
Now with the LDAP patches I don't even have a 'virtualdomains' file, so how
would I go about setting this up?
Anyone done this?
should I just create a virtualdomains file and stick ':remote' in it and
anything not found in the LDAP directory will get sent to
~aliases/.qmail-remote-default ?
All help appreciated!
Wil.
Anybody written a Perl module for Qmail::Queue?
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Russell Nelson <[EMAIL PROTECTED]> writes:
> Anybody written a Perl module for Qmail::Queue?
For talking to qmail-queue? Not quite, but it would be almost trivial to
turn my mjinject code into one.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
On Sun, Jul 25, 1999 at 11:02:53PM -0700, Russ Allbery wrote:
> Russell Nelson <[EMAIL PROTECTED]> writes:
>
> > Anybody written a Perl module for Qmail::Queue?
>
> For talking to qmail-queue? Not quite, but it would be almost trivial to
> turn my mjinject code into one.
As someone who's looked at the code, I second that comment.
--
John White johnjohn
at
triceratops.com
PGP Public Key: http://www.triceratops.com/john/public-key.pgp
I have found answeres to questions about how to log POP attempts in the archives
but all are only for successful retrievals... How do I log failed attempts?
Using Qmail 1.03
checkpassword
echo -n " qmail-pop3d"
tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup mark.bauercom.net \
/bin/checkpassword /usr/bin/poplog /var/qmail/bin/qmail-pop3d Maildir 2>&1
| \
/var/qmail/bin/splogger pop3d &
/usr/bin/popper
#!/bin/sh
echo "$TCPREMOTEIP" "$USER" | /var/qmail/bin/splogger pop3d 3
pop="$1"; shift; exec "$pop" "$@"
Hi,
I've just switched from sendmail to qmail. Almost every thing is working
fine except for my netscape mail.
In sendmail, I fetched my mail from an Exchange Server and used my local
machine for outgoing mails. Since switching from sendmail, I now get the
#5.7.1 message. I do understand that this is a relay problem.
This is my tcm.smtp.
203.172.10.50:allow,RELAYCLIENT=""
127.0.0.1:allow,RELAYCLIENT=""
:allow
203.172.10.50 is where I get my mail. And I do
tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp
However I still get the #5.7.1 error. Any help is appreciated. Thanks
Joel Gatdula Pira
Faculty
Institute of IT Studies
University of Asia and the Pacific
Pearl Drive, Ortigas Center, Pasig City
Joel Gatdula Pira <[EMAIL PROTECTED]> writes:
| In sendmail, I fetched my mail from an Exchange Server and used my local
*************
| machine for outgoing mails.
**************************
I assume you mean that you used SMTP to inject that mail into your
local machine. In that case, the underlined words above are a hint
about which network address qmail should be configured to accept relays
from.
| 203.172.10.50:allow,RELAYCLIENT=""
| 127.0.0.1:allow,RELAYCLIENT=""
| :allow
|
| 203.172.10.50 is where I get my mail.
So you have authorized the remote Exchange Server to relay through your
qmail? That's probably not what you intended to do.
In a new installation I'm doing for a client, I found the need for the
/var/qmail/control/recipientmap I used to use back in the 1.01 days. now
it seems not to respond, it's not even in the qmail-control manpage. was
it really canceled? is there an equivalent, i.e. so I won't need to break
up the old sendmail rules file into 11300 little .qmail files!!!
btw: the egroups post function still attempts to post to djb-qmail@koobera
which bounces. please fix it to post here (whoever is the liason) so I can
subscribe for digests.
TIA, Ira
On Mon, Jul 26, 1999 at 12:09:21PM +0300, Ira Abramov wrote:
>
>
> In a new installation I'm doing for a client, I found the need for the
> /var/qmail/control/recipientmap I used to use back in the 1.01 days. now
> it seems not to respond, it's not even in the qmail-control manpage. was
> it really canceled? is there an equivalent, i.e. so I won't need to break
> up the old sendmail rules file into 11300 little .qmail files!!!
A grep through the source 1.03 directory turns up UPGRADE:
WARNING for upgrades from 1.01: recipientmap is gone. The virtualdomains
mechanism has been expanded to support virtual users.
-- Martijn Koster, [EMAIL PROTECTED]
I wish smtproutes could take a prioritized list of destinations.
Our workstations has jam.net.uni-c.dk defined as "smarthost",
using smtproutes, which contains
:jam.net.uni-c.dk
If that host is down, my outgoing mail is deferred, and I
am not notified.
It would be nice if having
:jam.net.uni-c.dk
:nn.net.uni-c.dk
in smtproutes would try jam first, then nn.
What are my options? I cannot send mail out directly because
of a firewall.
--
Med venlig hilsen / Regards
Netdriftgruppen / Network Management Group
UNI-C
Tlf./Phone +45 35 87 89 41 Mail: UNI-C
Fax. +45 35 87 89 90 Bygning 304
E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
On Mon, 26 Jul 1999, torben fjerdingstad wrote:
> I wish smtproutes could take a prioritized list of destinations.
>
> Our workstations has jam.net.uni-c.dk defined as "smarthost",
> using smtproutes, which contains
> :jam.net.uni-c.dk
>
> If that host is down, my outgoing mail is deferred, and I
> am not notified.
>
> It would be nice if having
>
> :jam.net.uni-c.dk
> :nn.net.uni-c.dk
>
> in smtproutes would try jam first, then nn.
>
> What are my options? I cannot send mail out directly because
> of a firewall.
a little simplistic, but I'd run a script on cron once, say, every 10
minutes that will ping a packet to Jam, and swap to a backup version of
smtproutes and notify you if there's no echo, only to be swapped back and
check again in the next execution. pinging when up will return exit code
of 0, ping timed out will return 1 and host doesn't exist gives 2 (DNS
dead?). I'm not aware of an internal qmail solution.
taking it a step forward, you could use serialmail and check the load
balances on those two relays before releasing outgoing mail once a minute,
but that's just an overkill and delays mail :)
