qmail Digest 24 Jul 1999 10:00:01 -0000 Issue 707
Topics (messages 28112 through 28165):
virtual domain?
28112 by: "Mark Grimshaw" <[EMAIL PROTECTED]>
28116 by: Dave Sill <[EMAIL PROTECTED]>
28132 by: <[EMAIL PROTECTED]>
28133 by: <[EMAIL PROTECTED]>
Forwarding
28113 by: Gustavo Rios <[EMAIL PROTECTED]>
Help!
28114 by: Dave Sill <[EMAIL PROTECTED]>
28134 by: Troy Morrison <[EMAIL PROTECTED]>
28135 by: Dave Sill <[EMAIL PROTECTED]>
Radius Authentication
28115 by: Paul Farber <[EMAIL PROTECTED]>
smtproutes - possible without DNS ?
28117 by: Dave Sill <[EMAIL PROTECTED]>
qmail delivers to wrong maildir
28118 by: Asmodeus <[EMAIL PROTECTED]>
28121 by: Peter Rye <[EMAIL PROTECTED]>
28126 by: Mark Weinem <[EMAIL PROTECTED]>
28127 by: Sergei Kolobov <[EMAIL PROTECTED]>
28151 by: Asmodeus <[EMAIL PROTECTED]>
28161 by: Mark Weinem <[EMAIL PROTECTED]>
28162 by: Mark Weinem <[EMAIL PROTECTED]>
something just ain't right.
28119 by: Dave Sill <[EMAIL PROTECTED]>
28160 by: Keith Burdis <[EMAIL PROTECTED]>
Spooling mail for ISDN Dialups
28120 by: Simon Woodward <[EMAIL PROTECTED]>
28129 by: Giles Lean <[EMAIL PROTECTED]>
smtp routing
28122 by: Dave Sill <[EMAIL PROTECTED]>
28124 by: "Pieckiel, Kevin A" <[EMAIL PROTECTED]>
28125 by: Dave Sill <[EMAIL PROTECTED]>
a really strange one (again)
28123 by: Robbie Walker <[EMAIL PROTECTED]>
man pages and rpm
28128 by: Mate Wierdl <[EMAIL PROTECTED]>
28131 by: "Sam" <[EMAIL PROTECTED]>
Testing - Please ignore
28130 by: Marthe Nes�en Gangfl�t <[EMAIL PROTECTED]>
Qmail dies over and over. (lost spawn connection)
28136 by: Gustavo Rios <[EMAIL PROTECTED]>
28137 by: Vince Vielhaber <[EMAIL PROTECTED]>
28138 by: Gustavo Rios <[EMAIL PROTECTED]>
28139 by: Mark Delany <[EMAIL PROTECTED]>
28140 by: Dave Sill <[EMAIL PROTECTED]>
28141 by: Gustavo V G C Rios <[EMAIL PROTECTED]>
28142 by: "Soffen, Matthew" <[EMAIL PROTECTED]>
28143 by: Gustavo V G C Rios <[EMAIL PROTECTED]>
28144 by: "Soffen, Matthew" <[EMAIL PROTECTED]>
28145 by: Dave Sill <[EMAIL PROTECTED]>
28146 by: Gustavo V G C Rios <[EMAIL PROTECTED]>
28147 by: Rogerio Brito <[EMAIL PROTECTED]>
28148 by: Mark Delany <[EMAIL PROTECTED]>
28149 by: Mark Delany <[EMAIL PROTECTED]>
28150 by: Robbie Walker <[EMAIL PROTECTED]>
28157 by: "Sam" <[EMAIL PROTECTED]>
28158 by: "Peter C. Norton" <[EMAIL PROTECTED]>
Qmail Maildirs with Cyrus IMAP 1.60 BETA
28152 by: "Stephan Hadan" <[EMAIL PROTECTED]>
28159 by: RaTao von J <[EMAIL PROTECTED]>
ezmlm question
28153 by: "Denis Voitenko" <[EMAIL PROTECTED]>
28154 by: Todd at NM Technet <[EMAIL PROTECTED]>
prepending token to subject line
28155 by: M Lyons <[EMAIL PROTECTED]>
qmail-inject: fatal: unable to exec qq (#4.3.0) - huh?
28156 by: "Rob Baham" <[EMAIL PROTECTED]>
Outgoing message and maildir
28163 by: Rahmat Ara Bithi <[EMAIL PROTECTED]>
28164 by: Anand Buddhdev <[EMAIL PROTECTED]>
question on Serialmail and ETRN (fwd)
28165 by: Goh Sek Chye <[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]
----------------------------------------------------------------------
Hi all,
(Searchable archive at www.qmail.org is down.)
I'm having a problem with using qmail to send email to addresses
external to our domain. I've been running qmail for about a year
now and never noticed this before because we simply used it to
send mail locally within our ISP domain - which it did fine. However,
I've just installed ezmlm and subscribed some external email address
to various lists. I now notice that I get messages in SYSLOG such
as:
qmail: 932734110.641249 delivery 2: deferral:
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
for every external email address (within our domain -
<name>@salford.ac.uk - everything is fine).
I've been told that I need to add a 'virtualdomains' file to
/var/qmail/control to list our SMTP server and to send all non-local
emails through that. Something like (I've been told):
:catchall
post.salford.ac.uk:
and that I must also recompile qmail after altering something in one
of the qmail source files. What this source file is and what I should
change I haven't a clue.
Any advice (will be much appreciated)?
*****************************************
Mark Grimshaw
Head of Music Technology & Studio Production
Salford University Music Department
http://www.salford.ac.uk/music
Degrees planned for September 2000:
BSc(Hons) Computer & Video Games (contact [EMAIL PROTECTED])
HNC/HND/PGCert/PGDip/MA/MPhil Music Industry Management (contact
[EMAIL PROTECTED])
WebAir Internet Radio - http://hexie.memtech.salford.ac.uk/music2/webair
[EMAIL PROTECTED] wrote:
>(Searchable archive at www.qmail.org is down.)
There are three search engines listed at:
http://Web.InfoAve.Net/~dsill/lwq.html#list-archives
>qmail: 932734110.641249 delivery 2: deferral:
>Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
>
>I've been told that I need to add a 'virtualdomains' file to
>/var/qmail/control to list our SMTP server and to send all non-local
>emails through that.
Does the system qmail is running on have unrestricted access to the
Internet? If so, it should be able to contact remote sites
directly. If not, you should use control/smtproutes. Something like:
.salford.ac.uk:
salford.ac.uk:
:post.salford.ac.uk
Which says "deliver mail to *@*salford.ac.uk directly, forward
everything else to post.salford.ac.uk".
-Dave
On Fri, 23 Jul 1999, Mark Grimshaw wrote:
> Hi all,
>
> (Searchable archive at www.qmail.org is down.)
>
> I'm having a problem with using qmail to send email to addresses
> external to our domain. I've been running qmail for about a year
> now and never noticed this before because we simply used it to
> send mail locally within our ISP domain - which it did fine. However,
> I've just installed ezmlm and subscribed some external email address
> to various lists. I now notice that I get messages in SYSLOG such
> as:
>
> Any advice (will be much appreciated)?
huh?
Mark, please ask [EMAIL PROTECTED] for advice, Salford runs qmail
on the main relay systems so they should be able to help quickly
In this case you've hit the firewall filters which prevent you from
sending mail ditrectly off-campus. to fix the problem do this:
echo ':post.salford.ac.uk' >/var/qmail/control/smtproutes
Richard Letts
(former Network Services Manager, University of Salford, on his way to a
new job in Austin Texas)
On Fri, 23 Jul 1999, Dave Sill wrote:
> Does the system qmail is running on have unrestricted access to the
> Internet? If so, it should be able to contact remote sites
> directly. If not, you should use control/smtproutes. Something like:
no, it doesn't there are firewall filters in place which block amongst
other things SMTP, SNMP, IRC and AOL IM.
>
> .salford.ac.uk:
> salford.ac.uk:
> :post.salford.ac.uk
>
> Which says "deliver mail to *@*salford.ac.uk directly, forward
> everything else to post.salford.ac.uk".
from my (inside) knowledge of the DNS all of the dns entries will say send
mail to post.salford.ac.uk as the lowest priority entry anyway, so i'd
avoid all DNS lookups and just send to post -- which is in reality three
systems so don't put the domain literal adderss of one of them in there
RjL
Put the mail you want your root messages sent to in
/var/qmail/alias/.qmail-root
--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.
On Fri, 23 Jul 1999, Maria Zevenhoven wrote:
> all my mail accounts except for root are working fine... but root:
>
> I have a system, where all admins should get all mails sent to root. the
> mail for root is as default stored in /root/Mailbox, but I have there a
> .qmail, with the following information:
>
> --- start ---
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> ---end---
>
> but this just causes the mail to disappear: it doesn't find it's way to
> Mailbox but also not in the mailadresses specified in .qmail. I have not
> used .qmail elsewhere, so I can't be sure that it would work there, at least
> here it doesn't...
>
> -Maria
>
>
"Marc-Adrian Napoli" <[EMAIL PROTECTED]> wrote:
>
>I've been asked if we support "ERTN".
That's ETRN.
>Reading around... it looks like I have to have serialmail installed to
>support it.
Serialmail support AutoTURN, which does the same thing as ETRN, but
doesn't require the client to send an SMTP ETRN command.
>1. How do I find out if I have serialmail installed?
find / -name maildir2smtp -print
If it it finds it, you've probably got serialmail.
>2. If I do have serialmail installed, what is the difference between ERTN
>and people just dialing in and collecting their mail normally?
People don't dial into SMTP servers to collect mail. SMTP is a "push"
protocol, not a "pull". The ETRN command gives the SMTP server a
nudge, causing it to push messages queued to host that issued the
command, but it doesn't do it through that connection. AutoTURN gives
the SMTP server the nudge when the client system connects to port
25. It doesn't need the client to issue an ETRN command.
(The "pull" mail protocols are POP3 and IMAP.)
-Dave
> Serialmail support AutoTURN, which does the same thing as ETRN, but
> doesn't require the client to send an SMTP ETRN command.
Dave,
Just asking for clarification; does this mean that qmail does not support
ETRN, ever? (I realize it offers nearly identical functionality, so the
question is sort of academic.)
Troy
Troy Morrison <[EMAIL PROTECTED]> wrote:
>
>> Serialmail support AutoTURN, which does the same thing as ETRN, but
>> doesn't require the client to send an SMTP ETRN command.
>
>Just asking for clarification; does this mean that qmail does not support
>ETRN, ever? (I realize it offers nearly identical functionality, so the
>question is sort of academic.)
There's a patch available from www.qmail.org, I think.
-Dave
Yea, I used to use it but didn't want to pony up the money for the
simeltaneous-Use attribute feature.
If it's JUST the test server is then make sure you have the same radius
secret key on both machines.
Also, what does the log file say? Is it logging an authentication
failure? A hex dump may indicate a malformed authentication request.
Paul D. Farber II
Farber Technology
Ph. 570-628-5303
Fax 570-628-5545
[EMAIL PROTECTED]
On Thu, 22 Jul 1999, Gary Stewart wrote:
> Paul,
> Well the radius (Merit Radius) has been in production for quite some time
> now for all of our dialup authentications, and watching the logfile
> everything else comes through.. just the request from my test server gives
> me that error when trying to authenticate pop3. Do you think it may have
> something do do with the "type" parameter in the clients file maybe?
>
> Regards,
> Gary Stewart
>
>
> -----Original Message-----
> From: Paul Farber [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 22, 1999 4:44 PM
> To: Gary Stewart
> Cc: Qmail List
> Subject: Re: Radius Authentication
>
>
> I used to get that kind of dump from cistron radiusd when my old Netserver
> card would try and authenticate a user.... came down to the radius daemon
> was not set up correctly.
>
> Recheck the setup.
>
> Can you run radtest and get a failure? That would give you an idea if it
> was a radius or perl or network problem.
>
>
>
"Olivier M." <[EMAIL PROTECTED]> wrote:
>
>HOST1 = SCO Unix with qmail and a few scripts that are sending
> emails to the realworld via a relay. No dns access, subnet.
>IP = 192.168.0.50
>In /var/qmail/control/smtproutes, I have :
>:[192.168.0.10]
>
>HOST2 = linux server, with normal qmail configuration, allowing
> relaying for 192.*. World acces. Should act as relay.
>IP = 192.168.0.10
>
>Now, when I try to send a mail to [EMAIL PROTECTED] from the Host1, I get this
>in syslog :
>
>Jul 21 21:38:50 qmail qmail: 932593130.640000 new msg 50584
>Jul 21 21:38:50 qmail qmail: 932593130.640000 info msg 50584: bytes 265 from
><[EMAIL PROTECTED]> qp 840 uid 0
>Jul 21 21:38:50 qmail qmail: 932593130.840000 starting delivery 13: msg 50584 to
>remote [EMAIL PROTECTED]
It's not using your smtproutes file. Check the spelling and
permissions. If you still don't see a problem, try running
qmail-remote under your system call tracing tool
(trace/truss/strace/par/etc.)
>There is a connexion made to the relay, because in the log of Host2,I see :
>
>Jul 21 23:39:05 webima smtpd: 932593145.632655 tcpserver: status: 13/40
>Jul 21 23:39:05 webima smtpd: 932593145.640848 tcpserver: pid 3890 from 192.168.0.90
192.168.0.90 isn't HOST1, is it?
-Dave
On Fri, 23 Jul 1999, Weinem wrote:
> Is the delivery instruction "alias-ppp-mark@localhost" really correct?
In my (albeit limited) experience, it is syntactically incorrect.
Okay, from the filename /var/qmail/alias/.qmail-ppp-mark it seems that
you have a virtualdomain setup which is handled through 'ppp'. Ie: in
/var/qmail/control/virtualdomains, you have a line such as:
myvirtualdomain:ppp and you don't have a real (/etc/passwd) user named
ppp... Correct?
If so, mail to mark@myvirtualdomain should be handled by the above file
in /var/qmail/alias.
> I have changed this, it's .qmail-ppp-mark (with /home/mark/Maildir/ in
side) now.
> The new situation: no Mails in /var/qmail/alias/pppdir and no mails in
> /home/mark/Maildir. Must be still something wrong
What shows up in your mail logs?
I think you might have to show the contents of your config files and a
`ls -la` of /var/qmail/alias/ ... I, for one, can't see any reason why it
wouldn't work with the info you've given so far, assuming the config is
correct.
.Shawn
On Fri, Jul 23, 1999 at 01:47:10AM +0200, Mark Weinem wrote:
> Asmodeus wrote:
>
> > > > Why does it try to deliver to alias-ppp-mark@localhost and not to
> > > > mark@localhost or [EMAIL PROTECTED] (pandora.plagegeister.de is my
> > > > hostname)?
>
> Is the delivery instruction "to local alias-ppp-mark@localhost" really
> correct? Is this different from qmail 1.01?
>
>
> > > umm, it is probably because you have the format for the file wrong. I believe
> > > it is supposed to be .qmail-ppp-mark and in side the file you put a list of
> > > addresses/directives.
> >
> > Oh man, am I blind today... Sorry for the completely useless post, but
> > yes, removing the @localhost part of that filename will probably fix it.
> > Check the permissions as well. It should be owned by alias.
>
> I have changed this, it's .qmail-ppp-mark (with /home/mark/Maildir in
> side).
> But now: no mail in /var/qmail/alias/ppdir and no mail in
> /home/mark/Maildir.
> Must be still something wrong
I believe this is a fetchmail problem.
Try adding the smtpaddress option to your .fetchmailrc: something like
smtpaddress pandora.plagegeister.de should do the trick.
Asmodeus wrote:
> > Is the delivery instruction "alias-ppp-mark@localhost" really correct?
>
> In my (albeit limited) experience, it is syntactically incorrect.
>
> Okay, from the filename /var/qmail/alias/.qmail-ppp-mark
> it seems that you have a virtualdomain setup which is handled through
> 'ppp'. Ie: in /var/qmail/control/virtualdomains, you have a line such as:
> myvirtualdomain:ppp
> and you don't have a real (/etc/passwd) user named ppp... Correct?
Correct.
> If so, mail to mark@myvirtualdomain should be handled by the above file
> in /var/qmail/alias.
>
> What shows up in your mail logs?
>
> I think you might have to show the contents of your config files
> and a `ls -la` of /var/qmail/alias/ ... I, for one, can't see any reason
> why it wouldn't work with the info you've given so far, assuming the
> config is correct.
Here are the infos & files:
# ls -al /var/qmail/alias
total 7
drwxr-sr-x 3 alias qmail 1024 Jul 22 23:58 .
drwxr-xr-x 10 root qmail 1024 Jul 21 00:15 ..
-rw------- 1 alias qmail 260 Jul 22 23:59 .bash_history
-rw-r--r-- 1 root qmail 0 Jul 21 00:57
.qmail-mailer-daemon
-rw-r--r-- 1 root qmail 0 Jul 21 00:57 .qmail-postmaster
-rw-r--r-- 1 alias qmail 10 Jul 22 00:05
.qmail-ppp-default
-rw-r--r-- 1 alias qmail 20 Jul 22 18:59 .qmail-ppp-mark
-rw-r--r-- 1 root qmail 20 Jul 22 19:20 .qmail-root
drwx--S--- 5 alias qmail 1024 Jul 22 00:00 pppdir
# ls -al /var/qmail/
total 11
drwxr-xr-x 10 root qmail 1024 Jul 21 00:15 .
drwxr-xr-x 17 root root 1024 Jul 21 00:39 ..
drwxr-sr-x 3 alias qmail 1024 Jul 22 23:58 alias
drwxr-xr-x 2 root qmail 1024 Jul 21 00:36 bin
drwxr-xr-x 2 root qmail 1024 Jul 20 23:51 boot
drwxr-xr-x 2 root qmail 1024 Jul 22 02:55 control
drwxr-xr-x 2 root qmail 1024 Jul 20 23:51 doc
drwxr-xr-x 10 root qmail 1024 Jul 22 01:38 man
drwxr-x--- 11 qmailq qmail 1024 Jul 20 23:51 queue
-rwxr-xr-x 1 root qmail 205 Jul 21 00:22 rc
drwxr-xr-x 2 root qmail 1024 Jul 20 23:51 users
#ls -al /home/mark
-----
-rw-rw---- 1 mark mark 11 Jul 22 00:53 .qmail
drwxrwsr-x 11 mark mark 1024 Jul 21 04:17 Mail
drwx--S--- 5 mark mark 1024 Jul 21 01:31 Maildir
-----
/home/mark/.qmail:
-----
./Maildir/
-----
/var/qmail/alias/.alias-ppp-default:
-----
./pppdir/
-----
/var/qmail/alias/.qmail-ppp-mark:
-----
/home/mark/Maildir/
-----
/var/qmail/control/virtualdomains:
-----
:alias-ppp
-----
/var/log/mail.info:
-----
[configuration without /var/qmail/alias/.qmail-ppp-mark]:
Jul 22 16:04:26 pandora qmail: 932652266.748901 new msg 6253
Jul 22 16:04:26 pandora qmail: 932652266.749180 info msg 6253:
bytes 2905 from <[EMAIL PROTECTED]> qp 301 uid 1002
Jul 22 16:04:26 pandora qmail: 932652266.751958 starting delivery 26:
msg 6253 to local alias-ppp-mark@localhost
Jul 22 16:04:26 pandora qmail: 932652266.752170 status: local 1/10
remote 0/20
Jul 22 16:04:26 pandora qmail: 932652266.774033 delivery 26: success:
did_1+0+0/
Jul 22 16:04:26 pandora qmail: 932652266.774267 status: local 0/10
remote 0/20
Jul 22 16:04:26 pandora qmail: 932652266.774385 end msg 6253
Jul 22 16:04:27 pandora qmail: 932652267.787610 new msg 6253
Jul 22 16:04:27 pandora qmail: 932652267.787875 info msg 6253:
bytes 2912 from <[EMAIL PROTECTED]> qp 305 uid 1002
Jul 22 16:04:27 pandora qmail: 932652267.790627 starting delivery 27:
msg 6253 to local alias-ppp-mark@localhost
Jul 22 16:04:27 pandora qmail: 932652267.790820 status: local 1/10
remote 0/20
Jul 22 16:04:27 pandora qmail: 932652267.812740 delivery 27: success:
did_1+0+0/
Jul 22 16:04:27 pandora qmail: 932652267.812986 status: local 0/10
remote 0/20
Jul 22 16:04:27 pandora qmail: 932652267.813103 end msg 6253
[configuration with /var/qmail/alias/.qmail-ppp-mark]:
Jul 23 00:01:56 pandora qmail: 932680916.376903 new msg 6258
Jul 23 00:01:56 pandora qmail: 932680916.377163 info msg 6258:
bytes 3190 from <[EMAIL PROTECTED]> qp 228 uid 1002
Jul 23 00:01:56 pandora qmail: 932680916.380845 starting delivery 3:
msg 6258 to local alias-ppp-mark@localhost
Jul 23 00:01:56 pandora qmail: 932680916.381038 status: local 1/10
remote 0/20
Jul 23 00:01:56 pandora qmail: 932680916.400320 delivery 3:
deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
Jul 23 00:01:56 pandora qmail: 932680916.400561 status: local 0/10
remote 0/20
-----
Ciao,
Mark
Mark Weinem wrote:
> /var/qmail/alias/.qmail-ppp-mark:
> -----
> /home/mark/Maildir/
> -----
Won't work - replace it with "mark" - that should fix it.
sgk
On Fri, 23 Jul 1999, Mark Weinem wrote:
<Big snip>
> [configuration with /var/qmail/alias/.qmail-ppp-mark]:
>
> Jul 23 00:01:56 pandora qmail: 932680916.376903 new msg 6258
> Jul 23 00:01:56 pandora qmail: 932680916.377163 info msg 6258:
> bytes 3190 from <[EMAIL PROTECTED]> qp 228 uid 1002
> Jul 23 00:01:56 pandora qmail: 932680916.380845 starting delivery 3:
> msg 6258 to local alias-ppp-mark@localhost
> Jul 23 00:01:56 pandora qmail: 932680916.381038 status: local 1/10
> remote 0/20
> Jul 23 00:01:56 pandora qmail: 932680916.400320 delivery 3:
> deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
> Jul 23 00:01:56 pandora qmail: 932680916.400561 status: local 0/10
> remote 0/20
> -----
Ah. Its being handled by the user 'alias' who has no read/write
permission to Mark's maildir (~mark/Maildir)
Replace the contents of /var/qmail/alias/.qmail-ppp-mark with:
&mark@<the domain you have in /var/qmail/control/locals>
(replacing everything after the at symbol with a domain you have in
/var/qmail/control/locals)
Since qmail checks for a local domain before a virtualdomain, you won't
put it into a mail loop.
.Shawn
Hope this finally fixes it...
Sergei Kolobov wrote:
>
> Mark Weinem wrote:
> > /var/qmail/alias/.qmail-ppp-mark:
> > -----
> > /home/mark/Maildir/
> > -----
>
> Won't work - replace it with "mark" - that should fix it.
It works now,
thanks a lot!
Mark Weinem
Peter Rye wrote:
> I believe this is a fetchmail problem.
> Try adding the smtpaddress option to your .fetchmailrc: something like
> smtpaddress pandora.plagegeister.de should do the trick.
Yes, it does the trick :-)
Thanks a lot!
Mark
<[EMAIL PROTECTED]> wrote:
>
>So any other suggestions on what I can do to speed this thing up or should
>I just go back to sendmail?
No, don't go back to sendmail*. At least try Postfix first.
Whether or not you should give up on qmail depends upon how hard
you're willing to work on figuring out what the problem is.
>Another hint is that I'm using the Bruce Guentner rpm's. Is there
>something with those rpm's that would cause a slow down?
With all due respect and credit to the RPM producers, I really think
you're better off blowing everything qmail-related away and installing
from the tarball using the directions in "Life with qmail":
http://Web.InfoAve.Net/~dsill/lwq.html#installation
-Dave
*: sounds like a Weird Al parody based on an REM tune. :-)
On Wed 1999-07-21 (12:09), [EMAIL PROTECTED] wrote:
>
> I'm still having very poor performance with that mail list. Can someone
> please explain to me why qmail doesn't fill the concurrent qmail remote
> processes? I'm sitting here with 150,000 mails in the queue and
> concurrent remote's are like a 3/75 or 4/75.
>
> Also, can someone explain the preprocessed stage? This is my qmail-qstat:
>
> messages in queue: 157489
> messages in queue but not yet preprocessed: 121433
>
> I need to start pumping this mail out fast.
Sounds like you could benefit from using Russ Nelson's big-todo patch.
See:
http://www.qmail.org/big-todo.103.patch
According to Russ:
conf-split needs to be bigger if you have more than 23K distinct
messages (not addresses) in the queue. big-todo is needed if you're
injecting messages faster than qmail-send can process them.
Looks like you fall into both categories. As Dave Sill suggested, you'd
probably be better off building qmail from source using his instructions at:
http://Web.InfoAve.Net/~dsill/lwq.html#installation
Just before doing "2.5.5. Do the build" apply Russ' patch and edit conf-split
changing 23 to 231.
I'd suggest only using rpms once you're comfortable with how qmail works, and
you understand what the rpm author has done is his (or her I suppose :) SPEC
file.
> -jeremy
- Keith
PS: Russ, please add the "According to Russ:..." as a tip :)
--
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.
---
Hi,
I have been using qmail for a while and generally have few problems, however
our main mailserver still runs sendmail and I have been made responsible for
investigating replacing it with qmail. Most of the crossover I can handle,
expet for one part:
We have many customers who have an ISDN lan connection, where every now and
then their ISDN machine will connect and grab its mail from a mail spool.
Basically we have sendmail configured so *anything*@blah.com is accepted by our
mail server and spooled, it then sits and waits for post.blah.com to dialup and
connect and it then gets all its mail.
How can I get qmail to emulate this kind of set up ?
any ideas will be appreciated.
Simon Woodward.
---
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Simon Woodward - Network Engineer |
| Onyx Internet Ltd. Tel: +44 (0) 1642 216200 |
| Zetland Buildings, Fax: +44 (0) 1642 216201 |
| Exchange Square, E-mail: [EMAIL PROTECTED] |
| Middlesbrough, TS1 1DE URL: http://www.onyx.net/ |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
Diplomacy is about surviving until the next century.
Politics is about surviving until Friday afternoon.
-- Sir Humphrey Appleby
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
On Fri, 23 Jul 1999 14:10:48 +0100 (BST) Simon Woodward wrote:
> We have many customers who have an ISDN lan connection, where every now and
> then their ISDN machine will connect and grab its mail from a mail spool.
> Basically we have sendmail configured so *anything*@blah.com is accepted by our
> mail server and spooled, it then sits and waits for post.blah.com to dialup and
> connect and it then gets all its mail.
serialmail -- FAQ #2.4, http://pobox.com/~djb/serialmail.html.
Regards,
Giles
"Pieckiel, Kevin A" <[EMAIL PROTECTED]> wrote:
>
>I can't seem to figure out how to get my mail routing exactly as I want
>it. I have 50 or so computers at mysite.org. We are behind a firewall
>with a dedicated link to our HQ in another city. All mail generated by
>computers at mysite.org are routed through my mail server
>mail.mysite.org. If generated mail is not local (not to a mysite.org
>address or machine.mysite.org address where machine is any machine
>name), I want to route it through mailhost.hq.net. This can be done by
>adding :mailhost.hq.net in smtproutes.
>
>Here's where I have trouble:
>I want mail addressed to pc1.mysite.org, pc2.mysite.org, and
>pc3.mysite.org to be routed to those machines (they have qmail
>installed). Mail to ANY OTHER MACHINE at mysite.org should be delivered
>locally to mail.mysite.org no matter what the machine name is, even if
>that machine doesn't exist. Of course, a valid user must be specified
>or the mail will bounce, but that's not relevent to my question. How
>can I set this up? ll mail to any machine at mysite.org should be
>delievered to mail.mysite.org unless it's sent to pc1.mysite.org,
>pc2.mysite.org, or pc3.mysite.org, in which case mail is then routed to
>those machines.
Let's see if I've got this straight. You've got:
mail.mysite.org (your qmail box)
mailhost.hq.net (the relay to the rest of the world)
pcN.mysite.org (systems with local mail users)
And you want mail routed like this:
[EMAIL PROTECTED] -> remote to "user" on pcN.mysite.org
[EMAIL PROTECTED] -> local "user" on mailhost.hq.net
user@*.mysite.org -> local "user" on mailhost.hq.net
user@anywhere_else -> relay through mailhost.hq.net
OK, in control/smtproutes:
pc1.mysite.org:
pc2.mysite.org:
pc3.mysite.org:
:mailhost.hq.net
In control/locals:
mail.mysite.org
mysite.org
foo.mysite.org
bar.mysite.org (e.g., all the mysite.org hosts you want to
handle locally)
In control/rcphosts:
pc1.mysite.org
pc2.mysite.org
pc3.mysite.org
(plus contents of control/locals)
Then restart qmail and test.
-Dave
That's exactly what I want! I was hoping there was a way to avoid
adding all my client computers in control/locals that I wanted to have
delivered locally. If a machine name changes, this will be just one
more thing to keep up, but I suppose I can live with that. It goes by
DNS name, I presume? No matter what they call their computer in network
neighborhood, qmail will still see the DNS name?
Thanks for your reply!
Kevin
-----Original Message-----
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 23, 1999 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: smtp routing
Let's see if I've got this straight. You've got:
mail.mysite.org (your qmail box)
mailhost.hq.net (the relay to the rest of the world)
pcN.mysite.org (systems with local mail users)
And you want mail routed like this:
[EMAIL PROTECTED] -> remote to "user" on pcN.mysite.org
[EMAIL PROTECTED] -> local "user" on mailhost.hq.net
user@*.mysite.org -> local "user" on mailhost.hq.net
user@anywhere_else -> relay through mailhost.hq.net
OK, in control/smtproutes:
pc1.mysite.org:
pc2.mysite.org:
pc3.mysite.org:
:mailhost.hq.net
In control/locals:
mail.mysite.org
mysite.org
foo.mysite.org
bar.mysite.org (e.g., all the mysite.org hosts you want to
handle locally)
In control/rcphosts:
pc1.mysite.org
pc2.mysite.org
pc3.mysite.org
(plus contents of control/locals)
Then restart qmail and test.
-Dave
"Pieckiel, Kevin A" <[EMAIL PROTECTED]> wrote:
>That's exactly what I want! I was hoping there was a way to avoid
>adding all my client computers in control/locals that I wanted to have
>delivered locally. If a machine name changes, this will be just one
>more thing to keep up, but I suppose I can live with that.
Yes, it's unavoidable.
>It goes by DNS name, I presume? No matter what they call their
>computer in network neighborhood, qmail will still see the DNS name?
Right.
>Thanks for your reply!
No problem. Glad to help.
-Dave
Use tcpserver instead of inetd.
In fact, you can get tcpserver to log EVERY line of all SMTP connections if you
want.
ftp://koobera.math.uic.edu/www/ucspi-tcp.html
You should also see Dave Sill's excellent Life With Qmail and consider using
his installation procedure, I found it worthwhile enough to re-install qmail
using his procedure.
http://Web.InfoAve.Net/~dsill/lwq.html
At 04:39 AM 7/23/99 , you wrote:
>
> Hi
>
> Our Qmail 1.03 box is having problems getting mail from one particular site
> and I've been told to try and sort it out. When mail comes in from this site,
> I can watch the connection using netstat. The connection from their MX goes
> from ESTABLISHED straight to CLOSE as if the connection is getting broken. As
> qmail-smtpd doesn't provide log info I had to get a copy of their NTMail log
> file. It shows the following for most deliveries to our site.
>
> waiting 10038 mailhost.oursite.com
> (hmmmm.....10038. Winsock error?????)
>
> eventually mail is sent back to the sender undelivered. I'm 99% sure it's
> something at their end but in the interest of workplace harmony it'd be nice
> to get to the bottom of it.
>
> Any help appreciated
>
> Simon Rae
______________________
NovaMetrix Development
Robbie Walker, AMWL
P.O. Box 635 or 910-653-4006
106-B S. Main St 800-773-5647
Tabor City, NC 28463 910-653-2052 FAX
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.5.2
iQA/AwUBN5hvqTrJV5JQYcnnEQLxXgCgg0mT9jXOiv8eLX13NAMt8ltuD00AnR2l
+heO4UTwT7CMQvZYSB/BjI+X
=HMIG
-----END PGP SIGNATURE-----
Just a warning to rpm makers: at least under RH 6.0, the stuff in the
cat directories get gzipped, and then ordinary users cannot view those
man pages anymore. I do not really know what the heck is going on:
$ man qmail-command
rm: remove write-protected file `/var/qmail/man/cat8/qmail-command.8.gz'?
Formatting page, please wait...
sh: /var/qmail/man/cat8/qmail-command.8.gz: Permission denied
Error executing formatting or display command.
System command (cd /var/qmail/man ; (echo -e ".pl 1100i"; /bin/cat
/var/qmail/man/man8/qmail-command.8; echo ".pl \n(nlu+10") | /usr/bin/gtbl |
/usr/bin/groff -Tascii -mandoc | /bin/gzip > /var/qmail/man/cat8/qmail-command.8.gz)
exited with status 1.
rm: remove write-protected file `/var/qmail/man/cat8/qmail-command.8.gz'?
gunzip: /var/qmail/man/cat8/qmail-command.8.gz: unexpected end of file
The upshot is that the formatted man pages I think should not be
installed. (I think David S. and Sam already makes sure of this).
Mate
Mate Wierdl writes:
> Just a warning to rpm makers: at least under RH 6.0, the stuff in the
> cat directories get gzipped, and then ordinary users cannot view those
> man pages anymore. I do not really know what the heck is going on:
>
> $ man qmail-command
-rwxr-sr-x 1 root man 32320 Apr 9 19:26 /usr/bin/man
man expects stuff in cat to be writeable by the man group.
My RPMs only installs the nroff source. Formatted man pages are a waste of
space.
I also gzip nroff source whenever possible. Qmail is already messy enough,
so I don't bother in this case.
--
Sam
I am sorry that this topic is lasting so long, but my qmail dies and dies.
I AM GETTING CRAZY!
My qmail server dies all the time, the messages is:
lost spwan connection:..... exited .......
Someone pointed me about problems related to bad quality hardware.
It cannot be, once i already build my hole FreeBSD, from scratch and
nothing happens, and remenber making world it not a light proccess.
I have already done it more than once.
So, here goes some configurations i am running:
My uname output.
vitoria:/tmp# uname -a
FreeBSD vitoria.ddsecurity.com.br 3.2-STABLE FreeBSD 3.2-STABLE #1: Thu
Jul 15 13:52:22 EST 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/VITORIA i386
The login capabilities to which qmail/nofiles users belongs to.
vitoria:/tmp# limits -C default
Resource limits for class default:
cputime infinity secs
filesize infinity kb
datasize infinity kb
stacksize infinity kb
coredumpsize infinity kb
memoryuse infinity kb
memorylocked infinity kb
maxprocesses infinity
openfiles infinity
My kernel parameters:
vitoria:/tmp# sysctl -a | grep proc
kern.maxproc: 820
kern.maxfilesperproc: 1640
kern.maxprocperuid: 819
vfs.aio.max_aio_per_proc: 32
vfs.aio.max_aio_queue_per_proc: 256
vfs.aio.max_aio_procs: 32
vfs.aio.num_aio_procs: 0
vfs.aio.target_aio_procs: 0
hw.model: AMD-K6(tm) 3D processor
vitoria:/tmp# sysctl -a | grep file
kern.maxfiles: 1640
kern.bootfile: /kernel
kern.maxfilesperproc: 1640
kern.corefile: /dev/null
p1003_1b.mapped_files: 0
I see nothing wrong about such a configurations scenario.
Please, is there any qmail wizard here to help me.
I really need such a help, my users are getting nervous.
--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.
On 23-Jul-99 Gustavo Rios wrote:
> I am sorry that this topic is lasting so long, but my qmail dies and dies.
> I AM GETTING CRAZY!
>
> My qmail server dies all the time, the messages is:
> lost spwan connection:..... exited .......
>
> Someone pointed me about problems related to bad quality hardware.
> It cannot be, once i already build my hole FreeBSD, from scratch and
> nothing happens, and remenber making world it not a light proccess.
> I have already done it more than once.
I missed most of this so forgive me if I'm asking something you already
answered. Also it may not be till Sunday nite that I can answer you.
Since you successfully did a build world, for now I think we can rule
out a hardware problem. With perhaps the exception of disk, disk space,
or memory - I didn't see how much memory you have in the machine, may have
missed it.
Just to make sure, build world didn't fail at all, did it?
Next, where did your qmail come from? Did you get it from koobera and
install it as in Dave's Life With qmail or did you use a port/package?
After the build world, did you reinstall qmail? The same way as above?
Ok, to get ahead since I'll be away for a couple of days. Go to koobera
and get a fresh tarball and install it just like it says in LWQ:
http://Web.InfoAve.Net/~dsill/lwq.html
No port. No package. No RPM. Just from the tarball from koobera to
its being built and installed. Let me know what you get then.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Ok, here goes additional information.
On Fri, 23 Jul 1999, Vince Vielhaber wrote:
> Since you successfully did a build world, for now I think we can rule
> out a hardware problem. With perhaps the exception of disk, disk space,
> or memory - I didn't see how much memory you have in the machine, may have
> missed it.
192 MBytes RAM
384 Mbytes swap
> Just to make sure, build world didn't fail at all, did it?
No, no problem making world. No error at all.
Everything was a paradise, of course, since i decide to install qmail.
> Next, where did your qmail come from? Did you get it from koobera and
> install it as in Dave's Life With qmail or did you use a port/package?
Yeah, from Dave site.
> After the build world, did you reinstall qmail? The same way as above?
I build the world many times, after my system were ready, i installed
qmail, and other daemons too. Nothing wrong with my ftpd,telnetd httpd,
etc.... only qmail is the problem now.
> Ok, to get ahead since I'll be away for a couple of days. Go to koobera
> and get a fresh tarball and install it just like it says in LWQ:
>
> http://Web.InfoAve.Net/~dsill/lwq.html
>
thanks a lot for your time and cooperation.
At 03:09 PM Friday 7/23/99, Gustavo Rios wrote:
>I am sorry that this topic is lasting so long, but my qmail dies and dies.
>I AM GETTING CRAZY!
>
>My qmail server dies all the time, the messages is:
>lost spwan connection:..... exited .......
Right. Well you need to collect a few more facts then (and I may have
missed some earlier).
Such as:
1. Is there any pattern to this occuring? Time that qmail is up, number of
mails delivered? Time the OS has been up?
2. Does it change if you alter concurrency settings?
3. Are you starting qmail from your bootup scripts (rc, etc) or are you
starting it from a root shell?
4. Are lots of other things running on that system?
5. If so, does qmail stay up longer if they are not started?
6. When you quote messages, especially from logs, can you cut and paste
rather than paraphrase?
7. Can you show the list the log entries which preceed the "lost spawn"
message? Any correlation there? Eg, is it always the start of a remote
delivery that causes the lost spawn? Have you hit some common concurrency
number?
8. Are there any correlating entries in other syslog files?
Regards.
Gustavo Rios <[EMAIL PROTECTED]> wrote:
>My qmail server dies all the time, the messages is:
>lost spwan connection:..... exited .......
This usually means qmail-lspawn or qmail-rspawn has died. These
processes are exceedingly reliable, so if one of them has gone away,
it probably means something like:
o some idiot killed it
o the OS killed it because it ran out of memory
o some OS/library bug caused it to crash
You could try replacing qmail-rspawn and qmail-lspawn with wrappers
that run the real binaries under trace/strace/truss/par, or you can
attach to the running processes with a debugger.
One obvious question to ask, assuming this problem cropped up after a
period of normal operation, is "what had I changed around the time it
broke?"
-Dave
Mark Delany wrote:
>
> At 03:09 PM Friday 7/23/99, Gustavo Rios wrote:
> >I am sorry that this topic is lasting so long, but my qmail dies and dies.
> >I AM GETTING CRAZY!
> >
> >My qmail server dies all the time, the messages is:
> >lost spwan connection:..... exited .......
>
> Right. Well you need to collect a few more facts then (and I may have
> missed some earlier).
>
> Such as:
>
> 1. Is there any pattern to this occuring? Time that qmail is up, number of
> mails delivered? Time the OS has been up?
No pattern
Qmail does not get up more than 24 hours.
It already crashed more than 6 times a day.
my uptime:
4:00PM up 6 days, 21:18, 2 users, load averages: 0.19, 0.09, 0.03
> 2. Does it change if you alter concurrency settings?
I never changed concurrency settings.
Is it necessary ?
> 3. Are you starting qmail from your bootup scripts (rc, etc) or are you
> starting it from a root shell?
i start it from a root shell, here goes what i do to start it:
# export PATH=/var/qmail/bin:$PATH <enter>
# qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
> 4. Are lots of other things running on that system?
No, the system is by far idled.
> 5. If so, does qmail stay up longer if they are not started?
>
> 6. When you quote messages, especially from logs, can you cut and paste
> rather than paraphrase?
> 7. Can you show the list the log entries which preceed the "lost spawn"
> message? Any correlation there? Eg, is it always the start of a remote
> delivery that causes the lost spawn? Have you hit some common concurrency
> number?
vitoria:/var/log/qmail# tail -f @00000932675556
932677316.686885 end msg 276627
932677316.687905 new msg 276628
932677316.687915 info msg 276628: bytes 1432 from <> qp 39693 uid 408
932677316.708270 starting delivery 17: msg 276628 to remote
[EMAIL PROTECTED]
932677316.708629 status: local 0/10 remote 1/20
932677317.048603 delivery 17: success:
200.19.130.117_accepted_message./Remote_host_said:_250_SAA11788_Message_accepted_for_delivery/
932677317.049745 status: local 0/10 remote 0/20
932677317.049759 end msg 276628
932677410.051808 alert: oh no! lost spawn connection! dying...
932677410.054789 status: exiting
> 8. Are there any correlating entries in other syslog files?
>
> Regards.
Umm.. doesn't qmail HAVE to be started using CSH per the readme files
?
Doesn't sh have problems running it ?
> -----Original Message-----
> From: Gustavo V G C Rios [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 23, 1999 2:57 PM
> To: Mark Delany
> Cc: [EMAIL PROTECTED]
> Subject: Re: Qmail dies over and over. (lost spawn connection)
>
[snip]
> > 3. Are you starting qmail from your bootup scripts (rc, etc) or are
> you
> > starting it from a root shell?
>
> i start it from a root shell, here goes what i do to start it:
> # export PATH=/var/qmail/bin:$PATH <enter>
> # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
>
[snip]
"Soffen, Matthew" wrote:
>
> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
I dont realy know, once if you decide to start it at boot time, it will
be started using sh!
> > > 3. Are you starting qmail from your bootup scripts (rc, etc) or are
> > you
> > > starting it from a root shell?
> >
> > i start it from a root shell, here goes what i do to start it:
> > # export PATH=/var/qmail/bin:$PATH <enter>
> > # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
> >
> [snip]
>
My root (toor user) shell is BASH!!!!
>From the INSTALL file
8. Copy /var/qmail/boot/home (or proc) to /var/qmail/rc.
9. Enable deliveries of messages injected into qmail:
# csh -cf '/var/qmail/rc &'
[snip]
14. Add
csh -cf '/var/qmail/rc &'
to your boot scripts, so that the qmail daemons are restarted
whenever your system reboots. Make sure you include the &.
You may just wish to try this. See what happens.
> -----Original Message-----
> From: Gustavo V G C Rios [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 23, 1999 3:10 PM
> To: Soffen, Matthew
> Cc: Mark Delany; [EMAIL PROTECTED]
> Subject: Re: Qmail dies over and over. (lost spawn connection)
>
> "Soffen, Matthew" wrote:
> >
> > Umm.. doesn't qmail HAVE to be started using CSH per the readme
> files
>
> I dont realy know, once if you decide to start it at boot time, it
> will
> be started using sh!
>
> > > > 3. Are you starting qmail from your bootup scripts (rc, etc) or
> are
> > > you
> > > > starting it from a root shell?
> > >
> > > i start it from a root shell, here goes what i do to start it:
> > > # export PATH=/var/qmail/bin:$PATH <enter>
> > > # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail'
> &
> > >
> > [snip]
> >
>
> My root (toor user) shell is BASH!!!!
Gustavo V G C Rios <[EMAIL PROTECTED]> wrote:
>"Soffen, Matthew" wrote:
>>
>> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
That's the recommendation, but all that's necessary is disassociating
the child processes from the parent's tty. Csh and bash do that
automatically. Nohup can be used to force that, too.
>I dont realy know, once if you decide to start it at boot time, it will
>be started using sh!
Not if you do "csh -c qmail-start ...".
>> > i start it from a root shell, here goes what i do to start it:
>> > # export PATH=/var/qmail/bin:$PATH <enter>
>> > # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
I thought you said you installed qmail according to the LWQ
instructions. If so, you should be starting qmail via the startup
script linked to /usr/local/sbin/qmail.
-Dave
Dave Sill wrote:
>
> Gustavo V G C Rios <[EMAIL PROTECTED]> wrote:
> >"Soffen, Matthew" wrote:
> >>
> >> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
>
> That's the recommendation, but all that's necessary is disassociating
> the child processes from the parent's tty. Csh and bash do that
> automatically. Nohup can be used to force that, too.
>
> >I dont realy know, once if you decide to start it at boot time, it will
> >be started using sh!
>
> Not if you do "csh -c qmail-start ...".
>
> >> > i start it from a root shell, here goes what i do to start it:
> >> > # export PATH=/var/qmail/bin:$PATH <enter>
> >> > # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
>
> I thought you said you installed qmail according to the LWQ
> instructions. If so, you should be starting qmail via the startup
> script linked to /usr/local/sbin/qmail.
>
> -Dave
Yeah, i did according to the LWQ, but i see no way which could damage
qmail from starting from a root shell.
On Jul 23 1999, Gustavo Rios wrote:
> I am sorry that this topic is lasting so long, but my qmail dies and dies.
> I AM GETTING CRAZY!
>
> My qmail server dies all the time, the messages is:
> lost spwan connection:..... exited .......
As a palliative solution to your problem, you may run your
qmail supervised, until you identify the cause of this strange
behaviour.
This will, hopefully, alleviate the problems you're having
with your clients, but, of course, it's not a definitive
solution.
BTW, see if running qmail supervised rises the frequency of
the problems. If it does, then this may be a helpful hint.
Also, running qmail with strace or a similar program may prove
helpful.
Hope this helps a bit, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
(still an) Ugrad. Comp. Science student - "Windows? Linux and X!"
Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
At 04:24 PM Friday 7/23/99, Gustavo V G C Rios wrote:
Dave Sill wrote:
>
> Gustavo V G C Rios <[EMAIL PROTECTED]> wrote:
> >"Soffen, Matthew" wrote:
> >>
> >> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
>
> That's the recommendation, but all that's necessary is disassociating
> I thought you said you installed qmail according to the LWQ
Yeah, i did according to the LWQ, but i see no way which could damage qmail
from starting from a root shell.
Hmm. An interesting dilemma. We can see no way "which could damage qmail"
on a working Unix system if everything is done *exactly* according to the
instructions.
I'm not saying it's the cause, but you have to agree that it makes it a tad
difficult for us if you install and run according to the instructions,
excepting the instructions you don't feel a need to follow...
The archives will show that many problems reported on this list occur
precisely because people think they know better than the instructions.
Is it safe to assume that there are no other instances where you varied
from the instructions for similar reasons?
Regards.
> > 1. Is there any pattern to this occuring? Time that qmail is up, number of
> > mails delivered? Time the OS has been up?
>
>No pattern
Let me suggest that their might be one though. So it's worth looking for and
is probably the way in which you will discover your problem.
> 2. Does it change if you alter concurrency settings?
>I never changed concurrency settings.
>Is it necessary ?
I was more asking what happens if you *do* alter them. But I suspect that
looking for some sort of pattern is your best first approach.
i start it from a root shell, here goes what i do to start it:
># export PATH=/var/qmail/bin:$PATH <enter>
># qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
Enough has been said on this already. Please remove all modifications to
your system before bringing it in for a warranty claim.
> 7. Can you show the list the log entries which preceed the "lost spawn"
> > message? Any correlation there? Eg, is it always the start of a remote
> > delivery that causes the lost spawn? Have you hit some common concurrency
> > number?
And on the other 5 or 6 occassions per day, is there a pattern to these log
messages that you've tried to discover?
Regards.
If you installed qmail according to the LWQ instructions, then there's no
need to manually start qmail, it is started whenever you are in a networked
runlevel (assuming you set it up that way per the instructions). It is also
running supervised, which should restart it automatically if it does fail
for some reason.
At 03:24 PM 7/23/99 , you wrote:
>Dave Sill wrote:
>>
>> Gustavo V G C Rios <[EMAIL PROTECTED]> wrote:
>> >"Soffen, Matthew" wrote:
>> >>
>> >> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
>>
>> That's the recommendation, but all that's necessary is disassociating
>> the child processes from the parent's tty. Csh and bash do that
>> automatically. Nohup can be used to force that, too.
>>
>> >I dont realy know, once if you decide to start it at boot time, it will
>> >be started using sh!
>>
>> Not if you do "csh -c qmail-start ...".
>>
>> >> > i start it from a root shell, here goes what i do to start it:
>> >> > # export PATH=/var/qmail/bin:$PATH <enter>
>> >> > # qmail-start ./.Mailbox sh -c 'accustamp | cyclog /var/log/qmail' &
>>
>> I thought you said you installed qmail according to the LWQ
>> instructions. If so, you should be starting qmail via the startup
>> script linked to /usr/local/sbin/qmail.
>>
>> -Dave
>
>Yeah, i did according to the LWQ, but i see no way which could damage
>qmail from starting from a root shell.
______________________
NovaMetrix Development
Robbie Walker, AMWL
P.O. Box 635 or 910-653-4006
106-B S. Main St 800-773-5647
Tabor City, NC 28463 910-653-2052 FAX
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.5.2
iQA/AwUBN5jZSjrJV5JQYcnnEQKqngCfWCIj42BJHS1MotJTGI0eMvsK+scAmwcH
nr46Lj6rM06ndKrhUtFBQ+t1
=LBSh
-----END PGP SIGNATURE-----
On Fri, 23 Jul 1999, Gustavo Rios wrote:
> I build the world many times, after my system were ready, i installed
> qmail, and other daemons too. Nothing wrong with my ftpd,telnetd httpd,
> etc.... only qmail is the problem now.
Do this:
1. Start Qmail.
2. Do a "ps", and catalog all the qmail daemons that are running in the
background.
3. Attach copies of strace to every daemon. Make sure you have plenty of
free disk space for logging.
4. Once Qmail crashes, analyze the tail end of your strace dumps.
5. Report back with anything interesting you see in the dumps.
On Fri, Jul 23, 1999 at 03:17:06PM -0400, Soffen, Matthew wrote:
> Umm.. doesn't qmail HAVE to be started using CSH per the readme files
> ?
>
> Doesn't sh have problems running it ?
I think that FreeBSD uses the pdksh as /bin/sh (since it's a posix
shell, I guess), so it should work just fine.
--
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.
Dear all,
are there any resources of using Qmail with Cyrus IMAP ?
I hear of a patch in a mailing list archive, but the site is unreachable...
Thank you very much
Bye
Stephan Hadan
hi,
if you're going to use cyrus, you don't need maildir's ou mailbox's from qmail.
(cyrus has it's own storage format).
assign everything to ~alias and then use .qmail-default to pump everything to
cyrus/bin/deliver
good luck,
ratao
On 23-Jul-99 Stephan Hadan wrote:
> Dear all,
>
> are there any resources of using Qmail with Cyrus IMAP ?
>
> I hear of a patch in a mailing list archive, but the site is unreachable...
>
> Thank you very much
>
> Bye
>
> Stephan Hadan
----------------------------------
E-Mail: RaTao von J <[EMAIL PROTECTED]>
Date: 24-Jul-99
Time: 03:24:04
----------------------------------
How would I add text to the header of the subject of my list that runs on
Ezmlm?
Like it's done on PHP3 list. Every post has [PHP] inserted into every
subject.
Denis Voitenko
[EMAIL PROTECTED]
215 386-3923
denis,
this is probably off-topic for the qmail list but ...
you can't do this in ezmlm (plain version) but you can in ezmlm-idx. in
ezmlm-idx (any reasonably current version) just
cat PREFIX > ~listowner/listdir/prefix
where listowner is the user you run lists under, listdir is the name of
the list and PREFIX is the text you want prepended to the subject.
most people object to adding text to the subject of messages in a list.
i think that its considered bad form since many people can only see short
subjects in their MUAs and incoming mail sorting is best done of fields
other than the subject. the ezmlm-idx folx think this too and document it
in their faq about subject prefixes.
todd underwood
[EMAIL PROTECTED]
On Fri, 23 Jul 1999, Denis Voitenko wrote:
> Date: Fri, 23 Jul 1999 17:58:10 -0400
> From: Denis Voitenko <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: ezmlm question
>
> How would I add text to the header of the subject of my list that runs on
> Ezmlm?
> Like it's done on PHP3 list. Every post has [PHP] inserted into every
> subject.
>
> Denis Voitenko
> [EMAIL PROTECTED]
> 215 386-3923
>
>
Someone mentioned that you couldn't do this with EZMLM.
Couldn't you do something like:
|/usr/local/bin/ezmlm-reject
|perl -ne 's/^(subject\s*:)(.*)/$1\[foolist\]$2/i;print' | /usr/local/bin/ezmlm-send
|'/home/lyonsm/SOS'
|/usr/local/bin/ezmlm-warn '/home/lyonsm/SOS' || exit 0
.. ?
--
-m PGP fingerprint 87AD A49F E2AF 6243 DDA4 0BEC EA3A FDF8 1A0D B81A
finger for key
Hi.
As the saying goes I am really new at this... I've gotten qmail 1.03 compiled
and installed. I'm going to use it as our MX 20 mail relayer for
scitechsoft.com, but it isn't setup in DNS yet. I've got everything running and
was doing some testing and got some errors.
Here's what happened:
I echoed a message to myself like in the TEST.deliver file. That came
through to my account no problem.
I tried echoing a message to someplace not in the rcpthosts and it denied it
like it was supposed to.
Then, I tried emailing from an outside source to a bad account to check for a
bounce. Well, it kind of worked. I found the message in the
/var/qmail/queue/bounce directory, so the bounce process worked, but the
message won't send.
So I tried running ./qmail doqueue and it's still there. Then I looked at the log
files and this is an example what I found (the same messages [w/different
time stamps] are there repeatedly):
In the qmail log file:
/var/log/qmail/@00000932688182
932748993.865347 warning: trouble injecting bounce message, will try later
In the system error log file
/home/sites/home/logs/error:
qmail-inject: fatal: unable to exec qq (#4.3.0)
If you need it, here are my ./qmail start commands:
supervise /var/supervise/qmail/send /var/qmail/rc | setuser qmaill cyclog
/var/log/qmail & echo -n " qmail-smtpd"
supervise /var/supervise/qmail/smtpd tcpserver -v -x /etc/tcp.smtp.cdb
-u$QMAILDUID -g$NOFILESGID 0 25 /var/qmail/bin/qmail-smtpd-wrapper
2>&1 | setuser qmaill accustamp | setuser qmaill cyclog
/var/log/qmail/smtpd &
So, to get to my question, what does
qmail-inject: fatal: unable to exec qq (#4.3.0)
mean and how do I fix it?
If you need anything else, please let me know and I'll get it asap.
Thanks all.
Rob Baham
*********************************
Rob Baham, Network Administrator
Email: [EMAIL PROTECTED]
SciTech Software, Inc.
505 Wall Street
Chico, CA 95928, USA
Voice: (530) 894-8400
Fax : (530) 894-9069
www : http://www.scitechsoft.com
*********************************
How do i configure my SMTP to deliver all my outgoing messages to a
Maildir so that massages can be sent later by maildirsmtp?
Bithi
On Sat, Jul 24, 1999 at 02:36:52PM -0600, Rahmat Ara Bithi wrote:
> How do i configure my SMTP to deliver all my outgoing messages to a
> Maildir so that massages can be sent later by maildirsmtp?
>
> Bithi
echo ":alias-ppp" > /var/qmail/control/virtualdomains
As user alias, make a maildir to catch all outgoing mail:
su alias -c 'maildirmake /var/qmail/alias/pppdir'
echo './pppdir/' > ~alias/.qmail-ppp-default
Send qmail-send a HUP signal.
--
See complete headers for more info
Hi! Anand Buddhdev has provided me very good answers on Serialmail and
ETRN and I thought I should share it with others and also let the answers
be archived by the mailing list.
Thank you very much Anand Buddhdev!
---------- Forwarded message ----------
Date: Sat, 24 Jul 1999 11:02:18 +0300
From: Anand Buddhdev <[EMAIL PROTECTED]>
To: Goh Sek Chye <[EMAIL PROTECTED]>
Subject: Re: question on Serialmail and ETRN
On Sat, Jul 24, 1999 at 12:01:29PM +0800, Goh Sek Chye wrote:
> Hi! Sorry to trouble you here.
Hello Goh. No trouble at all.
> I read your posting below from the mailing list archive for qmail.
>
> I am getting very confused here and I need some enlightenment about
> qmail/serailmail.
>
> 1. qmail alone cannot support ETRN command. You must install serialmail to
> enable qmail to support ETRN command (True/False)?
Sort of true and false. qmail on its own does not support ETRN, and
probably never will. This is because qmail's author likes writing
modular software, where each little program does one thing, and does it
well. So to get funtionality similar to ETRN, you install serialmail,
which can also help in other instances. For example, if you look on the
qmail homepage, and look for "turnmail", you will see it is a use of
serialmail without ETRN, but with POP instead.
> 2. I have a server (running sendmail) acting as a secondary mail server
> for all my ISDN customer with different domain. Currently, they are using
> ETRN to nudge sendmail to push any new mails for their doamin to their
> mail server (the MX record with higher priority for their domain)
That's usually the standard way of doing it with sendmail.
> I want to use qmail/serialmail instead of sendmail. From your answer to
> the posting below, can I say that my customer do not need to change any
> thing (continue to use ETRN) if I migrate from sendmail to
> qmail/serialmail?
Correct.
> As I have quite a number of my customer using Microsoft Exchange Server,
> can I also say that I should patch qmail as described in your posting
> below?
qmail will work fine with MS Exchange. We have anumber of such customers
here. However, I heard somebody had trouble with MS Exchange because it
was looking for the 250-ETRN response to the EHLO command. Since qmail
itself doesn't support ETRN, it doesn't advertise it in its response. I
see no harm it patching qmail-smtpd with a few lines of code to
advertise ETRN and return a "250 Ok" to an ETRN. Try using the system
without patching first. If you have problems, then patch it as I
described.
> 3. After reading through serialmail docs, am I right to say that
> serialmail will store mails for each different domain in their respective
> directories?
Correct. The directory name will be the IP address of the customer.
> Does this mean that once my customer makes a smtp connection and issue
> ETRN, qmail will know exactly which directory the mails for the domain are
> stored and deliver it from there to the customer mail server(MX record
> with higher preference) ?
Small correction here. With the qmail model, the issue of lower/higher
MX records becomes irrelevant. With sendmail, you had:
MX 10 customer
MX 20 isp.mail.server
This is because sendmail, when kicked with an ETRN, will still do MX
processing as usual. With qmail, the serialmail package doesn't use MX
records (since it's designed for serial links, not routed links).
Therefore, your customer's domain will only have one MX record, like
this:
10 MX isp.mail.server.
All their mail will be stored in the maildir. When they connect, and
either send an ETRN, *or* even just send email, serialmail will be
triggered, and it will deliver the mail out of the customer's directory
to their IP address.
> If this is true, I am really impressed. This is a very well designed
> piece of software (in contrast with sendmail which will have to go through
> all its queue to single out if there are any new mails for the domain in
> response to ETRN )
Very true. qmail and it's auxilliary packages, like serialmail, are
impressive pieces of software. They're small, fast, modular, easy to use
and understand, and best of all, free!
--
See complete headers for more info
