Re: genericstable equivalent?
On Wed, 8 Aug 2001 23:03:42 -0700 (PDT), David Raistrick [EMAIL PROTECTED] said: mail sent from the robert31 local account would show as being from: [EMAIL PROTECTED] for all intents and purposes. man qmail-inject [cr] / CONTROL FILES [cr] Depends what you mean by local account. If you mean rewriting the headers of every single e-mail that passes through (or at least scanning the headers and rewriting if need be), look at mess822. If you just mean people sending using pine or elm or mutt or whatever, then you will probably want to look at the contents of control/me and control/defaultdomain . -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks
Mandrake 8.0 with postfix
Q1.) I am setuping with Mandrake 8.0 kernal 2.4.3, how can I remove all postfix? Q2.) Should I stop all the pop3 and IMAP service in Xinetd? Q3.) I should use courier-imap and qmail-pop3? Q4.) I have many existing email account with user name like [EMAIL PROTECTED] is it ok? Q5.) Is it I should install dot-forward package b4 install qmail? my .forward file don't work, how to check what error by./instcheck? Thanks a lot! Qmail user
Re: Mandrake 8.0 with postfix
On Thu, 09 Aug 2001 14:37:21 -0400, qmail [EMAIL PROTECTED] said: Q1.) I am setuping with Mandrake 8.0 kernal 2.4.3, how can I remove all postfix? rpm -e --nodeps postfix Q2.) Should I stop all the pop3 and IMAP service in Xinetd? Yes. Q3.) I should use courier-imap and qmail-pop3? If you want a standard POP3 daemon, and want to run IMAP for your users, then Yes. Q4.) I have many existing email account with user name like [EMAIL PROTECTED] is it ok? Yes. Q5.) Is it I should install dot-forward package b4 install qmail? No. Use .qmail. man dot-qmail my .forward file don't work Neither does my cat. Thanks a lot! Qmail luser Hints: 1. Use a real name 2. Read the archives 3. Read the FAQ 4. Read. -- Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. - Martin Golding
my .forward don't work,what can I do?
I tested the qmail delivery by: echo to: user | /var/qmail/bin/qmail-inject then I find a queue in ~user/Maildir/new/ when I add a .forward file under ~user with content: someone@localhost and do the delivery test again : echo to: user | /var/qmail/bin/qmail-inject it still have a queue inside ~user/Maildir/new and I go to ~someone/Maildir/new, there are nothing. is it mean that my dot-forward don't work? how can I check the what happen to dot-forward package, any error message it will generate after make setup check? or how to use the ./instcheck ? Thanks a lot~
Re: my .forward don't work,what can I do?
On Thu, 09 Aug 2001 15:56:19 -0400, qmail [EMAIL PROTECTED] said: when I add a .forward file under ~user with content: someone@localhost and do the delivery test again : echo to: user | /var/qmail/bin/qmail-inject it still have a queue inside ~user/Maildir/new and I go to ~someone/Maildir/new, there are nothing. Are you DDB? man dot-qmail -- I think there is a world market for maybe five computers. - Thomas Watson, chairman of IBM, 1943
How to flush the queue
Hi I am running qmail with the use of the supervise scripts and like to flush the queue immediately. First of all if reseted the Connection Timeout Table with qmail-tcpok, after that i've sended the ALARM SIGNAL (with svc -a qmail-send) to qmail-send. But it doesn't started to send all remote messages in the que. Why ? Pichler Wolfgang Dialog Austria Software Telekommunikation Ges.m.b.H. Goethestrasse 93 A-4020 Linz Tel +43 (0) 70 662774 37 Fax +43 (0) 70 662774 22 Mailmailto:[EMAIL PROTECTED] Web www.dialog-gruppe.at +++
Re: Flame Bait: Using Qmail as a front-line mail server
--- Sean Chittenden [EMAIL PROTECTED] wrote: * Exchange box is firewalled and boarded up and placed behind wallboard Except you can't do that with an NT box because you'll need access to reboot it every so many days and you can't do that remotely out of the box ;). Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
RE: Can anyone explain this?
Charles Cazabon wrote: eric [EMAIL PROTECTED] wrote: Anyone else seeing similar stuff happening? I'm running qmail-1.03 without any patches under RedHat 6.1 (kernel 2.2.12-20smp) Linux kernel version 2.2.12 has known bugs in its stack, and has been identified as a likely culprit for these symptoms before. Upgrade to 2.2.19 and the problem may just disappear. If this is the problem I have been experiencing (qmail-remote processes lasting a great deal longer than they should) then upgrading to 2.2.19 won't fix this problem. A work-around is to enable socket keep-alives which (at least for me) fixes the problem. I've put the patch on the web at: http://www.duff.org/qmail/ Richard P.S. Eric: ps -ef on modern RedHat distributions (and others) has a STIME column which will tell you when the process started running.
Re: hardware sizing ?
On 09 Aug (10:54), Graham Leggett wrote: I'm curious - you seem very anti Linux and particularly anti Redhat (and pro BSD, which isn't a bad thing), but I'm wondering why - were you bitten by a Redhat server in a former life? :) Seriously - can you give details? Linux evolves into a bastard, just look at the latest stuff. The libc is bloated, the kernel releases focus on USB support and the distributions are getting worse every day. RedHat 6.2 was the latest usable commercial one. Using Redhat 7.x and stable strong in one sentence is really not going to work. :) -- Christian Bauer System Services Blue Mars GmbH mailto:[EMAIL PROTECTED] Ebersheimstrasse 5 http://www.bluemars.de/ D-60320 Frankfurt/Main Tel: +49/(0)69/46 99 73-0
Re: my .forward don't work,what can I do?
On Thu, 09 Aug 2001 19:01:06 -0400, qmail [EMAIL PROTECTED] said: ...yes.. you are right, I forgotten to see the dot-qmail now I add this line in .qmail |dot-forward .forward ./Maildir/ U... try this in .qmail: [EMAIL PROTECTED] ./Maildir/ like I stated in the first e-mail. -- Calvin: I've been thinking, Hobbes Hobbes: On a weekend? Calvin: Well, it wasn't on purpose...
removing sendmail in OpenBSD
Going through the qmail installation instruction is lwq. Section 2.8.3 describes how to remove sendmail. At the end of the section it says I must create some symlinks for the old sendmail to /var/qmail/bin/sendmail. However the instructions give locations for sendmail that don't quite work on my system. (strangely enough the qmail/doc/REMOVE.sendmail doesn't mention the need for any symlinks ... are they really needed?) Can anyone tell me which of the many sendmail files on my OpenBSD 2.9 system I should remove and which I should symlink to qmail/bin/sendmail? My system contains the following sendmail files: /usr/libexec/sendmail/sendmail /usr/bin/sendmail /usr/share/sendmail Thanks! Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: removing sendmail in OpenBSD
On Thu, Aug 09, 2001 at 11:44:06AM +, Jean-Christian Imbeault wrote: [snip] Can anyone tell me which of the many sendmail files on my OpenBSD 2.9 system I should remove and which I should symlink to qmail/bin/sendmail? My system contains the following sendmail files: /usr/libexec/sendmail/sendmail This one can stay. chmod u-s it for security. /usr/bin/sendmail This one needs to become a symlink. Are you sure there is nothing in /usr/sbin/sendmail? /usr/share/sendmail This one can stay just fine. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: removing sendmail in OpenBSD
From: Peter van Dijk [EMAIL PROTECTED] /usr/libexec/sendmail/sendmail This one can stay. chmod u-s it for security. /usr/bin/sendmail This one needs to become a symlink. Ok. Are you sure there is nothing in /usr/sbin/sendmail? There is. Missed it. Should it be a symlink too? /usr/share/sendmail This one can stay just fine. Oops, it's a directory. Should have noticed that. So what is /usr/libexec/sendmail/sendmail? Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: removing sendmail in OpenBSD
On Thu, Aug 09, 2001 at 12:02:47PM +, Jean-Christian Imbeault wrote: [snip] Are you sure there is nothing in /usr/sbin/sendmail? There is. Missed it. Should it be a symlink too? Yes. /usr/share/sendmail This one can stay just fine. Oops, it's a directory. Should have noticed that. :) So what is /usr/libexec/sendmail/sendmail? That is (at least on FreeBSD, so don't hate me if it's different on OpenBSD :) the actual sendmail binary. /usr/bin/sendmail and /usr/sbin/sendmail are just symlinks to mailwrapper, which then invokes /usr/libexec/sendmail/sendmail for you, or for example qmail's sendmail wrapper, if configured as such in /etc/mail/mailer.conf. mailwrapper is, however, unreliable, which is why you should just use symlinks. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: removing sendmail in OpenBSD
On Thu, Aug 09, 2001 at 12:02:47PM +, Jean-Christian Imbeault wrote: From: Peter van Dijk [EMAIL PROTECTED] Are you sure there is nothing in /usr/sbin/sendmail? There is. Missed it. Should it be a symlink too? yes. So what is /usr/libexec/sendmail/sendmail? The actual sendmail binary. The others are just symlinks to mailwrapper which calls sendmail then (or another MTA, defined in /etc/mailer.conf). -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Mandrake 8.0 with postfix
At 14:37 09.08.2001 -0400, qmail wrote: Q1.) I am setuping with Mandrake 8.0 kernal 2.4.3, how can I remove all postfix? if installed by hand, you would'nt ask if installed by rpm, rpm --erase Q2.) Should I stop all the pop3 and IMAP service in Xinetd? yes Q3.) I should use courier-imap and qmail-pop3? yes Q4.) I have many existing email account with user name like [EMAIL PROTECTED] is it ok? yes, but you need to use /var/qmail/users/assign Q5.) Is it I should install dot-forward package b4 install qmail? my .forward file don't work, how to check what error by./instcheck? you don't need .forward, use .qmail instead (man dot-qmail) -- --/-/-- Lukas Beeler [EMAIL PROTECTED] ---\-\-- \ \ Project: D.R.E.A.M, every.de -- Your Community / /
done qmail installation but can't telnet to port 25
I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a connection refused message. I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like this: 127.:allow,RELAYCLIENT= 10.:allow,RELAYCLIENT= I think qmail is running a ps -ax gives: 11988 ?? S 0:00.05 svscan /service 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: qmail-start: 31908 ?? S 0:01.44 supervise qmail-smtpd 10717 ?? S 0:01.45 supervise qmail-send 32271 ?? I 0:00.01 supervise log 20618 ?? I 0:00.01 supervise log 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail Where else should I look for installation errors? I have a feeling readproctitle services errors in the ps output is not a good thing. Jc PS right ow my machine has a 10. address. I am testing the installation before putting on the Internet. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: removing sendmail in OpenBSD
On 9, Aug, 2001 at 02:06:28PM +0200, Peter van Dijk wrote: On Thu, Aug 09, 2001 at 12:02:47PM +, Jean-Christian Imbeault wrote: [snip] Are you sure there is nothing in /usr/sbin/sendmail? There is. Missed it. Should it be a symlink too? On my OpenBSD CURRENT machine there's no /usr/bin/sendmail, only one in /usr/sbin. I don't think you have one in /usr/bin, surprise me! ;-) So what is /usr/libexec/sendmail/sendmail? That is (at least on FreeBSD, so don't hate me if it's different on OpenBSD :) the actual sendmail binary. /usr/bin/sendmail and /usr/sbin/sendmail are just symlinks to mailwrapper, which then invokes /usr/libexec/sendmail/sendmail for you, or for example qmail's sendmail wrapper, if configured as such in /etc/mail/mailer.conf. mailwrapper is, however, unreliable, which is why you should just use symlinks. This is news to me, I've been using mailwrapper (e.g. /etc/mailer.conf) instead. What's so bad about mailwrapper? -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html Yeah, free sex really hurts the economy and innovation. Where can i *buy* a sex license? (I don't like stealing, you know). :-) Regards Morten -- ×·.¸¸.·´¨)¸.·´ ¸.·´¨) OMorten Liebach [EMAIL PROTECTED] (_¸.·´ (¸.·´ ¸.·× 0http://home1.stofanet.dk/liebach/ (_¸.·´ohttp://pc89225.stofanet.dk/ .
Re: removing sendmail in OpenBSD
Hello. Going through the qmail installation instruction is lwq. Section 2.8.3 describes how to remove sendmail. At the end of the section it says I must create some symlinks for the old sendmail to /var/qmail/bin/sendmail. However the instructions give locations for sendmail that don't quite work on my system. Well you found the files. So you know what to do. If not read on. (strangely enough the qmail/doc/REMOVE.sendmail doesn't mention the need for any symlinks ... are they really needed?) Yes ! You have read the rest of the instructions, haven`t you ? ie. INSTALL..that`s where the links happen. Can anyone tell me which of the many sendmail files on my OpenBSD 2.9 system I should remove and which I should symlink to qmail/bin/sendmail? My system contains the following sendmail files: /usr/libexec/sendmail/sendmail /usr/bin/sendmail /usr/share/sendmail Just do this... mv /usr/libexec/sendmail/sendmail /usr/libexec/sendmail/sendmail.old mv /usr/bin/sendmail /usr/bin/sendmail.old chmod 0 /usr/libexec/sendmail/sendmail.old /usr/bin/sendmail.old ln -s /var/qmail/bin/sendmail /usr/bin What does this all mean ?? First you are renaming the files with .old names so you can always go back easily but programs won`t find them anymore. The chmod 0 is to remove the setuid bit to prevent local users from getting extra privilidges through sendmails security holes. The ln -s links the old sendmail location to qmail`s sendmail wrapper. This is so programs expecting to use sendmail at it`s default location will be diverted to qmails mimicking wrapper. Thanks! Jc Regards...Martin
log files
hi I have a running qmail box, with (at this time) only 1 problem: The qmail-send program write its logs to tty1 and not in the log files. I've setted qmail up with the use of supervise und multilog (tcpserver). All the other processes (qmail-pop3d/qmail-smtpd) are putting there logs in the right files. so can anyone help me for solving this problem ? Here are my running processes and the start scripts: my running processes ---cut--- 99 ?S 0:09 svscan /service 114 ?S 0:00 supervise vmailmgrd 115 ?S 0:00 supervise log 116 ?S 0:00 supervise qmail-pop3d 117 ?S 0:00 supervise log 118 ?S 0:00 supervise qmail-smtpd 119 ?S 0:00 supervise log 120 ?S 0:00 supervise qmail-send 121 ?S 0:03 supervise log ---cut--- my qmail-send rc looks like: ---cut--- #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH qmail-start Maildir /usr/local/bin/multilog /var/log/qmail/qmail-send ---cut--- my qmail-send/log/run file: ---cut--- #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/qmail-send ---cut--- Pichler Wolfgang Dialog Austria Software Telekommunikation Ges.m.b.H. Goethestrasse 93 A-4020 Linz Tel +43 (0) 70 662774 37 Fax +43 (0) 70 662774 22 Mailmailto:[EMAIL PROTECTED] Web www.dialog-gruppe.at +++
Re: removing sendmail in OpenBSD
Follow-up. My system contains the following sendmail files: /usr/libexec/sendmail/sendmail /usr/bin/sendmail /usr/share/sendmail You sure about /usr/bin/sendmail ? On my OpenBSD v2.8 it was /usr/sbin/sendmail Which results in :- mv /usr/libexec/sendmail/sendmail /usr/libexec/sendmail/sendmail.old mv /usr/sbin/sendmail /usr/sbin/sendmail.old chmod 0 /usr/libexec/sendmail/sendmail.old /usr/sbin/sendmail.old ln -s /var/qmail/bin/sendmail /usr/sbin Regards...martin
Re: done qmail installation but can't telnet to port 25
On Thu, 09 Aug 2001 12:31:34 +, Jean-Christian Imbeault [EMAIL PROTECTED] said: I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a connection refused message. It would appear as if you have followed Life With Qmail. Good. In this case, tail -f /var/log/qmail/smtpd/current and start qmail. See if any errors come up, and paste them here. I can tell you now that, from your ps output, qmail is not running. If it was, there would be a tcpserver running as well, listening to port 25 and spawning qmail-smtpd when you telnet there... -- Press any key to continue or any other key to quit...
Re: done qmail installation but can't telnet to port 25
case, tail -f /var/log/qmail/smtpd/current and start qmail. @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O I can tell you now that, from your ps output, qmail is not running. If it was, there would be a tcpserver running as well, listening to port 25 and spawning qmail-smtpd when you telnet there... Sorry, cut that out of the output. There is a tcpserver running. I'm thinking that the reason qmail is unahppy is that my machine is not on the Internet yet. So the name the machine has will not resolve properly. Though I was hoping I could test the machine without putting out on the Big Bad Internet. Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: done qmail installation but can't telnet to port 25
I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a connection refused message. Too vague...you typed what exactly ? Hopefully :- telnet localhost 25 or telnet 127.0.0.1 25 I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like this: 127.:allow,RELAYCLIENT= 10.:allow,RELAYCLIENT= AND... You`ve put it in /etc/tcp.smtp BUT have you built the cdb yet ? ie. qmailctl cdb OR, in case that doesn`t work tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp /etc/tcp.smtp I think qmail is running a ps -ax gives: 11988 ?? S 0:00.05 svscan /service 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: qmail-start: 31908 ?? S 0:01.44 supervise qmail-smtpd 10717 ?? S 0:01.45 supervise qmail-send 32271 ?? I 0:00.01 supervise log 20618 ?? I 0:00.01 supervise log 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail You need to do :- ps waux | grep qmail to show ALL the qmail processes. ...later...Martin
Re: Flame Bait: Using Qmail as a front-line mail server
enough anti Microsoft shit and lets get on with life. Ross [moved to mutt from Outlook for this listperfer Outlook] On Thu, Aug 09, 2001 at 09:17:24AM +0100, Adam Nealis wrote: --- Sean Chittenden [EMAIL PROTECTED] wrote: * Exchange box is firewalled and boarded up and placed behind wallboard Except you can't do that with an NT box because you'll need access to reboot it every so many days and you can't do that remotely out of the box ;). Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
Re: removing sendmail in OpenBSD
On Thu, Aug 09, 2001 at 02:33:47PM +0200, Morten Liebach wrote: [snip] This is news to me, I've been using mailwrapper (e.g. /etc/mailer.conf) instead. What's so bad about mailwrapper? It invokes the real sendmail when it gets in any kind of trouble. A fix for this is in a FreeBSD PR that hasn't been committed to the STABLE branch yet. It is also untested right now. Don't expect it to be fixed in the near future. Yeah, free sex really hurts the economy and innovation. Where can i *buy* a sex license? (I don't like stealing, you know). :-) Oh I don't know, I always just do that illegally :) Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 01:10:34PM +, Jean-Christian Imbeault wrote: case, tail -f /var/log/qmail/smtpd/current and start qmail. @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O Fix your run file: you've got the letter O in there where you should have the number 0. I'm thinking that the reason qmail is unahppy is that my machine is not on the Internet yet. So the name the machine has will not resolve properly. That has nothing to do with it. Just change the O to 0 and you should be in business. Chris
Re: hardware sizing ?
On Thu, Aug 09, 2001 at 10:54:50AM +0200, Graham Leggett wrote: Henning Brauer wrote: I want to have a strong and fast mail server on redhat 7.1 which is make strong and fast mail server and redhat in one sentence? Interesting. I'm curious - you seem very anti Linux and particularly anti Redhat (and pro BSD, which isn't a bad thing), but I'm wondering why - were you bitten by a Redhat server in a former life? :) Seriously - can you give details? We build all our servers on RedHat and have had no problems. We only have about 6,000 users but they are distributed around several data centers in the UK and Ireland. Ross Regards, Graham -- - [EMAIL PROTECTED] There's a moon over Bourbon Street tonight...
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 01:10:34PM +, Jean-Christian Imbeault wrote:
case, tail -f /var/log/qmail/smtpd/current and start qmail.
@40003b728c052b1e1bdc tcpserver: fatal: no IP address for O
You got an O ('oh') that should be a 0 ('zero').
Unless your hostname is O ('oh') in which case it's just a resolving
problem :)
Greetz, Peter
--
Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: done qmail installation but can't telnet to port 25
On Thu, 09 Aug 2001 13:10:34 +, Jean-Christian Imbeault [EMAIL PROTECTED] said: case, tail -f /var/log/qmail/smtpd/current and start qmail. @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O Ah, then this is a configuration error. Please put the contents of /service/qmail-smtpd/run in a post. -- Win95 not found, [P]arty, [C]elebrate, [D]rink ?
Re: my .forward don't work,what can I do?
On Thu, 09 Aug 2001 21:24:52 -0400, qmail [EMAIL PROTECTED] said: Great, it works, I forward to [EMAIL PROTECTED] la, but what problem I have in setup .forward? I don't have any error message I still can't forward the message by dot-forward What do your logs say? I have tried and persisted to point out that you don't need .forward, but since you obviously aren't taking the hint, tail -f /var/log/qmail/send/current, send a test message, and tell us what it says. in my .qmail file: |dot-forward .forward ./Maildir/ Just for the fun of it, try putting /var/qmail/bin/dot-forward. Oh, what the hell. While you're at it, ls -l /var/qmail/bin/dot-forward and give us the output. -- Customer: I'm running Windows '98 Tech: Yes. Customer: My computer isn't working now. Tech: Yes, you said that.
Re: qmail on AFS
Got a solution for this; thanks for all your help. The problem was qmail was unable to deliver mail if the Maildir is stored on AFS. Andrea mentioned that AFS is very similar to CODA, and the CODA solution is to use rename() as I was planning on doing. Peter had cautioned that rename will overwrite existing files whereas hard links will not lose any existing files. Archived discussion threads indicate that renaming is still relatively safe because the email file name is composed of the current date/time, PID and host name and it is unlikely that the PID would recycle within 1 second. The extended explanation of the problem is that AFS implements its own ACL, so that even the Unix root user may have no access to a users ~home directory; the holds true also that a user who has managed to log in to the Linux/Unix box may have no access to his own ~home directory. Access to AFS files are granted by tokens issued by the AFS/Kerberos authentication server. So during mail delivery, qmail-lspawn will setuid to become the email receipient, except that in most cases, this user will not have a valid token. So before we can even come to the problem of link() versus rename(), qmail is stymied by a lack to access to the Maildir. My solution of choice is to make qmail-local.c setuid to a mail delivery user (I picked qmaill) and make the qmail-local binary be setuid and owned by qmaill. The Maildir/tmp directory will grant allow lookup, insert, and delete privileges to qmaill, and Maildir/new will grant lookup, and insert to qmaill. The lack of a delete privilege on Maildir/new means that if a rename() is going to overwrite an existing file, AFS fails this operation because it implies a delete of the existing file, which privilege has not been granted to qmaill. (This scenario was tested by me by making qmail-local.c always generate the same email file name; on the first delivery it succeeds; on subsequent deliveries qmail defers the delivery as long as a file of the same name exists in Maildir/new.) In conjunction with all of the above, I will need a cron job to periodically refresh qmaill's AFS/Kerberos token so that qmaill will always have a valid token in order to make use of the ACL privileges that have been given to qmaill. The unified diff of my patch to qmail-local.c appears below for whatever you want to do with it. -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 123 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160 --- qmail-local.c.orig Wed Aug 8 14:34:18 2001 +++ qmail-local.c Thu Aug 9 01:05:42 2001 @@ -1,5 +1,6 @@ #include sys/types.h #include sys/stat.h +#include errno.h #include readwrite.h #include sig.h #include env.h @@ -44,6 +45,77 @@ int flagdoit; int flag99; +/* Wed Aug 8 16:02:32 2001, Rudy Zung on vice1.bluezulu.com + * The AFS patch short form: + * 1) Incorporate the AFS patch into qmail-local.c + * 2) Compile per INSTALL + * 3) Issue: chmod u+s /var/bin/qmail/qmail-local + * 4) Issue: chown qmaill /var/bin/qmail/qmail-local + * 5) Issue: fs setacl ~home qmaill l + * 6) Issue: fs setacl ~home/Maildir/tmp qmaill lidk + * 7) Issue: fs setacl ~/home/Maildir/new qmaill lik + * IMPORTANT: ~home/Maildir/new MUST NEVER HAVE d privilege for qmaill, + * system:authuser, or system:anyuser. The qmail-local process must + * not have the ability to delete files. + * 8) Create qmaill as an AFS user; use the AFS kas and pts utilities. + * Make sure that the AFS UID for qmaill matches the /etc/passwd UID + * for qmaill + * 9) su to qmaill and run the AFS utility klog. + * (Consider cron job to refresh this token prior to its expiration) + * 10) Follow INSTALL for starting up qmail processes. + * The commands needed for the fs setacl can be embedded into the + * AFS uss template file for subsequent users who will be created via the + * uss utility. + * + * Long form: The AFS patch is designed to solve a couple of problems where + * the Maildir is in AFS space: AFS does not support hard links thus + * instead of the normal qmail operation of using link(2) to move an email + * message from Maildir/tmp to Maildir/new, we have to use rename(2). Under + * AFS, a processes Unix UID has no bearing on file access on AFS volumes. + * Access to AFS space is managed via AFS/Kerberos tokens, which are valid + * for a limited lifetime usually of less than 24 hours. An AFS/Kerberos + * token is granted by a separate authentication to the authentication + * server, and may not necessarily be integrated with the Unix login(1) + * command. Thus it is a very posssible scenario that a user may have his + * home directory in AFS, and has managed to log in to the Unix box, but + * have no access to his ~home directory because he hasn't requested + * a AFS/Kerberos token. In the normal case, qmail-lspawn will setuid to + * the email receipient which usually will have full access to ~home and + * Maildir
Re: my .forward don't work,what can I do?
Brett Randall wrote: On Thu, 09 Aug 2001 21:24:52 -0400, qmail [EMAIL PROTECTED] said: Great, it works, I forward to [EMAIL PROTECTED] la, but what problem I have in setup .forward? I don't have any error message I still can't forward the message by dot-forward What do your logs say? I have tried and persisted to point out that you don't need .forward, but since you obviously aren't taking the hint, tail -f /var/log/qmail/send/current, send a test message, and tell us what it says. in my .qmail file: |dot-forward .forward ./Maildir/ Just for the fun of it, try putting /var/qmail/bin/dot-forward. Oh, what the hell. While you're at it, ls -l /var/qmail/bin/dot-forward and give us the output. -- Customer: I'm running Windows '98 Tech: Yes. Customer: My computer isn't working now. Tech: Yes, you said that. haha windows 98 and Me Dear Brett, I also try usr /var/qmail/bin/dot-forward in .qmail, still don't work. ls -l /var/qmail/bin/dot-forward: -rwxr-xr-x1 root root29604 Aug 9 18:34 /var/qmail/bin/dot-forward* what ownership should it be? ..
RE: hardware sizing ?
I suppose that all your users set the same servers (pop, smtp...) in their mal software so you use something to reroute each user on the good server which stock his mailbox. how do you do that ? thanx -Message d'origine- De : Ross Cooney [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 9 août 2001 14:16 À : [EMAIL PROTECTED] Objet : Re: hardware sizing ? On Thu, Aug 09, 2001 at 10:54:50AM +0200, Graham Leggett wrote: Henning Brauer wrote: I want to have a strong and fast mail server on redhat 7.1 which is make strong and fast mail server and redhat in one sentence? Interesting. I'm curious - you seem very anti Linux and particularly anti Redhat (and pro BSD, which isn't a bad thing), but I'm wondering why - were you bitten by a Redhat server in a former life? :) Seriously - can you give details? We build all our servers on RedHat and have had no problems. We only have about 6,000 users but they are distributed around several data centers in the UK and Ireland. Ross Regards, Graham -- - [EMAIL PROTECTED] There's a moon over Bourbon Street tonight...
Re: hardware sizing ?
On Thu, Aug 09, 2001 at 03:54:39PM +0100, François Philippo wrote: I suppose that all your users set the same servers (pop, smtp...) in their mal software so you use something to reroute each user on the good server which stock his mailbox. how do you do that ? thanx I am not sure what you are saying. We do use the one server for POP and SMTPno need to re-route email to good server. Ross -Message d'origine- De : Ross Cooney [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 9 août 2001 14:16 À : [EMAIL PROTECTED] Objet : Re: hardware sizing ? On Thu, Aug 09, 2001 at 10:54:50AM +0200, Graham Leggett wrote: Henning Brauer wrote: I want to have a strong and fast mail server on redhat 7.1 which is make strong and fast mail server and redhat in one sentence? Interesting. I'm curious - you seem very anti Linux and particularly anti Redhat (and pro BSD, which isn't a bad thing), but I'm wondering why - were you bitten by a Redhat server in a former life? :) Seriously - can you give details? We build all our servers on RedHat and have had no problems. We only have about 6,000 users but they are distributed around several data centers in the UK and Ireland. Ross Regards, Graham -- - [EMAIL PROTECTED]There's a moon over Bourbon Street tonight...
clustering ??
what does exactly mean clustering with Qmail ? - 2 servers redondant with a load balancing which accede to the same disk system or - 2 differents servers where each one stock half of mailboxes with a multiplexor who reroute user request on the good server following LDAP attribute or a table? or - something else ? thanx @+
Re: hardware sizing ?
On Thu, Aug 09, 2001 at 03:28:42PM +0100, François Philippo wrote: where could I find reference about hardware sizing for a mail server with qmail, courier. ?? os list: http://cr.yp.to/qmail/faq/orientation.html#os file systems: http://cr.yp.to/qmail/faq/reliability.html#filesystems no official recommended hardware that I know. Ross
Re: genericstable equivalent?
David Raistrick [EMAIL PROTECTED] wrote: I admit its rather annoying to only have the option of doing a -prepend instead of mapping ala sendmails virtualusertable... But I find NO equivalent for sendmails genericstable ?!?!?! Is this true? Who knows? We're not sendmail people. I've never even heard of genericstable; it's not like it's a standard technical term. mail sent from the robert31 local account would show as being from: [EMAIL PROTECTED] for all intents and purposes. Is there a way to do this with qmail?? Hundreds of ways to do this -- ofmipd (sp?) and @fixme/fixup are two that I can think of off the top of my head. This question is asked (and answered) hundreds of times in the qmail list archives, so you didn't look very hard for an answer. Search for masquerade domain. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: done qmail installation but can't telnet to port 25
Jean-Christian Imbeault [EMAIL PROTECTED] wrote: I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a connection refused message. [...] I think qmail is running a ps -ax gives: 11988 ?? S 0:00.05 svscan /service 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: qmail-start: 31908 ?? S 0:01.44 supervise qmail-smtpd 10717 ?? S 0:01.45 supervise qmail-send 32271 ?? I 0:00.01 supervise log 20618 ?? I 0:00.01 supervise log 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail Your installation has at least two problems, just from the above output, and possibly many more. Try again, following Life with qmail to the letter instead of however you did it this time. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
recordio
hi list I want to setup qmail to log all incoming SMTP traffic. I am using redhat 7.0 qmail 1.03 which was setup with LWQ. my startup script is: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 1100 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 21 I have looked at: http://cr.yp.to/qmail/faq/servers.html#recordio and I guess the answer is: QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 1100 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 recordio smtp /var/qmail/bin/qmail-smtpd 21 but I am not sure. any hints would be gratefully accepted. Ross
Re: log files
Wolfgang Pichler [EMAIL PROTECTED] wrote: I have a running qmail box, with (at this time) only 1 problem: The qmail-send program write its logs to tty1 and not in the log files. [...] my qmail-send rc looks like: ---cut--- #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH qmail-start Maildir /usr/local/bin/multilog /var/log/qmail/qmail-send ---cut--- my qmail-send/log/run file: ---cut--- #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/qmail-send Your qmail-send rc? Do you mean /service/qmail-send/run or /var/qmail/rc? In any case, you can't have multilog in that script plus a log/run script and still make sense. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: clustering ??
On Thu, Aug 09, 2001 at 04:04:47PM +0100, François Philippo wrote: what does exactly mean clustering with Qmail ? You mean qmail-ldap, not qmail. Use qmail-ldaps list then. And read http://www.lifewithqmail.org/ldap/ before; at least three times. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
qmail-remote crashed ...
Hi, what could be the reason for such an error message???: 2001-08-09 16:55:10.524490500 new msg 365071 2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from qp 2344 uid 8001 2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote [EMAIL PROTECTED] 2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ 2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100 I've patched qmail with a few patches, to have SMTP_AUTH, QMTP, Spamcontrol ... and it compiled without any problems. I have this qmail running on another server without any problems but on my server qmail-remote crashes. Why? Local mail delivery works on both servers. Remote delivery works only on the other server, but not on mine :-( Thanks! /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-)
Re: Dan, how do we solve this problem?
Chris Hardie writes: After reading some initial responses to this, I thought it was worth asking for clarification: (4) and (5) together would indicate that the user wants to use his ownership of the slow connection's IP address as a source for the mail, but wants to deliver it via tha fast DUL-listed connection. Is that the problem we're addressing? Well, on one level he just wants it to work, but on another level he would like to be able to tell qmail to use the slow static IP connection. On the one hand, as Greg says, he can use operating system facilities, but on the other hand, bind() exists to solve the problem, except that qmail-remote won't do a bind() without patching. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | All extremists should Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | be shot.
Re: Flame Bait: Using Qmail as a front-line mail server
Steve writes: 1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. Use smtproutes. It essentially functions as an MX record with priority -1 (in other words, a stronger priority than any possible MX record). The other way you could do it is with split DNS. djbdns (http://www.djbdns.org) makes split DNS trivially easy. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | All extremists should Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | be shot.
Re: qmail-remote crashed ...
Martin Hasenbein [EMAIL PROTECTED] wrote: what could be the reason for such an error message???: [...] 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ [...] I've patched qmail with a few patches, [...] There's your answer -- your patches are buggy. Remove the patches and recompile a stock qmail. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-remote crashed ...
On Thu, Aug 09, 2001 at 04:59:08PM +0200, Martin Hasenbein wrote: Hi, what could be the reason for such an error message???: 2001-08-09 16:55:10.524490500 new msg 365071 2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from qp 2344 uid 8001 2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote [EMAIL PROTECTED] 2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ 2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100 I've patched qmail with a few patches, to have SMTP_AUTH, QMTP, Spamcontrol ... and it compiled without any problems. I have this qmail running on another server without any problems but on my server qmail-remote crashes. Why? Local mail delivery works on both servers. Remote delivery works only on the other server, but not on mine :-( What patches have you installed? To try to debug the setup type: ll | mail [EMAIL PROTECTED] and post your output. This will tell you if your qmail-queue is broken Ross Thanks! /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9 mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-) -- _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
Removing Headers with qmail
Hi guys, I am looking for a solution to remove most of the headers in a message, so that the recepient cannot see any info of my internal network. Looking thru the archives of this mailing list, I can see that most ppl would recommend using the qmail-queue patch + qmail-qfilter or qmail-masq to do the job. After Removing headers it should look something like this: - Return-Path: [EMAIL PROTECTED] Received: from sophia.pacific.net.sg ([203.120.90.146]) by pob5.pacific.net.sg (Post.Office MTA v3.5.3 release 223 ID# 0-53829L2S100V35) with ESMTP id sg for [EMAIL PROTECTED]; Wed, 8 Aug 2001 23:45:23 +0800 Received: from muncher.math.uic.edu (muncher.math.uic.edu [131.193.178.181]) by sophia.pacific.net.sg with SMTP id f78FjLE09845 for [EMAIL PROTECTED]; Wed, 8 Aug 2001 23:45:21 +0800 (SGT) Received: ( Information Filtered ) Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk Delivered-To: mailing list [EMAIL PROTECTED] Date: Wed, 8 Aug 2001 09:41:33 -0600 From: John Doe[EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Whats up * My questions are: 1) Is there any other way to do the job, maybe even a different MTA ( Sorry, i know this is a qmail list but i'll go for what does the job best ) 2) If I am already using qmail-scanner, with the qmail-queue environment set, how do i call qmail-qfilter? Thks in advance, Paul Tan
RE: qmail-queue question
Edward, I've had problems with qmail-remote hanging - it had nothing to do with the queue lifetime, but with some code in qmail-remote failing, possibly due to an O/S bug. A fix which works for me is to enable socket keep-alives. This will kill the socket if it has died after about 2-3 hours. I've put a patch on the web at http://www.duff.org/qmail/ Richard -Original Message- From: Edward McLain [mailto:[EMAIL PROTECTED]] On a side note, is there any reason that qmail-remote should start up and then just sit there connected to a remote host for like 6 or 7 hours trying to send one email? I get this all the freaking time and I'm just wandering what exactly the freaking thing is doing? (although this problem only really seems to occur with mindspring.com, yet if I telnet to port 25 of mindsprings mail server and send the same message through telnet to the same user, from the same user as the one qmail's trying to send it works just fine and I don't get any errors or return codes.)
Re: Removing Headers with qmail
Paul Tan [EMAIL PROTECTED] wrote: I am looking for a solution to remove most of the headers in a message, so that the recepient cannot see any info of my internal network. Why? Your internal network is firewalled off, right? Futzing with headers is, in general, a very bad idea. What problem are you trying to solve? Perhaps there's a better way to do it. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: after using .forward, can use also have copy of the message?
i can't believe i'm going to say this... you guys are a bad influence :-) this is covered in-depth in the lwq/faqs, which you obviously haven't read - please re-read, comprehend and then re-ask the question (hint: look for the function of the dot-qmail file) - hogan can .forward remain a copy to original user email maildir? what is the difference between [EMAIL PROTECTED] [EMAIL PROTECTED] in .forward file?
Re: recordio
On Thu, Aug 09, 2001 at 09:36:46AM -0600, Charles Cazabon wrote: Ross Cooney [EMAIL PROTECTED] wrote: and I guess the answer is: QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 1100 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 recordio smtp /var/qmail/bin/qmail-smtpd 21 You guess wrong -- that puts recordio as the port number for tcpserver to listen on. recordio should go immediately before qmail-smtpd. QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 1100 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 smtp recordio /var/qmail/bin/qmail-smtpd 21 This it? Thanks, Ross Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ --- -- _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
Re: Re: Can I use qmail for this purpose? (newbie)
Jean-Christian Imbeault [EMAIL PROTECTED] wrote: [Mike Hodson [EMAIL PROTECTED] wrote] Another great resource is 'Life With Qmail' at www.lifewithqmail.org. Got that already. But as I found out it's Linux-centric. I'll be installing on OpenBSD and worse for me is that I don't know OpenBSD well at all. Life with qmail is *NOT* Linux-centric. I've used it myself to install qmail under OpenBSD, Solaris, IRIX, and Tru64-UNIX. I know others who've used it under FreeBSD and NetBSD. Yes, it's Linux-compatible. It would be stupid to produce documentation for any Unix software these days that isn't. As evidence of LWQ's non-Linux-centricity, I include these quotes: FreeBSD: includes GCC by default Then, using your favorite editor, remove all of the file except the lines you want. For example, here's what IDS would look like for FreeBSD after editing: On BSD systems (no /etc/inittab), put the following in /etc/rc.local and reboot the system: Note: Under Solaris, the normal id program won't work right in this script. Instead of id, use /usr/xpg4/bin/id, e.g.: -Dave
RE: qmail-queue question
OK... Let me explain this a little bit better and maybe clear some things up. 1. I've been using unix for about 8 years now and when someone says to restart a service or proggy after changing a config file, by god that service or proggy gets restarted, even if it takes a kill -9 or killall -9 to do it. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) 4. I am a freaking consultant and I wouldn't bother this mailing list unless it was something worthwhile. But when all the instructions fail, and searching through code, and rewriting part of qmail-remote output actual logging, this is generally the place to turn to. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, that is what mailing list are for aren't they. Arrogance is nice and all, but what good does it do you an empty room when everyone has left you. Any real help on this issue would be appreciated from anyone. Later, Ed McLain -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 9:58 AM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail on AFS
-BEGIN PGP SIGNED MESSAGE- Andrea mentioned that AFS is very similar to CODA, and the CODA solution is to use rename() as I was planning on doing. Peter had cautioned that rename will overwrite existing files whereas hard links will not lose any existing files. Archived discussion threads indicate that renaming is still relatively safe because the email file name is composed of the current date/time, PID and host name and it is unlikely that the PID would recycle within 1 second. I think rename() is safe. Even link() is of course better, the event that two nodes of the cluster are writing a mail with same data,pid,hostname (???) is obviously very very rare (impossible?). The extended explanation of the problem is that AFS implements its own ACL, so that even the Unix root user may have no access to a users ~home directory; the holds true also that a user who has managed to log in to the Linux/Unix box may have no access to his own ~home directory. Like Coda. Access to AFS files are granted by tokens issued by the AFS/Kerberos authentication server. Like Coda, but Coda doesn't use kerberos. So during mail delivery, qmail-lspawn will setuid to become the email receipient, except that in most cases, this user will not have a valid token. I don't know well AFS, but with Coda / Vpopmail is trivial. It's sufficient to get a token for vpopmail and root users. When qmail starts, it launch 2 scripts to get root and vpopmail tokens. Then, crontab perform authentication for root / vpopmail every 4 hours (security reasons, tokens are valid for much longer). I really didn't need to patch qmail-local. In conjunction with all of the above, I will need a cron job to periodically refresh qmaill's AFS/Kerberos token so that qmaill will always have a valid token in order to make use of the ACL privileges that have been given to qmaill. Yep. But I don't see the needs for patching qmail-local.c (except for rename()). - --- Cordiali saluti / Best regards Andrea Cerrito ^^ Net.Admin @ Centro MultiMediale di Terni S.p.A. P.zzale Bosco 3A 05100 Terni IT Tel. +39 0744 5441330 Fax. +39 0744 5441372 -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.3 for non-commercial use http://www.pgp.com iQEVAwUBO3K16vo9HK4+yTI3AQF0IQgAmgnnlQABR9szQN2KQHrxOLaSo92xxs8u 4vIkfmYT7eZrEIlYoRBazBa+8TfDyUqORNxatydzIBqiHBQcEf7AxBT8BhegNu9n QN8UNhCOEJNRHf/DvluInZm2I6+MRxity2o6psKfkWliFFaP6Lu6G8bw41J0qKul sVUkm5XtBzC5cfkiDzqAHmr+J8yv5CJiOAYuOueQ+yY2KJd0qlvMEmewBYr0rDsK kCuGEqrcxc0khtu8Wt1mdqHGhLN2yoMafhw2CUCggxiqrB5xLuoydNdAM/i/YuA1 76REBt/7LckUAH2Lb0Ej8TD0UC5w1G7MoQ1m1QEwY3ONfgdAsZ/L/Q== =wble -END PGP SIGNATURE-
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: OK... Let me explain this a little bit better and maybe clear some things up. Okay. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. This can cause qmail-queue to not be run, but not qmail-remote to crash. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. That doesn't give all the information about that message; in particular, delivery status lines don't contain the message number, only the delivery number, which you get from the starting delivery lines. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, What do you think I'm doing? You're wasting everyone's time by posting incomplete reports -- I'm trying to help you post better reports, so we can _help_ you. You want better service than that? Call Russ Nelson -- he'll come to your house and hold your hand, given sufficient incentive. For free, it doesn't get any better than this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: recordio
Ross Cooney [EMAIL PROTECTED] wrote: You guess wrong -- that puts recordio as the port number for tcpserver to listen on. recordio should go immediately before qmail-smtpd. [...] This it? Why don't you try it and see? Wouldn't that have been easier than mailing back to the list and asking if it will work? Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: deleting messages from the queue
eric [EMAIL PROTECTED] wrote: It's ridiculous because if qmail-[smtpd] could do the lookup and reject for invalid users, I would not have hardly any bounced messages. It's ridiculous because if pigs had wings, they could fly. Pigs don't have wings, and qmail-smtpd can't do the lookups. You either need to stop wishing your pig could fly or trade it for a bird. Yep. But getting them to change is gonna be darn near impossible. Do what I did: add them to badmailfrom. Again, getting them to change will be darn near impossible. But, the real point here is that I'm wondering if there is any way to change the default bounce message to something they will process. How would we know? Have you asked them what will work? Let me guess: they don't respond. ... PLUS, there is legitimate mail coming in from both of those servers for valid users. Doing it this way, I'd be blocking that as well. Set up a web page explaining that pm0.net is being blocked until they stop abusing your mail service. Send the prayer-chain granny the URL. -Dave
Re: qmail-queue question
3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards.
Again Local Deliveries not working - I'm LOST, really...
Hi list: I am experiencing the same trouble a few days ago... My Qmail will accept inbound and deliver to Maildir but not from LOCALHOST... Box is openbsd 2.9. Mails for accounts in my box arrive smooth. But if I try to send FROM localhost to local ... will not. Here is the log/long version: bash-2.05# telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail to [EMAIL PROTECTED] 250 ok rcpt to [EMAIL PROTECTED] 250 ok data 354 go ahead . 250 ok 997364882 qp 23545 Mail will never arrive... This time I will post every piece of log/control file... thanks. /var/log/qmail/current @40003b72949c101d82dc new msg 165132 @40003b72949c10372174 info msg 165132: bytes 182 from qp 23545 uid 2850 @40003b72949c152f64ac starting delivery 42: msg 165132 to local @megadeth.dnsalias.com @40003b72949c1538e25c status: local 1/10 remote 0/20 @40003b72949c15965054 delivery 42: success: @40003b72949c16d0c83c status: local 0/10 remote 0/20 @40003b72949c16e67704 end msg 165132 /var/log/qmail/ @40003b7292e524747754 tcpserver: ok 20928 0:209.99.238.152:25 pb1.pair.com:216.92.131.4::22410 @40003b7292e825fd51a4 tcpserver: end 20928 status 0 @40003b7292e826006e84 tcpserver: status: 0/20 @40003b7294800544a3f4 tcpserver: status: 1/20 @40003b729480058c72c4 tcpserver: pid 24758 from 127.0.0.1 @40003b72948007491acc tcpserver: ok 24758 0:127.0.0.1:25 localhost:127.0.0.1::25094 @40003b7295542e74e414 tcpserver: end 24758 status 0 @40003b7295542e8f9bec tcpserver: status: 0/20 /var/log/qmail/qmail-pop3d/current @40003b72943c007cfa24 tcpserver: status: 0/40 @40003b7295702fa1d70c tcpserver: status: 1/40 @40003b7295702fc948b4 tcpserver: pid 25741 from 192.168.0.77 @40003b7295702fd114cc tcpserver: ok 25741 0:192.168.0.1:110 :192.168.0.77::3791 @40003b72957110903624 tcpserver: end 25741 status 256 @40003b72957110934f1c tcpserver: status: 0/40 /var/log/maillog (when using PHP function mail() points to /var/qmail/bin/qmail-inject) Aug 9 10:42:54 jupiter sendmail[6217]: gethostbyaddr(209.99.238.152) failed: 2 Aug 9 10:42:54 jupiter sendmail[6217]: f79Dgso06217: from=www, size=276, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], relay=www@localhost Aug 9 10:44:09 jupiter sendmail[20485]: f79Dgso06217: to=Martin Marconcini [EMAIL PROTECTED], ctladdr=www (67/67), delay=00:01:15, xdelay=00:01:15, mailer=esmtp, pri=30276, relay=megadeth.dnsalias.com. [209.99.238.152], dsn=4.0.0, stat=Deferred: Connection timed out with megadeth.dnsalias.com. Here is the key... however a ping to megadeth.dnsalias.com responds almost instantly. Also to Jupiter.marconcini.com.ar... I don't know what's causing this delay. I have reversing for 192.168.x.x. Obviously not to dnsalias.com... Here are my control files: bash-2.05# cat defaultdomain dnsalias.com bash-2.05# cat me megadeth.dnsalias.com bash-2.05# cat rcpthosts megadeth.dnsalias.com marconcini.com.ar localhost jupiter.megadeth.dnsalias.com jupiter.marconcini.com.ar (I added these two today) bash-2.05# cat defaultdelivery ./Maildir/ bash-2.05# cat locals megadeth.dnsalias.com marconcini.com.ar localhost jupiter.megadeth.dnsalias.com jupiter.marconcini.com.ar (I also added these) bash-2.05# cat plusdomain dnsalias.com bash-2.05# ./qmailctl stat /service/qmail-send: up (pid 31163) 24915 seconds /service/qmail-send/log: up (pid 27572) 15 seconds /service/qmail-smtpd: up (pid 27476) 24915 seconds /service/qmail-smtpd/log: up (pid 9291) 15 seconds /service/qmail-pop3d: up (pid 18246) 24915 seconds /service/qmail-pop3d/log: up (pid 1581) 14 seconds messages in queue: 0 messages in queue but not yet preprocessed: 0 Well I guess that's all. One more thing. If you send a message to [EMAIL PROTECTED] it will arrive perfectly. But the problem is from localhost. (I added localhost to rcpthosts and locals, and it worked for a few days/hours?). Any ideas? Any other log I am missing? Mails are LOST forever... I don't know where they go. Any help will be appreciated. And by the way, this used to work before I touch anything... Regards, Martin Marconcini www.marconcini.com.ar Life must be lived looking forward and can be understood only looking backward. Soren Kierkegaard
Re: deleting messages from the queue
dave, all, It's ridiculous because if pigs had wings, they could fly. Pigs don't have wings, and qmail-smtpd can't do the lookups. You either need to stop wishing your pig could fly or trade it for a bird. this comment has the obviously unintended and unfortunate side-effect of implying that qmail is a pig and other, less-well-written, MTAs are more like birds. :-) that can't be what you intended. todd underwood vice president chief technology officer oso grande technologies, inc. [EMAIL PROTECTED]
RE: qmail-queue question
-Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the daemons to stop loading and running without editing /etc/inittab and commenting out the line that runs the svcscanboot and doing a kill -HUP 1. Then I have to do a kill or killall on all the qmail daemons to actually shut it down. Later, ed
Yes, this is a bug in qmail's virtualdomains VERP handling
Yes, this is a bug. Is Dan going to issue a qmail-1.04? He was very prompt in issuing qmail-1.03 when a bug was discovered in qmail-smtpd's handling of a null envelope recipient. -russ p.s. Apologies to mycroft. No, I didn't understand his description of the problem he was trying to solve. Pavel Kankovsky writes: On 8 Aug 2001, John R. Levine wrote: Like I said: It's true, qmail doesn't work the way you might first have guessed it does. That doesn't mean it's wrong. The fact qmail--or any other piece of software--does something does not mean it is correct. Executive summary: qmail breaks VERP under certain circumstances. Let H be a host running qmail, A and B users at H, and V a virtual domain redirected to B@H. Let X@V, i.e. B-X@H, be forwarded to some other, maybe remote, address, say K@L. Now, let's assume A uses QMAILINJECT=r qmail-inject X@V to send a VERPed message M to X@V. M is forwarded to K@L. Now, let's assume the delivery to K@L fails and the message is bounced back to A. Well, it should be bounced to A-X=V@H, shouldn't it? After all, A sent the message to X@V, and VERP is supposed to preserve the *original* recipient address. Indeed, qmail-inject's manpage says: r Use a per-recipient VERP. qmail-inject will append each recipient address to the envelope sender of the copy going to that recipient. Unfortunately, the return address in the scenario described above is A-B-X=V@H Is A supposed to know B- is superflous (if and only if the domain is V!) and should be removed? Is A supposed to analyze qmail's configurations files in order to fix something that should have never been broken? (BTW: I cannot find any code analyzing virtualdomains in ezmlm. Am I blind?) A does not care what is recorded in Delivered-To or what a program run from ~B/.qmail-V-... sees in its environment. A cares what qmail does when he sends a message and asks qmail to use VERP. Is this scenario purely artifical? Not at all. It is easy to imagine a host run by some ISP-like company hosting both an email forwarding service implemented as a virtual domain and some mailing lists. P.S. I wonder whether we will see any reaction from DJB himself. --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] Resistance is futile. Open your source code and prepare for assimilation. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | All extremists should Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | be shot.
Re: Why is there no ucspi-tcp mailing list
On Tue, Aug 07, 2001 at 09:25:12AM -0400, martin wrote: Replying to myself...sigh. I left out 'mailing list'. Obviously there are mentions of ucspi-tcp. Well, there's no compulsion of the author to do so, now is there? When I've had a question about any of the ucspi-tcp tools, a Google search pretty quickly exposes any number of citations on any number ofmailing lists, germaine to the specific use of the utility. Did you have a specific question in mind? -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 12:31:34PM +, Jean-Christian Imbeault wrote: I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a connection refused message. I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like this: Wy do you want people to connect to port 23 of your machine? You don't need a telnet server to use a telnet client... Are you running qmail-smtpd? _How_ are you running qmail-smtpd? Via inetd or via tcpserver? -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path
Re: Again Local Deliveries not working - I'm LOST, really...
On Thu, Aug 09, 2001 at 02:34:06PM -0230, Martin Marconcini wrote: Hi list: I am experiencing the same trouble a few days ago... My Qmail will accept inbound and deliver to Maildir but not from LOCALHOST... Box is openbsd 2.9. Mails for accounts in my box arrive smooth. But if I try to send FROM localhost to local ... will not. Here is the log/long version: bash-2.05# telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail to [EMAIL PROTECTED] 250 ok rcpt to [EMAIL PROTECTED] 250 ok data 354 go ahead . 250 ok 997364882 qp 23545 Mail will never arrive... Try talking proper SMTP instead: 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go ahead Subject: Whatever Whatever . 250 ok 997364882 qp 23545 /var/log/maillog (when using PHP function mail() points to /var/qmail/bin/qmail-inject) Aug 9 10:42:54 jupiter sendmail[6217]: gethostbyaddr(209.99.238.152) failed: 2 Aug 9 10:42:54 jupiter sendmail[6217]: f79Dgso06217: from=www, size=276, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], relay=www@localhost Aug 9 10:44:09 jupiter sendmail[20485]: f79Dgso06217: to=Martin Marconcini [EMAIL PROTECTED], ctladdr=www (67/67), delay=00:01:15, xdelay=00:01:15, mailer=esmtp, pri=30276, relay=megadeth.dnsalias.com. [209.99.238.152], dsn=4.0.0, stat=Deferred: Connection timed out with megadeth.dnsalias.com. See all that stuff that says sendmail? qmail doesn't seem to be involved here. Chris
Re: Why is there no ucspi-tcp mailing list
I left out 'mailing list'. Obviously there are mentions of ucspi-tcp. Well, there's no compulsion of the author to do so, now is there? When I've had a question about any of the ucspi-tcp tools, a Google search pretty quickly exposes any number of citations on any number ofmailing lists, germaine to the specific use of the utility. Did you have a specific question in mind? Well I was having problems with some junk mail. qmail takes the mail before checking to see if the user exists. It then tries to send a bounce but spam doesn`t usually have a good address so the bounce bounces. So I thought I would put some doamins/IP`s in tcprules. I then wanted to test the rule but the docs are vague. I have now successfully done that. I really want to use rblsmtp but there are two problems a) It uses text records so has to be patched. b) The RSS/dul etc. are now pay for commercial sites. Unfortunately, we are real small so that is a problem. I still don`t really understand why there is no mention of ucspi-tcp either on it`s own mailing list or under qmail (or whatever) on Dan`s mailing list page. -- Brian 'you Bastard' Reichert
RE: Again Local Deliveries not working - I'm LOST, really...
Try talking proper SMTP instead: 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go ahead Subject: Whatever Whatever . 250 ok 997364882 qp 23545 This way it worked... however the mail program will say from: to: Subject: whatever And the msg body indeed has: Whatever IF I try mail from: martin email.. rcpt to: martin email. It will happen the same... why it may not be working the other way? /var/log/maillog (when using PHP function mail() points to /var/qmail/bin/qmail-inject) Aug 9 10:44:09 jupiter sendmail[20485]: f79Dgso06217: to=Martin See all that stuff that says sendmail? qmail doesn't seem to be involved here. It's qmail-inject (which is linked to sendmail binary) I mean I deleted sendmail binady from the OpenBSD box and added a sendmail linking to qmail's sendmail. The reason for this? It's in www.lifewithqmail.org. Now, messages arrive, that means qmail seems to be properly configured... what could be happending? Thanks for your answer! Martin.
Re: Again Local Deliveries not working - I'm LOST, really...
On Thu, Aug 09, 2001 at 03:15:38PM -0230, Martin Marconcini wrote: Try talking proper SMTP instead: 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go ahead Subject: Whatever Whatever . 250 ok 997364882 qp 23545 This way it worked... however the mail program will say from: to: Subject: whatever And the msg body indeed has: Whatever IF I try mail from: martin email.. rcpt to: martin email. It will happen the same... why it may not be working the other way? If you don't put From and To headers in your message, there won't be any From and To headers in your message. What appears in these headers has nothing to do with the SMTP MAIL FROM and RCPT TO commands. /var/log/maillog (when using PHP function mail() points to /var/qmail/bin/qmail-inject) Aug 9 10:44:09 jupiter sendmail[20485]: f79Dgso06217: to=Martin See all that stuff that says sendmail? qmail doesn't seem to be involved here. It's qmail-inject (which is linked to sendmail binary)I mean I deleted sendmail binady from the OpenBSD box and added a sendmail linking to qmail's sendmail. The reason for this? It's in www.lifewithqmail.org. Those log entries come from sendmail, *not* from any qmail program. I promise. Chris
RE: Again Local Deliveries not working - I'm LOST, really...
If you don't put From and To headers in your message, there won't be any From and To headers in your message. What appears in these headers has nothing to do with the SMTP MAIL FROM and RCPT TO commands. Now a question... Why I usually do a telnet xxx 25 and send a mail like I did and I works? Is there any configuration? I mean I did mail to: email, rcpt to: email my whole life! I swear! Nevermind anyway. It's qmail-inject (which is linked to sendmail binary)I mean I deleted sendmail binady from the OpenBSD box and added a sendmail linking to qmail's sendmail. The reason for this? It's in www.lifewithqmail.org. Those log entries come from sendmail, *not* from any qmail program. I promise. I believe you. I will investigate further...
Re: deleting messages from the queue
Todd Underwood [EMAIL PROTECTED] wrote: dave, all, It's ridiculous because if pigs had wings, they could fly. Pigs don't have wings, and qmail-smtpd can't do the lookups. You either need to stop wishing your pig could fly or trade it for a bird. this comment has the obviously unintended and unfortunate side-effect of implying that qmail is a pig and other, less-well-written, MTAs are more like birds. :-) that can't be what you intended. Pigs are fairly intelligent[1], as anyone who knows farm animals will tell you. Birds, on the other hand, are notoriously dim (bird brain, for example). -Dave [1] They're also clean, contrary to popular impression. They do like to wallow in mud, but that's for comfort and protection from the Sun.
Re: hardware sizing ?
henning, all, It's a matter of fact that qmail isn't as reliable on Linux as on *BSD as it relies on some FFS semantics ext2fs just doen not fulfill. If that is the case then there is a bug in qmail - the software should be correct to the system underneath it, not apply semantics that aren't supported and say it's their problem, not ours...! when it doesn't work properly. No, it's a bug in ext2fs. that's crap, of course. if it's a bug in ext2 then it's a bug in softupdates and large numbers of other filesystems that don't provide syncrhonous metadata updates by default (although all of them do and can). there has just been a long discussion about exactly this issue on the linux kernel mailing list, specifically whether the SUS (single unix specification) requires than an fsync also synch a directory tree up to the root before returning. the conclusion of many people on the lkml (including those advocating the behavior) is that SUS does not require this behavior although it would be nice to offer an ext2 or vfs option for supporting it. people also noted that linux uses the semantics of fsync(dir) to synchronize the name metadata for a file and that that is fast and efficient (as others have noted, ext2 also offers the option of mounting filesystems and directories in synchronous mode, but that slows down everything of course). a patch to make qmail fsync the parent directory has been around for a long time and causes qmail to behave reliably (and fast!) on linux. the bottom line is that FFS semantics are not universal and they haven't been for a long time, even among bsds. assuming that they are is a mistake. todd underwood vice president chief technology officer oso grande technologies, inc. [EMAIL PROTECTED]
Re: qmail-queue question
On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the mystery. What did they say? I'm sure if you bother, you'll see that it's not a mystery at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: Again Local Deliveries not working - I'm LOST, really...
Martin Marconcini [EMAIL PROTECTED] wrote: Mails for accounts in my box arrive smooth. But if I try to send FROM localhost to local ... will not. [...] @40003b72949c101d82dc new msg 165132 @40003b72949c10372174 info msg 165132: bytes 182 from qp 23545 uid 2850 @40003b72949c152f64ac starting delivery 42: msg 165132 to local @megadeth.dnsalias.com @40003b72949c1538e25c status: local 1/10 remote 0/20 @40003b72949c15965054 delivery 42: success: That's not right. qmail logs something like 1+0+0 or various things. Are you using something weird as an MDA? What's your default delivery argument? You could be dropping messages on the floor. /var/log/maillog (when using PHP function mail() points to /var/qmail/bin/qmail-inject) Aug 9 10:42:54 jupiter sendmail[6217]: gethostbyaddr(209.99.238.152) failed: 2 Nope, that's sendmail. What's sendmail doing here? You've got bigger issues to fix. I think you failed to install qmail properly. Any help will be appreciated. And by the way, this used to work before I touch anything... Conclusion: you touched something and broke the system. So what did you touch, and why haven't you changed it back to the way it was? Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? No -- that is the proper way to stop qmail with daemontools. This doesn't seem to always work [...] Nope -- it always works. If not, you didn't install daemontools and your /service directories properly. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Again Local Deliveries not working - I'm LOST, really...
Martin Marconcini [EMAIL PROTECTED] wrote: Try talking proper SMTP instead: 220 megadeth.dnsalias.com ESMTP helo megadeth.dnsalias.com 250 megadeth.dnsalias.com mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] [...] This way it worked... however the mail program will say from: to: [...] The addresses given in the SMTP conversation have absolutely nothing to do with the From: and To: headers you see when you view the message in your MUA. Messages can show up in your mailbox without even having From: and To: headers. If you want your MUA to say the right things, then compose the message properly. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Upgrading Daemontools
I don't know if this is a good place for these questions, sorry if it = isn't 1. I'm using daemontools .70. I would like to upgrade to .76. I = believe I should stop qmail first, right...? 2. Do I need to hunt down and remove the old svscan. It's in = /usr/local/bin now. I know the new one installs to /package. 3. My rc.d qmail script (forgot where I got it) seems to start svscan, = but the new one starts in inittab. Does this make the script useless? 4. Should I even bother upgrading? Thanks John Logiudice
[OT] Re: deleting messages from the queue
On Thu, Aug 09, 2001 at 02:33:45PM -0400, Dave Sill wrote: Pigs are fairly intelligent[1], as anyone who knows farm animals will tell you. Birds, on the other hand, are notoriously dim (bird brain, for example). That's not very accurate. I keep birds (specifically, parrots) as pets, and I find that they are extremely intelligent. --Adam -- Adam McKenna [EMAIL PROTECTED] | Help stop animal abuse at Petco! http://flounder.net/publickey.html | http://www.mickaboofriends.org GPG: 17A4 11F7 5E7E C2E7 08AA | 38B0 05D0 8BF7 2C6D 110A |
Re: Again Local Deliveries not working - I'm LOST, really...
On Thu, Aug 09, 2001 at 03:26:16PM -0230, Martin Marconcini wrote: If you don't put From and To headers in your message, there won't be any From and To headers in your message. What appears in these headers has nothing to do with the SMTP MAIL FROM and RCPT TO commands. Now a question... Why I usually do a telnet xxx 25 and send a mail like I did and I works? Is there any configuration? I mean I did mail to: email, rcpt to: email my whole life! I swear! If you mean, How come other MTAs let me get away with that?, it's simple. qmail speaks SMTP properly, and is not very forgiving about those that don't. The ability to handle arbitrary variations in the SMTP protocol would require a parser in qmail-smtpd, which would complicate the code unnecessarily. I have yet to see another MTA which sends mail in the format you describe, so a parser is unecessary. Another former poor SMTP speaker, GW
RE: qmail-queue question
Ok.. after searching through the logs for a bit, I have discovered the following about some of the messages getting stuck in the queue.. This is the method I used to do this test, if it's wrong tell me, but this is what I did. First off I ran: [root@mail qmail]# ps ax | grep qmail-remote | wc -l 35 Not a problem. So now I run: [root@mail qmail]# ps ax | grep qmail-remote 1822 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1826 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1827 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1833 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1834 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1836 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1838 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1839 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1841 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] 1842 ?S 0:00 qmail-remote mindspring.com mcculley@in- prepaid.com [EMAIL PROTECTED] 1843 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1844 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1846 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1847 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1848 ?S 0:00 qmail-remote microsoft.com [EMAIL PROTECTED] 1850 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1851 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] 1852 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1854 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1855 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1856 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1858 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1859 ?S 0:00 qmail-remote mindspring.com mcculley@in- prepaid.com [EMAIL PROTECTED] 1860 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1861 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1862 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1863 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1864 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1865 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] 1866 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1868 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1869 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1870 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1871 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1872 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] [root@mail qmail]# Nothing to weird here except all of the connections to mindspring.com. So I go and do a mailq and look up the message id numbers. Then I go do: [root@mail send]# grep 112603 * | /usr/local/bin/tai64nlocal 2001-08-08 17:42:58.097835500.s:@40003b71ba7b2578952c starting delivery38: msg 112603 to remote [EMAIL PROTECTED] 2001-08-08 20:42:43.879282500.s:@40003b71d96719f67df4 starting delivery44: msg 112603 to remote [EMAIL PROTECTED] 2001-08-08 20:42:43.879282500.s:@40003b71dec231dccf04 starting delivery129: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so as someone pointed out I have to now search by the deliver number.. So I ran: [root@mail send]# grep delivery 366 * | /usr/local/bin/tai64nlocal 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so the last attempt started at 1:41PM.. So what happened to the one before it? [root@mail send]# grep delivery 26: * | /usr/local/bin/tai64nlocal 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09
Re: Upgrading Daemontools
John Logiudice [EMAIL PROTECTED] wrote: 1. I'm using daemontools .70. I would like to upgrade to .76. [...] 4. Should I even bother upgrading? Not unless v.0.76 provides some new feature that you need, or fixes some bug in v.0.70 which you cannot work around. Don't futz with a working system just for the hell of it. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
Ok.. so as someone pointed out I have to now search by the deliver number.. So I ran: [root@mail send]# grep delivery 366 * | /usr/local/bin/tai64nlocal 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery 366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so the last attempt started at 1:41PM.. So what happened to the one before it? [root@mail send]# grep delivery 26: * | /usr/local/bin/tai64nlocal 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery 26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 13:41:28.533103500.s:@40003b72c33a3620be2c delivery 26: deferral: qmail-remote_crashed./ [root@mail send]# Ok.. so qmail-remote crashed.. but why? Unless something very unusual is happening to your system, I'd say that someone or something killed it. An unpatched qmail-remote has no record of crashing in the last, oh, 3 years of people using it. It had also been running for over 3 hours? That's not necessarily a problem. Mail is allowed to get stuck. Is any mail getting thru to these sites or are they all failing? Well to test it out I did the following: [root@mail qmail]# telnet mx09.mindspring.com 25 Trying 207.69.200.36... Connected to mx09.mindspring.com. Escape character is '^]'. 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) helo mail.highspd.net 250 pickering.mail.mindspring.net Hello mail.highspd.net [208.62.90.230], please to meet you mail from: [EMAIL PROTECTED] 250 [EMAIL PROTECTED] Sender ok rcpt to: [EMAIL PROTECTED] 250 [EMAIL PROTECTED]... Recipient ok data 354 Enter mail, end with . on a line by itself this is a test. please disregard . 250 tn5s62.1dc.37kbi14 Message accepted for delivery quit 221 pickering.mail.mindspring.net closing connection Connection closed by foreign host. Ok.. so I can send mail directly just fine.. So what in the heck is going on here? This is what is puzzling me the most..? Hard to say. It could be that the contents of the mail are a problem for mindspring, are they large? Do they have binary data? It could be that qmail-remote is connecting to an MX that's particularly slow or dead. It could be that you have an smtproutes entry for that domain that points incorrectly. BTW.. this was happening with stock qmail also before I patched it with the qmail-queue patch for qmailscanner. If you are saying you are sure that qmail-remote was crashing with a stock qmail install, then I'd be highly suspicious of a library/compiler/OS problem. I know that might sound like a cop-out, but a crashing qmail-remote is virtually unheard of. It's also possible that there is some sort of system resource that is becoming unavailable causing the kernel to kill the qmail-remote. Does this happen to all qmail-remotes or only those sending to mindspring? Does it happen to all qmail-remotes or only those that run for a long time? If you can reliably determine which ones are going to crash in advance of them crashing, then do a system call trace on one of them to see why it's dying. Show us the trace. Regards.
outgoinip-patch
Hi, I've found the qmail-1.03-version of Maex's outgoingip.patch on the net. I patched my qmail and it compiled without any errors. When I first tried to send out an eMail, my logs said: qmail-remote crashed As soon as I added the file outgoingip, qmail worked properly. Did anyone has the same problem before. Is there an error in the patch? Can anybody help me? Thanks /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-)
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Ok.. so qmail-remote crashed.. but why? Who knows? Did you kill it? It had also been running for over 3 hours? So? Long messages to a slow host can do this. Well to test it out I did the following: [...] You didn't use proper SMTP syntax, which qmail-remote would have. Who says you connected to the same machine as qmail-remote did? mx09.mindspring.com could be a cluster of machines sitting behind a load balancer. mail from: [EMAIL PROTECTED] rcpt to: [EMAIL PROTECTED] This isn't proper SMTP. Any ideas? Just one: stop worrying until you have evidence of an actual problem. Everything you've described so far can be completely normal behaviour. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: outgoinip-patch
Martin Hasenbein [EMAIL PROTECTED] wrote: [...] I patched my qmail and it compiled without any errors. When I first tried to send out an eMail, my logs said: qmail-remote crashed [...] Is there an error in the patch? Yes. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Removing Headers with qmail
On Thu, Aug 09, 2001 at 11:47:44PM +0800, Paul Tan wrote: I am looking for a solution to remove most of the headers in a message, so that the recepient cannot see any info of my internal network. If you're using tcpserver (and if you're not, you should be), see: http://marc.theaimsgroup.com/?l=qmailm=98678523400345w=2 for a painless solution to your problem. Chris PGP signature
About processes
Hi, ps ax | grep qmail-remote shows the running processes that are currently sending message, each process is a message been sent, ok? ps ax | grep qmail-smtpd show the running processes that are currently arriving, right? But it shows: 1016 ?S 4:30 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 15498 ?S 0:44 /var/qmail/bin/qmail-smtpd 19168 ?S 0:00 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd How many messages are arriving? 1, 2 or 3? Thanks, Ari
Re: Yes, this is a bug in qmail's virtualdomains VERP handling
On Thu, 9 Aug 2001, Russell Nelson wrote: Yes, this is a bug. Surprised? :) Is Dan going to issue a qmail-1.04? Well, he could probably address other issues as well, e.g. a latent problem with the interpretation of program return codes (summarized in my posting titled qmail vs ld.so execve() from September 14, 2000), or that [0.0.0.0] thing. --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] Resistance is futile. Open your source code and prepare for assimilation.
Re: About processes
On Thu, 09 Aug 2001 22:46:27 GMT, [EMAIL PROTECTED] said: 1016 ?S 4:30 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 15498 ?S 0:44 /var/qmail/bin/qmail-smtpd 19168 ?S 0:00 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd You've got two problems here: 1. Your setup script is passing the args QMAILDUID and NOFILESGID to tcpserver. Try passing $QMAILDUID and $NOFILESGID. 2. Your setup script has spawned tcpserver on port 25 (smtp) twice. (Either that, or you've started qmail twice). Those tcpserver lines simply show that your server is waiting for a connection on port 25. The /var/qmail/bin/qmail-smtpd line is the one which shows an open connection. -- C:\DOS C:\DOS\RUN RUN\DOS\RUN C:\WINDOWS C:\WINDOWS\GO C:\PC\CRAWL
Re: About processes
On Thu, Aug 09, 2001 at 10:46:27PM +, [EMAIL PROTECTED] wrote: ps ax | grep qmail-remote shows the running processes that are currently sending message, each process is a message been sent, ok? Right. ps ax | grep qmail-smtpd show the running processes that are currently arriving, right? But it shows: 1016 ?S 4:30 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 15498 ?S 0:44 /var/qmail/bin/qmail-smtpd 19168 ?S 0:00 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd How many messages are arriving? 1, 2 or 3? One, but whatever script you're using to start qmail-smtpd is screwed up. To fix it, you probably need to change -uQMAILDUID -gNOFILESGID to -u$QMAILDUID -g$NOFILESGID. And when you get things straightened out, you should never have two invocations of tcpserver running on the same port at the same time (like you do above), though you can have many qmail-smtpds running at the same time (one for each incoming SMTP connection). Chris PGP signature
qmailanalog operation
Hi all! I have just installed the qmailanalog 0.70 binary for openbsd. I've noticed that there doesn't appear to be alot of information on qmailanalog. atm I'm having problems with getting started.I use multilog on my qmail system. Would someone be kind enough to offer some starting off instructions to see results with this program? (: Many Thanks. Gareth.
Re: hardware sizing ?
On Thu, Aug 09, 2001 at 01:58:41PM -0400, Dan Melomedman wrote: On Thu, Aug 09, 2001 at 07:47:20PM +0200, Henning Brauer wrote: Really have a look at the sources. You'll see the difference very fast. There are strong rules for code on OpenBSD, style(9) is just a tiny excerpt. The code is just written with correctnedd in mind, and with paranoia. I trust you on the clean source of OpenBSD, that's one of their primary goals, however it doesn't make their OS better. In fact in computing, Yes it does. Having a clear and consistent code makes the code easier to maintain and read. Code that is easy to maintan and read is easier to make secure and safe since other people than the creator can easily comprehend it. In the long run, this usually makes for a better product. Writing clean and correct code is one of the first things you'll learn in software design. -- Lars Hansson Technical Consultant/System Administrator UNET, Inc.Makati City, Philippines e-mail: [EMAIL PROTECTED]
Re: qmailanalog operation
Hello Gareth. Hi all! I have just installed the qmailanalog 0.70 binary for openbsd. I've noticed that there doesn't appear to be alot of information on qmailanalog. atm I'm having problems with getting started.I use multilog on my qmail system. Would someone be kind enough to offer some starting off instructions to see results with this program? (: Many Thanks. Gareth. Try this (call it mylog (for example) and put it in /usr/local/bin. Don`t forget to change the e-mail address. - #!/bin/sh PATH=/usr/local/bin/qmailanalog:/usr/local/bin:$PATH export PATH umask 077 TMP_FILE=/var/log/qmail/qmailanalog.tmp EXT_FILE=/var/log/qmail/qmailanalog.ext OUT_FILE=/var/log/qmail/qmailanalog.out LOG_FILE=/var/log/qmail/* rm -f $TMP_FILE $OUT_FILE cat MAIL_HEADER $OUT_FILE From: Postmaster@domain To: whoever@domain Subject: `hostname` qmail statistics MAIL_HEADER touch $EXT_FILE cat $EXT_FILE $LOG_FILE | matchup $TMP_FILE 5$EXT_FILE.new mv $EXT_FILE.new $EXT_FILE zoverall $TMP_FILE $OUT_FILE echo --- $OUT_FILE zfailures $TMP_FILE $OUT_FILE echo --- $OUT_FILE zdeferrals $TMP_FILE $OUT_FILE echo --- $OUT_FILE #zddist $TMP_FILE $OUT_FILE #Echo --- $OUT_FILE #zrxdelay $TMP_FILE $OUT_FILE echo --- $OUT_FILE zrecipients $TMP_FILE $OUT_FILE echo --- $OUT_FILE #zsuccesses $TMP_FILE $OUT_FILE #echo --- $OUT_FILE #zsenders $TMP_FILE $OUT_FILE #echo --- $OUT_FILE zrhosts $TMP_FILE $OUT_FILE #echo --- $OUT_FILE #zsendmail $TMP_FILE $OUT_FILE #echo --- $OUT_FILE #zsuids $TMP_FILE $OUT_FILE /var/qmail/bin/qmail-inject $OUT_FILE rm -f $TMP_FILE $OUT_FILE --- unrem the other ones if you like but it will be big. I just use the zoverall, zfailures, zdeferrals, zrecipients and zrhosts. Then :- type crontab -e and add this :- 01 1 * * */usr/local/bin/mylog esc : wq (normal vi stuff). To test you can just invoke it at any time by doing /usr/local/bin/mylog. Have fun. Oh...no times as I haven`t patched and added tai64nfrac. Regards...Martin
Re: About processes
Brett Randall [EMAIL PROTECTED] wrote: On Thu, 09 Aug 2001 22:46:27 GMT, [EMAIL PROTECTED] said: 1016 ?S 4:30 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 15498 ?S 0:44 /var/qmail/bin/qmail-smtpd 19168 ?S 0:00 /usr/local/bin/tcpserver -v -H -uQMAILDUID -gNOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd [...] 2. Your setup script has spawned tcpserver on port 25 (smtp) twice. No. tcpserver forks for each connections, and then spawns it's child process. This is normal. To answer the original poster's question, this shows one message currently being received over the network (the process which is /var/qmail/bin/qmail-smtpd). Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: About processes
I've fixed up the tcpserver, thanks! So each qmail-remote is a message going out and each qmail-smtpd without tcpserver is a message arriving. Thanks, Ari
Online monitor
Hi, Is there some tool to check online qmail log, like messages arriving and going out with output to browser? Thanks, Ari
Re: About processes
Now I've change the variable, -uQMAILDUID -gNOFILESGID to -u$QMAILDUID -g$NOFILESGI and restarted qmail, but sometimes I can it twice processes of: 2173 pts/0S 0:00 /usr/local/bin/tcpserver -v -H -u401 -g400 0 smtp /var/qmail/bin/qmail-smtpd 2714 pts/0S 0:00 /usr/local/bin/tcpserver -v -H -u401 -g400 0 smtp /var/qmail/bin/qmail-smtpd or 3 times: 2831 pts/0S 0:00 /usr/local/bin/tcpserver -v -H -u401 -g400 0 smtp /var/qmail/bin/qmail-smtpd 2173 pts/0S 0:00 /usr/local/bin/tcpserver -v -H -u401 -g400 0 smtp /var/qmail/bin/qmail-smtpd 2830 pts/0S 0:00 /usr/local/bin/tcpserver -v -H -u401 -g400 0 smtp /var/qmail/bin/qmail-smtpd Why? Thanks, Ari [EMAIL PROTECTED] escreveu: I've fixed up the tcpserver, thanks! So each qmail-remote is a message going out and each qmail-smtpd without tcpserver is a message arriving. Thanks, Ari
readproctitle service errors?
After finally getting qmail to work last night and at the suggestion of some posters I've decided to re-do my installation. I've re-installed the OS (OpendBSD 2.9) and started from scratch again, trying to follow lwq as closely as possible. I'm at the daemontools install step and have a suspicion I did something wrong. After rebooting a quick ps -ax gives this: PID TT STAT TIME COMMAND 1 ?? Is 0:00.01 /sbin/init 10120 ?? Ss 0:00.02 syslogd 16273 ?? Ss 0:00.00 portmap 9437 ?? Ss 0:00.01 inetd 14360 ?? Is 0:00.40 /usr/sbin/sshd 28258 ?? Is 0:00.00 /usr/sbin/sendmail -q30m 15084 ?? Ss 0:00.00 cron 8076 ?? Ss 0:00.01 telnetd -k 32438 p0 Ss 0:00.08 -sh (sh) 14112 p0 R+ 0:00.00 ps -ax 6223 C0- I 0:00.01 /bin/sh /command/svscanboot 9852 C0- I 0:00.01 readproctitle service errors: ... 7865 C0- S 0:00.01 svscan /service 520 C0 Ss+ 0:00.09 -csh (csh) 18317 C1 Is+ 0:00.00 /usr/libexec/getty Pc ttyC1 24652 C2 Is+ 0:00.00 /usr/libexec/getty Pc ttyC2 I'm worried that readproctitle service errors: indicates an error. What is readproctile? Thanks! Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: recordio
On Thu, Aug 09, 2001 at 11:17:14AM -0600, Charles Cazabon wrote: Ross Cooney [EMAIL PROTECTED] wrote: You guess wrong -- that puts recordio as the port number for tcpserver to listen on. recordio should go immediately before qmail-smtpd. [...] This it? Why don't you try it and see? Wouldn't that have been easier than mailing back to the list and asking if it will work? Why dont you stop being such an asshole and either help or shutup. Ross Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ --- -- _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
