qmail Digest 8 Oct 1999 10:00:01 -0000 Issue 783
Topics (messages 31334 through 31399):
qmail-popup
31334 by: Brendan Pratt
31353 by: Ken Jones
31394 by: Brendan Pratt
option -v on /bin/mail
31335 by: phil.ipal.net
31338 by: Anand Buddhdev
31357 by: phil.ipal.net
users/assign question
31336 by: phil.rigel.ipal.net
31339 by: Anand Buddhdev
31340 by: David Dyer-Bennet
Re: A second strange problem.
31337 by: Thomas M. Sasala
31344 by: Bruno Wolff III
31355 by: Thomas M. Sasala
31358 by: Markus Stumpf
31359 by: Dave Sill
31364 by: Thomas M. Sasala
31396 by: Michael Boyiazis
Re: supervise and qmail
31341 by: Dave Sill
31345 by: Petr Novotny
31347 by: Timothy L. Mayo
31349 by: Russell Nelson
31350 by: Dave Sill
31351 by: Petr Novotny
31354 by: Frank D. Cringle
31360 by: phil.ipal.net
31363 by: phil.ipal.net
31376 by: Frank D. Cringle
Re: Supervise and qmail/tcpserver
31342 by: Dave Sill
31392 by: Robert Wojciechowski Jr.
Re: Speed up qmail-smtpd
31343 by: Dave Sill
31346 by: Russell Nelson
Re: Suggestions requested
31348 by: Tyler Frederick
mini qmail question
31352 by: Tatsuya Murase
Relaying to mailhub.
31356 by: eric
Ensuring operation
31361 by: Nagendra Mishr
31367 by: David Dyer-Bennet
31369 by: Stan Horwitz
31370 by: Dave Sill
31371 by: Markus Stumpf
31372 by: Jeff Taylor
31374 by: Kai MacTane
31378 by: Dave Sill
Re: Queue stalls
31362 by: Dave Sill
31373 by: B. Engineer
31377 by: Dave Sill
31391 by: Kevin Sawyer
Re: fetchmail to work with qmail
31365 by: Dave Sill
Re: Authentification problem with pop3d
31366 by: Dave Sill
Re: logging died when I added dot-forwarding
31368 by: Dave Sill
New mail notification
31375 by: dizzy.media2000.kappa.ro
quotacheck for pop toaster
31379 by: Jon Rust
31382 by: Jon Rust
Duplicate Messages
31380 by: eric
31381 by: Russell Nelson
31386 by: eric
Re: qmail as secondary MX
31383 by: Claus F�rber
Qmail Anti-Relaying problem :)
31384 by: Seyyed Hamid Reza Hashemi Golpayegani
I Have a Problem on Qmail Anti-Relaying
31385 by: Seyyed Hamid Reza Hashemi Golpayegani
31390 by: David Harris
IMAP & qmail
31387 by: Alexander Grekhov
31388 by: Sam
31389 by: David Harris
problem with svscan in daemontools 0.61
31393 by: George Hong
31397 by: Frank D. Cringle
up to date FTP
31395 by: phil.ipal.net
Problems with own mailing list...q
31398 by: Volker Jung
eXtreme forwarding - is it possbile ?
31399 by: Thomas Foerster
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]
----------------------------------------------------------------------
Hi All,
After having a crash today, I've discovered that I'm now getting
authentication errors.
I'm not a programmer, so if I've missed something obvious, then you'll
understand why. :-)
--cut here--
snowy:/work# telnet virtual 110
Trying 203.56.37.8...
Connected to proxy.overflow.net.au.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user sales%sumdomain.com.au
+OK
pass 1111111
-ERR aack, child crashed
Connection closed by foreign host.
--cut here--
The actual password and usernames are correct when I try them.
Oh, and I'm also using vpopmail here too, hence the domain details in the
above clipping.
It all worked perfectly until the lockup, which required me to run e2fsck on
the drive.
--
Current Net Legislation will slow us down and cost us more!
Tell you Local Federal Member NOW it will hurt your business
For more info visit http://www.efa.org.au/Campaigns/99.html
--
C u laitr
-------------------------------------------------------------------------
Brendan Pratt Overflow Internet Services
Mobile : +61-418-746657
Phone : +61-7-55-463-832
E-Mail : [EMAIL PROTECTED]
-------------------------------------------------------------------------
Others have reported a similar problem and traced it to a corrupted
~vpopmail/domains/sumdomain.com.au/vpasswd file
Others have reported corrupted binaries of vchkpw programs. Try
reinstalling vchkpw and checking the vpasswd file for strangeness.
ken Jones
Inter7
Brendan Pratt wrote:
>
> Hi All,
>
> After having a crash today, I've discovered that I'm now getting
> authentication errors.
>
> I'm not a programmer, so if I've missed something obvious, then you'll
> understand why. :-)
>
> --cut here--
> snowy:/work# telnet virtual 110
> Trying 203.56.37.8...
> Connected to proxy.overflow.net.au.
> Escape character is '^]'.
> +OK <[EMAIL PROTECTED]>
> user sales%sumdomain.com.au
> +OK
> pass 1111111
> -ERR aack, child crashed
> Connection closed by foreign host.
> --cut here--
>
> The actual password and usernames are correct when I try them.
>
> Oh, and I'm also using vpopmail here too, hence the domain details in the
> above clipping.
>
> It all worked perfectly until the lockup, which required me to run e2fsck on
> the drive.
>
> --
> Current Net Legislation will slow us down and cost us more!
> Tell you Local Federal Member NOW it will hurt your business
> For more info visit http://www.efa.org.au/Campaigns/99.html
> --
>
> C u laitr
> -------------------------------------------------------------------------
> Brendan Pratt Overflow Internet Services
> Mobile : +61-418-746657
> Phone : +61-7-55-463-832
> E-Mail : [EMAIL PROTECTED]
> -------------------------------------------------------------------------
Hi Ken,
----- Original Message -----
From: Ken Jones <[EMAIL PROTECTED]>
> Others have reported a similar problem and traced it to a corrupted
> ~vpopmail/domains/sumdomain.com.au/vpasswd file
I thought that might have been the case too, but I'm also having problems
with users that are in /etc/passwd file too.
> Others have reported corrupted binaries of vchkpw programs. Try
> reinstalling vchkpw and checking the vpasswd file for strangeness.
Have already tried that out, but without any luck. I also reinstalled qmail
as well, so as to make sure that all bases were covered.
> > --cut here--
> > snowy:/work# telnet virtual 110
> > Trying 203.56.37.8...
> > Connected to proxy.overflow.net.au.
> > Escape character is '^]'.
> > +OK <[EMAIL PROTECTED]>
> > user sales%sumdomain.com.au
> > +OK
> > pass 1111111
> > -ERR aack, child crashed
> > Connection closed by foreign host.
> > --cut here--
--
Current Net Legislation will slow us down and cost us more!
Tell you Local Federal Member NOW it will hurt your business
For more info visit http://www.efa.org.au/Campaigns/99.html
--
C u laitr
-------------------------------------------------------------------------
Brendan Pratt Overflow Internet Services
Mobile : +61-418-746657
Phone : +61-7-55-463-832
E-Mail : [EMAIL PROTECTED]
-------------------------------------------------------------------------
With sendmail, the -v option on /bin/mail gave me a copy of the
SMTP conversation if the message wasn't queued. Is there any
way to get this under qmail? It isn't essential, but it's a
nice logging touch for soe of my mail generating scripts.
--
Phil Howard
[EMAIL PROTECTED]
On Thu, Oct 07, 1999 at 06:02:56AM -0500, [EMAIL PROTECTED] wrote:
/bin/mail submits the message to sendmail with the -v switch, and
because sendmail is a single program, it can display its conversation.
With qmail, you submit the message to qmail-inject, which simply
deposits the message into the queue, and lets qmail-send do the
delivery. So you can't see the SMTP conversation.
> With sendmail, the -v option on /bin/mail gave me a copy of the
> SMTP conversation if the message wasn't queued. Is there any
> way to get this under qmail? It isn't essential, but it's a
> nice logging touch for soe of my mail generating scripts.
> --
> Phil Howard
> [EMAIL PROTECTED]
--
See complete headers for more info
Anand Buddhdev wrote:
> /bin/mail submits the message to sendmail with the -v switch, and
> because sendmail is a single program, it can display its conversation.
> With qmail, you submit the message to qmail-inject, which simply
> deposits the message into the queue, and lets qmail-send do the
> delivery. So you can't see the SMTP conversation.
So basically, it's queued anyway.
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Why do I need /var/qmail/users/assign? Things work fine
without it. It seems like it implements another way to
do aliases. Which way is the right way to make an alias
with qmail ... in /var/qmail/alias/.qmail-whatever or in
users/assign with a line beginning with "whatever"?
--
Phil Howard
[EMAIL PROTECTED]
On Thu, Oct 07, 1999 at 06:28:18AM -0500, [EMAIL PROTECTED] wrote:
When qmail-lspawn begins an attempt at delivery, it _first_ consults
users/assign, and failing to find an address in there, falls back to
consulting /etc/passwd. If you have no special needs, you can do without
a users/assign file.
> Why do I need /var/qmail/users/assign? Things work fine
> without it. It seems like it implements another way to
> do aliases. Which way is the right way to make an alias
> with qmail ... in /var/qmail/alias/.qmail-whatever or in
> users/assign with a line beginning with "whatever"?
You can do aliases both ways; there's nothing particular for or against
either method, but the purists might argue that using users/assign is
faster because CDB lookups are faster, and also since qmail-lspawn
always tries to open users/assign first, it will save a few system calls
if it can find an entry in there.
> --
> Phil Howard
> [EMAIL PROTECTED]
--
See complete headers for more info
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes on 7 October 1999 at 06:28:18 -0500
> Why do I need /var/qmail/users/assign? Things work fine
> without it. It seems like it implements another way to
> do aliases. Which way is the right way to make an alias
> with qmail ... in /var/qmail/alias/.qmail-whatever or in
> users/assign with a line beginning with "whatever"?
Depends how many aliases you have in real and virtual domains. I'm
managing all mine without users/assign, including mailboxes in 16
virtual domains. None of them have more than a few tens of mailboxes,
so it's easy to go to their controlling directory and see what's
there.
If I had hundreds of aliases in some of them, I'd probably find myself
seriously considering users/assign.
--
David Dyer-Bennet **Update your records, forwarding expires soon** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
I was getting something like this (please note this is not
the actual log - I can post that tomorrow is someone wants to see
it):
933785415.436366 tcpserver: status: 1/40
933785415.437241 tcpserver: pid 6010 from 127.0.0.1
933785415.462990 tcpserver: ok 6010 localhost:127.0.0.1:25
localhost:127.0.0.1:root:4309
933785453.943401 tcpserver: end 6010 status 256
933785453.943468 tcpserver: status: 0/40
When the status in the next to last line was 0, the message
was delivered. When the status was 256, the message was not
delivered. I could not find any information about exit codes
in any of the documentation. I fixed the problem code, which
made the problem go away. But it still doesn't change the fact
that I had the problem. The remote system thought the message was
delivered, but it was not (i.e., all responses from smtpd where +OK,
but the message never showed up). This seems broken to me.
What do you mean by the 'final' ok? OK to ending the
data segment?
-Tom
Harald Hanche-Olsen wrote:
>
> + Markus Stumpf <[EMAIL PROTECTED]>:
>
> | As with disappering messages:
> | smtpd simply accepts the email and hands it on to other processes
> | (qmail-queue).
>
> That statement may be a bit misleading. The cronology is the other
> way around: qmail-smtpd hands the message to qmail-queue, and does not
> give the final OK until qmail-queue has exited with a zero status
> code. Any SMTP client that doesn't wait for that final OK is broken.
>
> - Harald
--
+-------------------------------------------------------------------+
+ Thomas M. Sasala, Electrical Engineer [EMAIL PROTECTED] +
+ MRJ Technology Solutions http://www.mrj.com +
+ 10461 White Granite Drive, Suite 102 (W)(703)277-1714 +
+ Oakton, VA 22124 (F)(703)277-1702 +
+-------------------------------------------------------------------+
On Thu, Oct 07, 1999 at 07:32:45AM -0400,
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> I was getting something like this (please note this is not
> the actual log - I can post that tomorrow is someone wants to see
> it):
>
> 933785415.436366 tcpserver: status: 1/40
> 933785415.437241 tcpserver: pid 6010 from 127.0.0.1
> 933785415.462990 tcpserver: ok 6010 localhost:127.0.0.1:25
> localhost:127.0.0.1:root:4309
> 933785453.943401 tcpserver: end 6010 status 256
> 933785453.943468 tcpserver: status: 0/40
>
> When the status in the next to last line was 0, the message
> was delivered. When the status was 256, the message was not
> delivered. I could not find any information about exit codes
> in any of the documentation. I fixed the problem code, which
> made the problem go away. But it still doesn't change the fact
> that I had the problem. The remote system thought the message was
> delivered, but it was not (i.e., all responses from smtpd where +OK,
> but the message never showed up). This seems broken to me.
This stuff is pretty much irrelevant. You can't expect to check the status
of which messages were accepted successfully by looking at the exit code.
SMTP allows for the transfer of more than one message and for messages
to be resent after some failure in the same session. So a single exit code
can't tell you all of what you need to know. The data command will return a
success code if the message was successfully accepted. This is what needs to
be checked.
I think you are missing the point. I'm not looking at the
exit code. Let me be specific. I was using a Java transport class
that was not properly written. I would send a message with this class
and the class would say the message was sent. However, in reality,
smtpd would reject the message.
To debug the problem I used recordio. I noticed that the
class was not reading any output from smptd. It just stuffed the
whole message into smptd and exited. So, I modified the class to
read input and check for +OK and -ERROR.
I recorded an entire session where every response from smptd
was +OK, BUT the mail was never delivered. By pouring through the
logs, I noticed that when there was an exit code of 256, the mail
was not delivered. When the exit code was 0, the mail was delivered.
Somewhere during this whole process, I saw the message about bad
cr/lf. Once I fixed that problem, everything started to work.
So, the point here is that smtpd responded with +OK for everything,
leading me to believe the mail had been accepted and was delivered.
However, the mail *never* showed up in the queue. The qmail log was
blank and the smtpd log showed an exit code of 256.
> This stuff is pretty much irrelevant. You can't expect to check the status
> of which messages were accepted successfully by looking at the exit code.
> SMTP allows for the transfer of more than one message and for messages
> to be resent after some failure in the same session. So a single exit code
> can't tell you all of what you need to know. The data command will return a
> success code if the message was successfully accepted. This is what needs to
> be checked.
--
+-------------------------------------------------------------------+
+ Thomas M. Sasala, Electrical Engineer [EMAIL PROTECTED] +
+ MRJ Technology Solutions http://www.mrj.com +
+ 10461 White Granite Drive, Suite 102 (W)(703)277-1714 +
+ Oakton, VA 22124 (F)(703)277-1702 +
+-------------------------------------------------------------------+
On Thu, Oct 07, 1999 at 11:24:57AM -0400, Thomas M. Sasala wrote:
> To debug the problem I used recordio. I noticed that the
> class was not reading any output from smptd. It just stuffed the
> whole message into smptd and exited. So, I modified the class to
> read input and check for +OK and -ERROR.
SMTP dialog does not use "+OK" oder "-ERROR", but "Codes". See RFC 821
for examples and definitions.
Whatever you've logged, it was NOT an smtp session, if the system
responded with "+OK" or "-ERROR". This looks more like a POP session.
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> I think you are missing the point. I'm not looking at the
>exit code. Let me be specific. I was using a Java transport class
>that was not properly written. I would send a message with this class
>and the class would say the message was sent. However, in reality,
>smtpd would reject the message.
>
> To debug the problem I used recordio. I noticed that the
>class was not reading any output from smptd. It just stuffed the
>whole message into smptd and exited. So, I modified the class to
>read input and check for +OK and -ERROR.
+OK and -ERR (not ERROR) are from POP, not SMTP.
> I recorded an entire session where every response from smptd
>was +OK, BUT the mail was never delivered.
Please post that.
>By pouring through the
>logs, I noticed that when there was an exit code of 256, the mail
>was not delivered. When the exit code was 0, the mail was delivered.
>Somewhere during this whole process, I saw the message about bad
>cr/lf. Once I fixed that problem, everything started to work.
If you saw the cr/lf message, I can assure you qmail-smtpd returned
an error on the SMTP DATA command.
> So, the point here is that smtpd responded with +OK for everything,
>leading me to believe the mail had been accepted and was delivered.
If your SMTP daemon is doing "+OK", it's not qmail-smtpd. In fact,
it's probably not even an SMTP daemon.
>However, the mail *never* showed up in the queue. The qmail log was
>blank and the smtpd log showed an exit code of 256.
The qmail-send log would be blank if no message was successfully
injected, e.g., because of a stray LF.
-Dave
My bad. This is true - the +OK and -ERROR are from
POP sessions. I should of said XXX ok for the smtp session.
I was getting 2xx ok as responses.
Markus Stumpf wrote:
>
> SMTP dialog does not use "+OK" oder "-ERROR", but "Codes". See RFC 821
> for examples and definitions.
> Whatever you've logged, it was NOT an smtp session, if the system
> responded with "+OK" or "-ERROR". This looks more like a POP session.
>
> \Maex
>
> --
> SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
> Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
> Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
> D-80807 Muenchen | Fax: +49 (89) 32356-299 |
--
+-------------------------------------------------------------------+
+ Thomas M. Sasala, Electrical Engineer [EMAIL PROTECTED] +
+ MRJ Technology Solutions http://www.mrj.com +
+ 10461 White Granite Drive, Suite 102 (W)(703)277-1714 +
+ Oakton, VA 22124 (F)(703)277-1702 +
+-------------------------------------------------------------------+
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Subject: Re: A second strange problem.
>
>
> So, the point here is that smtpd responded with +OK for everything,
> leading me to believe the mail had been accepted and was delivered.
> However, the mail *never* showed up in the queue. The qmail log was
> blank and the smtpd log showed an exit code of 256.
I could be way wrong here, but didn't someone see the 256 as the return
code from the bare-line-feed problem in a log someplace?
Michael Boyiazis -----
[EMAIL PROTECTED]
NetZero
Mail/Sys/Network Admin
__________________________________________
NetZero - Defenders of the Free World
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html
[EMAIL PROTECTED] wrote:
>Would there be any reason not to use supervise for qmail-start?
I can't think of a good reason not to.
>I notice that much documentation (I'm still working on merging
>the various sources of documentation and resolving apparent
>conflicts)
Differences aren't necessarily conflicts. There's more than one way to
skin a cat, you know.
>shows starting qmail-smtpd with supervise and tcpserver
>but just starts qmail-start by itself.
Look at "Life with qmail":
http://Web.InfoAve.Net/~dsill/lwq.html
>What I want is a clean way to shut qmail down, either smtp side
>(because I don't want anything coming in on the network) or the
>local side (because I might be messing with delivery targets) or
>both (because I'm shutting the whole system down).
A very slight modification to the "qmail" script in LWQ will allow
this.
-Dave
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7 Oct 99, at 9:09, Dave Sill wrote:
> >Would there be any reason not to use supervise for qmail-start?
>
> I can't think of a good reason not to.
Um, like, qmail-start only spawns a few daemons and then goes
away, doesn't it? Definitely I can't see it running around my
machine. Therefore you can't supervise it - supervise works on
daemons, not on daemon-spawners.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBN/ys51MwP8g7qbw/EQKhnwCfSOo3FFRGT/nevFtTp4n5YPsA1EgAoNdC
WRTiOiahEO8cqLBfTvSYJybg
=r5Sy
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
Misleading. supervise can control any process with does not daemonize
itself or put itself in the background. Here are the contents of my
/var/qmail/rc script which specifically uses supervise. Other examples
can be found as well.
======= start of /var/qmail/rc ============
#! /bin/sh
# Using cyclog to log the messages
# Using dot-forward to support sendmail-style ~/.forward files.
# Using qmail-local to deliver messages to ~/Maildir/ by default.
exec env - PATH="/var/qmail/bin:$PATH" \
/usr/local/bin/supervise /var/run/qmail qmail-start '|dot-forward .forward
./Maildir/' /usr/local/bin/accustamp | \
/usr/local/bin/setuser qmaill \
/usr/local/bin/cyclog -s10000000 -n200 /var/adm/qmail
======= end of /var/qmail/rc ==============
Note: you will NOT find qmail-start in your process list after it
completes. qmail start launches 3 other daemons and then replaces itself
with the qmail-send process. It is the qmail-send process NOT qmail-start
itself that you need to supervise and control.
On Thu, 7 Oct 1999, Petr Novotny wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 7 Oct 99, at 9:09, Dave Sill wrote:
> > >Would there be any reason not to use supervise for qmail-start?
> >
> > I can't think of a good reason not to.
>
> Um, like, qmail-start only spawns a few daemons and then goes
> away, doesn't it? Definitely I can't see it running around my
> machine. Therefore you can't supervise it - supervise works on
> daemons, not on daemon-spawners.
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.0.2 -- QDPGP 2.60
> Comment: http://community.wow.net/grt/qdpgp.html
>
> iQA/AwUBN/ys51MwP8g7qbw/EQKhnwCfSOo3FFRGT/nevFtTp4n5YPsA1EgAoNdC
> WRTiOiahEO8cqLBfTvSYJybg
> =r5Sy
> -----END PGP SIGNATURE-----
> --
> Petr Novotny, ANTEK CS
> [EMAIL PROTECTED]
> http://www.antek.cz
> PGP key ID: 0x3BA9BC3F
> -- Don't you know there ain't no devil there's just God when he's drunk.
> [Tom Waits]
>
---------------------------------
Timothy L. Mayo mailto:[EMAIL PROTECTED]
Senior Systems Administrator
localconnect(sm)
http://www.localconnect.net/
The National Business Network Inc. http://www.nb.net/
One Monroeville Center, Suite 850
Monroeville, PA 15146
(412) 810-8888 Phone
(412) 810-8886 Fax
Petr Novotny writes:
> Um, like, qmail-start only spawns a few daemons and then goes
> away, doesn't it? Definitely I can't see it running around my
> machine. Therefore you can't supervise it - supervise works on
> daemons, not on daemon-spawners.
qmail-start execs (not forks) qmail-send. I supervise it. Floats my
boat.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
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!
"Petr Novotny" <[EMAIL PROTECTED]> wrote:
>On 7 Oct 99, at 9:09, Dave Sill wrote:
>
>> I can't think of a good reason not to [run qmail-start under
>> supervise].
>
>Um, like, qmail-start only spawns a few daemons and then goes
>away, doesn't it?
No, not exactly. It starts a few daemons then exec's
qmail-send. qmail-start goes away, but its PID is inherited by
qmail-start.
-Dave
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7 Oct 99, at 9:47, Timothy L. Mayo wrote:
> Note: you will NOT find qmail-start in your process list after it
> completes. qmail start launches 3 other daemons and then replaces itself
> with the qmail-send process. It is the qmail-send process NOT qmail-start
> itself that you need to supervise and control.
Oh this is how. I thought it spawns four daemons and exits. I
should read the sources more often :-)
Does that means that qmail-send remains parent for the other three
daemons - ie. if it dies, it takes the children to the grave too?
Otherwise I would think that supervise re-starting qmail-start would
cause some confusion...
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBN/y2OlMwP8g7qbw/EQLn+QCeOXSNXbbbEUPB92+tWnKmhAtM35MAn2jm
Svbko/hDfHuzpTJouLsJ8eZj
=Z8xO
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
"Petr Novotny" <[EMAIL PROTECTED]> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 7 Oct 99, at 9:47, Timothy L. Mayo wrote:
> > Note: you will NOT find qmail-start in your process list after it
> > completes. qmail start launches 3 other daemons and then replaces itself
> > with the qmail-send process. It is the qmail-send process NOT qmail-start
> > itself that you need to supervise and control.
>
> Oh this is how. I thought it spawns four daemons and exits. I
> should read the sources more often :-)
>
> Does that means that qmail-send remains parent for the other three
> daemons - ie. if it dies, it takes the children to the grave too?
> Otherwise I would think that supervise re-starting qmail-start would
> cause some confusion...
Here's an extract from 'pstree -c' on a machine running qmail with
daemontools-0.61:
|-svscan-+-supervise---tcpserver
| |-supervise---multilog
| |-supervise---qmail-send-+-qmail-clean
| | |-qmail-lspawn
| | `-qmail-rspawn
| |-supervise---multilog
| |-supervise---tcpserver
| |-supervise---multilog
| |-supervise---tcpserver
| `-supervise---multilog
The tcpservers are listening for smtp, qmtp, pop3.
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 2304) 467101; fax: 943357
Dave Sill wrote:
> [EMAIL PROTECTED] wrote:
>
> >Would there be any reason not to use supervise for qmail-start?
>
> I can't think of a good reason not to.
>
> >I notice that much documentation (I'm still working on merging
> >the various sources of documentation and resolving apparent
> >conflicts)
>
> Differences aren't necessarily conflicts. There's more than one way to
> skin a cat, you know.
As I say "apparent". I am figuring these things out, and am often
interpolating, or even extrapolating, my own way of doing things.
I've been on the mailing list for over a year before I had the chance
to put qmail on a full running system.
> Look at "Life with qmail":
That's one with difference with qmail HOWTO :-)
> A very slight modification to the "qmail" script in LWQ will allow
> this.
What I've done is just that, located as /etc/qmail/rc . I also put the
tcprules files in /etc/qmail. Then instead of invoking /var/qmail/rc
from /etc/qmail/rc I just copied my /etc/qmail/rc into /var/qmail/rc.
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Frank D. Cringle wrote
> Here's an extract from 'pstree -c' on a machine running qmail with
> daemontools-0.61:
>
> |-svscan-+-supervise---tcpserver
> | |-supervise---multilog
> | |-supervise---qmail-send-+-qmail-clean
> | | |-qmail-lspawn
> | | `-qmail-rspawn
> | |-supervise---multilog
> | |-supervise---tcpserver
> | |-supervise---multilog
> | |-supervise---tcpserver
> | `-supervise---multilog
>
> The tcpservers are listening for smtp, qmtp, pop3.
What is "svscan"?
I didn't see that in my copy of daemontools.
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
> Frank D. Cringle wrote
>
> > Here's an extract from 'pstree -c' on a machine running qmail with
> > daemontools-0.61:
> ...
> What is "svscan"?
>
> I didn't see that in my copy of daemontools.
Which version?
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 2304) 467101; fax: 943357
"Robert Wojciechowski Jr." <[EMAIL PROTECTED]> wrote:
>> # svc -dx /var/supervise/qmail/qmail-smtpd
>
>doesn't kill the tcpserver process, but supervise does die. Why?
Don't know. Trace the supervise process with your OS's system call
tracer to see where/why it's dying.
-Dave
Turns out that I needed to start tcpserver with exec. Then all went well.
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
PGP: 0xF2CA68F2 - http://www.wojo.com/pgpkeys/robertw.asc
-----Original Message-----
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 07, 1999 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: Supervise and qmail/tcpserver
"Robert Wojciechowski Jr." <[EMAIL PROTECTED]> wrote:
>> # svc -dx /var/supervise/qmail/qmail-smtpd
>
>doesn't kill the tcpserver process, but supervise does die. Why?
Don't know. Trace the supervise process with your OS's system call
tracer to see where/why it's dying.
-Dave
"Jorge Mota" <[EMAIL PROTECTED]> wrote:
>I have a problem with the qmail-smtp daemon because is very slow to
>receive mail from a host in the network, and the mail client always
>display a message to tell me: "the smtp server do not respond, wait
>another 60 seconds". I don't now how can I solve this problem and
>improve the response of the server.
Sounds like a name server problem. How are you starting qmail-smtpd?
If you get really stuck, try running qmail-smtp under a system call
tracing utility via a wrapper.
-Dave
Jorge Mota writes:
> I have a problem with the qmail-smtp daemon because is very slow to
> receive mail from a host in the network, and the mail client always
> display a message to tell me: "the smtp server do not respond, wait
> another 60 seconds". I don't now how can I solve this problem and
> improve the response of the server.
Check for DNS problems, specifically no reverse dns.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
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!
Steve, check out vpopmail from inter7 (www.inter7.com). It's intended for
multi-domain sites, but it's just as simple to set it up with your domain
as a virtualdomain. It maintains it's own userlist, has Maildir support,
and works with qmailadmin for {creating,removing,editing}
{accounts,aliases,forwards}. I've just recently checked it out and was
very impressed.
- T
---
Tyler J. Frederick
Senior Systems Engineer
fc.com, Inc.
On Wed, 6 Oct 1999, Steve Philp wrote:
> We're currently using Qmail to host approximately 50 mailboxes for a
> single domain. The accounts have been created as system accounts on a
> Red Hat 6.0 machine. We're currently trying to find solutions to a
> couple problems:
> I've looked at qmailadmin, but it seems to require the use of virtual
> domains and user setup outside of system files. I'd love to move to
Hi,
I've attempted to implement mini-qmail on a firewall here at work.
After doing the what is
described on the qmail web pages as the prescription for mini-qmail, I
find that sending a test message with qmail-inject exits with a
"communication with server failed (#4.4.2)" error.
I seem to be getting some sort of connection timeout, yet the qmqpd
server acknowledges some sort of traffic. The main qmail log is silent,
and no mail is ever received.
I'm attempting to run the mini-qmail setup on a RH 5.2 system (qmail
compiled straight from
1.03 sources + DNS patch) and the qmqpd is running on a RH 6 system
(where qmail is compiled from
Mr. Guenter's src.rpms). The qmqpservers file on the mini-qmail box
does contain the IP address
and not the hostname of the qmqpd server. I have also made sure the
permissions on qmail-qmqpc
match those on qmail-queue. When mini-qmail is in operation, the
firewall is designated as
the MX in the DNS tables.
If there are others out there happily running mini-qmail on their
firewalls to handle incoming
and outgoing mail, I'd appreciate any tips you could offer.
Thanks in advance,
--Tatsuya Murase
We are upgrading a machine from sendmail 8.8.8 (Solaris stock)
to qmail. In order to relay mail for particular domains we'll need
the appropriate files in /var/qmail/control/, and /etc/tcp.smtp.cdb
Are there any other pitfalls to be watch out for? We haven't had time
to test and unfortuntately can't now that the machine is in production.
Thanks.
Does anyone know the best way to monitor running Systems? I.e. I want
to know that somthing is wrong with the system... Is the best way to
read the logs?
Nagendra
Nagendra Mishr <[EMAIL PROTECTED]> writes on 7 October 1999 at 12:48:55 -0400
>
> Does anyone know the best way to monitor running Systems? I.e. I want
> to know that somthing is wrong with the system... Is the best way to
> read the logs?
"Best way" is always a red herring. Reading the full logs will give
you the most information, and use the most time. Developing patterns
for something like swatch to read the logs for you, and refer possible
problems to your attention, will use less time, but may miss
unexpected situations. It's also useful to have another system try an
SMTP session (and POP if you're suppporting that) regularly, and page
you if it fails; this can notify you *sooner* if something gets
wedged.
(And with qmail you probably want to run matchup from qmailanalog, and
then some of the statistics scripts, and read their output regularly.)
--
David Dyer-Bennet **Update your records, forwarding expires soon** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
On Thu, 7 Oct 1999, Nagendra Mishr wrote:
>
> Does anyone know the best way to monitor running Systems? I.e. I want
> to know that somthing is wrong with the system... Is the best way to
> read the logs?
It seems to me that your question is beyond the topic of the qmail list.
There are a number of packages that monitor Unix systems, including some
that your vendor may be able to supply. The public domain package that we
use is called Nocol and it can be obtained via the Web, but I do not have
the URL for it handy right now. Another package that does system
monitoring that I heard good things about is called "Big Brother" which
you can also find via a Web search.
Nagendra Mishr <[EMAIL PROTECTED]> wrote:
>Does anyone know the best way to monitor running Systems? I.e. I want
>to know that somthing is wrong with the system... Is the best way to
>read the logs?
This is a real can o' worms.
It's easy to verify that certain processes are running and certain
functions are working. But determining that all parts of it are
working is whole 'nuther story.
Personally, I use Big Brother to periodically connect to port 25
remotely and look for the qmail-send process locally. I'm pretty
confident that if both those tests succeed, qmail is "working".
If had to be more sure, I'd have a cron job on a monitoring system
send a message to a remote system via SMTP which would go to a special
mailbox that sends a reply, probably using Peter Samuel's
"vacation". If the monitoring system didn't receive the expected
response in the alloted timeframe, it'd raise an alarm.
-Dave
On Thu, Oct 07, 1999 at 12:48:55PM -0400, Nagendra Mishr wrote:
> Does anyone know the best way to monitor running Systems? I.e. I want
> to know that somthing is wrong with the system... Is the best way to
> read the logs?
Could you be a bit more specific on what you want to monitor?
If you simply want to monitor is qmail system is running, the easiest
would IMHO be to send an email via cron (e.g. every 5 mins) from a "remote"
system (not the system running qmail) and relay it to another account on
that remote system.
Set up the receiving account with a small script that e.g. checks
incoming mail's Received lines for dates. Thus you can see how long the
email took to pass through the qmail system. The script could also
create a status file that could be checked from the cron job that creates
the email and create a pager alert.
However this has an additional point of failure if the mail system on
the remote system does not work properly.
We currently have a small script that only checks if the SMTPD is
answering (sending HELO, MAIL FROM, RCPT TO and RSET and checking
for the response codes) and I have set up a tcpserver (for allow/deny) that
fires of /var/qmail/bin/qmail-qstat. Another small script connects to that
port and parses the two lines returned from qmail-qstat and checks
for the size of the queue against a high water mark (this is mainly to
see, if we're hit by a spammer relaying via one of our customers that
uses us as an outgoing relay. In that case the queue is usually filling
fast).
HTH,
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
Yes, the logs are very useful. I use Xlogmaster
http://www.gnu.org/software/xlogmaster/xlogmaster.html
It allows me to monitor /var/log/messages, /var/log/warn, and
/var/log/mail in one window. It has alarms to run programs, send
e-mail, play sound files, etc. when a regexp shows up in the log. I
have alarms for port scans, the printer running out of paper, etc. It
is nice.
Jeff
Quoting Nagendra Mishr <[EMAIL PROTECTED]>:
>
> Does anyone know the best way to monitor running Systems? I.e. I want
> to know that somthing is wrong with the system... Is the best way to
> read the logs?
>
> Nagendra
>
Text written by Nagendra Mishr at 12:48 PM 10/7/99 -0400:
>
>Does anyone know the best way to monitor running Systems? I.e. I want
>to know that somthing is wrong with the system... Is the best way to
>read the logs?
Depends on your situation. If you have multiple machines, and especially if
you have a shell account on some machine in a different location, you might
want to run something like Big Brother.
Big Brother is a set of shell scripts that run periodic tests on a variety
of services (including POP3 and SMTP), give a display of the situation on a
Web page, and can even page you if something goes wrong.
In particular, for its testing of services, it actually tries to form an
SMTP or POP3 connection to the machine being monitored. This means it's
doing real tests; if this script can't make an SMTP connection, then it's
likely that real users can't, either. I really like this as a monitoring
method. In general, where possible, I really like the idea of remote
testing on the actual ports used rather than simply looking at the logs; I
feel that you look at the logs *after* something goes wrong, so you can
figure out what it was. But some errors won't show up in the logs.
Additionally, Big Brother has an optional client portion that sits on the
monitored machine and lets you know if any of certain listed (configurable)
processes aren't running.
I can't give it a completely untarnished recommendation; I do have some
problems with Big Brother. For one, I think it should be reimplemented in
Perl; many of the text-manipulation and similar tasks it performs would be
so much cleaner there. And it's not as versatile or flexible as it could
be; trying to bend it to do things that are similar to, but not quite, what
it already does always seems harder than it should be. I would definitely
not recommend it for a large and complex monitoring situation, and I would
caution anyone evaluating it that while it's pretty nice as long as you
only want the functionality that already comes with it, it gets crotchety
and brittle when you alter it.
However, you might want to look at the way it does things and then roll
your own. You can find Big Brother at http://www.maclawran.ca.
-----------------------------------------------------------------
Kai MacTane
System Administrator
Online Partners.com, Inc.
-----------------------------------------------------------------
>From the Jargon File: (v4.0.0, 25 Jul 1996)
hungus /huhng'g*s/ /adj./
[perhaps related to slang `humongous'] Large, unwieldy, usually unman-
ageable. "TCP is a hungus piece of code."
Kai MacTane <[EMAIL PROTECTED]> wrote:
>I can't give it a completely untarnished recommendation; I do have some
>problems with Big Brother. For one, I think it should be reimplemented in
>Perl;
See "Big Sister", a perl-based reimplementation of Big Brother by
someone other than the author of Big Brother.
Sean MacGuire has his reasons for doing BB in shell, but that's for
another list.
-Dave
Kevin Sawyer <[EMAIL PROTECTED]> wrote:
>I'm not actually "seeing" messages really. Here's some more information.
>If wait a day or so then run "du -s /var/qmail/queue" I'll see say 120MB in
>that hierarchy.
Run qmail-qstat and qmail-read at this point. Then check the logs for
messages relating to the undelivered messages.
>If I then run "/etc/rc.d/init.d/qmail restart" I can
>immediately use "df" to watch my /var partition usage shrink.
OK, that's great. But if you want to figure out what's going on,
instead of just flushing the queue, you'll need to use subtler
techniques.
>... My concurrencylocal/remote are both set to the
>compiled maximum of 120 and this box is definitely mean enough to support
>that.
Are you consistently hitting those maxima?
>It just doesn't make sense to me that only SOME messages don't get delivered
>locally while others continue to get delivered just fine.
I can't explain it with the information I have so far, but I'm dead
certain there's a rational explanantion for it.
-Dave
On Thu, 7 Oct 1999, Dave Sill wrote:
> >... My concurrencylocal/remote are both set to the
> >compiled maximum of 120 and this box is definitely mean enough to support
> >that.
> Are you consistently hitting those maxima?
What are the ways that can be checked?
Regards
Burzin
"B. Engineer" <[EMAIL PROTECTED]> wrote:
>On Thu, 7 Oct 1999, Dave Sill wrote:
>
>> >... My concurrencylocal/remote are both set to the
>> >compiled maximum of 120 and this box is definitely mean enough to support
>> >that.
>> Are you consistently hitting those maxima?
>
>What are the ways that can be checked?
Look for lines in the log like:
1999-09-29 08:24:54.586305500 status: local 0/10 remote 3/20
The 10 is concurrencylocal, 20 is concurrencyremote, 0 is current
number of qmail-locals, and 3 is current number of qmail-remots.
-Dave
> Run qmail-qstat and qmail-read at this point. Then check the logs for
> messages relating to the undelivered messages.
qmail-qstat typically shows about 500 messages in the queue and 0 messages
not yet processed.
qmail-qread only shows remotes that are marked as "done" or very recently
tried. No locals.
> >If I then run "/etc/rc.d/init.d/qmail restart" I can
> >immediately use "df" to watch my /var partition usage shrink.
>
> OK, that's great. But if you want to figure out what's going on,
> instead of just flushing the queue, you'll need to use subtler
> techniques.
I'm all ears...
> >... My concurrencylocal/remote are both set to the
> >compiled maximum of 120 and this box is definitely mean
> enough to support
> >that.
>
> Are you consistently hitting those maxima?
Never. Even when I send SIGALRM to qmail-send, I'm luck to get 2 locals and
40 remotes.
> >It just doesn't make sense to me that only SOME messages
> don't get delivered
> >locally while others continue to get delivered just fine.
>
> I can't explain it with the information I have so far, but I'm dead
> certain there's a rational explanantion for it.
Again, I'm all ears. I'd love to resolve this. It's almost like messages
are randomly sneaking into the queue without qmail-send being able to see
them until it is restarted. Fun fun...
--Kevin
Emmanuel Nee <[EMAIL PROTECTED]> wrote:
>i was trying to get mail from a remote server. It seem to work
>successfully but do not know where is the mail residing after that.
>Please help if you can.
Please provide more information. What does your .fetchmailrc say? What
do your qmail logs say?
-Dave
Ng Hak Beng <[EMAIL PROTECTED]> wrote:
> Qmail is run using tcpserver, but when I telnet to port 110, I do the
>usual USER <myUID> & PASS <mytextpasswd>, if get a failed authentification.
>
> Do I have to create a .cdb to get pop3d to allow my pop
> connection?
No, if you're connecting to port 110 successfully, which you must be
if you're entering USER and PASS commands, you're already past that
hurdle.
> All the files in ~/control seems ok to me. Or have I missed
> out on some important file.
None of the files in /var/qmail/control are related to POP
authentication.
> Appreciate any help! Thanks in advance.
Try the checkpassword test documented on www.qmail.org.
-Dave
Brandon Dudley <[EMAIL PROTECTED]> wrote:
>Dave Sill wrote:
>> I don't use dot-forward, so I don't know for sure, but I
>> suspect you really need something like:
>>
>> csh -cf 'qmail-start "|dot-forward .forward
>> ./Mailbox" splogger qmail &'
>>
>> Note the line break after the dot-forward command.
>
>tried all 3 permutations, all gave different errors.
Include a cut-n-paste copy of your command, and the resulting error.
> part of the problem is that when I try to change the csh line,
>the shell fails to execute using the explicit PATH statement, so it
>cannot find the executables.
I don't follow. Again, cut-n-paste the command you entered and the
response.
>Sorry, I didn't save the errors.
Sorry, I can't help you without them.
-Dave
First sorry if this question is answered in docs.
My problem is that I want the "You have new mail" notification to
use Maildir (a patch for bash or a PAM module or a biff program).
I have a RH 6.1 with shadow and QMail 1.03
Thanx
I was going to use Paul Gregg's mailquotacheck.sh for managing
mailbox sizes on my pop toaster. However, I noticed this line:
# Get the users 'home' directory - where there .qmail file is
dir="$HOME"
Bah! All of my delivery directories are in
/var/qmail/popboxes/domain/userid, and all use Maildir for delivery.
Since there is no $HOME for that user, I don't think this will work.
How can I get mailquotacheck.sh to check the size of ./Maildir/ in
these user-less mailboxes?
The .qmail files look like so for each mail directory:
|/var/qmail/bin/mailquotacheck.sh
./Maildir/
Each .qmail file is a link to a master file:
mail0:/var/qmail/popboxes/domain1/user{274} # ls -l
total 5
lrwxr-xr-x 1 root qmail 28 Oct 1 23:52 .qmail ->
/var/qmail/control/dot-qmail
Thanks,
jon
As a few folks pointed out in private email, the whole point of PG's
mailquotacheck is to check the size of pop toaster accounts. My bad.
Saw $HOME, and immediately thought of what $HOME usually means.
Why is it not working though? I've got 10's of megabytes of files in
my delivery directory (just to test this out) and all deliveries are
proceeding normally. All test messages are 20k or larger (so the 1k
thing isn't stopping them). mailquotacheck.sh is in the correct
directory, and is executable. /bin/sh is in the correct place. ??
Jon
At 12:50 PM -0700 10/7/99, Jon Rust wrote:
>I was going to use Paul Gregg's mailquotacheck.sh for managing
>mailbox sizes on my pop toaster. However, I noticed this line:
>
> # Get the users 'home' directory - where there .qmail file is
> dir="$HOME"
>
>Bah! All of my delivery directories are in
>/var/qmail/popboxes/domain/userid, and all use Maildir for delivery.
>Since there is no $HOME for that user, I don't think this will work.
>How can I get mailquotacheck.sh to check the size of ./Maildir/ in
>these user-less mailboxes?
>
>The .qmail files look like so for each mail directory:
>
> |/var/qmail/bin/mailquotacheck.sh
> ./Maildir/
>
>Each .qmail file is a link to a master file:
>
> mail0:/var/qmail/popboxes/domain1/user{274} # ls -l
> total 5
> lrwxr-xr-x 1 root qmail 28 Oct 1 23:52 .qmail ->
> /var/qmail/control/dot-qmail
>
>
>Thanks,
>jon
I have just migrated to qmail from sendmail 8.8.8 (Solaris)
We have a web based email system that is using the following
syntax:
/usr/lib/sendmail -f 'sendingdomain.com <[EMAIL PROTECTED]>' -bm
This works fine for sending - but seems to send duplicate messages --
all time stamps and unique IDs are exactly the same on the two
messages.
Help is appreciated. I removed my /var/qmail/* dirs and
redid a make setup check but no go.
Thanks.
eric writes:
> I have just migrated to qmail from sendmail 8.8.8 (Solaris)
>
> We have a web based email system that is using the following
> syntax:
>
> /usr/lib/sendmail -f 'sendingdomain.com <[EMAIL PROTECTED]>' -bm
Try /usr/lib/sendmail -f '[EMAIL PROTECTED]' -bm
The address handed to the -f should be an RFC821 address, since it's
used to set the envelope sender, not an RFC822 address.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
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!
Yes this seemed to do the trick. Thanks for the response.
Eric
; > I have just migrated to qmail from sendmail 8.8.8 (Solaris)
; >
; > We have a web based email system that is using the following
; > syntax:
; >
; > /usr/lib/sendmail -f 'sendingdomain.com <[EMAIL PROTECTED]>' -bm
;
; Try /usr/lib/sendmail -f '[EMAIL PROTECTED]' -bm
;
; The address handed to the -f should be an RFC821 address, since it's
; used to set the envelope sender, not an RFC822 address.
deden purnamahadi <[EMAIL PROTECTED]> schrieb/wrote:
> ----- Transcript of session follows -----
> ... while talking to gemini.uninet.net.id.:
> >>>RCPT To:<[EMAIL PROTECTED]>
> <<< 571 <[EMAIL PROTECTED]>... we do not relay
Gemini does not know that it is supposed to accept mail for
uninet.net.id. With qmail, you would have to add uninet.net.id to your
rcpthosts. For sendmail, read its documentation.
--
Claus Andre Faerber <http://www.faerber.muc.de>
PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Hi ,
I have installed Redhar Linux 6.0 and qmail 1.03 on it . I have install POP3
daemen on that . OutLook Express and other pop3 clients can send a message
that have a sender e-mail address that not on my domain.com . For example if
my domain is morva.com you can send a mail message from my PoP3 daemon
that's sender address is from hotmail.com !?!?!?
I want to deliver only the mails that from my domain and reject mails that
don't from my domain ! So how can I do this on my pop3 and sending mechanism
?
Thanx
Hamid Hashemi
Tehran - Iran
Seyyed Hamid Reza Hashemi Golpayegani [mailto:[EMAIL PROTECTED]] wrote:
> I have installed Redhar Linux 6.0 and qmail 1.03 on it . I have install POP3
> daemen on that . OutLook Express and other pop3 clients can send a message
> that have a sender e-mail address that not on my domain.com . For example if
> my domain is morva.com you can send a mail message from my PoP3 daemon
> that's sender address is from hotmail.com !?!?!?
> I want to deliver only the mails that from my domain and reject mails that
> don't from my domain ! So how can I do this on my pop3 and sending mechanism
>?
Just filtering mail based on the sender domain is a bad idea. It's easy enough
to someone to abuse your server just by spoofing a domain on your machine..
then you get the fallout from the spam. If you really want to do this, search
the list archives and/or qmail.org and you'll find some patches floating
around.
If you know that your users are going to come from a specific block of ip
addresses, then setup tcpserver to set the RELAYCLIENT environment variable for
connects from this ipaddress block, and setup a "rcpthosts" file. For more
information see www.qmail.org and the qmail manual pages
If you don't have the luxury of all your users being in one ipaddress block,
then a good solution is to require POP before SMTP. This way you only allow
computers which have previously authenticated though SMTP to relay mail though
your machine. I have setup a tool to do this:
http://www.davideous.com/smtp-poplock/
- David Harris
Principal Engineer, DRH Internet Services
Does anyone use any IMAP server with maildirs? I'm going to install mail
server where all our company e-mail will be stored and I think IMAP is more
suitable for this purpose than POP. Cyrus does not seem to support maildirs
and I did not find any patches for it. WU-IMAP seems to be the only
solution.
I'd like to know if anyone is using such configuration as "production
server".
Thanks
Alexander
On Thu, 7 Oct 1999, Alexander Grekhov wrote:
> Does anyone use any IMAP server with maildirs? I'm going to install mail
> server where all our company e-mail will be stored and I think IMAP is more
> suitable for this purpose than POP. Cyrus does not seem to support maildirs
> and I did not find any patches for it. WU-IMAP seems to be the only
There are Maildir patches for UW-IMAP somewhere out there.
I'll probably have a working Maildir IMAP server in about 3-4 weeks.
--
Sam
Alexander Grekhov [mailto:[EMAIL PROTECTED]] wrote:
> Does anyone use any IMAP server with maildirs? I'm going to install mail
> server where all our company e-mail will be stored and I think IMAP is more
> suitable for this purpose than POP. Cyrus does not seem to support maildirs
> and I did not find any patches for it. WU-IMAP seems to be the only
> solution.
>
> I'd like to know if anyone is using such configuration as "production
> server".
http://www.davideous.com/imap-maildir/
I took a maildir patch for UW-IMAP and then hammed out all the stupid problems
I could see until it was working for me. I've also heard good reports from
others, so it is definitely "in production".
- David Harris
Principal Engineer, DRH Internet Services
Hi there,
I have daemontool 0.61 installed for qmail on Redhat Linux 6.0.
Everything works fine except two problems related to svscan:
1. I have qmail, qmail-smtpd, qmail-pop3d directories under directory
/var/lock/qmailsvc with run script in each directory. When I run svscan
in /var/lock/qmailsvc, the processes will all be invoked and work. If I
put it in the script, it will give the error message and fails:
Here is the script:
#! /bin/sh
# Source function library.
. /etc/rc.d/init.d/functions
QPATH=/var/lock/qmailsvc
case "$1" in
start)
cd $QPATH
/usr/local/bin/svscan &
;;
stop)
pid=`pidofproc svscan`
kill $pid
sleep 2
cd $QPATH
/usr/local/bin/svc -dx *
;;
*)
echo "usage: $0 start|stop"
;;
esac
The error message is:
svscan: warning: unable to start supervise qmail: file does not exist
svscan: warning: unable to start supervise qmail-smtpd: file does not
exist
svscan: warning: unable to start supervise qmail-pop3d: file does not
exist
2. The second question is that it doesn't write to the log file, all
the message will be displayed at the console window.
Take qmail as example:
Here is the directory structure:
[root@roadrunner qmail]# pwd
/var/lock/qmailsvc/qmail
[root@roadrunner qmail]# ls -la */*
-rwxrwxr-x 1 qmaill nofiles 74 Sep 24 16:17 log/run
prw------- 1 qmaill nofiles 0 Oct 6 17:03 supervise/control
-rw------- 1 qmaill nofiles 0 Sep 24 16:19 supervise/lock
prw------- 1 qmaill nofiles 0 Sep 24 16:19 supervise/ok
-rw-r--r-- 1 root root 18 Oct 6 17:05 supervise/status
log/supervise:
total 3
drwx------ 2 qmaill nofiles 1024 Sep 24 16:19 .
drwxrwxr-x 3 qmaill nofiles 1024 Sep 24 17:34 ..
prw------- 1 qmaill nofiles 0 Sep 24 16:11 control
-rw------- 1 qmaill nofiles 0 Sep 24 16:11 lock
prw------- 1 qmaill nofiles 0 Sep 24 16:11 ok
-rw-r--r-- 1 qmaill nofiles 18 Sep 24 16:19 status
[root@roadrunner qmail]# more run
#! /bin/sh
exec qmail-start "|dot-forward .forward
./Maildir/" tai64n qmail
[root@roadrunner qmail]# more log/run
#! /bin/sh
exec setuidgid qmaill multilog -s 1000000 -n 10 /var/log/qmail
Can anyone give me a hint where I might have done wrong?
Thanks.
--George
George Hong <[EMAIL PROTECTED]> writes:
> Hi there,
> I have daemontool 0.61 installed for qmail on Redhat Linux 6.0.
Bruce Guenter has an rpm spec for daemontools-0.61 that I found helpful.
> Everything works fine except two problems related to svscan:
> 1. I have qmail, qmail-smtpd, qmail-pop3d directories under directory
> /var/lock/qmailsvc with run script in each directory. When I run svscan
> in /var/lock/qmailsvc, the processes will all be invoked and work. If I
> put it in the script, it will give the error message and fails:
> Here is the script:
> #! /bin/sh
>
> # Source function library.
> . /etc/rc.d/init.d/functions
>
> QPATH=/var/lock/qmailsvc
>
> case "$1" in
> start)
> cd $QPATH
> /usr/local/bin/svscan &
> ;;
> stop)
> pid=`pidofproc svscan`
> kill $pid
> sleep 2
> cd $QPATH
> /usr/local/bin/svc -dx *
> ;;
> *)
> echo "usage: $0 start|stop"
> ;;
> esac
> The error message is:
> svscan: warning: unable to start supervise qmail: file does not
> exist
Do you have an old version of daemontools still installed? Maybe the
script is picking up a different version from that found in your
shell's PATH. Something similar happened to me when bash remembered
/usr/local/bin/svc (old version) even though I had installed
/usr/bin/svc (new version). 'hash -r' fixed that. I think the error
message was the same as yours.
> svscan: warning: unable to start supervise qmail-smtpd: file does not
> exist
> svscan: warning: unable to start supervise qmail-pop3d: file does not
> exist
>
> 2. The second question is that it doesn't write to the log file, all
> the message will be displayed at the console window.
> Take qmail as example:
> Here is the directory structure:
> [root@roadrunner qmail]# pwd
> /var/lock/qmailsvc/qmail
> [root@roadrunner qmail]# ls -la */*
> -rwxrwxr-x 1 qmaill nofiles 74 Sep 24 16:17 log/run
You need to chmod +t log
> prw------- 1 qmaill nofiles 0 Oct 6 17:03 supervise/control
>
> -rw------- 1 qmaill nofiles 0 Sep 24 16:19 supervise/lock
> prw------- 1 qmaill nofiles 0 Sep 24 16:19 supervise/ok
> -rw-r--r-- 1 root root 18 Oct 6 17:05 supervise/status
>
> log/supervise:
> total 3
> drwx------ 2 qmaill nofiles 1024 Sep 24 16:19 .
> drwxrwxr-x 3 qmaill nofiles 1024 Sep 24 17:34 ..
> prw------- 1 qmaill nofiles 0 Sep 24 16:11 control
> -rw------- 1 qmaill nofiles 0 Sep 24 16:11 lock
> prw------- 1 qmaill nofiles 0 Sep 24 16:11 ok
> -rw-r--r-- 1 qmaill nofiles 18 Sep 24 16:19 status
>
> [root@roadrunner qmail]# more run
> #! /bin/sh
> exec qmail-start "|dot-forward .forward
> ./Maildir/" tai64n qmail
You don't need to explicitly invoke tai64n. Just put 't' on the
multilog command line in log/run.
> [root@roadrunner qmail]# more log/run
> #! /bin/sh
> exec setuidgid qmaill multilog -s 1000000 -n 10 /var/log/qmail
>
> Can anyone give me a hint where I might have done wrong?
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 2304) 467101; fax: 943357
Apparently the FTP server I have been using to download qmail and
stuff is not up to date. The latest version of daemontools it
has is 0.53 and I'm reading of people using 0.61 and using programs
I don't have. So I'm wanting to get an up to date site.
The reason I was using FTP in the first place was so that I could
automate a mirror and be notified of new stuff. Downloading from
the web page manually has the disadvantage of not being automated
and the download links being scattered about (it would be better
if they were collected in one place). I'd rather use FTP or RSYNC
as that way I can readily detect changes.
--
Phil Howard
[EMAIL PROTECTED]
|
Hello,
please let me describe in detail what problems I
have working with qmail correctly. I have a database with about 20000 mail
adresses inside. To everyone of that adresses I wish to send the same mail (0,1
MB of size) using qmail. It is no problem to create such a mail and to inject it
to qmail´s queue by using qmail-inject and sending the mail on standard
input. It is easy to send single mails by that method. But with huge amounts of
data there occur a few problems that I cannot fix.
The easiest way to do that work would be to
generate 20000 emails and to inject them via qmail-inject. But this technique
has a few disadvantages: You fill up your harddisk with many, many copies of the
nearly same file. This seams to me as wasting resources. By the way you have the
problem that qmail´s queue gets filled up after only a few messages (about
1000) and you always get fatal errors by qmail-inject. I got the following
ones:
qmail-inject: fatal: qq trouble creating files
in queue (#4.3.0)
qmail-inject: fatal: envelope adress too long
for queue (#5.1.3)
I am sure to have enough disk space and no
quotas limiting it. There the problem can´t lie. The best way I could
imagine to do that job would be: You create your mail only ONCE. You send it to
qmail. You tell qmail that you want it delivering that mail to 20000 adresses.
Qmail should decide how to do that job. I think there are more efficient
algorhytms to send mails than one after another as mail servers have the ability
to deliver the same mail to many recipients which would enormally decrease
resource wasting. But how can I set up such a method???
Do I have to filter adresses that reside on the
same remote host or is that a abilty of qmail? How do I prevent queue from
becoming filled up? Is there any way to talk to qmail bedirectionally via a
technique similar to APIs (You call a function and get back detailed results,
for example - queue full, retry later or - even better - retry within xxx
seconds as qmail should know about its delivering speed and so
on...)?
Many thanks for your help
Volker Jung
|
Hi there,
i have [EMAIL PROTECTED]
This one is a POP-Account AND it forwards the Mail to an outside
adresse not handled by my server.
$cat .qmail-phreak
./users/chris/
&[EMAIL PROTECTED]
So, the [EMAIL PROTECTED] should go to [EMAIL PROTECTED],
so that this user handles everything. QMail now claims that it already
delivered this mail and bounces it.
How can i reach my goal without setting the same options for postmaster
as
for phreak?
Thanks a lot,
Thomas
