qmail Digest 27 Aug 2001 10:00:01 -0000 Issue 1469
Topics (messages 68550 through 68564):
anybody managed to use latest courier-imap with vmailmgr ?
68550 by: Olivier M.
Re: more "unable to start supervise"
68551 by: dermini.nevada.edu
Re: qmail/sendmail coexistance
68552 by: Scott Gifford
68558 by: Henning Brauer
68562 by: Scott Gifford
[Announce] oMail-webmail 0.98.4
68553 by: Olivier M.
newbie: statis: local 0/10 remote 0/20 startup/shutdown problem
68554 by: System Administrator
68555 by: Chris Johnson
68557 by: System Administrator
68560 by: Chris Johnson
68563 by: Eric L. Howard
68564 by: Peter van Dijk
error at boot: /var/qmail/rc: exec: env: not found
68556 by: Jack D. Browning
qmail not delivering mail to local users
68559 by: hauser
68561 by: Henning Brauer
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to 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,
Tired many many things (followed docs & howto), but I still
get "Connection closed" immediately after I try to connect
to port 143.
Is courier-imap not supporting external modules anymore ? (authvmailmgr)
I hope not... :) It was working great with older (about 12 months old)
versions.
Thanks!
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
I chmodded the runfiles 000 as you said and I still get the "file does not
exist" error. To check the symlinks, I manually entered the
/var/qmail/supervise/ directory and ran svscan. Still I get the "file does
not exist" error:
svscan: warning: unable to start supervise qmail-send: file does not exist
svscan: warning: unable to start supervise qmail-send/log: file does not
exist
svscan: warning: unable to start supervise qmail-smtpd: file does not
exist
svscan: warning: unable to start supervise qmail-smtpd/log: file does not
exist
Thanks for the advice though,
Duncan
On Sat, 25 Aug 2001, Lukas Beeler wrote:
> try chmodding the runfiles to 000. Then, supervise will tell you, that
> it could'nt start the run file, and not "file not found". If it still
> reports file not found, there's somewhere an error in those symlinks.
> If it shows "could'nt start thr run file", the error is in the run
> files, which most probably contain something, that directs to an
> nonexistent program
Henning Brauer <[EMAIL PROTECTED]> writes:
> On Fri, Aug 24, 2001 at 11:11:28PM +0200, Henning Brauer wrote:
> > No. no way without using another machine or hacking ipme.c.
>
> Correcting myself. There is another way, though not really of choice
> here IMHO. You can put all domains in question in locals and call
> whatever sendmail uses for the local delivery, so both MTAs let the
> MDA write to the same mailboxes. While this setp (though without an
> MDA) works fine using Maildirs and thus two Maildir-aware MTAs (or
> MDAs), it may cause problems here as concurrent deliveries to the same
> mbox file obviously don't work. So there is a theoretical solution
> without patching qmail - but in practice...
Ah, very clever! To avoid the locking problem, just call sendmail
itself instead of the MDA. A little performance penalty, but you
should be able to live with that.
You'll probably need a small shell script (or C program, if the extra
performance is worth the effort) to convert the envelope information
qmail passes in the environment to the command-line parameters
sendmail will expect, but should be pretty easy...Something like:
qmail2sendmail:
#!/bin/sh
/usr/lib/sendmail -i -f "$SENDER" "$RECIPIENT"
then put in ~alias/.qmail-default "|/path/to/qmail2sendmail", or use
it as your defaultdelivery method when starting qmail.
Good luck,
----ScottG.
On Sun, Aug 26, 2001 at 04:12:10AM -0400, Scott Gifford wrote:
> Henning Brauer <[EMAIL PROTECTED]> writes:
> > On Fri, Aug 24, 2001 at 11:11:28PM +0200, Henning Brauer wrote:
> > > No. no way without using another machine or hacking ipme.c.
> > Correcting myself. There is another way, though not really of choice
> > here IMHO. You can put all domains in question in locals and call
> > whatever sendmail uses for the local delivery, so both MTAs let the
> > MDA write to the same mailboxes. While this setp (though without an
> > MDA) works fine using Maildirs and thus two Maildir-aware MTAs (or
> > MDAs), it may cause problems here as concurrent deliveries to the same
> > mbox file obviously don't work. So there is a theoretical solution
> > without patching qmail - but in practice...
> Ah, very clever! To avoid the locking problem, just call sendmail
> itself instead of the MDA. A little performance penalty, but you
> should be able to live with that.
Dunno, that's the obvious solution. Very clever. It still involves syncing
the domain list between qmail and sendmail, but a usable solution without
patching.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg, Germany *
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
Henning Brauer <[EMAIL PROTECTED]> writes:
> On Sun, Aug 26, 2001 at 04:12:10AM -0400, Scott Gifford wrote:
> > Henning Brauer <[EMAIL PROTECTED]> writes:
> > > On Fri, Aug 24, 2001 at 11:11:28PM +0200, Henning Brauer wrote:
> > > > No. no way without using another machine or hacking ipme.c.
> > > Correcting myself. There is another way, though not really of choice
> > > here IMHO. You can put all domains in question in locals and call
> > > whatever sendmail uses for the local delivery, so both MTAs let the
> > > MDA write to the same mailboxes. While this setp (though without an
> > > MDA) works fine using Maildirs and thus two Maildir-aware MTAs (or
> > > MDAs), it may cause problems here as concurrent deliveries to the same
> > > mbox file obviously don't work. So there is a theoretical solution
> > > without patching qmail - but in practice...
> > Ah, very clever! To avoid the locking problem, just call sendmail
> > itself instead of the MDA. A little performance penalty, but you
> > should be able to live with that.
>
> Dunno, that's the obvious solution. Very clever. It still involves syncing
> the domain list between qmail and sendmail, but a usable solution without
> patching.
Make /var/qmail/locals a symlink to /etc/mail/sendmail.cw (or wherever
you keep your sendmail.cw), and make sure that everything local is in
sendmail.cw (not directly in sendmail.cf), and that should be solved,
too.
Amazing what batting something around on a mailing list can do! :)
----ScottG.
Bonjour!
A new version of oMail-webmail is now available: this is version 0.98.3,
with some news:
* updated Italian translation (Fabio Erri)
* added Serbian translation [no]
* added Dutch translation [er]
You will find more infos about this GPL-licensed software,
as well as an online demo of latest version under
http://webmail.omnis.ch/omail.pl?action=about
* Download:
http://prdownloads.sourceforge.net/omail/omail-webmail-0.98.4.tar.gz
* Other URL's: (cvs, releases, etc)
http://freshmeat.net/projects/omail-webmail/
* If you are interested to help, fell free to get the files from the
anonymous CVS, and you are welcome on the devel mailing list.
* There are currently 2 mailing lists :
- omail-news : read-only announce mailing list (for new release announces)
> http://lists.sourceforge.net/mailman/listinfo/omail-news <
- omail-devel : public mailing list for devel & support.
> http://lists.sourceforge.net/mailman/listinfo/omail-devel <
Regards,
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
Hello,
I recently installed qmail on a FreeBSD 4.3 system. I used the
lifewithqmail howto. I have a problem with the system not doing a proper
shutdown or startup with the same process: local 0/10 remote 0/20. I
have
no other information. can someone please help me, or point me in the
right
direction?
thank you
Steven
On Sun, Aug 26, 2001 at 06:39:14PM -0400, System Administrator wrote:
> I recently installed qmail on a FreeBSD 4.3 system. I used the lifewithqmail
> howto. I have a problem with the system not doing a proper shutdown or
> startup with the same process: local 0/10 remote 0/20. I have no other
> information. can someone please help me, or point me in the right direction?
Nobody can point you in the right direction if you have no other information.
It's not at all clear what your problem is or why you even think you have one.
"local 0/10 remote 0/20" is a type of log entry that you'll see frequently. It
means that at the moment there are zero local deliveries and zero remote
delveries in progress. It's completely normal; you'll see a line of this type
in your logs after each delivery is completed.
Chris
PGP signature
I apologize for the lack of information, here is what i discovered:
qmail starts from:
/usr/local/etc/rd.c/qmail.sh (which is a link to /var/qmail/rc) as
follows:
#/var/qmail/rc
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "`cat /var/qmail/control/defaultdelivery`"
I removed the link, so it does not start from there. I added this
line in /etc/rc.conf:
csh -cf '/var/qmail/rc &'
Now it no longer hangs on Local initialization package: Local 0/10
Remote 0/20
(I had to press ctrl-c to break out).
It still doesn't shutdown properly (bear in mind I am new to both unix
and qmail):
shutting down daemon processes: alert: cannot start qmail-send, process
already running
I figure I need somekind of shutdown script for it, since the
rc.shutdown seems
to try running csh -cf '/var/qmail/rc &' again. Can you help me out?
thank you
Steven
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 26, 2001 6:45 PM
To: System Administrator
Cc: Qmail (E-mail)
Subject: Re: newbie: statis: local 0/10 remote 0/20 startup/shutdown
problem
On Sun, Aug 26, 2001 at 06:39:14PM -0400, System Administrator wrote:
> I recently installed qmail on a FreeBSD 4.3 system. I used the
lifewithqmail
> howto. I have a problem with the system not doing a proper shutdown or
> startup with the same process: local 0/10 remote 0/20. I have no other
> information. can someone please help me, or point me in the right
direction?
Nobody can point you in the right direction if you have no other
information.
It's not at all clear what your problem is or why you even think you
have one.
"local 0/10 remote 0/20" is a type of log entry that you'll see
frequently. It
means that at the moment there are zero local deliveries and zero remote
delveries in progress. It's completely normal; you'll see a line of this
type
in your logs after each delivery is completed.
Chris
On Sun, Aug 26, 2001 at 08:03:41PM -0400, System Administrator wrote:
> qmail starts from:
> /usr/local/etc/rd.c/qmail.sh (which is a link to /var/qmail/rc) as
> follows:
>
> #/var/qmail/rc
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start "`cat /var/qmail/control/defaultdelivery`"
It hung because you didn't put the command in the background. And you saw the
"local 0/10 remote 0/20" line on your console because you didn't provide for
any logging.
> I removed the link, so it does not start from there. I added this
> line in /etc/rc.conf:
>
> csh -cf '/var/qmail/rc &'
rc.conf is not a shell script; it's merely a place where you can set variables.
So this particular bit of script will never be executed.
> Now it no longer hangs on Local initialization package: Local 0/10
> Remote 0/20
> (I had to press ctrl-c to break out).
>
> It still doesn't shutdown properly (bear in mind I am new to both unix
> and qmail):
>
> shutting down daemon processes: alert: cannot start qmail-send, process
> already running
>
> I figure I need somekind of shutdown script for it, since the
> rc.shutdown seems
> to try running csh -cf '/var/qmail/rc &' again. Can you help me out?
You said that you used Life with qmail to install and set up qmail. But it
doesn't appear that you did; LWQ would have you start qmail using daemontools.
I would suggest going back and installing carefully as per the LWQ
instructions.
Chris
PGP signature
I know LWQ is the generally accepted and blessed way of install for those on
the list, but have you checked out
http://matt.simerson.net/computing/mail.shtml
???
I'm a FBSD user also and the howtos there got me over the hump when I first
started in w/ qmail. The howtos utilize the ports system which is a HUGE
plus...and I'm not anything near a proficient coder, but I was able to look
through the patches supplied on the site and could pull out what I
needed/wanted and kept flying...
Just a thought...
~ELH~
At a certain time, now past, System Administrator spake thusly:
> Hello,
>
> I recently installed qmail on a FreeBSD 4.3 system. I used the
> lifewithqmail howto. I have a problem with the system not doing a proper
> shutdown or startup with the same process: local 0/10 remote 0/20. I
> have
> no other information. can someone please help me, or point me in the
> right
> direction?
>
> thank you
>
> Steven
>
>
>
--
Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m
----------------------------------------------------------------------
www.OutreachNetworks.com 313.297.9900
On Sun, Aug 26, 2001 at 08:31:33PM -0400, Chris Johnson wrote:
[snip]
>
> rc.conf is not a shell script; it's merely a place where you can set variables.
> So this particular bit of script will never be executed.
In fact, rc.conf is sourced in several scripts. Everytime a script
sources rc.conf, something will try to start qmail. This includes the
shutdown scripts.
Greetz, Peter
--
Against Free Sex! http://www.dataloss.nl/Megahard_en.html
I'm a total newbie to Linux & qmail.
(See "general info" below for program versions, etc.)
qmail installation attempted to follow the much appreciated Life with qmail.
problem:
qmail seems to run fine when typing the following from the console:
/var/qmail/rc
or when I type:
svscan /service
However, when I enter the single line from section 2.7 of Life with qmail at the
bottom of "/etc/inittab":
SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan
/service </dev/null >/dev/console
2>/dev/console
I get the following continuous error at boot or at "kill -HUP 1":
/var/qmail/rc: exec: env: not found
When I type in the same line from the console, starting with "env - PATH=/usr...." it
works fine.
I suspect it is something an experienced person would easily resolve, but don't see
anything directly (or maybe obvious
enough for me to grasp) relating to this in any of the available resources.
Thanks in advance for any suggestions.
general info:
- RedHat Linux 7.1
- qmail 1.03
- daemontools 0.70
- Life with qmail 2001-06-07
Jack D. Browning
[EMAIL PROTECTED]
hi,
qmail isn't able to deliver email to a local user.
the user exists and has a home dir with with a maildir within.
i have installed qmail according to life with qmail.
does any one know what i am doing wrong.
the contents of the send log is as follows,
@400000003b89864438c9970c status: local 0/10 remote 0/20
@400000003b8989ad0601123c new msg 216051
@400000003b8989ad06016ffc info msg 216051: bytes 1287 from
<[EMAIL PROTECTED]> qp 1648 uid 501
@400000003b8989ad06a9e4fc starting delivery 1: msg 216051 to local
[EMAIL PROTECTED]
@400000003b8989ad06aa4a8c status: local 1/10 remote 0/20
@400000003b8989ad10b2509c new msg 216052
@400000003b8989ad10b2a2a4 info msg 216052: bytes 1405 from
<[EMAIL PROTECTED]> qp 1650 uid 507
@400000003b8989ad114a6a1c starting delivery 2: msg 216052 to local
'cat_/var/qmail/control/defaultdelivery'@email.nyandashs.qld.edu.au
@400000003b8989ad114aeeec status: local 2/10 remote 0/20
@400000003b8989ad114b15fc delivery 1: success: did_0+1+0/qp_1650/
@400000003b8989ad114b3d0c status: local 1/10 remote 0/20
@400000003b8989ad14467bac end msg 216051
@400000003b8989ad15e73b2c delivery 2: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400000003b8989ad15e7b444 status: local 0/10 remote 0/20
@400000003b8989ad169cfe6c bounce msg 216052 qp 1653
@400000003b8989ad16a124ec end msg 216052
@400000003b8989ad1a38ab5c new msg 216053
@400000003b8989ad1a3df2ec info msg 216053: bytes 2018 from <> qp 1653 uid 506
@400000003b8989ad1ad88d0c starting delivery 3: msg 216053 to remote
[EMAIL PROTECTED]
@400000003b8989ad1adc7124 status: local 0/10 remote 1/20
@400000003b8989b1011f9324 delivery 3: failure:
Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_is
n't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
@400000003b8989b1012bfed4 status: local 0/10 remote 0/20
@400000003b8989b10233e56c bounce msg 216053 qp 1661
@400000003b8989b102381b8c end msg 216053
@400000003b8989b102435a74 new msg 216052
@400000003b8989b10248b974 info msg 216052: bytes 2611 from <#@[]> qp 1661
uid 506
@400000003b8989b10292b2f4 starting delivery 4: msg 216052 to local
[EMAIL PROTECTED]
@400000003b8989b10296c204 status: local 1/10 remote 0/20
@400000003b8989b107dbb224 new msg 216051
@400000003b8989b107e18654 info msg 216051: bytes 2731 from <#@[]> qp 1664
uid 500
@400000003b8989b1082f5834 starting delivery 5: msg 216051 to local
[EMAIL PROTECTED]
@400000003b8989b108337acc status: local 2/10 remote 0/20
@400000003b8989b10838b2bc delivery 4: success: did_0+1+0/qp_1664/
@400000003b8989b1083d8904 status: local 1/10 remote 0/20
@400000003b8989b108446ea4 end msg 216052
@400000003b8989b1127c3b2c new msg 216052
@400000003b8989b112822e9c info msg 216052: bytes 2845 from <#@[]> qp 1667
uid 500
@400000003b8989b112c8307c starting delivery 6: msg 216052 to local
[EMAIL PROTECTED]
@400000003b8989b112cc5ecc status: local 2/10 remote 0/20
@400000003b8989b112e0f454 delivery 5: success: did_0+1+0/qp_1667/
@400000003b8989b112e68dec status: local 1/10 remote 0/20
@400000003b8989b112ed4894 end msg 216051
@400000003b8989b113cea7e4 delivery 6: failure:
This_message_is_looping:_it_already_has_my_Delivered-To_line._(#5.4.6)/
@400000003b8989b113d8b234 status: local 0/10 remote 0/20
@400000003b8989b113df6cdc triple bounce: discarding bounce/216052
@400000003b8989b113e210a4 end msg 216052
the qmail rc script is as follows,
#!/bin/sh
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "'cat /var/qmail/control/defaultdelivery'"
the qmail smtpd run script is as follows,
#!/bin/sh
exec /usr/local/bin/softlimit -m 3000000 \
/usr/local/bin/tcpserver -v -R -l 0 -x /etc/tcp.smtp.cdb -c 20 \
-u 501 -g 500 0 25 /var/qmail/bin/qmail-smtpd 2>&1
the contents of /var/qmail/control/locals is,
email.nyandashs.qld.edu.au
the contents of /var/qmail/control/defaultdelivery is,
./Maildir/
the contents of /var/qmail/defaultdomain is,
nyandashs.qld.edu.au
the contents of /var/qmail/control/me is,
email.nyandashs.qld.edu.au
regards,
eric.
On Mon, Aug 27, 2001 at 10:07:51AM +1000, hauser wrote:
> @400000003b8989ad114a6a1c starting delivery 2: msg 216052 to local
> 'cat_/var/qmail/control/defaultdelivery'@email.nyandashs.qld.edu.au
Copy&Paste scripts from lwq rather than retyping them.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg, Germany *
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
