Re: Q problem.
Hello, I am facing a similar problem, qmail-qstat messages in queue: 3697 messages in queue but not yet preprocessed: 0 qmail-qread 11 Apr 2001 16:29:39 GMT #1377194 15538 remote [EMAIL PROTECTED] 11 Apr 2001 16:38:45 GMT #1377217 15549 remote [EMAIL PROTECTED] 11 Apr 2001 16:53:52 GMT #1377355 15543 remote [EMAIL PROTECTED] 11 Apr 2001 17:03:56 GMT #1377401 15539 remote [EMAIL PROTECTED] 11 Apr 2001 17:12:14 GMT #1377539 15540 All these messages belong to this particular remote host...which doesn't even have an MTA running. How can I safely delete these messages and stop them from re-occuring. FYI, I am running Qmail installed from memphis RPMS on RH6.2 Thanks in advance. Regards Sumith These mail have been there (or thats what i thik) since yesterday. How do i delete them or force them out. They will be retried periodically for up to a week, after which they will be bounced. Change /var/qmail/control/queuelifetime (man qmail-send) to do this earlier. Greetz, Peter.
qmail Digest 14 Apr 2001 10:00:01 -0000 Issue 1334
qmail Digest 14 Apr 2001 10:00:01 - Issue 1334 Topics (messages 60686 through 60715): Re: clustering 60686 by: Rizwan 60692 by: Karsten W. Rohrbach 60710 by: Benjamin Lee Q problem. 60687 by: Rizwan 60688 by: Peter van Dijk 60689 by: Rizwan 60715 by: Sumith Re: qmail on Mac OSX? 60690 by: Paul Makepeace 60693 by: Paul J. Schinder Re: Best qmail patches for hosting email for many domains 60691 by: Charles Cazabon smtp and pop not working 60694 by: Steven Katz 60702 by: Chris Johnson 60703 by: Steven Katz 60704 by: Charles Cazabon 60705 by: Al Sparks Pine for Maildir 60695 by: Steven Katz 60700 by: Al Sparks 60706 by: Stefan Laudat 60709 by: Peter Cavender ZConnected_to_XXX_but_... 60696 by: Clifford Tse 60697 by: Peter van Dijk 60698 by: Clifford Tse Pop goes my weasel 60699 by: Meuse, Andy Re: help me 60701 by: Al Sparks Qmail Works, But I'm Sure It's Running Backwards! 60707 by: Br. Kurt Van Kuren OSB movipage 60708 by: Franco Galian Maildir (dir) to file for /var/mail/$USR (Inbox) [imapd] 60711 by: alexus 60712 by: Peter Cavender 60714 by: Robin S. Socha reality check not working (was: smtp and pop not working) 60713 by: Robin S. Socha Administrivia: To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To subscribe to the digest, e-mail: [EMAIL PROTECTED] To bug my human owner, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- Hi there, Have a look at the piranha high availability clustering of Red Hat. there is a piranha rpm available which does something similar ( for tcp/ip services). Rizwan On Fri, 13 Apr 2001, Peter van Dijk wrote: On Thu, Apr 12, 2001 at 06:37:35PM -0700, Brett wrote: Can someone point me towards documentation on the subject of clustering qmail machines? That is, we're going to be setting up several machines all with the big concurrency patch in an effort to send out more mail faster. Tying all these qmail installations together through a controller machine is where I start to get hazy. If somebody's done it before and can offer some pointers, I'd be much appreciative. The search engine always says it's broken when I try to search the archives so I apologize if this is in there somewhere. Thanks in advance. I have a central box that generates all configfiles and puts them in a directory called /conf/mail on a NetApp fileserver, from which all qmail boxes copy their configuration periodically. Make sure you copy stuff to tmpfiles and then move 'm (also when generating files to go into /conf/mail). Especially over NFS, doing it any different is guaranteed trouble. It works like a charm. Greetz, Peter. -- In the name of Allah, Most Gracious, Most Merciful -- Praise be to Allah, the Cherisher and Sustainer of the world; Most Gracious, Most Merciful; Master of the Day of Judgment. Thee do we worship, and Thine aid we seek. Show us the straight way, The way of those on whom Thou hast bestowed Thy Grace, those whose (portion) is not wrath, and who go not astray. Qur'aan Ch:1 Peter van Dijk([EMAIL PROTECTED])@2001.04.13 10:23:26 +: I have a central box that generates all configfiles and puts them in a directory called /conf/mail on a NetApp fileserver, from which all qmail boxes copy their configuration periodically. Make sure you copy stuff to tmpfiles and then move 'm (also when generating files to go into /conf/mail). Especially over NFS, doing it any different is guaranteed trouble. in several projects i used rsync[1] over ssh (openssh[2]) for distributing configuration between machines (push updates). rsync does a great job, supporting incremental/differential updates and moving the files in place after they have been transmitted and verified. happy easter /k links: [1] http://rsync.samba.org/ [2] http://www.openssh.com/ -- Microsoft isn't the answer. Microsoft is the question, and the answer is no. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de Slightly off topic... I was wondering if anyone has used something like 'watch' or 'stat' (or somthing else?) to detect the modification (change) of a file or directory, and then trigger an rsync? Of course, I could settle with a crond rsync every minute or so, I guess! I do this at the moment, was just thinking about an
vpopmail doesn't deliver mails
Hi! I've set up qmail with vpopmail. Now I created a domain and a user by using vpopmail. Every time I send a message to [EMAIL PROTECTED] it doesn't deliver the mail to ~user/Maildir and I don't get an error message from the server. Here is a part of my maillog (new entry when mail arrives): Apr 14 13:17:36 hostname qmail: 987247056.830997 status: local 0/10 remote 0/20 Thanks Christian Maier
Re: Pine for Maildir
Actually, last I checked those patches don't work with the newest pine sources. In this case RTFM'ing wouldn't help now would it. Perhaps he should have asked the list; oh wait he did. did I say the patches work on the latest pine version ? umm... nope. if he's so eager to have the latest version with maildir (which it doesn't support it by default) maybe he's ambitious in modifying it to suit his needs :-X -davidu -- Stefan Laudat CCNA CCAI - "- I think my men can take care of one little penguin. - No Mr. Gates, your men are already dead."
Re: reality check not working (was: smtp and pop not working)
Robin S. Socha, Bastard Consultant From Hell http://socha.net/ You're not kidding, huh? Your response to Al has nothing to do with qmail. There is enough traffic without this sort of nonsense. Please keep your flames off the list.
qmail-pop3d and supervise
Hi, folks. Thanks to the mailing list archives, I've been able to configure qmail-pop3d to run under supervise...almost. I have one remaining problem: I still get "Connection refused" when I telnet to port 110. These are the processes running on the system: $ ps -ax | grep qmail 160 ?S 0:00 supervise qmail-send 163 ?S 0:29 supervise qmail-smtpd 166 ?S 0:32 supervise qmail-pop3d 167 ?S 0:00 qmail-send 169 ?S 0:00 /usr/local/bin/multilog t s250 /var/log/qmail/qma 657 ?S 0:00 splogger qmail 658 ?S 0:00 qmail-lspawn ./Mailbox 659 ?S 0:00 qmail-rspawn 660 ?S 0:00 qmail-clean When I telnet to port 110, I get: telnet: Unable to connect to remote host: Connection refused But if I stop the qmail-pop3d and then start it from the command line using the following command, I can connect: /usr/bin/tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup myhost \ /usr/local/bin/checkvpw /var/qmail/bin/qmail-pop3d Maildir This is the same thing as I have in the /var/qmail/supervise/qmail-pop3d/run script... Any ideas why this may not be working as a service? Also, could I run UW IMAP to provide the POP3 service instead of qmail-pop3d? Thanks. Rehan
Re: qmail-pop3d and supervise
On Sat, Apr 14, 2001 at 01:38:03PM -0400, Rehan Zaidi wrote: Hi, folks. Thanks to the mailing list archives, I've been able to configure qmail-pop3d to run under supervise...almost. I have one remaining problem: I still get "Connection refused" when I telnet to port 110. These are the processes running on the system: $ ps -ax | grep qmail 160 ?S 0:00 supervise qmail-send 163 ?S 0:29 supervise qmail-smtpd 166 ?S 0:32 supervise qmail-pop3d 167 ?S 0:00 qmail-send 169 ?S 0:00 /usr/local/bin/multilog t s250 /var/log/qmail/qma 657 ?S 0:00 splogger qmail 658 ?S 0:00 qmail-lspawn ./Mailbox 659 ?S 0:00 qmail-rspawn 660 ?S 0:00 qmail-clean What is the output of: $ ps -ax | grep tcp When I telnet to port 110, I get: telnet: Unable to connect to remote host: Connection refused That tells us that tcpserver probably isn't running which means that the run script is probably not running or runnable. But if I stop the qmail-pop3d and then start it from the command line using the following command, I can connect: /usr/bin/tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup myhost \ /usr/local/bin/checkvpw /var/qmail/bin/qmail-pop3d Maildir This is the same thing as I have in the /var/qmail/supervise/qmail-pop3d/run script... Is that script readable, executable? What is the output of: $ ls -l /var/qmail/supervise/qmail-pop3d/run Also, rather then showing us the tcpserver command, much more instructive would be a cat of the run file, so show us the output of: $ cat /var/qmail/supervise/qmail-pop3d/run Regards.
Re: qmail-pop3d and supervise
From: "Rehan Zaidi" [EMAIL PROTECTED] This is the same thing as I have in the /var/qmail/supervise/qmail-pop3d/run script... What if you run the /var/qmail/supervise/qmail-pop3d/run script from the command line? Maybe there is a syntax error in there? Is there anything in the logs? Also, could I run UW IMAP to provide the POP3 service instead of qmail-pop3d? I *think* so although haven't tried it (only tried IMAP). There is a patch for UW IMAP that you need to apply to get it to support Maildirs.
Re: qmail-pop3d and supervise
Thanks to Mark and David for the quick replies. The problem was that the scripts weren't executable. I assumed that they didn't need to be because SMTP and send seemed to be working fine, and the permissions for those run scripts didn't include execution. Next question... Supervise is using 95+% of the CPU on the system (RedHat 7.0) when qmail is running and 80-90% when it's not. Is that normal? Thanks again. Rehan
Did my first email make it through?
Hello everyone... I was wondering if the first email qmail list. I've seen a fair number of messages since then, but no response to mine. Since most messages do get responses on this mailing list, I was hoping I'd get some clarification. Thanks in advance, Br. Kurt
Re: Maildir (dir) to file for /var/mail/$USR (Inbox) [imapd]
- Original Message -
From: "Peter Cavender" [EMAIL PROTECTED]
To: "alexus" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, April 14, 2001 1:37 AM
Subject: Re: Maildir (dir) to file for /var/mail/$USR (Inbox) [imapd]
Hi
.. let's start from right note here .. by sayin' i'm using qmail w/
Maildir
and imapd (doesn't really matter which one but if someone wants to know
i'm
using the one the came with pine package (uw-imapd)) ..
Ummm, it DOES matter, because IMAP accesses the mail
even though that i said it doesn't matter i still desided to specify it...
if you read more carefully you'll see it says
i used pine's imapd (uw-imapd)
with a patch of maildir from www.qmail.org website
and i'm using very
popular client known as Outlook Express and/or Outlook and i'm sure many
more will have same problem/thing..
It shouldn't matter WHAT client you are using...
i know, that's what i'm trying to accomplish .. to be as much as more
compatible with all clients
since there is no Inbox from client point of view (it points to god
knows
where probably standard unix box /var/mail/$user or somethin),
Not at all, it is ~/Maildir
I have to
browse for an additiona folder which would be in $HOME/Maildir.. and it
also
addes this folder in the list of others.. unfortinatly I can't just
change
name of that folder Maildir to Inbox due to conflict with existing on
e-mail
client end (and none existing on server side) folder/file.
what i need is: I want everyone's standard e-mail client to take Maildir
as
a Inbox
Then configure your IMAP / POP server to serve the right folder...this
should all be server-side!
configure.. it's not like it has options for that.. basicly i'd have to
re-write part of the code for that.. and i'm not a programmer .. i realize
that gotta be done on server side.. *duh* that's what i'm trying to write
this whole letter all about how to do it on server side!
my question is: how do i do that?
CourierIMAP
Courier IMAP is the most not standard imapd is ever, you can't create any
folders outside of Inbox.. all other imapd allows you to do that.. plus all
"sent mail" doesn't goes into "sent mai" in courier imap ('cause there is no
one and once again it can not be created 'cause it outside of inbox)
solution: .. maybe i can somehow trick my system in that Maildir is not
really a dir and it's just a file? this way I can put a symbol link into
/var/mail/$user to that file that's somehow is directory (Maildir) ?
or maybe there are other solutions for that?
it's really uncomfortable for me to do it and for for others users to
explain to add Maildir in their clients and there are some other
complications to that (which I dont really want to bore you with)
please e-mail me any possible solutions here
thanks in advance
Bye
I hope this helps...it seems you are coming at the problem from the wrong
direction..
so far it didn't...
--P
Re: Qmail Works, But I'm Sure It's Running Backwards!
* "Br. Kurt Van Kuren OSB" [EMAIL PROTECTED] [010414 04:08]: stpeters.sk.ca stpeterscollege.ca LOCALHOST gecko.stpeterscollege.ca mail.stpeterscollege.ca .com .edu .org .to This is wrong. You can't use wildcards in rcpthosts, and you shouldn't list other hosts than stpeters.sk.ca and stpeterscollege.ca in rcpthosts. RELAYCLIENT="" should take care of the relaying. If it doesn't, there is something wrong with your tcprules/tcpserver setup. The error message from qmail should be changed to "This domain isn't in my list of allowed rcpthosts and RELAYCLIENT isn't set" --- we've been seeing to many examples of Kurt's misconception over the last few weeks... -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/ PGP signature
Re: qmail-pop3d and supervise
On Sat, Apr 14, 2001 at 02:48:03PM -0400, Rehan Zaidi wrote: Thanks to Mark and David for the quick replies. The problem was that the scripts weren't executable. I assumed that they didn't need to be because SMTP and send seemed to be working fine, and the permissions for those run scripts didn't include execution. Then they didn't run. Most likely what /is/ running is a script you started manually. See my thoughts on your next question. Next question... Supervise is using 95+% of the CPU on the system (RedHat 7.0) when qmail is running and 80-90% when it's not. Is that normal? No. But if a script for qmail-smtp, for instance, was already running, then the "run" script's attempt to start tcpserver is failing continuously and continuously trying to restart. Check your logs - you'll probably find a message from tcpserver that it can't bind to port 25 because it's already in use. Tim
Re: qmail-pop3d and supervise
- Original Message - From: "Rehan Zaidi" [EMAIL PROTECTED] to run under supervise...almost. /usr/bin/tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup myhost \ /usr/local/bin/checkvpw /var/qmail/bin/qmail-pop3d Maildir I had a hell of a time also - mainly because I did NOT include the word "exec" the first couple of times. bash-2.04# cat /var/qmail/supervise/qmail-pop3d/run #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ tcpserver -v -H -R 0 pop-3 /var/qmail/bin/qmail-popup \ updegrove.net /var/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 bash-2.04# ls -la /var/qmail/supervise/qmail-pop3d/run -rwxr-xr-x 1 root wheel 189 Apr 10 21:01 /var/qmail/supervise/qmail-pop3d/run bash-2.04# qmailctl stat (if you followed LWQ you called this script"qmail") qmail-pop3d: up (pid 24828) 282032 seconds qmail-send: up (pid 4390) 282032 seconds qmail-smtpd: up (pid 28329) 282032 seconds qmail-pop3d/log: up (pid 19750) 282032 seconds qmail-send/log: up (pid 11681) 282031 seconds qmail-smtpd/log: up (pid 4835) 282032 seconds Hope this helps Rick Up
Procmail headaches
Hi all. The qmail-start script (the default one which comes with qmail) has the line "qmail-start '|preline procmail' splogger qmail". Is there some way to avoid a defaultdelivery action, without modifying the log stuff ?. I want to avoid the '|preline procmail' because everytime a message is delivered to a user, procmail gives the following messages: Apr 15 03:04:02 roku qmail: 987296642.282146 delivery 1: success: procmail:_Couldn't_create_"/var/spool/mail/someuser"/did_0+0+1/ Of course, it couldn't create /var/spool/mail/someuser, because /var/spool/mail doesn't exists. The conf file .procmailrc has the DEFAULT MAILDIR variables pointing to the local Mailbox, and the messages are delivered correctly, but anyway procmail insist to write to a non-existent directory (i love sendmail still-dependent software ). Thanks David Gmez "The question of whether computers can think is just like the question of whether submarines can swim." -- Edsger W. Dijkstra
Re: Pine for Maildir
Stefan Laudat wrote: there are patches for pine Maildir access, please rtfm at www.qmail.org I've tested that and worked a couple of months ago. I am working on this issue right now. What it's boiled down to has been my installing the courier-imap package with the intent of having Pine access that. I've patched pine's source code with Mattias Larsson's pine-maildir-4.33 patch; but couldn't figure out how to configure Pine to access the Maildirs (namely due to lack of documentation on Larsson's patch, and his site seems to be down as well). I would be interested to hear of the patch you used and the configuration adjustments you made to Pine. By the way, I must say that I do not care for mutt. The interface is rather dirty (I don't mean its aesthetics) and the configuration rather cryptic. Maybe I just didn't devote enough time to it? Anyways, it's not a viable option. -- Keith Network Engineer Triton Technologies, Inc.
Re: Pine for Maildir
On Sat, 14 Apr 2001, Nick (Keith) Fish wrote: Stefan Laudat wrote: there are patches for pine Maildir access, please rtfm at www.qmail.org I've tested that and worked a couple of months ago. I am working on this issue right now. What it's boiled down to has been my installing the courier-imap package with the intent of having Pine access that. I've patched pine's source code with Mattias Larsson's pine-maildir-4.33 patch; but couldn't figure out how to configure Pine to access the Maildirs (namely due to lack of documentation on Larsson's patch, and his site seems to be down as well). I would be interested to hear of the patch you used and the configuration adjustments you made to Pine. By the way, I must say that I do not care for mutt. The interface is rather dirty (I don't mean its aesthetics) and the configuration rather cryptic. Maybe I just didn't devote enough time to it? Anyways, it's not a viable option. i use that same patch for pine 4.33. it appears to work much better than whatever i was using before. something with pine 4.10 i think. in pine's config i simply set inbox-path to the string: $MAIL /etc/profile.d/qmail.sh exists to set $MAIL (and $MAILDROP) properly. that profile file came with Bruce Guenter's qmail rpms (http://em.ca/~bruceg/qmail+patches/). typically $MAIL would look like: /home/user/Maildir/ (with the trailing slash). i've never used pine with imap, so i'm not sure how that works. i never cared for mutt either, although i never spent a huge amount of time trying to figure it out. my main issue with it is that i could never get it to sort my inbox properly (just normal sorting - by arrival time - how the files in the maildir are already sorted). it could be due to me having tried old version of mutt. -tcl.
Re: Pine for Maildir
tc lewis wrote: i use that same patch for pine 4.33. it appears to work much better than whatever i was using before. something with pine 4.10 i think. in pine's config i simply set inbox-path to the string: $MAIL /etc/profile.d/qmail.sh exists to set $MAIL (and $MAILDROP) properly. that profile file came with Bruce Guenter's qmail rpms (http://em.ca/~bruceg/qmail+patches/). typically $MAIL would look like: /home/user/Maildir/ (with the trailing slash). *chuckles* Sure enough, that worked. It even moves read messages from ~/Maildir/new to ~/Maildir/cur. Ah well. A little more info on this (for the archives if not for anyone presently dealing with it): - My $MAIL environment variable is not set because I did not use those particular RPMs for the install. To set it for your users, check out /etc/profile (just set the line with MAIL="/some/path/here" to MAIL="/home/$USER/Maildir"). NOTE: Apparently, you must set inbox-path as an absolute path (which means you can't set it to ~/Maildir because pine doesn't seem to recognize ~/ as /home/$USER/). This, obviously, will make root's Maildir inaccessible on 99% of Linux systems, to solve this, either make a symlink from /home/root to /root (or whatever root's home directory is) or make a /root/.pinerc file with the line inbox-path=/root/Maildir - You can set inbox-path for pine globally by editing /etc/pine.conf or you can force your users to use that inbox-path by editing /etc/pine.conf.fixed i've never used pine with imap, so i'm not sure how that works. Well, I've been devoting a couple of hours to understanding courier-imap in all of its intracacies and I'd say that your method is loads simpler yet just as reliable. -tcl. By the way, for those of you trying to obtain a copy of the file pine-maildir-4.33 to patch pine with, I realize Larrson's site is down so I have an alternate copy up at http://unix-web.triton.net/~ennui/pine-maildir-4.33 To apply the patch, just copy the file into the directory you extracted pine into and do `patch -p1 pine-maildir-4.33' -- Keith Network Engineer Triton Technologies, Inc.
Re: Procmail headaches
On Sun, Apr 15, 2001 at 03:20:10AM +0200, David Gmez wrote: The qmail-start script (the default one which comes with qmail) ? There are a set of possible start-up scripts in /var/qmail/boot. None are named qmail-start. qmail-start is a program in /var/qmail/bin. man qmail-start "qmail-start '|preline procmail' splogger qmail" Apparently your distribution or your chosen RPM is using .../boot/proc as the start-up script. to avoid a defaultdelivery action, without modifying the log stuff ?. I You can certainly use one of the other ones in .../boot or edit the one you currently have. Look at .../boot/home if you want delivery to a traditional Un*x mailbox named "Mailbox" in the user's home directory, or .../boot/maildir if you want delivery to a maildir named "Maildir" in the user's home directory. Tim
Many Thanks Guys!
Hello everyone... Well, I've figured out what my problem was, and how it occurred. Please keep this one for your files because it will happen again. I used to be able to do a stock qmail install when my GNATbox firewall had an inbound tunnel / alias for one domain: stpeters.sk.ca But then we added three more domains on my new Linux Mandrake server, and suddenly the old qmail setup didn't work. It didn't make sense that adding aliases on the GNATbox would cause the tcpserver to change, but IT DID. So I was right about adding my Inbound Tunnel and Outbound Mappings from the firewall to my problem report. I created an new tcp.smtp that matched : 207.195.105.60:allow,RELAYCLIENT="" 192.168.1.:allow,RELAYCLIENT="" where 207.195.105.60 = stpeterscollege.ca and 192.168.1. is my Private Service Network. So, my suspicion that somehow I'd turned the qmail setup around by adding the wildcard domains to rcpthosts was correct. All I've got now in rcpthosts is: stpeters.sk.ca stpeterscollege.ca LOCALHOST gecko.stpeterscollege.ca mail.stpeterscollege.ca And thanks to Johann! Now I know how to use .bashrc to change my user PATH and that pwd means "print working directory"! Happy Easter! br. kurt
