Re: Mail Stuck in Queue
>What's the output of "ps awwux | grep qmail"? For both Mr. Johnson and Mr. Delaney (whose message is now queued): root@wndrgrl:~/qmail-1.03# ps awwux|grep qmail root 242 0.0 0.2 1068 332 ?SApr30 0:01 /usr/local/bin/tcpserver -R -H 0 110 /var/qmail/bin/qmail-popup wndrgrl.goldblatt.net /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir qmaild 14559 0.0 0.4 1356 556 pts/1S16:28 0:00 /usr/local/bin/tcpserver -x /etc/tcprules/tcp.smtp.cdb -u 1004 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd root 14560 0.0 0.2 1056 292 pts/1S16:28 0:00 /var/qmail/bin/splogger smtpd 3 root@wndrgrl:~/qmail-1.03# So apparently qmail-send isn't running. But based on the qmail pictures at crypto, qmail-send is triggered by qmail-queue. I suppose I'm misinterpreting "triggered" to mean spawned or forked, when it means signaled? As I write this I'm also investigating the supervise scripts (section 2.8.2.2) at LWQ; am I correct in believing that correctly installing qmail under supervise (rather than rc.d as now) would resolve my issue, and that qmail-send would then go about unsticking my queue? Thank you. ag _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Mail Stuck in Queue
On Wed, May 02, 2001 at 09:30:17PM -, Aaron Goldblatt wrote: > As I indicated, syslog shows noting useful. Just lots of me logging in via > SSH and su'ing to root. No qmail-related entries, save the rbl rejection, > since 4/30/01 at quarter past noon. This is in /var/log/messages, right? Try looking at /var/log/maillog. If there is no such thing, check the contents of /etc/syslog.conf to figure out where 'mail' messages are being sent. > ps aux shows this (again, beware wordwrap): > > root 242 0.0 0.2 1068 332 ? S Apr30 0:01 /usr/local/bin/tcpserver -R -H 0 110 >/var/qmail/bin/qmail-popup wndrg... > qmaild 9798 0.0 0.4 1356 556 ? S 12:34 0:00 /usr/local/bin/tcpserver -R -H -x >/etc/tcprules/tcp.smtp.cdb -u 1004 ... > root 9799 0.0 0.2 1056 292 ? S 12:34 0:00 /var/qmail/bin/splogger smtpd 3 How did you generate this output? In other words, did you run ps aux | grep qmail or did you just run 'ps aux' and cut-n-paste the relevant parts? The reason I ask is that you are not showing the following entries: qmails 223 0.0 0.6 936 384 con- I Fri01AM 0:58.06 qmail-send root 240 0.0 0.4 880 264 ?? I Fri01AM 0:07.17 qmail-lspawn ./Maildir/ qmailr 241 0.0 0.6 892 364 ?? I Fri01AM 0:03.92 qmail-rspawn qmailq 242 0.0 0.5 868 292 ?? I Fri01AM 0:10.63 qmail-clean These are created when you run 'qmail-start' through one of your system startup scripts. Normally that script is a copy of one of the files in /var/qmail/boot . I don't know what OS you're running, so I can't tell you where to look, but you should have such a script. Those 4 programs are the programs that actually control mail delivery, both locally (qmail-lspawn) and remotely (qmail-rspawn). They need to be running. Tim -- * * * | 1) It's SLOW!--> "man tcpserver" - especially -R,-H,-l qmail | 2) Roaming users --> http://www.lifewithqmail.org/lwq.html#relaying FAQS | 3) Secondary MX --> list in rcpthosts, NOT in locals/virtualdomains * * * | 4) Discard mail --> "#" line ONLY, in appropriate .qmail file
Re: Mail Stuck in Queue
Aaron Goldblatt <[EMAIL PROTECTED]> wrote: > > All mail that gets queued for delivery simply sits in the queue and doesn't > get delivered. [...] > ps aux shows this (again, beware wordwrap): > > root 242 0.0 0.2 1068 332 ?SApr30 0:01 > /usr/local/bin/tcpserver -R -H 0 110 /var/qmail/bin/qmail-popup > wndrg...qmaild9798 0.0 0.4 1356 556 ?S12:34 0:00 > /usr/local/bin/tcpserver -R -H -x /etc/tcprules/tcp.smtp.cdb -u 1004 ... > root 9799 0.0 0.2 1056 292 ?S12:34 0:00 > /var/qmail/bin/splogger smtpd 3 qmail-send isn't running (the part that actually takes messages out of the queue, and delivers them locally or remotely). Run your qmail-start script or equivalent, or issue an appropriate command to svscan. 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: Mail Stuck in Queue
On Wed, May 02, 2001 at 09:30:17PM -, Aaron Goldblatt wrote: > All mail that gets queued for delivery simply sits in the queue and doesn't > get delivered. It doesn't matter if the mail is for local delivery, or is > relay mail headed for a remote mail server. Is qmail-send running? It doesn't sound like it is. What's the output of "ps awwux | grep qmail"? Chris PGP signature
Re: Mail Stuck in Queue
Is qmail running? What does ps aux | grep qmail show? (Or whatever ps is appropriate for your OS?) Regards. On Wed, May 02, 2001 at 09:30:17PM -, Aaron Goldblatt wrote: > After resolving the POP slowdown issue with the help of some of the more > polite folks here, I have developed a new problem. > > All mail that gets queued for delivery simply sits in the queue and doesn't > get delivered. It doesn't matter if the mail is for local delivery, or is > relay mail headed for a remote mail server. > > What I am aware of changing: I added -R and -H to tcpserver's command line, > and I added my 10.x.x.x network to tcp.smtp.cdb. I can now deliver mail via > SMTP to rblsmtpd, and it does queue the mail, so I doubt the issue is in my > tcp connection rules. > > I am accepting connections with rblsmtpd with the no-TXT-records patch, and > logging is being done by splogger to /var/log/messages. > > There are no messages indicating anything related to qmail in syslog since > the issue began, except for one notation where rblsmtpd rejected a message > from a black holed site. > > The line invoking rblsmtpd is (beware wordwrap): > > /usr/local/bin/tcpserver -R -H -x /etc/tcprules/tcp.smtp.cdb \ >-u 1004 -g 2108 0 smtp /usr/local/bin/rblsmtpd -r > blackholes.mail-abuse.org \ >-r dialups.mail-abuse.org \ >-r 'relays.mail-abuse.org:Open relay problem - see > http://www.mail-abuse.org/cgi-bin/nph-rss?%IP%>' \ >/var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 & > > > > > I can see messages queueing in /var/qmail/queue/mess/*, but they are not > delivered either locally or to a remote host (mail.swbell.net). > > Through testing with other mail servers, I have determined that > mail.swbell.net is operating normally -- it both sends and receives mail. > I've sent test messages to my problem machine via mail.swbell.net and found > them in my queue, waiting for local delivery. > > /var/qmail/queue/lock/trigger has permissions as described in LWQ. > > The home directories of the users on the system are owned by themselves. > Some are world-readable, some are not. None are world-writable: > > drwx-- 5 aaronusers4096 Feb 24 07:37 aaron > drwx--x--x 5 bluerose users4096 Feb 24 07:37 blueroses > drwx--x--x 5 boby users4096 Apr 11 21:32 boby > drwx--x--x 5 dhwork users4096 Mar 16 01:48 dhwork > drwx--x--x 5 djh users4096 Feb 24 07:38 djh > drwx--x--x 5 dnslog users4096 Mar 24 08:25 dnslog > drwx--x--x 5 ebay users4096 Feb 24 07:38 ebay > drwx--x--x 5 friendof users4096 Feb 24 07:39 friendofbillw > drwx--x--x 5 gtg users4096 Mar 29 09:37 gtg > drwx--x--x 5 listsusers4096 May 2 12:44 lists > drwx--x--x 6 netgeek users4096 Apr 13 21:37 netgeek > drwx--x--x 6 rc5 users4096 Feb 25 08:56 rc5 > drwx--x--x 17 rnbwpnt users4096 Apr 29 05:56 rnbwpnt > drwx--x--x 6 shewolf users4096 Apr 23 18:42 shewolf > drwx--x--x 5 shik users4096 Feb 24 07:41 shik > drwx--x--x 5 thesaint users4096 May 2 14:24 thesaint > drwx--x--x 5 vendors users4096 Feb 24 07:42 vendors > drwx--x--x 5 viquiusers4096 Feb 24 07:42 viqui > > > > This is the output from qmail-showctl: > > qmail home directory: /var/qmail. > user-ext delimiter: -. > paternalism (in decimal): 2. > silent concurrency limit: 120. > subdirectory split: 23. > user ids: 1003, 1004, 1005, 0, 1006, 1007, 1008, 1009. > group ids: 2108, 2107. > > badmailfrom: (Default.) Any MAIL FROM is allowed. > bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. > bouncehost: (Default.) Bounce host name is wndrgrl.goldblatt.net. > concurrencylocal: (Default.) Local concurrency is 10. > concurrencyremote: (Default.) Remote concurrency is 20. > databytes: (Default.) SMTP DATA limit is 0 bytes. > defaultdomain: Default domain name is goldblatt.net. > defaulthost: Default host name is goldblatt.net. > doublebouncehost: (Default.) 2B recipient host: wndrgrl.goldblatt.net. > doublebounceto: (Default.) 2B recipient user: postmaster. > envnoathost: (Default.) Presumed domain name is wndrgrl.goldblatt.net. > helohost: (Default.) SMTP client HELO host name is wndrgrl.goldblatt.net. > idhost: (Default.) Message-ID host name is wndrgrl.goldblatt.net. > localiphost: (Default.) Local IP address becomes wndrgrl.goldblatt.net. > locals: > Messages for localhost are delivered locally. > Messages for wndrgrl.goldblatt.net are delivered locally. > Messages for virtualhost.goldblatt.net are delivered locally. > Messages for goldblatt.net are delivered locally. > me: My name is wndrgrl.goldblatt.net. > percenthack: (Default.) The percent hack is not allowed. > plusdomain: Plus domain name is goldblatt.net. > qmqpservers: (Default.) No QMQP servers. > queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
Re: Mail stuck in queue - what to do about it?
On Thu, Jan 27, 2000 at 12:39:11PM -0800, Mark Delany wrote: > On Thu, Jan 27, 2000 at 08:31:09PM +, Chris Green wrote: > > I have 36 messages which appear to be permanently stuck in the queue, > > I'm running qmail 1.03 with the holdremote patch on Mandrake Linux > > 6.1. > > > > Normally everything runs quite smoothly but I sent a *lot* of mail > > (by my standards!) last night, probably a few hundred messages in > > ten minutes or so and these 36 messages have 'stuck'. Most of the > > messages were to the same destination so I can't see what's special > > about these. > > What did you conclude from looking at the log messages associated > with sending these messages? Do the log messages indicate a reason > why they might be "stuck"? Is it a reason that you can fix? Is it > a reason that someone else is likely to fix? > Aha, a good point, sorry! They have been 'deferred' because the sender domain doesn't resolve, I 'bounced' them using mutt so the From: address doesn't change and they were originally from a domain that no longer exists! Thanks for your help - I must remember to look in the logs next time, a bit like RTFM but it's RTFL. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Mail stuck in queue - what to do about it?
On Thu, Jan 27, 2000 at 09:39:58PM -, Petr Novotny wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 27 Jan 00, at 20:31, Chris Green wrote: > > I have tried 'kill -ALRM ' but that doesn't seem to > > encourage anything to happen. > > Try running qmail-tcpok _before_ ALRMing qmail-send. > Nothing interesting happens. > > What do I have to do to get rid of these > > messages? It doesn't matter too much if there lost even. > > Why does it matter then that they're in queue? If they're > undeliverable for a week, they'll get deleted (bounced) anyway. > A good point, maybe I'll just forget about them until they get sent back to me. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Mail stuck in queue - what to do about it?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27 Jan 00, at 20:31, Chris Green wrote: > I have tried 'kill -ALRM ' but that doesn't seem to > encourage anything to happen. Try running qmail-tcpok _before_ ALRMing qmail-send. > What do I have to do to get rid of these > messages? It doesn't matter too much if there lost even. Why does it matter then that they're in queue? If they're undeliverable for a week, they'll get deleted (bounced) anyway. -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOJC7LlMwP8g7qbw/EQInMACg+g6ygPCq5/X4AmAjtyBwjQ2zXiMAoPUu uwMrydreqnTFg17Z6FOX+fCh =YD2n -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Mail stuck in queue - what to do about it?
On Thu, Jan 27, 2000 at 08:31:09PM +, Chris Green wrote: > I have 36 messages which appear to be permanently stuck in the queue, > I'm running qmail 1.03 with the holdremote patch on Mandrake Linux > 6.1. > > Normally everything runs quite smoothly but I sent a *lot* of mail > (by my standards!) last night, probably a few hundred messages in > ten minutes or so and these 36 messages have 'stuck'. Most of the > messages were to the same destination so I can't see what's special > about these. What did you conclude from looking at the log messages associated with sending these messages? Do the log messages indicate a reason why they might be "stuck"? Is it a reason that you can fix? Is it a reason that someone else is likely to fix? Regards.
