qmail-pop3d
After I test the qmail-smtpd and qmail-send is ok,it seems to me ok. I try to install qmail-pop3d and start this service. I add the run script in /var/qmail/supervise/qmail-pop3d I use the method to test the checkpasswd program, the response is ok. #!/bin/sh exec /usr/local/bin/softlimit -m 200 /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup sbs01.helka.com.hk /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 but I find a process: root 8461 0.0 0.0 00 ?Z11:17 0:00 [supervise defunction is it ok? I can't check the pop3 with email client. anything that I should install after enable qmail-pop3d?
Re: qmail-pop3d
On Mon, Aug 13, 2001 at 11:42:25AM -0400, qmail wrote: After I test the qmail-smtpd and qmail-send is ok,it seems to me ok. I try to install qmail-pop3d and start this service. I add the run script in /var/qmail/supervise/qmail-pop3d I use the method to test the checkpasswd program, the response is ok. #!/bin/sh exec /usr/local/bin/softlimit -m 200 /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup sbs01.helka.com.hk /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 but I find a process: root 8461 0.0 0.0 00 ?Z11:17 0:00 [supervise defunction is it ok? I can't check the pop3 with email client. anything that I should install after enable qmail-pop3d? I have two questions for you: 1. What is the output of 'svstat /service/*' ? 2. Is it just linewrap issues, or is 'run' really multilined without escape characters like that? -- Greg White
qmail-pop3d inbox messages limit
I have noticed that if a user has more than about 5500 messages in their inbox the server dies with the following error: -ERR unable to scan $HOME/Maildir I look at qmail-pop3d.c but couldn't see anything that would explain this. Any thoughts? Thanks, Alberto Alonso Marlabs Inc. http://www.marlabs.com Hosting Services http://hosting.marlabs.com
Re: qmail-pop3d inbox messages limit
On Wed, Aug 08, 2001 at 08:22:14AM -0500, Alberto Alonso wrote: I have noticed that if a user has more than about 5500 messages in their inbox the server dies with the following error: -ERR unable to scan $HOME/Maildir I look at qmail-pop3d.c but couldn't see anything that would explain this. Any thoughts? It ran out of memory, probably. The fix is in the archive. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: qmail-pop3d inbox messages limit
Peter van Dijk wrote: On Wed, Aug 08, 2001 at 08:22:14AM -0500, Alberto Alonso wrote: I have noticed that if a user has more than about 5500 messages in their inbox the server dies with the following error: -ERR unable to scan $HOME/Maildir I look at qmail-pop3d.c but couldn't see anything that would explain this. Any thoughts? It ran out of memory, probably. The fix is in the archive. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html Thanks, that did it. I keep forgetting that with qmail we use the softlimit for memory. Alberto Alonso Marlabs Inc. http://www.marlabs.com Hosting Services http://hosting.marlabs.com
qmail-pop3d and /var/spool/mail
I want to migrate my sendmail-server to qmail. I have to decide to use /var/spool/mail with |/usr/sbin/qmail-procmail to store the mails on the server. But the qmail-pop3-server doesn't work. I use this command-line for the server: tcpserver 0 110 /var/qmail/bin/qmail-popup servername /usr/bin/checkpassword /var/qmail/bin/qmail-pop3d /var/spool/mail But ther's always this error-message when I want to fetch the mails: -ERR unable to scan $HOME/Maildir So I try the pop3lite-server and then it works perfectly. Is this normal that the qmail-pop3d doesn't work with the /var/spool/mail directory or must I hack the code? What's the best solution? Use a other pop3-server!? Any ideas? Thnaks! Severin Olloz
Re: qmail-pop3d and /var/spool/mail
At 14:28 05.08.2001 +0200, Severin Olloz wrote: Any ideas? qmail-pop3d supports only maildir spools. use gnu-pop3d, qpopper or similar to pop your vms -- --/-/-- Lukas Beeler [EMAIL PROTECTED] ---\-\-- \ \ My HomePage: URL:http://www.projectdream.org / /
Re: qmail-pop3d and /var/spool/mail
On Sun, Aug 05, 2001 at 02:28:39PM +0200, Severin Olloz wrote: I have to decide to use /var/spool/mail with |/usr/sbin/qmail-procmail to store the mails on the server. But the qmail-pop3-server doesn't work. qmail-pop3d does not support any mail storage format asifr from Maildir. Either switch to maildir (you won't regret it) or use another pop3d. -- * 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-pop3d and /var/spool/mail
On Sun, Aug 05, 2001 at 02:28:39PM +0200, Severin Olloz wrote: I want to migrate my sendmail-server to qmail. I have to decide to use /var/spool/mail with |/usr/sbin/qmail-procmail to store the mails on the server. mbox or Maildir format? Both are perfectly possible in /var/spool/mail (we currently do Maildir in /var/spool/mail as well). If mbox: qmail-pop3d can't do it. If Maildir: get a checkpassword module that understands /var/spool/mail. I don't know if any are readily available. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
qmail-pop3d
Hi! I have a little problem with qmail-pop3d...I've been trying to set qmail-pop3d to work with supervise. Everything else works fine but qmail-pop3d. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. This is my /var/qmail/supervise/qmail-pop3d/run script: #!/bin/sh QMAILDUID=`/usr/bin/id -u qmaild` NOFILESGID=`/usr/bin/id -g qmaild` MAXPOP3=`cat /var/qmail/control/pop3concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 -c $MAXPOP3 -u $QMAILDUID -g $NOFILESGID 0 pop3 \ /var/qmail/bin/qmail-popup homer.rixtele.com \ /usr/local/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 What could possible be wrong? Joel
qmail-pop3d strange?
Hello tveryone. last four months, i have a very strange problem with qmail. every one/two week i look at server this situation: ---ps auxw--extract root 8093 0.0 0.1 1056 280 ?SJul24 0:00 /var/qmail/bin/qmail-popup ratel.ru /home/vpop mail/bin/vchkpw /var/qm root 8094 0.0 0.3 1728 896 ?SJul24 0:00 /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail -pop3d Maildir root 8097 0.0 0.1 1056 280 ?SJul24 0:00 /var/qmail/bin/qmail-popup ratel.ru /home/vpop mail/bin/vchkpw /var/qm root 8098 0.0 0.3 1728 896 ?SJul24 0:00 /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail -pop3d Maildir root 8102 0.0 0.1 1056 280 ?SJul24 0:00 /var/qmail/bin/qmail-popup ratel.ru /home/vpop mail/bin/vchkpw /var/qm root 8103 0.0 0.1 1056 280 ?SJul24 0:00 /var/qmail/bin/qmail-popup ratel.ru /home/vpop mail/bin/vchkpw /var/qm root 8104 0.0 0.3 1728 896 ?SJul24 0:00 /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail -pop3d Maildir root 8105 0.0 0.3 1728 896 ?SJul24 0:00 /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail -pop3d Maildir --- i.e. lot of this process. (great than in list, about 20-30 pair). in this state, server did not answer on the ping, and all services do not work propertly (timeout). ps auxw snap, got via crontab script. after 5/10 minits, system going in normal mode, and number of qmail process return to normal.. anybody has this bug? or plz, help, how i can diagnostic source of problem. qmail-pop3 log, does not contain any error message. -- Best regards, vlad mailto:[EMAIL PROTECTED]
Re: qmail-pop3d
what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
Re: qmail-pop3d
Hi They does'nt say anything, /var/log/qmail/qmail-pop3d/current is empty... - Original Message - From: Dushyanth Harinath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 26, 2001 11:05 AM Subject: Re: qmail-pop3d what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
Re: qmail-pop3d
did u follow lifewithqmail.org ..there must be something wrong in the start up script of qmail-pop3d regards dushyanth Hi They does'nt say anything, /var/log/qmail/qmail-pop3d/current is empty... - Original Message - From: Dushyanth Harinath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 26, 2001 11:05 AM Subject: Re: qmail-pop3d what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/ -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
RE: qmail-pop3d
Hi, It looks like you are trying to use the /var/qmail/supervise/qmail-smtpd/run script ? tray this instead. #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup \ homer.rixtele.com /usr/local/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 -Original Message- From: Joel Aasma [mailto:[EMAIL PROTECTED]] Sent: den 26 juli 2001 09:55 To: [EMAIL PROTECTED] Subject: qmail-pop3d Hi! I have a little problem with qmail-pop3d...I've been trying to set qmail-pop3d to work with supervise. Everything else works fine but qmail-pop3d. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. This is my /var/qmail/supervise/qmail-pop3d/run script: #!/bin/sh QMAILDUID=`/usr/bin/id -u qmaild` NOFILESGID=`/usr/bin/id -g qmaild` MAXPOP3=`cat /var/qmail/control/pop3concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 -c $MAXPOP3 -u $QMAILDUID -g $NOFILESGID 0 pop3 \ /var/qmail/bin/qmail-popup homer.rixtele.com \ /usr/local/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 What could possible be wrong? Joel
Re: qmail-pop3d
worked fine! thanks alot! Regards Joel - Original Message - From: Per-fredrik Pollnow (EPK) [EMAIL PROTECTED] To: 'Joel Aasma' [EMAIL PROTECTED] Cc: Qmail Mailing list (E-mail) [EMAIL PROTECTED] Sent: Thursday, July 26, 2001 12:55 PM Subject: RE: qmail-pop3d Hi, It looks like you are trying to use the /var/qmail/supervise/qmail-smtpd/run script ? tray this instead. #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup \ homer.rixtele.com /usr/local/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 -Original Message- From: Joel Aasma [mailto:[EMAIL PROTECTED]] Sent: den 26 juli 2001 09:55 To: [EMAIL PROTECTED] Subject: qmail-pop3d Hi! I have a little problem with qmail-pop3d...I've been trying to set qmail-pop3d to work with supervise. Everything else works fine but qmail-pop3d. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. This is my /var/qmail/supervise/qmail-pop3d/run script: #!/bin/sh QMAILDUID=`/usr/bin/id -u qmaild` NOFILESGID=`/usr/bin/id -g qmaild` MAXPOP3=`cat /var/qmail/control/pop3concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 -c $MAXPOP3 -u $QMAILDUID -g $NOFILESGID 0 pop3 \ /var/qmail/bin/qmail-popup homer.rixtele.com \ /usr/local/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21 What could possible be wrong? Joel
Re: qmail-pop3d
hi again
darn! it almost worked fine :/
The only thing is that when i do a /etc/init.d/qmail stop , pop3 is'nt
stopped.
here is my /etc/init.d/qmail script:
#!/bin/sh
# For Red Hat chkconfig
# chkconfig: - 30 80
# description: the qmail MTA
PATH=/var/qmail/bin:/bin:/usr/bin:/usr/local/bin:/usr/local/sbin
export PATH
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
case $1 in
start)
echo Starting qmail
if svok /service/qmail-send ; then
svc -u /service/qmail-send
else
echo qmail-send service not running
fi
if svok /service/qmail-smtpd ; then
svc -u /service/qmail-smtpd
else
echo qmail-smtpd service not running
fi
if svok /service/qmail-pop3d ; then
svc -u /service/qmail-pop3d
else
echo qmail-pop3d service not running
fi
if [ -d /var/lock/subsys ]; then
touch /var/lock/subsys/qmail
fi
;;
stop)
echo Stopping qmail...
echo qmail-smtpd
svc -d /service/qmail-smtpd
echo qmail-send
svc -d /service/qmail-send
echo qmail-pop3d
svc -d /service/qmail-pop3d
if [ -f /var/lock/subsys/qmail ]; then
rm /var/lock/subsys/qmail
fi
;;
stat)
svstat /service/qmail-send
svstat /service/qmail-send/log
svstat /service/qmail-smtpd
svstat /service/qmail-smtpd/log
svstat /service/qmail-pop3d
svstat /service/qmail-pop3d/log
qmail-qstat
;;
doqueue|alrm|flush)
echo Sending ALRM signal to qmail-send.
svc -a /service/qmail-send
;;
queue)
qmail-qstat
qmail-qread
;;
reload|hup)
echo Sending HUP signal to qmail-send.
svc -h /service/qmail-send
;;
pause)
echo Pausing qmail-send
svc -p /service/qmail-send
echo Pausing qmail-smtpd
svc -p /service/qmail-smtpd
echo Pausing qmail-pop3d
svc -p /service/qmail-pop3d
;;
cont)
echo Continuing qmail-send
svc -c /service/qmail-send
echo Continuing qmail-smtpd
svc -c /service/qmail-smtpd
echo Continuing qmail-pop3d
svc -c /service/qmail-pop3d
;;
restart)
echo Restarting qmail:
echo * Stopping qmail-smtpd.
svc -d /service/qmail-smtpd
echo * Stopping qmail-pop3d.
svc -d /service/qmail-pop3d
echo * Sending qmail-send SIGTERM and restarting.
svc -t /service/qmail-send
echo * Restarting qmail-smtpd.
svc -u /service/qmail-smtpd
echo * Restartng qmail-pop3d.
;;
cdb)
tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp /etc/tcp.smtp
chmod 644 /etc/tcp.smtp.cdb
echo Reloaded /etc/tcp.smtp.
;;
help)
cat HELP
stop -- stops mail service (smtp connections refused, nothing goes out)
start -- starts mail service (smtp connection accepted, mail can go out)
pause -- temporarily stops mail service (connections accepted, nothing
leaves)
cont -- continues paused mail service
stat -- displays status of mail service
cdb -- rebuild the tcpserver cdb file for smtp
restart -- stops and restarts smtp, sends qmail-send a TERM restarts it
doqueue -- sends qmail-send ALRM, scheduling queued messages for delivery
reload -- sends qmail-send HUP, rereading locals and virtualdomains
queue -- shows status of queue
alrm -- same as doqueue
flush -- same as doqueue
hup -- same as reload
HELP
;;
*)
echo Usage: $0
{start|stop|restart|doqueue|flush|reload|stat|pause|cont|cdb|queue|help}
exit 1
;;
esac
exit 0
and the /var/qmail/supervise/qmail-pop3d/run is the one you posted
regards
joel
qmail-pop3d || tcpserver (sometimes timing out?)
Howdy, searching the archives i had not come across anything that seem'd to match my problem (sorry if i missed it) I've been using qmail with tcpserver for sometime now, and have came across a problem that is puzzeling me concerning users (dialups) not being able to get past a certain number of emails when receiving. Instead getting a timeout message. These users sometimes would have a lot of mail in the $HOME/Maildir/cur even when they claim they haven't been able to download it yet. We have ran across users who have had this problem, without having a large quantity of mail in cur/ or new/ as well, but not as frequent. Users who have a lot of mail, do not have any messages over 5k. (which is what i first thought) This happens sparatically, and I have been unable to recreate the error myself. But co-workers claimed they too have had it happen to them, as well as an above-average # of complaints. rc.qmail: /usr/local/bin/tcpserver -R -H 0 110 /var/qmail/bin/qmail-popup mail /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir I have checked, and rechecked the portmasters which users connect to. 3ms ping across the network. The area does have bad phone lines (thanks sprint), but I can't see how this would affect a user who is connected@46000 Would dirty phone-lines cause this much problems? Does this sound familiar to anyone?
Re: qmail-pop3d || tcpserver (sometimes timing out?)
rc.qmail: /usr/local/bin/tcpserver -R -H 0 110 /var/qmail/bin/qmail-popup mail /bin/checkpassword /var/qmail/bin/qmail-pop3d Try using tcpserver -l -R -H ... It might help. -Kittiwat
qmail-pop3d hanging email retrieval
This is going to be a long message, but please stick with me. This problem is driving me nuts! In summary, I am having problems with emails getting stuck when fetched from qmail-pop3d. They are almost always attached MS Word documents. They aren't necessarily long, I've got 32k messages that do it and 1M messages. I'm running on kernel 2.0.39, qmail 1.03, daemontools 0.70, ucspi-tcp 0.88 and a slightly modified checkpassword to handle pop accounts in my virtual domains. This system has been in place since 1999 and has always had an occasional problem but recently I am getting 1 or 2 messages a week that are sticking. I have 2 different cases where this happens. The first is when my home system, using fetchmail, is downloading messages. If the home machine's MTU/MRU is set to 1500 or 1480 the messages in question will hang. If I change the MRU to 576 then they pass through. I don't know if any messages hang using 576, but I haven't seen any. My MTU/MRU has to be set to 1500 so that we can get to certain webpages, so leaving it at 576 is not an option. This is all via a dialup diald/ppp session to my ISP (the same one that the webserver is colocated at). The other case is from work. I handle all their email and webhosting. They are connected to the net via direcPC, a win95 machine running winRoute Pro and the local lan. The upstream side is a modem connection to the same ISP where the webserver is located. In this case I cannot change the MTU/MRU and who knows what direcPC is doing as packets pass through their system. To fix this case I move the mail to the web directory and download it using Explorer. When we use Agent 1.8 on the lan to download messages from the webserver it will exhibit the same 'hanging' that I see with the home system. In both cases I can watch the connection with 'snort -v -i eth0 port 110' and the connection just stops cold partway through the message. I've upgraded the system's kernel from 2.0.36 to 2.0.29 and updated all the qmail related software but it is still happening. I'm running the qmail services using the methods described in 'Life with Qmail'. I've only found a few references to similar problems when searching and no solutions. Someone else must have run into this before! Thanks for any help, Brian -- Brian C. Lane - Linux Programmer/Consultant/Writer www.brianlane.com www.nexuscomputing.com Liberty Privacy 'zine Editor www.libertynews.org I made wine out of raisins so I wouldn't have to wait for it to age. -- Stephen Wright
Re: qmail-pop3d hanging email retrieval
Brian Lane [EMAIL PROTECTED] wrote: In summary, I am having problems with emails getting stuck when fetched from qmail-pop3d. They are almost always attached MS Word documents. They aren't necessarily long, I've got 32k messages that do it and 1M messages. I'm running on kernel 2.0.39, qmail 1.03, daemontools 0.70, ucspi-tcp 0.88 and a slightly modified checkpassword to handle pop accounts in my virtual domains. This system has been in place since 1999 and has always had an occasional problem but recently I am getting 1 or 2 messages a week that are sticking. I assume you mean Linux kernel 2.0.39? What patches? What vendor's kernel? Or did you compile from a Linus tarball? I have 2 different cases where this happens. The first is when my home system, using fetchmail, is downloading messages. If the home machine's MTU/MRU is set to 1500 or 1480 the messages in question will hang. If I change the MRU to 576 then they pass through. I don't know if any messages hang using 576, but I haven't seen any. This smells strongly of a kernel TCP/IP bug. qmail-pop3d knows nothing of packets or MTU -- it just sees a couple of fds. Linux has had a couple of real bad bugs like this in the past; a long-standing one wasn't fixed until very recently in 2.2.19. You could be running into this bug. I've only found a few references to similar problems when searching and no solutions. Someone else must have run into this before! Linux 2.0.3x (where x 6) doesn't get tested nearly as widely as older or newer versions. Is there any reason you can't upgrade this system to 2.2.19 or better? Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-pop3d hanging email retrieval
On Fri, Jul 06, 2001 at 09:34:39PM -0600, Charles Cazabon wrote: Brian Lane [EMAIL PROTECTED] wrote: In summary, I am having problems with emails getting stuck when fetched from qmail-pop3d. They are almost always attached MS Word documents. They aren't necessarily long, I've got 32k messages that do it and 1M messages. I'm running on kernel 2.0.39, qmail 1.03, daemontools 0.70, ucspi-tcp 0.88 and a slightly modified checkpassword to handle pop accounts in my virtual domains. This system has been in place since 1999 and has always had an occasional problem but recently I am getting 1 or 2 messages a week that are sticking. I assume you mean Linux kernel 2.0.39? What patches? What vendor's kernel? Or did you compile from a Linus tarball? Sorry, Linux 2.0.39 on what used to be a RH 5.2 system but has been heavily upgraded over the years. The kernel itself is from an un-patched tarball. I have 2 different cases where this happens. The first is when my home system, using fetchmail, is downloading messages. If the home machine's MTU/MRU is set to 1500 or 1480 the messages in question will hang. If I change the MRU to 576 then they pass through. I don't know if any messages hang using 576, but I haven't seen any. This smells strongly of a kernel TCP/IP bug. qmail-pop3d knows nothing of packets or MTU -- it just sees a couple of fds. Linux has had a couple of real bad bugs like this in the past; a long-standing one wasn't fixed until very recently in 2.2.19. You could be running into this bug. I'm afraid that its something like that. I was hoping my upgrade to 2.0.39 would fix any odd kernel bugs. I've been avoiding a complete upgrade because it means a total system rebuild and I really hate doing that. It looks like a rebuild is probably in the future, unless anyone has a better suggestion. Thanks, Brian -- Brian C. Lane - Linux Programmer/Consultant/Writer www.brianlane.com www.nexuscomputing.com Liberty Privacy 'zine Editor www.libertynews.org In every country and in every age, the priest has been hostile to liberty. He is always in alliance with the despot, abetting his abuses in return for protection to his own. -- Thomas Jefferson, 1814
qmail pop3d startup
-- Hello all: I followed LWQ's directions for setting up qmail-pop3d: it wont start up and i get this in my messages log: Jul 3 10:37:44 mckenna qmail: Starting qmail: done Jul 3 10:37:44 mckenna qmail: qmail-pop3d service not running Jul 3 10:37:44 mckenna qmail: /etc/rc3.d/S80qmail: svok: command not found Jul 3 10:37:44 mckenna rc: Starting qmail: succeeded Ju ==end of log== here are the directions for adding to the qmail startup script: (btw: i have zero shell-scripting experience) 7. Add the following to qmailctl's start section: if svok /service/qmail*pop3d ; then svc *u /service/qmail*pop3d else echo qmail*pop3d service not running fi i am stumped... did i spell something wrong? TIA, david
Re: qmail pop3d startup
i think my problem is that i did not install daemontools... whoops... so when i try to make daemontools: [root@mckenna daemontools-0.70]# make ./compile tai64nlocal.c tai64nlocal.c: In function `main': tai64nlocal.c:54: warning: assignment makes pointer from integer without a cast tai64nlocal.c:55: dereferencing pointer to incomplete type tai64nlocal.c:56: dereferencing pointer to incomplete type tai64nlocal.c:57: dereferencing pointer to incomplete type tai64nlocal.c:58: dereferencing pointer to incomplete type tai64nlocal.c:59: dereferencing pointer to incomplete type tai64nlocal.c:60: dereferencing pointer to incomplete type make: *** [tai64nlocal.o] Error 1 should i nuke this install? if so how do i? david -- Hello all: I followed LWQ's directions for setting up qmail-pop3d: it wont start up and i get this in my messages log: Jul 3 10:37:44 mckenna qmail: Starting qmail: done Jul 3 10:37:44 mckenna qmail: qmail-pop3d service not running Jul 3 10:37:44 mckenna qmail: /etc/rc3.d/S80qmail: svok: command not found Jul 3 10:37:44 mckenna rc: Starting qmail: succeeded Ju ==end of log== here are the directions for adding to the qmail startup script: (btw: i have zero shell-scripting experience) 7. Add the following to qmailctl's start section: if svok /service/qmail*pop3d ; then svc *u /service/qmail*pop3d else echo qmail*pop3d service not running fi i am stumped... did i spell something wrong? TIA, david --
Re: qmail pop3d startup
I got the same thing... it *probibly* a header problem (not sure... looked good to me). just comment out the lines and recompile... its not a critical program. Just edit the tai64nlocal.c and put a double hash '//' (no quotes) on the lines listed and it will compile install. -- Paul Farber Farber Technology [EMAIL PROTECTED] Ph 570-628-5303 Fax 570-628-5545 On Wed, 4 Jul 2001, David Dahl wrote: i think my problem is that i did not install daemontools... whoops... so when i try to make daemontools: [root@mckenna daemontools-0.70]# make ./compile tai64nlocal.c tai64nlocal.c: In function `main': tai64nlocal.c:54: warning: assignment makes pointer from integer without a cast tai64nlocal.c:55: dereferencing pointer to incomplete type tai64nlocal.c:56: dereferencing pointer to incomplete type tai64nlocal.c:57: dereferencing pointer to incomplete type tai64nlocal.c:58: dereferencing pointer to incomplete type tai64nlocal.c:59: dereferencing pointer to incomplete type tai64nlocal.c:60: dereferencing pointer to incomplete type make: *** [tai64nlocal.o] Error 1 should i nuke this install? if so how do i? david -- Hello all: I followed LWQ's directions for setting up qmail-pop3d: it wont start up and i get this in my messages log: Jul 3 10:37:44 mckenna qmail: Starting qmail: done Jul 3 10:37:44 mckenna qmail: qmail-pop3d service not running Jul 3 10:37:44 mckenna qmail: /etc/rc3.d/S80qmail: svok: command not found Jul 3 10:37:44 mckenna rc: Starting qmail: succeeded Ju ==end of log== here are the directions for adding to the qmail startup script: (btw: i have zero shell-scripting experience) 7. Add the following to qmailctl's start section: if svok /service/qmail*pop3d ; then svc *u /service/qmail*pop3d else echo qmail*pop3d service not running fi i am stumped... did i spell something wrong? TIA, david
Re: qmail pop3d startup
Title: Re: qmail pop3d startup i am a moron! i am talking to myself... from the qmail list archives== Mike Jackson wrote: Hi, Box is Mandrake 8.0 final, kernel 2.4.3-20mdk. I get the following error when trying to compile daemontools. It also happened to me on a Redhat 7.1 box. I think it's something gcc version 2.96 2731 related. Somebody please help me patch this file so it will compile. Mr. Jackson - this apparently affects Linux 2.4.x kernels. The fix (also applicable to a similar error when compiling the clockspeed package) is to change sys/time.h on line 2 of the problem file to time.h. Hope this helps. -d - -- David Talkington http://www.spotnet.org i think my problem is that i did not install daemontools... whoops... so when i try to make daemontools: [root@mckenna daemontools-0.70]# make ./compile tai64nlocal.c tai64nlocal.c: In function `main': tai64nlocal.c:54: warning: assignment makes pointer from integer without a cast tai64nlocal.c:55: dereferencing pointer to incomplete type tai64nlocal.c:56: dereferencing pointer to incomplete type tai64nlocal.c:57: dereferencing pointer to incomplete type tai64nlocal.c:58: dereferencing pointer to incomplete type tai64nlocal.c:59: dereferencing pointer to incomplete type tai64nlocal.c:60: dereferencing pointer to incomplete type make: *** [tai64nlocal.o] Error 1 should i nuke this install? if so how do i? david -- Hello all: I followed LWQ's directions for setting up qmail-pop3d: it wont start up and i get this in my messages log: Jul 3 10:37:44 mckenna qmail: Starting qmail: done Jul 3 10:37:44 mckenna qmail: qmail-pop3d service not running Jul 3 10:37:44 mckenna qmail: /etc/rc3.d/S80qmail: svok: command not found Jul 3 10:37:44 mckenna rc: Starting qmail: succeeded Ju ==end of log== here are the directions for adding to the qmail startup script: (btw: i have zero shell-scripting experience) 7. Add the following to qmailctl's start section: if svok /service/qmail*pop3d ; then svc *u /service/qmail*pop3d else echo qmail*pop3d service not running fi i am stumped... did i spell something wrong? TIA, david -- --
Is it possible to use qmail-pop3d with mailbox format
Hi all, I am using qmail-1.03-30 and its working fine as far as SMTP connection is concern. But i am using ipop3d for for pop daemon, which is very slow. Is it possible to use qmail-pop3d with Mailbox format ??? Regards Lokesh
Re: Is it possible to use qmail-pop3d with mailbox format
[EMAIL PROTECTED] writes: Hi all, I am using qmail-1.03-30 and its working fine as far as SMTP connection is concern. But i am using ipop3d for for pop daemon, which is very slow. Is it possible to use qmail-pop3d with Mailbox format ??? No. Switch to Maildir format. It's much more managable. You can remove unwanted emails from a user's mailbox (My email download is taking forever. Do I have a multi-megabyte email? Could you delete it?). You can insert bulletins just by symlinking to them. You can delete emails which haven't been read for a certain period of time. And it's reliable over NFS, which Mailbox isn't. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | #exclude windows.h Potsdam, NY 13676-3213 | +1 315 268 9201 FAX |
qmail-pop3d
Hi.
I am new in qmail. Can anyone help me ?
Problem: I could not access my email dir using Outlook Express (OE)
via pop3 port. (110)
I have installed and configured qmail smtpd successfully. I (or
anyone else) can send and received e-mail locally and remotely. No
problemo. I run qmail under tcpserver.
I also tried to run its /var/qmail/bin/qmail-pop3d using xinetd.
Below is my configuration:-
$ vi /etc/xinetd.d/ipop3
6 service pop3
7 {
8 disable = no
9 socket_type = stream
10 wait= no
11 user= root
12 server = /usr/local/bin/tcpserver 0
110 \
13 /var/qmail/bin/qmail-popup mail.my-
domainname \
14 /bin/checkpassword /var/qmail/bin/qmail-pop3d
Maildir
15 log_on_success += USERID
16 log_on_failure += USERID
17 }
my-domainname is a valid domain (with another name).
The defaultdelivery is ./Maildir, which means that my email
directories are located in:-
/home/mail/poptest100/Maildir/
Below is the out of /var/log/messages:-
May 31 11:23:52 mail xinetd[26929]: Exiting...
May 31 11:23:52 mail xinetd: xinetd shutdown succeeded
May 31 11:23:53 mail xinetd[27013]: attribute server expects 1 values
and 4 values were specified [line=12]
May 31 11:23:53 mail xinetd[27013]: Bad operator for
attribute: /var/qmail/bin/qmail-popup [line=13]
May 31 11:23:53 mail xinetd[27013]: finger disabled, removing
May 31 11:23:53 mail xinetd[27013]: imap disabled, removing
May 31 11:23:53 mail xinetd[27013]: imaps disabled, removing
May 31 11:23:53 mail xinetd[27013]: swat disabled, removing
May 31 11:23:53 mail xinetd[27013]: pop3s disabled, removing
May 31 11:23:53 mail xinetd[27013]: linuxconf disabled, removing
May 31 11:23:53 mail xinetd[27013]: pop2 disabled, removing
May 31 11:23:53 mail xinetd[27013]: xinetd Version 2.1.8.9pre9
started with
May 31 11:23:53 mail xinetd[27013]: libwrap
May 31 11:23:53 mail xinetd[27013]: options compiled in.
May 31 11:23:53 mail xinetd[27013]: Started working: 2 available
services
May 31 11:23:56 mail xinetd: xinetd startup succeeded
May 31 11:24:54 mail spop3d[27532]: user poptest100 authenticated
May 31 11:24:54 mail spop3d[27532]: session ended for user poptest100
--
When I used my OE, I can send email to my other remote account. But
my OE could not received email from my mail.my-domainname.
I think the problem is either in:-
a) accessing the email directory (./Maildir) itself. I have checked
the permission and found it is okay. Owner (poptest100) can read and
execute directories and subdirectories under its own home directory.
or
b) my xinetd.d/ipop3 account setup is not right. I do not know about
this one. I am also new in xinetd.
Can anyone give me any suggestion ? I think I do not have to
reinstall my redhat 7.0 and qmail from stratch. I am nearly finishing
my qmail installation.
Just FYI, before this I am using sendmail and I have no problem using
my OE to access my email via pop3.
Thank you in advance
Re: qmail-pop3d
On Thu, May 31, 2001 at 06:19:22AM -, Deen wrote: Hi. I am new in qmail. Can anyone help me ? 12 server = /usr/local/bin/tcpserver 0 110 \ 13 /var/qmail/bin/qmail-popup mail.my- domainname \ 14 /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 15 log_on_success += USERID 16 log_on_failure += USERID 17 } Here you start one tcpwrapper (tcpserver) by another. No can do that! Use tcpserver _or_ xinetd. Not both. -- Grtz, Arjen.
Re: qmail-pop3d
On Thu, May 31, 2001 at 06:19:22AM -, Deen wrote: Hi. I am new in qmail. Can anyone help me ? Problem: I could not access my email dir using Outlook Express (OE) via pop3 port. (110) I have installed and configured qmail smtpd successfully. I (or anyone else) can send and received e-mail locally and remotely. No problemo. I run qmail under tcpserver. I also tried to run its /var/qmail/bin/qmail-pop3d using xinetd. Below is my configuration:- tcpserver is a replacement for inetd, xinetd CO. Which means you shouldn't run both tcpserver and xinetd. Choose one of them and things will probably work much better -- I recommend tcpserver. Jörgen
Re: qmail-pop3d - thanks
Hi Arjen van Drie, J=F6rgen_Perss Thanks to both of you. I have used the tcpserver instead. However, I am still not satisfied. (no offence to both of you). Last time, when I was using sendmail, I used aliases as forwarding, so that I do not have to create home dir for each pop users. I found a doc written by Paul Gregg title Single-UID based POP3 box HOWTO. (I don't remember the URL coz' I got a hard copy). Has anyone successfully implemented his HOWTO yet ? There are things that I do not understand in his HOWTO.
Re: qmail-pop3d - thanks
Thank you Arjen van Drie J=F6rgen_Perss. I have successfully access the pop3 under tcpserver. I don't know much about tcpserver tough.
Re: qmail-pop3d - thanks
Thank you Arjen van Drie J=F6rgen_Perss. I have successfully access the pop3 under tcpserver. I don't know much about tcpserver tough.
Re: qmail-pop3d - thanks
Thank you Arjen van Drie J=F6rgen_Perss. I have successfully access the pop3 under tcpserver. I don't know much about tcpserver tough.
Re: qmail-pop3d - thanks
On Thu, May 31, 2001 at 08:11:19AM -, Deen wrote: Hi Arjen van Drie, J=F6rgen_Perss Thanks to both of you. I have used the tcpserver instead. However, I am still not satisfied. (no offence to both of you). Last time, when I was using sendmail, I used aliases as forwarding, so that I do not have to create home dir for each pop users. Forwarding mail has nothing to do with pop3d nor with tcpserver. Anyway, there are many ways to forward mail under qmail. Take a look at fastforward[1], it might be what you are looking for. Jörgen [1] http://cr.yp.to/fastforward.html
Re: qmail-pop3d - thanks
Deen [EMAIL PROTECTED] wrote: I found a doc written by Paul Gregg title Single-UID based POP3 box HOWTO. (I don't remember the URL coz' I got a hard copy). Has anyone successfully implemented his HOWTO yet ? There are things that I do not understand in his HOWTO. Various people have implemented single-UID POP3/IMAP virtual domains for qmail. vmailmgr does this. I'm not sure if that's quite what you mean. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: qmail-pop3d and /var/spool/mail or NO /HOME/$USER
Charles Olds [EMAIL PROTECTED] wrote: My goal is: Install qmail to work with virtual users. (i.e. No account in /etc/passwd. No /home/user. Mail delivered to /var/spool/mail.) You're limiting your options here by insisting on mbox format and /var/spool/mail. Much of the better software intended to be used with qmail uses Maildir format, and storage outside of /var/spool/mail . I have downloaded and installed qmail, tcpserver, qmailadmin, etc.. Everything looks good and runs except qmail-pop3d does not work with virtual users. When trying to retrieve mail I get the message No /HOME/$USER directory... Please recommend a POP3 server that will work with qmail and allow mail to be retrieved from /var/spool/mail. I'd personally recommend vmailmgr for virtual domain setups. However, it does necessitate Maildir storage (well, mostly) and at least one system account per virtual domain. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
qmail-pop3d advice ( migrate to vpopmail ? )
Hi all, I have a server which has about 50.000 e-mail accounts. POP3 concurrency is set to 150 and timeout to 90 seconds. A couple of days ago, my users started to feel a huge delay in getting their messages via POP and sometimes, they even cannot connect. I checked the number of simultaneous number of connections and is not close to 150. Of course, concurrency increased a little bit ( around 100 ) in the past few days, but it didn't reach the limit yet. I think my machine is on its knees right now :((, but I cannot afford to have a better hardware at this moment. What can I do to improve performance ? ( I mean software performance... ). The migrating to vpopmail would help ? What about mysql to authenticate users ? Thanks Renato - Brazil P.S. I'm using qmail+vmailmgr, so I have thousands of passwd.cdb files...
Re: qmail-pop3d advice ( migrate to vpopmail ? )
Renato [EMAIL PROTECTED] wrote: Hi all, Don't post a new question by replying to an existing thread. This messes up the threading in our MUAs and in the list archives. As for your problem: it's the absolute #1 most frequently asked question. It's in the FAQs, it's in the list archives hundreds of times, and its even in one mailing list member's .sig. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
qmail-pop3d and /var/spool/mail or NO /HOME/$USER
My goal is: Install qmail to work with virtual users. (i.e. No account in /etc/passwd. No /home/user. Mail delivered to /var/spool/mail.) I have downloaded and installed qmail, tcpserver, qmailadmin, etc.. Everything looks good and runs except qmail-pop3d does not work with virtual users. When trying to retrieve mail I get the message No /HOME/$USER directory... Please recommend a POP3 server that will work with qmail and allow mail to be retrieved from /var/spool/mail. Many thanks in advance. Charles Olds
Re: qmail-pop3d and /var/spool/mail or NO /HOME/$USER
I can certainly understand not using /etc/passwd but Why not maildirs?? I would really recommend vpopmail or vwhatever the name of that package I can't seem to remember right now ? qmail-pop3d only is used for Maildirs (not the virtual user problem) other poppers are availible, check the qmail page. - Original Message - From: Charles Olds [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 8:44 AM Subject: qmail-pop3d and /var/spool/mail or NO /HOME/$USER My goal is: Install qmail to work with virtual users. (i.e. No account in /etc/passwd. No /home/user. Mail delivered to /var/spool/mail.) I have downloaded and installed qmail, tcpserver, qmailadmin, etc.. Everything looks good and runs except qmail-pop3d does not work with virtual users. When trying to retrieve mail I get the message No /HOME/$USER directory... Please recommend a POP3 server that will work with qmail and allow mail to be retrieved from /var/spool/mail. Many thanks in advance. Charles Olds
Re: qmail-pop3d and /var/spool/mail or NO /HOME/$USER
On 20 May 2001, at 20:44, Charles Olds wrote: [...] Please recommend a POP3 server that will work with qmail and allow mail to be retrieved from /var/spool/mail. Try qpopper. http://www.eudora.com/qpopper/ It's actually mentioned in 'Life with qmail . Dean Dean Staff Protus IP Solutions 210 - 2379 Holly Lane Ottawa, ON K1V 7P2 Canada 613-733- ex 546 Fax 613-248-4553 e-mail: [EMAIL PROTECTED] Web: http://www.protus.com
Re: Using vchkpw (vpopmail) with qmail-pop3d?
Steven Katz [EMAIL PROTECTED] wrote: I'm trying to get the smtp after pop authentication part of vpopmail to work. I followed the LWQ instructions to install qmail and I'm using qmail-pop3d. Where should the below startup line for vchkpw be placed? In qmail-pop3d/run. See: http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223 -Dave
Using vchkpw (vpopmail) with qmail-pop3d?
Excellent list people, I'm trying to get the smtp after pop authentication part of vpopmail to work. I followed the LWQ instructions to install qmail and I'm using qmail-pop3d. Where should the below startup line for vchkpw be placed? Thanks! Steven 12. How to use vchkpw with qmail-pop3d server Here is a sample startup line for qmail-pop3d and vchkpw env - PATH=/var/qmail/bin:/usr/local/bin \ tcpserver -H -R 0 pop-3 \ /var/qmail/bin/qmail-popup your.domain.com \ /home-dir-of-vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir
RE: qmail-pop3d not working?
Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while pop was working) and got: qmail-pop3d: up (pid 598) 1420 seconds qmail-send: up (pid 594) 1420 seconds qmail-smtpd: up (pid 595) 1420 seconds qmail-pop3d/log: up (pid 28975) 0 seconds qmail-send/log: up (pid 596) 1420 seconds qmail-smtpd/log: up (pid 599) 1420 seconds Then I did it again (when pop stopped working) and got: qmail-pop3d: up (pid 598) 1678 seconds qmail-send: up (pid 594) 1678 seconds qmail-smtpd: up (pid 595) 1678 seconds qmail-pop3d/log: up (pid 26225) 0 seconds qmail-send/log: up (pid 596) 1678 seconds qmail-smtpd/log: up (pid 599) 1678 seconds Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps increasing, even after it stops working. However, doing 'ps auxw | grep pop3' while pop is working (up to 15 minutes after rebooting) gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma But doing it again when pop stops working gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 4454 0.0 0.6 1344 516 ?S09:17 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma There does seem to be a connection to the second instance of tcpserver. How can I find why and where the second tcpserver instance is being initiated? Thanks again, everyone. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
Re: qmail-pop3d not working?
The zero seconds for qmail-pop3d/log is your problem. The logging output of qmail-pop3d is ultimately filling up the pipe buffer and then wedging since the pipe is never drained by qmail-pop3d/log. The zero seconds is telling you that qmail-pop3d/log is repeatedly being started and is exiting immediately. You need to work out why that is. 1. Is qmail-pop3d/log/run executable? 2. What does it have in it exactly? Is the script correct? 3. What happens if you run it manually - what output do you get? Regards. On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote: Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while pop was working) and got: qmail-pop3d: up (pid 598) 1420 seconds qmail-send: up (pid 594) 1420 seconds qmail-smtpd: up (pid 595) 1420 seconds qmail-pop3d/log: up (pid 28975) 0 seconds qmail-send/log: up (pid 596) 1420 seconds qmail-smtpd/log: up (pid 599) 1420 seconds Then I did it again (when pop stopped working) and got: qmail-pop3d: up (pid 598) 1678 seconds qmail-send: up (pid 594) 1678 seconds qmail-smtpd: up (pid 595) 1678 seconds qmail-pop3d/log: up (pid 26225) 0 seconds qmail-send/log: up (pid 596) 1678 seconds qmail-smtpd/log: up (pid 599) 1678 seconds Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps increasing, even after it stops working. However, doing 'ps auxw | grep pop3' while pop is working (up to 15 minutes after rebooting) gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma But doing it again when pop stops working gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 4454 0.0 0.6 1344 516 ?S09:17 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma There does seem to be a connection to the second instance of tcpserver. How can I find why and where the second tcpserver instance is being initiated? Thanks again, everyone. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
RE: qmail-pop3d not working?
Sorry, I do have /var/qmail/supervise/qmail-pop3d/log/run (with permissions: -rw-rw-r--). I'll fix that and see what happens. It looks like: #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \ /var/log/qmail/pop3d Steven -Original Message- From: Steven Katz [EMAIL PROTECTED] Sent: Friday, April 27, 2001 10:24 AM To: [EMAIL PROTECTED] Subject: RE: qmail-pop3d not working? Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while pop was working) and got: qmail-pop3d: up (pid 598) 1420 seconds qmail-send: up (pid 594) 1420 seconds qmail-smtpd: up (pid 595) 1420 seconds qmail-pop3d/log: up (pid 28975) 0 seconds qmail-send/log: up (pid 596) 1420 seconds qmail-smtpd/log: up (pid 599) 1420 seconds Then I did it again (when pop stopped working) and got: qmail-pop3d: up (pid 598) 1678 seconds qmail-send: up (pid 594) 1678 seconds qmail-smtpd: up (pid 595) 1678 seconds qmail-pop3d/log: up (pid 26225) 0 seconds qmail-send/log: up (pid 596) 1678 seconds qmail-smtpd/log: up (pid 599) 1678 seconds Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps increasing, even after it stops working. However, doing 'ps auxw | grep pop3' while pop is working (up to 15 minutes after rebooting) gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma But doing it again when pop stops working gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 4454 0.0 0.6 1344 516 ?S09:17 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma There does seem to be a connection to the second instance of tcpserver. How can I find why and where the second tcpserver instance is being initiated? Thanks again, everyone. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
RE: qmail-pop3d not working?
POP instantly started working once I fixed the perms! Thanks! Steven -Original Message- From: Steven Katz [EMAIL PROTECTED] Sent: Friday, April 27, 2001 11:08 AM To: [EMAIL PROTECTED] Subject: RE: qmail-pop3d not working? Sorry, I do have /var/qmail/supervise/qmail-pop3d/log/run (with permissions: -rw-rw-r--). I'll fix that and see what happens. It looks like: #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \ /var/log/qmail/pop3d Steven -Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Friday, April 27, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? The zero seconds for qmail-pop3d/log is your problem. The logging output of qmail-pop3d is ultimately filling up the pipe buffer and then wedging since the pipe is never drained by qmail-pop3d/log. The zero seconds is telling you that qmail-pop3d/log is repeatedly being started and is exiting immediately. You need to work out why that is. 1. Is qmail-pop3d/log/run executable? 2. What does it have in it exactly? Is the script correct? 3. What happens if you run it manually - what output do you get? Regards. On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote: Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while pop was working) and got: qmail-pop3d: up (pid 598) 1420 seconds qmail-send: up (pid 594) 1420 seconds qmail-smtpd: up (pid 595) 1420 seconds qmail-pop3d/log: up (pid 28975) 0 seconds qmail-send/log: up (pid 596) 1420 seconds qmail-smtpd/log: up (pid 599) 1420 seconds Then I did it again (when pop stopped working) and got: qmail-pop3d: up (pid 598) 1678 seconds qmail-send: up (pid 594) 1678 seconds qmail-smtpd: up (pid 595) 1678 seconds qmail-pop3d/log: up (pid 26225) 0 seconds qmail-send/log: up (pid 596) 1678 seconds qmail-smtpd/log: up (pid 599) 1678 seconds Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps increasing, even after it stops working. However, doing 'ps auxw | grep pop3' while pop is working (up to 15 minutes after rebooting) gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma But doing it again when pop stops working gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 4454 0.0 0.6 1344 516 ?S09:17 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma There does seem to be a connection to the second instance of tcpserver. How can I find why and where the second tcpserver instance is being initiated? Thanks again, everyone. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
RE: qmail-pop3d not working?
I don't have qmail-pop3d/log/run, but I do have /var/qmail/supervise/qmail-pop3d/run (with permissions: -rwxr-xr-x). It looks like: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 I also have /var/log/qmail/pop3d, which is empty, as you might've guessed. The output of running 'qmail-pop3d/run' manually is: tcpserver: fatal: unable to bind: address already used -Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Friday, April 27, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? The zero seconds for qmail-pop3d/log is your problem. The logging output of qmail-pop3d is ultimately filling up the pipe buffer and then wedging since the pipe is never drained by qmail-pop3d/log. The zero seconds is telling you that qmail-pop3d/log is repeatedly being started and is exiting immediately. You need to work out why that is. 1. Is qmail-pop3d/log/run executable? 2. What does it have in it exactly? Is the script correct? 3. What happens if you run it manually - what output do you get? Regards. On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote: Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while pop was working) and got: qmail-pop3d: up (pid 598) 1420 seconds qmail-send: up (pid 594) 1420 seconds qmail-smtpd: up (pid 595) 1420 seconds qmail-pop3d/log: up (pid 28975) 0 seconds qmail-send/log: up (pid 596) 1420 seconds qmail-smtpd/log: up (pid 599) 1420 seconds Then I did it again (when pop stopped working) and got: qmail-pop3d: up (pid 598) 1678 seconds qmail-send: up (pid 594) 1678 seconds qmail-smtpd: up (pid 595) 1678 seconds qmail-pop3d/log: up (pid 26225) 0 seconds qmail-send/log: up (pid 596) 1678 seconds qmail-smtpd/log: up (pid 599) 1678 seconds Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps increasing, even after it stops working. However, doing 'ps auxw | grep pop3' while pop is working (up to 15 minutes after rebooting) gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma But doing it again when pop stops working gives me: root 591 0.0 0.4 1272 344 ?S09:06 0:00 supervise qmail-pop3d root 596 0.0 0.6 1344 512 ?S09:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 4454 0.0 0.6 1344 516 ?S09:17 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma There does seem to be a connection to the second instance of tcpserver. How can I find why and where the second tcpserver instance is being initiated? Thanks again, everyone. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
qmail-pop3d not handling enough messages
hy! i've gat a qmail-system with vpopmail, using the qmail-pop3d as popper. my problem is, that the number of messages in my cur grew up to 23240 and now i cant get them anymore, the pop3d gives out an error like cant change to $Home/Maildir.. anyone help? thx thomas
RE: qmail-pop3d not working?
Does anyone have any idea why pop would stop delivering 15 minutes after rebooting? I've provided my findings below. Thanks again for any help you may provide. You're a great list! Steven -Original Message- From: Steven Katz [EMAIL PROTECTED] Sent: Monday, April 23, 2001 10:19 AM To: [EMAIL PROTECTED] Subject: RE: qmail-pop3d not working? It seems to be only pop that stops working after 15 minutes, as messages are piling up in the Maildirs. My mail client reports: A timeout occurred while communicating with the server. (Account: '[EMAIL PROTECTED]', POP3 Server: 'mail.idma.com', Error Number: 0x800ccc19). At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: tcpserver: fatal: unable to bind: address already used My /qmail-pop3d/run file looks like: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 Doing 'ps auxw | grep pop3' gives me: root 593 0.0 0.4 1272 344 ?SN 08:06 0:00 supervise qmail-pop3d root 601 0.0 0.6 1344 512 ?SN 08:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 10162 0.0 0.6 1344 516 ?SN 08:24 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 31977 0.0 0.7 1556 616 pts/0S08:38 0:00 grep pop3 Doing 'cd /var/qmail/supervise svstat qmail-smtpd' gives me: qmail-smtpd: up (pid 596) 1962 seconds Doing 'ls -l ~/* | grep Maildir --after-context=4' gives me: /home/steven/Maildir: total 16 drwxrwxr-x2 steven steven 4096 Apr 21 23:22 cur drwxrwxr-x2 steven steven 8192 Apr 23 08:36 new drwxrwxr-x2 steven steven 4096 Apr 23 08:36 tmp -Original Message- From: Steven Katz [EMAIL PROTECTED] Sent: Monday, April 23, 2001 9:32 AM To: [EMAIL PROTECTED] Subject: RE: qmail-pop3d not working? Uh oh-- I may have celebrated too soon. For some reason, I can send but can't receive 15 minutes after rebooting. Does that sound familiar to anyone? Steven
Re: qmail-pop3d not working?
Steven Katz [EMAIL PROTECTED] wrote: Does anyone have any idea why pop would stop delivering 15 minutes after rebooting? It sounds odd. I can't think of a reason offhand which would cause this. However, something else odd struck me: Doing 'ps auxw | grep pop3' gives me: [...] /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 10162 0.0 0.6 1344 516 ?SN 08:24 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 31977 0.0 0.7 1556 616 pts/0S08:38 0:00 You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: qmail-pop3d not handling enough messages
On Tue, Apr 24, 2001 at 01:44:32PM +, Thomas Ackermann wrote: i've gat a qmail-system with vpopmail, using the qmail-pop3d as popper. my problem is, that the number of messages in my cur grew up to 23240 and now i cant get them anymore, the pop3d gives out an error like cant change to $Home/Maildir.. You mean -ERR unable to scan $HOME/Maildir, right? Oh, well. It's been a year, so i might just repeat it completely. See below. I don't remember getting feedback whether the suggested change to prioq.c really made a difference. the adjust your resource limit is done with softlimit, if you use daemontools. Regards, Uwe Date: Tue, 28 Mar 2000 18:20:01 + From: Uwe Ohse [EMAIL PROTECTED] To: Gary Richardson [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: qmail-pop3 problems with 'large' accounts Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Tue, Mar 28, 2000 at 09:25:26AM -0800 On Tue, Mar 28, 2000 at 09:25:26AM -0800, Gary Richardson wrote: I'm having problems with a pop user checking their. There are around 12000 emails in their MailDir directory and I get the following error when I try to download them: -ERR unable to scan $HOME/Maildir Connection closed by foreign host. out of memory. qmail-pop3d needs space for 12000 filenames, with maybe 30 characters each (depending on the length of the hostname part of the file name), plus 5 (new/\0), plus another 8 bytes for meta information, accounting for about 50 bytes of memory, plus whatever your C library needs, plus whatever the kernel needs. Unfortunately qmail-pop3d suffers from memory fragmentation, so the actual memory usage is somewhat higher. You might get a far better behaviour if you change the number 100 in the line GEN_ALLOC_readyplus(prioq,struct prioq_elt,p,len,a,i,n,x,100,prioq_readyplus) in prioq.c to, say, 5000, and recompile qmail-pop3d, and install that and only that - the change will eat 5000*8 bytes in qmail-send. Or: Adjust your resource limits. Or: clean up your mail dir. pop3 wasn't designed to deal with that number of messages anyway (as wasn't maildir). Regards, Uwe
Re: qmail-pop3d not working?
Charles Cazabon said, You have two tcpserver instances, both trying to bind to the same interface(s) and port. At least one of those _has_ to be failing, and it should be showing up in your logs. Steve said, At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: I use this to check for status on supervised processes. bash-2.04# cd /var/qmail/supervise; svstat * */log qmail-pop3d: up (pid 658) 178697 seconds qmail-send: up (pid 9480) 178696 seconds qmail-smtpd: up (pid 3846) 178697 seconds qmail-pop3d/log: up (pid 11946) 178697 seconds qmail-send/log: up (pid 7901) 178697 seconds qmail-smtpd/log: up (pid 13335) 178697 seconds When you supervise, and one of the seconds columns stays at 0 seconds, you definitely have a problem. After you reboot, or better yet, when your pop stops working, try that and see what happens. Also, do not start pop3d from the command line if you are starting it in your boot scripts, even if pop3 is not working properly. Hope that helped Rick Up
RE: qmail-pop3d not working?
How strange-- now my mail client is giving me the following error when I try to send mail from this account (or send mail to this account from somewhere else): The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I haven't started installing relay-ctrl (smtp after pop auth) yet. In fact, as unbelievable as it sounds, I hadn't done anything since I was finally able to send and receive after changing POP3 to pop3.. Steven -Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 10:38 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Now change POP3 to pop3 and run it again. Go on... humor me. It's only the third time I've told you what your problem is. Yes, that did it! Just received 200+ messages. Thanks for all your help, everyone. You might want to feed this back to the faqts people. Let's others benefit from what you've learnt. Regards.
Re: qmail-pop3d not working?
From: Steven Katz [EMAIL PROTECTED] The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I am not an expert, but I don't think that is qmail talking because I have caused every possible error every step of the way, so check for yourself. I think you are running Exim An Internet mailer for Unix systems. http://www.exim.org [root@ns2 /root]# telnet 208.25.75.162 25 Trying 208.25.75.162... Connected to 208.25.75.162. Escape character is '^]'. 220 shasta.idma.com ESMTP Exim 3.13 #1 Mon, 23 Apr 2001 00:08:04 -0700 Hope that helped Rick Up
Re: qmail-pop3d not working?
Steven == Steven Katz [EMAIL PROTECTED] writes: The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). This error isn't a qmail one. (Try `cd ~/qmail-1.03 grep prohibited by administrator *'). In fact, the word `administrator' would appear to display evidence of a lowly MS Winblowz machine somewhere running an SMTP server, and your DNS settings are directing mail to that server rather than your nice, shiny, spanking brand new one. Try pinging mail.idma.com and see what mail server you are REALLY getting (and maybe try deleting any other mail servers that you previously had running on your *nix box). B. -- I had a fortune cookie the other day and it said: 'Outlook not so good'. I said: 'Sure, but Microsoft ships it anyway'.
RE: qmail-pop3d not working?
Sure enough, Exim is running, but I didn't realize this would cause problems. When I try to remove it, I get the following: # rpm -e exim error: removing these packages would break dependencies: smtpdaemon is needed by fetchmail-5.5.0-2 smtpdaemon is needed by mutt-1.2.5i-8. I understand mutt is recommended for Maildirs. Does this mean I'll be unable to use it? Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Monday, April 23, 2001 1:21 AM To: Steven Katz; [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? From: Steven Katz [EMAIL PROTECTED] The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I am not an expert, but I don't think that is qmail talking because I have caused every possible error every step of the way, so check for yourself. I think you are running Exim An Internet mailer for Unix systems. http://www.exim.org [root@ns2 /root]# telnet 208.25.75.162 25 Trying 208.25.75.162... Connected to 208.25.75.162. Escape character is '^]'. 220 shasta.idma.com ESMTP Exim 3.13 #1 Mon, 23 Apr 2001 00:08:04 -0700 Hope that helped Rick Up
Re: qmail-pop3d not working?
Just type: # rpm -e --nodeps exim And be happy! You don't need it... Steven == Steven Katz [EMAIL PROTECTED] writes: Sure enough, Exim is running, but I didn't realize this would cause problems. When I try to remove it, I get the following: # rpm -e exim error: removing these packages would break dependencies: smtpdaemon is needed by fetchmail-5.5.0-2 smtpdaemon is needed by mutt-1.2.5i-8. I understand mutt is recommended for Maildirs. Does this mean I'll be unable to use it? Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Monday, April 23, 2001 1:21 AM To: Steven Katz; [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? From: Steven Katz [EMAIL PROTECTED] The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I am not an expert, but I don't think that is qmail talking because I have caused every possible error every step of the way, so check for yourself. I think you are running Exim An Internet mailer for Unix systems. http://www.exim.org [root@ns2 /root]# telnet 208.25.75.162 25 Trying 208.25.75.162... Connected to 208.25.75.162. Escape character is '^]'. 220 shasta.idma.com ESMTP Exim 3.13 #1 Mon, 23 Apr 2001 00:08:04 -0700 Hope that helped Rick Up -- Hardware, n.: The parts of a computer system that can be kicked. - The Devil's Dictionary to Computer Studies
RE: qmail-pop3d not working?
You're right, I removed it and I am happy! Note to archive archeologists: Running Exim and qmail simultaneously will cause intermittent problems. There's my contribution to the time capsule. Thanks again, everyone. Steven -Original Message- From: Brett Randall [EMAIL PROTECTED] Sent: Monday, April 23, 2001 3:08 AM To: Steven Katz Cc: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Just type: # rpm -e --nodeps exim And be happy! You don't need it... Steven == Steven Katz [EMAIL PROTECTED] writes: Sure enough, Exim is running, but I didn't realize this would cause problems. When I try to remove it, I get the following: # rpm -e exim error: removing these packages would break dependencies: smtpdaemon is needed by fetchmail-5.5.0-2 smtpdaemon is needed by mutt-1.2.5i-8. I understand mutt is recommended for Maildirs. Does this mean I'll be unable to use it? Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Monday, April 23, 2001 1:21 AM To: Steven Katz; [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? From: Steven Katz [EMAIL PROTECTED] The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I am not an expert, but I don't think that is qmail talking because I have caused every possible error every step of the way, so check for yourself. I think you are running Exim An Internet mailer for Unix systems. http://www.exim.org [root@ns2 /root]# telnet 208.25.75.162 25 Trying 208.25.75.162... Connected to 208.25.75.162. Escape character is '^]'. 220 shasta.idma.com ESMTP Exim 3.13 #1 Mon, 23 Apr 2001 00:08:04 -0700 Hope that helped Rick Up -- Hardware, n.: The parts of a computer system that can be kicked. - The Devil's Dictionary to Computer Studies
Re: qmail-pop3d not working?
On some systems, it can be helpful to do a grep -i pop /etc/services to find out what the nomenclature is as well. FYI (to the original poster), that POP3 you misspelt (un*x is usually case sensitive) is just looked up in a file like /etc/services and the port substituted in. - Original Message - It means change the POP3 to pop3 and try the command again. If you get the same error, try pop-3. If none of those work, substitute 110 instead. It's not necessary to include the quotes.
Re: qmail-pop3d not working?
4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? The page he referenced at http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223 does indeed have POP3 in uppercase. Dave Sill may wish to update that with a comment or two.
Re: qmail-pop3d not working?
Mark Delany [EMAIL PROTECTED] wrote: You might want to feed this back to the faqts people. Let's others benefit from what you've learnt. It's fixed. -Dave
Re: Can I use qmail-pop3d for both mbox and maildir format?
Michael Cheung [EMAIL PROTECTED] wrote: Can I use qmail-pop3d for both mbox and maildir format? No, but SolidPOP handles both: http://solidpop3d.pld.org.pl/ -Dave
RE: qmail-pop3d not working?
Uh oh-- I may have celebrated too soon. For some reason, I can send but can't receive 15 minutes after rebooting. Does that sound familiar to anyone? Steven -Original Message- From: Brett Randall [EMAIL PROTECTED] Sent: Monday, April 23, 2001 3:08 AM To: Steven Katz Cc: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Just type: # rpm -e --nodeps exim And be happy! You don't need it... Steven == Steven Katz [EMAIL PROTECTED] writes: Sure enough, Exim is running, but I didn't realize this would cause problems. When I try to remove it, I get the following: # rpm -e exim error: removing these packages would break dependencies: smtpdaemon is needed by fetchmail-5.5.0-2 smtpdaemon is needed by mutt-1.2.5i-8. I understand mutt is recommended for Maildirs. Does this mean I'll be unable to use it? Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Monday, April 23, 2001 1:21 AM To: Steven Katz; [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? From: Steven Katz [EMAIL PROTECTED] The message could not be sent because one of the recipients was rejected by the server. Server Response: '550 relaying to [EMAIL PROTECTED] prohibited by administrator'. (Account: '[EMAIL PROTECTED]', SMTP Server: 'mail.idma.com', Error Number: 0x800ccc79). I am not an expert, but I don't think that is qmail talking because I have caused every possible error every step of the way, so check for yourself. I think you are running Exim An Internet mailer for Unix systems. http://www.exim.org [root@ns2 /root]# telnet 208.25.75.162 25 Trying 208.25.75.162... Connected to 208.25.75.162. Escape character is '^]'. 220 shasta.idma.com ESMTP Exim 3.13 #1 Mon, 23 Apr 2001 00:08:04 -0700 Hope that helped Rick Up -- Hardware, n.: The parts of a computer system that can be kicked. - The Devil's Dictionary to Computer Studies
RE: qmail-pop3d not working?
It seems to be only pop that stops working after 15 minutes, as messages are piling up in the Maildirs. My mail client reports: A timeout occurred while communicating with the server. (Account: '[EMAIL PROTECTED]', POP3 Server: 'mail.idma.com', Error Number: 0x800ccc19). At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run' gives me: tcpserver: fatal: unable to bind: address already used My /qmail-pop3d/run file looks like: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 Doing 'ps auxw | grep pop3' gives me: root 593 0.0 0.4 1272 344 ?SN 08:06 0:00 supervise qmail-pop3d root 601 0.0 0.6 1344 512 ?SN 08:06 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 10162 0.0 0.6 1344 516 ?SN 08:24 0:00 /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma root 31977 0.0 0.7 1556 616 pts/0S08:38 0:00 grep pop3 Doing 'cd /var/qmail/supervise svstat qmail-smtpd' gives me: qmail-smtpd: up (pid 596) 1962 seconds Doing 'ls -l ~/* | grep Maildir --after-context=4' gives me: /home/steven/Maildir: total 16 drwxrwxr-x2 steven steven 4096 Apr 21 23:22 cur drwxrwxr-x2 steven steven 8192 Apr 23 08:36 new drwxrwxr-x2 steven steven 4096 Apr 23 08:36 tmp -Original Message- From: Steven Katz [EMAIL PROTECTED] Sent: Monday, April 23, 2001 9:32 AM To: [EMAIL PROTECTED] Subject: RE: qmail-pop3d not working? Uh oh-- I may have celebrated too soon. For some reason, I can send but can't receive 15 minutes after rebooting. Does that sound familiar to anyone? Steven
qmail-pop3d not working?
I've installed qmail according to the LWQ instructions, and qmail-pop3d according to faqts instructions (http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223). At this point, I'm able to send mail only from the clients listed in tcp.smtp. However, I'm unable to receive mail at any of the clients (though I can see messages piling up in the Maildirs). My /qmail-pop3d/run file: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 The FQDN (idma.com) is the same name that appears in /control/me, locals, and rcpthosts. Is it acceptable for this to just be the domain name, or do I need to include the hostname? Is that 'Maildir' that follows the invocation of qmail-pop3d supposed to an absolute path? Thanks for any assistance you can offer. Steven
Re: qmail-pop3d not working?
On Sun, Apr 22, 2001 at 12:08:54PM -0700, Steven Katz wrote: I've installed qmail according to the LWQ instructions, and qmail-pop3d according to faqts instructions (http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223). At this point, I'm able to send mail only from the clients listed in tcp.smtp. However, I'm unable to receive mail at any of the clients (though I can see messages piling up in the Maildirs). My /qmail-pop3d/run file: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 The FQDN (idma.com) is the same name that appears in /control/me, locals, and rcpthosts. Is it acceptable for this to just be the domain name, or do I need to include the hostname? Is that 'Maildir' that follows the invocation of qmail-pop3d supposed to an absolute path? Thanks for any assistance you can offer. You need to give us a *lot* more information than "I'm unable to receive mail..." For example: 1. You haven't told us whether the tcpserver in your qmail-pop3d/run is running. Is it? 2. You haven't told us what happens when you try and connect to the POP port. What does happen? 3. You haven't shown us what gets logged. What is logged? 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? Regards.
RE: qmail-pop3d not working?
-Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 12:28 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? On Sun, Apr 22, 2001 at 12:08:54PM -0700, Steven Katz wrote: I've installed qmail according to the LWQ instructions, and qmail-pop3d according to faqts instructions (http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223). At this point, I'm able to send mail only from the clients listed in tcp.smtp. However, I'm unable to receive mail at any of the clients (though I can see messages piling up in the Maildirs). My /qmail-pop3d/run file: #!/bin/sh exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 The FQDN (idma.com) is the same name that appears in /control/me, locals, and rcpthosts. Is it acceptable for this to just be the domain name, or do I need to include the hostname? Is that 'Maildir' that follows the invocation of qmail-pop3d supposed to an absolute path? Thanks for any assistance you can offer. You need to give us a *lot* more information than "I'm unable to receive mail..." For example: 1. You haven't told us whether the tcpserver in your qmail-pop3d/run is running. Is it? According to ps it is. Is there anything else I can use to verify that it's running properly? 2. You haven't told us what happens when you try and connect to the POP port. What does happen? My mail client reports the following: Unable to connect to the server. (Account: '[EMAIL PROTECTED]', POP3 Server: 'mail.idma.com', Error Number: 0x800ccc0e). 3. You haven't shown us what gets logged. What is logged? Log files are being created in log/qmail/smtpd, but not in log/qmail/pop3d. Does that provide a good clue? 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? I followed both the LWQ and the above mentioned faqts instructions exactly, and double checked. Thanks again. Steven Regards.
Re: qmail-pop3d not working?
exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? I followed both the LWQ and the above mentioned faqts instructions exactly, and double checked. Hmm. On FreeBSD, Linux *and* Solaris using "POP3" in uppercase fails, while in lowercase it succeeds. With all due respect to faqts, can I suggest that you try the qmail-pop3/run file with a lowercase "pop3"? Also of course, you can run the service manually, by: # sh -x qmail-po3d/run And show us the output. Regards.
Can I use qmail-pop3d for both mbox and maildir format?
Hi; I move mail system from sendmail to qmail. so I won't to change the former mbox format. But I add a virtualdomain, it seems I have to use maildir format for the virtualdomain. Can I use qmail-pop3d for both mbox and maildir format? Thanks inadvance. Regards; Michael
Re: qmail-pop3d not working?
"Steven" == Steven Katz [EMAIL PROTECTED] writes: -Original Message- From: Mark Delany [EMAIL PROTECTED] snip You need to give us a *lot* more information than "I'm unable to receive mail..." For example: 1. You haven't told us whether the tcpserver in your qmail-pop3d/run is running. Is it? According to ps it is. Is there anything else I can use to verify that it's running properly? What is the output of `ps auxw | grep pop3'? What is the output of `cd /var/qmail/supervise svstat qmail-smtpd'? 2. You haven't told us what happens when you try and connect to the POP port. What does happen? My mail client reports the following: Unable to connect to the server. (Account: '[EMAIL PROTECTED]', POP3 Server: 'mail.idma.com', Error Number: 0x800ccc0e). Outlook Expectless sucks butt cheek. Telnet to port 110 and do: USER yourusername PASS yourpassword And give us the error message. Then give us `ls -l ~/* | grep Maildir --after-context=4' when logged in as yourself. Then give us `ls -l ~/.. | grep yourusername' 3. You haven't shown us what gets logged. What is logged? Log files are being created in log/qmail/smtpd, but not in log/qmail/pop3d. Does that provide a good clue? Depends. Is multilog running as part of the sv scripts in pop3d/log/run? This should appear in `ps auxw | grep pop3'. 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? I followed both the LWQ and the above mentioned faqts instructions exactly, and double checked. -- "Bubble Memory, n.: A derogatory term, usually referring to a person's intelligence. See also vacuum tube." - The Devil's Dictionary to Computer Studies
Re: qmail-pop3d not working?
"Mark" == Mark Delany [EMAIL PROTECTED] writes: # sh -x qmail-po3d/run qmail-pop3d even (just in case he takes it literally ;) -- "SOFTWARE, n.: Formal evening attire for female computer analysts." - The Devil's Dictionary to Computer Studies
RE: qmail-pop3d not working?
-Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 7:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? I followed both the LWQ and the above mentioned faqts instructions exactly, and double checked. Hmm. On FreeBSD, Linux *and* Solaris using POP3 in uppercase fails, while in lowercase it succeeds. With all due respect to faqts, can I suggest that you try the qmail-pop3/run file with a lowercase pop3? Also of course, you can run the service manually, by: # sh -x qmail-po3d/run And show us the output. I get: tcpserver: fatal: unable to figure out port number for POP3 I'll bet that's meaningful, but I don't know what it means! Steven Regards.
Re: qmail-pop3d not working?
On Sun, Apr 22, 2001 at 08:49:27PM -0700, Steven Katz wrote: Also of course, you can run the service manually, by: # sh -x qmail-po3d/run And show us the output. I get: tcpserver: fatal: unable to figure out port number for POP3 I'll bet that's meaningful, but I don't know what it means! It means change the POP3 to pop3 and try the command again. If you get the same error, try pop-3. If none of those work, substitute 110 instead. It's not necessary to include the quotes. Tim
Re: qmail-pop3d not working?
On Sun, Apr 22, 2001 at 08:49:27PM -0700, Steven Katz wrote: -Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 7:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 POP3 /var/qmail/bin/qmail-popup \ idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 4. Oh, and you haven't told us whether you followed instructions exactly when setting up qmail-pop3d/run. Do the instructions really say to use POP3 in uppercase? I followed both the LWQ and the above mentioned faqts instructions exactly, and double checked. Hmm. On FreeBSD, Linux *and* Solaris using POP3 in uppercase fails, while in lowercase it succeeds. With all due respect to faqts, can I suggest that you try the qmail-pop3/run file with a lowercase pop3? Also of course, you can run the service manually, by: # sh -x qmail-po3d/run And show us the output. I get: tcpserver: fatal: unable to figure out port number for POP3 I'll bet that's meaningful, but I don't know what it means! Now change POP3 to pop3 and run it again. Go on... humor me. It's only the third time I've told you what your problem is. Regards.
Re: qmail-pop3d not working?
Now change POP3 to pop3 and run it again. Go on... humor me. It's And if that doesn't work try pop-3 or type more /etc/servicesthen scroll to where port 110 is listed - use that exact spelling OR make the /etc/services file say POP3 Mine says: pop-3 110/tcp # POP version 3 pop-3 110/udp So I would need the all lowercase pop-3 with the dash CaPs CoUnT and so do - (dashes) Hope that helped Rick Up
RE: qmail-pop3d not working?
-Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 8:55 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? On Sun, Apr 22, 2001 at 08:49:27PM -0700, Steven Katz wrote: -Original Message- From: Mark Delany [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 7:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Now change POP3 to pop3 and run it again. Go on... humor me. It's only the third time I've told you what your problem is. Yes, that did it! Just received 200+ messages. Thanks for all your help, everyone. Now to figure out smpt after pop authentication.. Steven Regards.
RE: qmail-pop3d not working?
Mine says: pop3 110/tcp pop-3 # POP version 3 The 3rd column is claimed to be an alias, so I guess either would've worked. Steven -Original Message- From: Rick Updegrove [EMAIL PROTECTED] Sent: Sunday, April 22, 2001 9:42 PM To: [EMAIL PROTECTED] Subject: Re: qmail-pop3d not working? Now change POP3 to pop3 and run it again. Go on... humor me. It's And if that doesn't work try pop-3 or type more /etc/servicesthen scroll to where port 110 is listed - use that exact spelling OR make the /etc/services file say POP3 Mine says: pop-3 110/tcp # POP version 3 pop-3 110/udp So I would need the all lowercase pop-3 with the dash CaPs CoUnT and so do - (dashes) Hope that helped Rick Up
Re: qmail-pop3d not working?
Now change POP3 to pop3 and run it again. Go on... humor me. It's only the third time I've told you what your problem is. Yes, that did it! Just received 200+ messages. Thanks for all your help, everyone. You might want to feed this back to the faqts people. Let's others benefit from what you've learnt. Regards.
Re: qmail-pop3d and supervise
The high CPU usage problem went away after I fixed the properties of the /var/qmail/supervise/qmail-pop3d and qmail-pop3d/log directories. I hadn't followed LWQ when I first created them. Now everything seems to be fine. And I've learned a lot about qmail in the last few days. :-) Time to tackle vmailmgr... Rehan
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
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
Logging patch for qmail-pop3d and qmail-popup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I wrote a small patch to do some logging of POP account usage.
I only wanted to have some loggin of users loggin in and the message
size retrieved. Also any error that occurs is logged in order to
facilitate incorrect login attempts and other errors. NO PASSWORD are
written to the logfile.
Please give some feedback.
Here it is.
diff -Naur qmail-1.03.orig/qmail-pop3d.c qmail-1.03/qmail-pop3d.c
- --- qmail-1.03.orig/qmail-pop3d.c Sat Feb 24 14:26:54 2001
+++ qmail-1.03/qmail-pop3d.cSat Feb 24 22:52:55 2001
@@ -41,6 +41,9 @@
char ssinbuf[128];
substdio ssin = SUBSTDIO_FDBUF(saferead,0,ssinbuf,sizeof ssinbuf);
+char sserrbuf[128];
+substdio sserr = SUBSTDIO_FDBUF(safewrite,2,sserrbuf,sizeof
sserrbuf);
+
void put(buf,len) char *buf; int len;
{
substdio_put(ssout,buf,len);
@@ -53,8 +56,25 @@
{
substdio_flush(ssout);
}
+void writelog(char *x1, char *x2, char *x3, char *x4)
+{
+ char strnum[FMT_ULONG];
+
+ strnum[fmt_ulong(strnum,getpid())] = 0;
+
+ substdio_puts(sserr,"pop3d: pid ");
+ substdio_puts(sserr,strnum);
+ substdio_puts(sserr," ");
+ if (x1) substdio_puts(sserr,x1);
+ if (x2) substdio_puts(sserr,x2);
+ if (x3) substdio_puts(sserr,x3);
+ if (x4) substdio_puts(sserr,x4);
+ substdio_puts(sserr,"\n");
+ substdio_flush(sserr);
+}
void err(s) char *s;
{
+ writelog("-ERR ", s, 0, 0);
puts("-ERR ");
puts(s);
puts("\r\n");
@@ -193,6 +213,7 @@
rename(m[i].fn,line.s); /* if it fails, bummer */
}
okay();
+ writelog("QUIT", 0, 0, 0);
die();
}
@@ -257,6 +278,7 @@
int i;
unsigned long limit;
int fd;
+ char strnum[FMT_ULONG];
i = msgno(arg);
if (i == -1) return;
@@ -271,6 +293,8 @@
substdio_fdbuf(ssmsg,read,fd,ssmsgbuf,sizeof(ssmsgbuf));
blast(ssmsg,limit);
close(fd);
+ strnum[fmt_ulong(strnum,m[i].size)] = 0;
+ writelog("RETR: ", "msglen: ", strnum, 0);
}
struct commands pop3commands[] = {
diff -Naur qmail-1.03.orig/qmail-popup.c qmail-1.03/qmail-popup.c
- --- qmail-1.03.orig/qmail-popup.c Mon Jun 15 12:53:16 1998
+++ qmail-1.03/qmail-popup.cSat Feb 24 22:52:55 2001
@@ -38,6 +38,9 @@
char ssinbuf[128];
substdio ssin = SUBSTDIO_FDBUF(saferead,0,ssinbuf,sizeof ssinbuf);
+char sserrbuf[128];
+substdio sserr = SUBSTDIO_FDBUF(safewrite,2,sserrbuf,sizeof
sserrbuf);
+
void puts(s) char *s;
{
substdio_puts(ssout,s);
@@ -46,8 +49,25 @@
{
substdio_flush(ssout);
}
+void writelog(char *x1, char *x2, char *x3, char *x4)
+{
+ char strnum[FMT_ULONG];
+
+ strnum[fmt_ulong(strnum,getpid())] = 0;
+
+ substdio_puts(sserr,"popup: pid ");
+ substdio_puts(sserr,strnum);
+ substdio_puts(sserr," ");
+ if (x1) substdio_puts(sserr,x1);
+ if (x2) substdio_puts(sserr,x2);
+ if (x3) substdio_puts(sserr,x3);
+ if (x4) substdio_puts(sserr,x4);
+ substdio_puts(sserr,"\n");
+ substdio_flush(sserr);
+}
void err(s) char *s;
{
+ writelog("-ERR ", s, 0, 0);
puts("-ERR ");
puts(s);
puts("\r\n");
@@ -67,7 +87,7 @@
void err_authoriz() { err("authorization first"); }
void okay() { puts("+OK \r\n"); flush(); }
- -void pop3_quit() { okay(); die(); }
+void pop3_quit() { okay(); writelog("QUIT", 0, 0, 0); die(); }
char unique[FMT_ULONG + FMT_ULONG + 3];
@@ -88,7 +108,14 @@
int wstat;
int pi[2];
- - if (fd_copy(2,1) == -1) die_pipe();
+ /* Don't know why this is needed has no effect when removed
+ it stands in the way of good logging with multilog
+ checked qmail-pop3d it does not use the fd 2
+ it only writes to stdout not stderr not even for errors
+ Willy De la Court [EMAIL PROTECTED]
+ */
+
+ /* if (fd_copy(2,1) == -1) die_pipe();*/
close(3);
if (pipe(pi) == -1) die_pipe();
if (pi[0] != 3) die_pipe();
@@ -140,6 +167,7 @@
seenuser = 1;
if (!stralloc_copys(username,arg)) die_nomem();
if (!stralloc_0(username)) die_nomem();
+ writelog("USER: ", arg, 0, 0);
}
void pop3_pass(arg) char *arg;
{
@@ -153,6 +181,7 @@
space = arg + str_chr(arg,' ');
if (!*space) { err_syntax(); return; }
*space++ = 0;
+ writelog("APOP: ", arg, 0, 0);
doanddie(arg,space - arg,space);
}
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use http://www.pgp.com
iQA/AwUBOsoypf4IaGw3x6aJEQJeHQCfT1AIeTmy86XZIfDKcfPWk0Lh/3gAn2YQ
b8k/K/VPwyTvQxC5JFyLEumH
=/0QT
-END PGP SIGNATURE-
RE: Qmail + pop3d
Keith, Although the directories MAY be on a separate logial partitions (I used Red Hat 7's auto partition, so I can't say exactly how RH7 does it), they are NOT, however, on two physical Hard Drives. I only have one 3 Meg drive in the machine. Also, I can copy the file manually with the "mv" command without the error (?). The only time I get the error is when I call one of the "elq", "qail" or "pinq" wrappers. I agree with you on Mutt. I think I will just stick with Mutt. As you said, it is very feature rich - just a little cryptic! Bill -Original Message- From: ennui [mailto:ennui]On Behalf Of Nick (Keith) Fish Sent: Friday, March 23, 2001 5:39 PM To: Bill Andersen; Qmail Mailing List Subject: Re: Qmail + pop3d Bill Andersen wrote: I read the docs and found the nice little wrappers for "elq","pinq" and "qail", but I always get the following error when it calls the maildir2mbox command... maildir2mbox: fatal: unable to move /home/bill/Mailtmp to /var/spool/mail/bill: cross-device link I'm a Linux newbie, so I just went to POP3 from my PC in order to get my mail. However, I would really like to run pine. (I did get Mutt working with maildir, so I'me not completely locked to my PC!!! Thank goodness) I'm sure it's obvious what I have wrong to someone who knows *nix... Help anyone? Bill Well, are those directories on separate devices (i.e. two different hard drives)? If so (and this is judging from the error message), that's probably your problem. Try copying the Maildir over to the var directory somewhere and then run the maildir2mbox command. BTW, if I was you, I would just stick with mutt and Maildir. Maildir is by far the best format for storing e-mail to date and mutt is an excellent and featureful MUA, although syntax can be a bitch. My second recommendation would be to download the patch to make Pine work with Maildir. What you're trying to do, I would call a distant third. Power to ya, though. --- Keith Network Engineer Triton Technologies, Inc.
RE: Qmail + pop3d
I read the docs and found the nice little wrappers for "elq","pinq" and "qail", but I always get the following error when it calls the maildir2mbox command... maildir2mbox: fatal: unable to move /home/bill/Mailtmp to /var/spool/mail/bill: cross-device link I'm a Linux newbie, so I just went to POP3 from my PC in order to get my mail. However, I would really like to run pine. (I did get Mutt working with maildir, so I'me not completely locked to my PC!!! Thank goodness) I'm sure it's obvious what I have wrong to someone who knows *nix... Help anyone? Bill In Reply to: Or, is it a hard operation to make the system use Maildir ? How would i then make 'pine' work and all that i mean... Charles Cazabon wrote: No, it's not difficult. Again, check djb's site and FAQ, and www.qmail.org. RTFM.
Re: qmail-pop3d bug
On Sun, Mar 11, 2001 at 07:37:06PM +, Mark Delany wrote: [...] A more sensible strategy might be to introduce a new "info" flag (say '3' equals POP wire size) on the filename, eg, a 10,000 byte email has a name something like this: Maildir/new/980195114.16740.geex:2,RS3,1 From reading URL:http://cr.yp.to/proto/maildir.html, it is not clear to me that this would be the proper format for such an 'info' extension. I would worry that MUAs and other software dealing with maildir (scripts!) would expect info semantics in the 2, series to be at the end of the filenames. Optimally the wire-size is calculated when the mail is written to Maildir/tmp/ and then applied as an "info" flag when the file is moved to Maildir/new/. A possible complication with this approach is that my reading of Maildir infers that "info" can only be set when the file moves from Maildir/new/ to Maildir/cur/. No, this is not what that document says. It says "When you move a file from new to cur, you have to change it's name [...]" You *have* to change the name when the file move from new/ to cur/ , but there is no specification of other cases; in fact, lots of MUA's will change info when the file has been in cur/ for a while: mutt, for example, moves the file from new/ to cur/, adds :2, and only modifies that to be 2,S after the user has read the message (it is no longer 'N'ew). Vince.
Re: qmail-pop3d bug
A more sensible strategy might be to introduce a new "info" flag (say '3' equals POP wire size) on the filename, eg, a 10,000 byte email has a name something like this: Maildir/new/980195114.16740.geex:2,RS3,1 From reading URL:http://cr.yp.to/proto/maildir.html, it is not clear to me that this would be the proper format for such an 'info' extension. I would worry that MUAs and other software dealing with maildir (scripts!) would expect info semantics in the 2, series to be at the end of the filenames. Indeed, and given that "info is morally equivalent to the Status field used by mbox readers" I suspect that the my suggested syntax is beyond the original intent. Optimally the wire-size is calculated when the mail is written to Maildir/tmp/ and then applied as an "info" flag when the file is moved to Maildir/new/. A possible complication with this approach is that my reading of Maildir infers that "info" can only be set when the file moves from Maildir/new/ to Maildir/cur/. No, this is not what that document says. It says "When you move a file from new to cur, you have to change it's name [...]" You stopped quoting before the most important part! Here's the complete sentence. "When you move a file from new to cur, you have to change its name from uniq to uniq:info." To me that implies that a file in new cannot have an "info" section. You *have* to change the name when the file move from new/ to cur/ , but there is no specification of other cases; in fact, lots of MUA's will change info when the file has been in cur/ for a while: mutt, for example, moves the file from new/ to cur/, adds :2, and only modifies that to be 2,S after the user has read the message (it is no longer 'N'ew). Right, but that's my point. To specify another case. Regards.
Re: qmail-pop3d bug
On Mon, Mar 12, 2001 at 11:03:33AM +, Mark Delany wrote: To me that implies that a file in new cannot have an "info" section. You're right. I didn't think the original point throuhgh. Regards, Vince.
Re: qmail-pop3d bug
Peter van Dijk wrote: Not if it's calculated as the file is written to the Maildir. True, but that hurts writing performance. Have you tested this? It doesn't seem that qmail has ever been CPU bound -- and if the CPU has spare cycles while writing, then counting lines and adding bytes for CR/LF won't hurt writing performance at all. -- Michael T. Babcock (PGP: 0xBE6C1895) http://www.fibrespeed.net/~mbabcock/
Re: qmail-pop3d bug
On Mon, Mar 12, 2001 at 08:55:47AM -0500, Michael T. Babcock wrote: Peter van Dijk wrote: Not if it's calculated as the file is written to the Maildir. True, but that hurts writing performance. Have you tested this? It doesn't seem that qmail has ever been CPU bound -- and if the CPU has spare cycles while writing, then counting lines and adding bytes for CR/LF won't hurt writing performance at all. 'hurts writing performance' (although you are right :) also means 'increases resource use', in whatever way. Measuring in wall-clock time, the performance hit is probably negligible indeed. Greetz, Peter.
Re: qmail-pop3d bug
John R. Levine wrote: Pop3d just reports the file sizes, while it's clear from the RFC that it's supposed to report the wire size of each message, i.e., the size using cr/lf as a line terminator, so the sizes it reports are too small. Peter van Dijk replied: Yes. This behaviour is known. Fixing it, however, involves a *huge* performance downgrade of qmail-pop3d. Scott Gifford pondered: A solution I have considered is storing the messages in wire format. Especially for POP/IMAP-only clients, seems like it could be a medium-sized performance win, since the line-conversion is done only once, regardless of how many times the message is downloaded. If the message were kept in wire-format from SMTP through delivery, no line conversion would be required at either end, and a larger performance gain would be possible. Has anybody tried this, or anything like it? Something like that, yes. My last job involved building custom SMTP and POP3 servers from scratch. I stored messages in a quasi-maildir-ish folder scheme, and left the CRLF linebreaks intact. Since there were no local users on this box, there was no need to worry about local MUA's, and everything ran smoothly. I would think that it probably wouldn't be too much trouble to rig an MUA to look for CRLFs, so that it could coexist in this environment if need be. ---Kris Kelley
Re: qmail-pop3d bug
On Sat, Mar 10, 2001 at 05:47:29PM -0500, Scott Gifford wrote: Peter van Dijk [EMAIL PROTECTED] writes: On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote: The usual mailbox vs. maildir war has flared up on inet-access, and points out a bug in qmail-pop3d. When you do a LIST command, it gives you the size of each message. Pop3d just reports the file sizes, while it's clear from the RFC that it's supposed to report the wire size of each message, i.e., the size using cr/lf as a line terminator, so the sizes it reports are too small. [ ... ] Yes. This behaviour is known. Fixing it, however, involves a *huge* performance downgrade of qmail-pop3d. A solution I have considered is storing the messages in wire format. Especially for POP/IMAP-only clients, seems like it could be a medium-sized performance win, since the line-conversion is done only once, regardless of how many times the message is downloaded. If the message were kept in wire-format from SMTP through delivery, no line conversion would be required at either end, and a larger performance gain would be possible. Has anybody tried this, or anything like it? Have not tried it, but it sounds like it would definitely work. Greetz, Peter.
Re: qmail-pop3d bug
On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote: The usual mailbox vs. maildir war has flared up on inet-access, and points out a bug in qmail-pop3d. When you do a LIST command, it gives you the size of each message. Pop3d just reports the file sizes, while it's clear from the RFC that it's supposed to report the wire size of each message, i.e., the size using cr/lf as a line terminator, so the sizes it reports are too small. I gather nobody's ever reported this as a bug, and I expect that the only thing that uses the size is the "don't download bigger than size X" option for which it's close enough, but it's still wrong. If I mis-remember correctly, qpopper may have a similar problem in that the stated size does not necessarily match the size sent down the wire. How so? Because qpopper adds X-UIDL and Status: headers to the out-going message (perhaps it includes this in the size calc but I haven't looked at the code in such a long time, or perhaps it only adds those headers when the mail is re-written). I use courier-imap, and its POP daemon does get the sizes right, presumably by reading the files and adding the number of \n characters. A more sensible strategy might be to introduce a new "info" flag (say '3' equals POP wire size) on the filename, eg, a 10,000 byte email has a name something like this: Maildir/new/980195114.16740.geex:2,RS3,1 Optimally the wire-size is calculated when the mail is written to Maildir/tmp/ and then applied as an "info" flag when the file is moved to Maildir/new/. A possible complication with this approach is that my reading of Maildir infers that "info" can only be set when the file moves from Maildir/new/ to Maildir/cur/. Regards.
Re: qmail-pop3d bug
Yes. This behaviour is known. Fixing it, however, involves a *huge* performance downgrade of qmail-pop3d. Not if it's calculated as the file is written to the Maildir. 'Usually, during the AUTHORIZATION state of the POP3 session, the POP3 server can calculate the size of each message in octets when it opens the maildrop. . simply counts each occurance of this character in a message as two octets.' Typical of those RFCs authors that, consciously or otherwise, used a single implementation to guide much of their thinking on protocol design. POP3 is not the only standard that suffers as a consequence - consider SMTP and DNS? We shouldn't have to live with short-sightedness forever. Regards.
