qmail Digest 28 Jan 2000 11:00:00 -0000 Issue 894
Topics (messages 36220 through 36289):
How to watch the current receiving messages?
36220 by: Ari Arantes Filho
Re: About offline
36221 by: Faried Nawaz
Re: remote root qmail-pop with vpopmail advisory and exploit with patch
(fwd)
36222 by: Peter Haworth
Loopback? Was: open relay problem
36223 by: Peter Green
broadcast message
36224 by: TAG
Outlook address book oddity
36225 by: Simon Rae
36229 by: Frank Tegtmeyer
36230 by: Dave Sill
Annoyance
36226 by: Tim Hunter
36227 by: Peter Green
36228 by: Dave Sill
36235 by: Chris Johnson
36238 by: Paul Farber
Re: problems with 'mail' (procmail?)
36231 by: Dave Sill
Re: Queue Problem
36232 by: Dave Sill
Re: qmail-pop3d: unable to write pipe
36233 by: Dave Sill
Re: Message delivery failure question
36234 by: Dave Sill
Re: Strange queue behaviour]
36236 by: Faried Nawaz
36252 by: Chris Readle
36264 by: Chris Readle
Getting proper mail notifications
36237 by: Scott Schappell
36239 by: Mark Delany
36240 by: Charles Cazabon
36241 by: Vince Vielhaber
36243 by: Faried Nawaz
Re: What MUA do you use?
36242 by: Chris Garrigues
36250 by: Dave Sill
36259 by: Matthew Brown
36277 by: Mark E. Drummond
Re: Mail Stuck In Bin
36244 by: Dave Sill
Re: smtp authentication
36245 by: Dave Sill
Re: qmail delivery slowdown under high load
36246 by: richard.illuin.org
Re: More setup questions
36247 by: Dave Sill
Re: subdomain qmail locals
36248 by: Dave Sill
36256 by: Robert Sander
36257 by: Scott Schappell
36279 by: Scott Beck
36280 by: Scott Beck
Re: VIRTUAL DOMAIN
36249 by: Dave Sill
Qmail behaviour
36251 by: Adil Tahiri
36253 by: Dave Sill
more about procmail and qmail
36254 by: Jennifer Tippens
Re: [FIXED] Getting proper mail notifications
36255 by: Scott Schappell
Supervise won't kill tcpserver
36258 by: Bill Rogers
Mail stuck in queue - what to do about it?
36260 by: Chris Green
36261 by: Mark Delany
36262 by: Petr Novotny
36263 by: Chris Green
36265 by: Chris Green
DNS
36266 by: Juan E Suris
36267 by: Ruben van der Leij
36268 by: Russell P. Sutherland
36269 by: Juan E Suris
36270 by: Chris Johnson
36271 by: Steve Wolfe
36272 by: Juan E Suris
36284 by: Frank Tegtmeyer
Re: FLUSH QUEUE
36273 by: Stephen Mills
Re: big fat qmail-command hole
36274 by: Stig Hackv�n
36275 by: Phil Genera
36278 by: Magnus Bodin
"Upgrade" causing "temporary failure"
36276 by: Mark E. Drummond
Sleeping qmail
36281 by: Alok Bhatt
Re: Duplicates on outbound mail, not inbound
36282 by: D. J. Bernstein
Open Relay
36283 by: Muhammad Ali
36285 by: Lorens Kockum
cannot remove files in pic directory
36286 by: $BCf@>(J $B??0l(J
Qmail crashing TCP/IP-stack
36287 by: Henrik �hman
36288 by: Petr Novotny
36289 by: Henrik �hman
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Hi, With qmail-qread, qmail-qstat and qmHandle, I can watch the queue, but how can I see the current open stmp session that are receiving messages? And how can I get more information about these messages? Best regards, Ari
Md. Sifat Ullah Patwary wrote: I am running an offline Internet Server. I like to use qmail server in my LAN. How can I queue my out going mail from my LAN till the server goes online and how can i retrive my in coming mails which are also queued in other Inthernet mail (running qmail) server? Use serialmail -- http://cr.yp.to/serialmail.html. The AutoTURN feature will do exactly what you want.
Pavel Kankovsky wrote: > On Wed, 26 Jan 2000, Russell Nelson wrote: > > > > 2. qmail-send is run as root? > > > > Yup. Well, qmail-start is run as root. Along the line it gives up > > its rootness, becoming qmail-send, and leaving only qmail-lspawn > > running as root. > > Login is run as root. It switches to my privs and execs my login > shell. Therefore my login shell is run as root. Right? :) Login is run as root. Once you've entered a correct username/password pair, it switches to that user, so it isn't running as root any more. Your login shell runs as your user. It wouldn't make sense otherwise. Maybe this was a troll after all... -- Peter Haworth [EMAIL PROTECTED] "I have yet to see any problem, however complicated, which, when you looked at it the right way, did not become still more complicated." -- Poul Anderson
On Thu, Jan 27, 2000 at 10:02:45AM +0100, Dr. Erwin Hoffmann wrote: > Hi, > > try my SPAMCONTROL Patch I posted into this group recently. > However, I really advise everybody NOT to use the LOOPBACK address to be > included in the relaying control mechanism. Its easy enough to fake that. It's easy enough to fake a loopback address for packets coming in on a non-loopback device? This is not a qmail issue; this should be dealt with somewhere along the way by network filtering. Something like: ipchains -I accept 1 -S 127.0.0.1 -i !lo -j DENY theoretically should do the trick (untested). /pg -- Peter Green Gospel Communications Network, SysAdmin [EMAIL PROTECTED]
HI, Is there a way of sending all users a broadcast message?? --Many thans Tonino
Hi This is more of a petty annoyance than anything else, but I'd like to know if anyone else has experienced it. I recently was contacted by a user saying that they were getting bounce messages back each time they tried to send mail to a particular local address. Upon further investigation it turns out that although this recipient's email address in her Outlook address book was spelt correctly, there was a space after the last character. When I checked the qmail logs, this space appears as a question mark at causing the message to bounce. Anyone have any ideas? When I type a space after an email address directly in the 'TO' field it goes OK suggesting this is more than likely a flaw in Outlook. Any ideas??? ta Si
> Any ideas??? Encourage your users to hate Outlook ... Regards, Frank
[EMAIL PROTECTED] wrote: >This is more of a petty annoyance than anything else, but I'd like to >know if anyone else has experienced it. I recently was contacted by a >user saying that they were getting bounce messages back each time they >tried to send mail to a particular local address. Upon further >investigation it turns out that although this recipient's email address >in her Outlook address book was spelt correctly, there was a space after >the last character. When I checked the qmail logs, this space appears as >a question mark at causing the message to bounce. My address is "[EMAIL PROTECTED]", not "[EMAIL PROTECTED] ". If you use the latter, you should expect it to fail. The space is converted to a "?" in the logs because all non-printable characters are displayed as ?'s. The message isn't failing because of the conversion done for the log. >Anyone have any ideas? When I type a space after an email address >directly in the 'TO' field it goes OK suggesting this is more than >likely a flaw in Outlook. Your MUA strips trailing whitespace. One can argue that Outlook should also do that, but one can also argue that users should enter addresses correctly. Of course, any s/w that expects the user to do the right thing is either broken or rude. � :-) -Dave
I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. Thanks in advance Tim Hunter CIMx Company [EMAIL PROTECTED] http://www.cimx.com
On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: > I just noticed in my logs that a specific host, mrelay0.starwave.com keeps > opening a smtp connection every minute or so. Should I just outright deny > this connection from connecting or is there a way to find out what is going > on? > Nothing shows up in my logs as far as something being delivered. Isn't that the kind of behavior that happens when a bare LF is found? I'm seeing it a lot from www.projectorcentral.com (which is using Cold Fusion...). /pg -- Peter Green Gospel Communications Network, SysAdmin [EMAIL PROTECTED]
Peter Green <[EMAIL PROTECTED]> wrote: >On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: >> I just noticed in my logs that a specific host, mrelay0.starwave.com keeps >> opening a smtp connection every minute or so. Should I just outright deny >> this connection from connecting or is there a way to find out what is going >> on? >> Nothing shows up in my logs as far as something being delivered. > >Isn't that the kind of behavior that happens when a bare LF is found? Yeah, except well-behaved MTA's don't try to resend every minute. This can be debugged using recordio to record the SMTP session. See the FAQ. -Dave
On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: > I just noticed in my logs that a specific host, mrelay0.starwave.com keeps > opening a smtp connection every minute or so. Should I just outright deny > this connection from connecting or is there a way to find out what is going > on? > Nothing shows up in my logs as far as something being delivered. I had that same host doing that to me. It's sending a message with bare linefeeds in it. I just cut them off with tcpserver. Chris
They may be sending a bare linefeed in the message. Qmail seems to have this problem. From what I understand it's not gonna be fixed bacause it's the other server's fault.... not a qmail problem. Paul Farber Farber Technology [EMAIL PROTECTED] Ph 570-628-5303 Fax 570-628-5545 On Thu, 27 Jan 2000, Tim Hunter wrote: > I just noticed in my logs that a specific host, mrelay0.starwave.com keeps > opening a smtp connection every minute or so. Should I just outright deny > this connection from connecting or is there a way to find out what is going > on? > Nothing shows up in my logs as far as something being delivered. > > Thanks in advance > Tim Hunter > CIMx Company > [EMAIL PROTECTED] > http://www.cimx.com > > >
"Eric LaLonde" <[EMAIL PROTECTED]> wrote: >I've moved the file /var/spool/mail/user to ~user/Mailbox and made a >symbolic link back to /var/spool/mail/user, but it doesn't seem to >stay. It will say that I have new mail in /var/spool/mail/user, and >then when i go to view that mail via 'mail', it gives me this >message: > >This text is part of the internal format of your mail folder, and is >not a real message. It is created automatically by the mail system >software. If deleted, important folder data will be lost, and it >will be re-created with the data reset to initial values. > >I then quit out of mail, it saves it to mbox, and then the link >/var/spool/mail/user is gone. This line is in my maillog: Jan 25 >13:36:52 damacles procmail[5961]: Renamed bogus >"/var/spool/mail/root" into "/var/spool/mail/BOGUS.root.VUJ" > >Why is this happening, and why aren't my links sticking, and what >should i do? Procmail doesn't like the symlink in /var/spool/mail so it renames it. The fix is to read INSTALL.mbox and follow the directions for configuring the mail reader to look directly in ~user/Mailbox. -Dave
[EMAIL PROTECTED] wrote: >When I sent to a mailing list it ques the entire list (175,000 addresses) >then the que takes forever (24 hours) to deliver. Anyway to speed this up? >The server is a dedicated P 450, 128Meg, RedHat. Dedicated to qmail. 1. Increase concurrencyremote. Rebuild with conf-spawn set to 255 before raising it past 120. Install the "big concurrency" patch if you need to go past 255. 2. Put the queue on a fast disk on a dedicated SCSI interface. 3. Install dnscache. I can do 175k deliveries on my list server in ~3 hours, and I haven't done (2) yet. -Dave
John White <[EMAIL PROTECTED]> wrote: >Symptoms: users can issue USER and PASS commands, but an immediate >-ERR unable to write pipe >is issued. > >contents of >/service/qmail-pop3d/run: >#!/bin/sh > /usr/local/bin/tcpserver -v 0 pop3 /var/qmail/bin/qmail-popup \ > triceratops.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 > >Any ideas? I think you need to "exec" tcpserver. -Dave
"Randolph S. Kahle" <[EMAIL PROTECTED]> wrote: >"[...] deferral: Connected_to_151.xxx.x.xx_but_connection_died._(#4.4.2)/" > >The email is being send to an address <person_name>@<company>.com that >works when I send the email through another SMTP server. So, I thought this >might be a DNS problem. I switched my resolv.conf to point to the DNS that >the working SMTP server uses and this does not seem to fix the problem. It could still be a DNS problem. The other MTA might be lenient about DNS misconfiguration than qmail. Post the details and let a DNS expert check it out. -Dave
Chris Readle <[EMAIL PROTECTED]> writes: Chris Readle wrote: > > I'm having a bit of strand queue behaviour. Basically I've got 50+ (I > think 54, without looking) local-bound messages in the queue that I > cannot get to flush no matter what I try. I've tried sending an ALRM, a > HUP, stopping and restarting qmail and rebooting the server. The > messages are still there. Everything else seems to be running great and > new messages are going in and out with no problems, but these message > justs won't deliver. Any ideas? > > chris Show us what the logs say when you try to flush the queue.
Faried Nawaz wrote: > > Chris Readle <[EMAIL PROTECTED]> writes: > > Chris Readle wrote: > > > > I'm having a bit of strand queue behaviour. Basically I've got 50+ (I > > think 54, without looking) local-bound messages in the queue that I > > cannot get to flush no matter what I try. I've tried sending an ALRM, a > > HUP, stopping and restarting qmail and rebooting the server. The > > messages are still there. Everything else seems to be running great and > > new messages are going in and out with no problems, but these message > > justs won't deliver. Any ideas? > > > > chris > > Show us what the logs say when you try to flush the queue. I think I see the problem, now....I'm getting message has wrong owner and unable to switch to directory....I'll attach the relevant log portion. chris948992273.168662 starting delivery 121: msg 230524 to local [EMAIL PROTECTED] 948992273.168675 status: local 1/20 remote 0/30 948992273.171009 delivery 121: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992273.171024 status: local 0/20 remote 0/30 948992396.674129 starting delivery 122: msg 230525 to local [EMAIL PROTECTED] 948992396.674143 status: local 1/20 remote 0/30 948992396.674150 starting delivery 123: msg 230524 to local [EMAIL PROTECTED] 948992396.674162 status: local 2/20 remote 0/30 948992396.693089 starting delivery 124: msg 230532 to local [EMAIL PROTECTED] 948992396.693103 status: local 3/20 remote 0/30 948992396.693110 delivery 122: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693124 status: local 2/20 remote 0/30 948992396.693131 delivery 123: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693145 status: local 1/20 remote 0/30 948992396.693152 starting delivery 125: msg 230522 to local [EMAIL PROTECTED] 948992396.693164 status: local 2/20 remote 0/30 948992396.709790 starting delivery 126: msg 232574 to local [EMAIL PROTECTED] 948992396.709803 status: local 3/20 remote 0/30 948992396.709811 delivery 124: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709825 status: local 2/20 remote 0/30 948992396.709832 delivery 125: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709846 status: local 1/20 remote 0/30 948992396.728920 starting delivery 127: msg 232568 to local [EMAIL PROTECTED] 948992396.728933 status: local 2/20 remote 0/30 948992396.728940 delivery 126: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.728952 status: local 1/20 remote 0/30 948992396.750439 starting delivery 128: msg 232590 to local [EMAIL PROTECTED] 948992396.750452 status: local 2/20 remote 0/30 948992396.750459 delivery 127: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.750471 status: local 1/20 remote 0/30 948992396.768174 starting delivery 129: msg 232601 to local [EMAIL PROTECTED] 948992396.768187 status: local 2/20 remote 0/30 948992396.768194 delivery 128: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.768206 status: local 1/20 remote 0/30 948992396.772692 starting delivery 130: msg 230533 to local [EMAIL PROTECTED] 948992396.772705 status: local 2/20 remote 0/30 948992396.772712 delivery 129: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.772724 status: local 1/20 remote 0/30 948992396.786670 starting delivery 131: msg 232600 to local [EMAIL PROTECTED] 948992396.786683 status: local 2/20 remote 0/30 948992396.786690 delivery 130: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.786704 status: local 1/20 remote 0/30 948992396.787520 starting delivery 132: msg 232577 to local [EMAIL PROTECTED] 948992396.787533 status: local 2/20 remote 0/30 948992396.787540 delivery 131: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.787551 status: local 1/20 remote 0/30 948992396.802177 starting delivery 133: msg 232604 to local [EMAIL PROTECTED] 948992396.802190 status: local 2/20 remote 0/30 948992396.802197 delivery 132: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.802208 status: local 1/20 remote 0/30 948992396.820684 starting delivery 134: msg 232591 to local [EMAIL PROTECTED] 948992396.820697 status: local 2/20 remote 0/30 948992396.820704 delivery 133: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.820716 status: local 1/20 remote 0/30 948992396.839303 starting delivery 135: msg 232575 to local [EMAIL PROTECTED] 948992396.839316 status: local 2/20 remote 0/30 948992396.839323 delivery 134: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.839335 status: local 1/20 remote 0/30 948992396.840144 starting delivery 136: msg 232581 to local [EMAIL PROTECTED] 948992396.840157 status: local 2/20 remote 0/30 948992396.840164 delivery 135: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.840176 status: local 1/20 remote 0/30 948992396.859953 starting delivery 137: msg 230531 to local [EMAIL PROTECTED] 948992396.859967 status: local 2/20 remote 0/30 948992396.859974 delivery 136: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.859985 status: local 1/20 remote 0/30 948992396.875262 starting delivery 138: msg 232592 to local [EMAIL PROTECTED] 948992396.875274 status: local 2/20 remote 0/30 948992396.875281 delivery 137: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.875293 status: local 1/20 remote 0/30 948992396.876087 starting delivery 139: msg 232569 to local [EMAIL PROTECTED] 948992396.876100 status: local 2/20 remote 0/30 948992396.876106 delivery 138: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.876118 status: local 1/20 remote 0/30 948992396.890123 starting delivery 140: msg 232582 to local [EMAIL PROTECTED] 948992396.890136 status: local 2/20 remote 0/30 948992396.890143 delivery 139: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.890155 status: local 1/20 remote 0/30 948992396.904920 starting delivery 141: msg 232570 to local [EMAIL PROTECTED] 948992396.904933 status: local 2/20 remote 0/30 948992396.904939 delivery 140: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.904951 status: local 1/20 remote 0/30 948992396.925058 starting delivery 142: msg 232571 to local [EMAIL PROTECTED] 948992396.925071 status: local 2/20 remote 0/30 948992396.925078 delivery 141: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.925090 status: local 1/20 remote 0/30 948992396.944740 starting delivery 143: msg 232587 to local [EMAIL PROTECTED] 948992396.944753 status: local 2/20 remote 0/30 948992396.944760 delivery 142: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.944771 status: local 1/20 remote 0/30 948992396.960305 starting delivery 144: msg 232583 to local [EMAIL PROTECTED] 948992396.960318 status: local 2/20 remote 0/30 948992396.960325 delivery 143: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.960337 status: local 1/20 remote 0/30 948992396.961138 starting delivery 145: msg 232593 to local [EMAIL PROTECTED] 948992396.961151 status: local 2/20 remote 0/30 948992396.961158 delivery 144: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.961170 status: local 1/20 remote 0/30 948992396.981837 starting delivery 146: msg 232605 to local [EMAIL PROTECTED] 948992396.981850 status: local 2/20 remote 0/30 948992396.981857 delivery 145: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.981869 status: local 1/20 remote 0/30 948992397.001238 starting delivery 147: msg 232579 to local [EMAIL PROTECTED] 948992397.001251 status: local 2/20 remote 0/30 948992397.001258 delivery 146: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.001270 status: local 1/20 remote 0/30 948992397.002055 starting delivery 148: msg 232602 to local [EMAIL PROTECTED] 948992397.002068 status: local 2/20 remote 0/30 948992397.002075 delivery 147: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.002087 status: local 1/20 remote 0/30 948992397.016799 starting delivery 149: msg 232594 to local [EMAIL PROTECTED] 948992397.016811 status: local 2/20 remote 0/30 948992397.016818 delivery 148: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.016830 status: local 1/20 remote 0/30 948992397.030390 starting delivery 150: msg 232572 to local [EMAIL PROTECTED] 948992397.030403 status: local 2/20 remote 0/30 948992397.030410 delivery 149: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.030422 status: local 1/20 remote 0/30 948992397.048259 starting delivery 151: msg 232584 to local [EMAIL PROTECTED] 948992397.048271 status: local 2/20 remote 0/30 948992397.048278 delivery 150: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.048290 status: local 1/20 remote 0/30 948992397.068683 starting delivery 152: msg 232606 to local [EMAIL PROTECTED] 948992397.068695 status: local 2/20 remote 0/30 948992397.068702 delivery 151: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.068714 status: local 1/20 remote 0/30 948992397.089426 starting delivery 153: msg 230528 to local [EMAIL PROTECTED] 948992397.089439 status: local 2/20 remote 0/30 948992397.089446 delivery 152: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.089457 status: local 1/20 remote 0/30 948992397.105158 starting delivery 154: msg 232573 to local [EMAIL PROTECTED] 948992397.105172 status: local 2/20 remote 0/30 948992397.105178 delivery 153: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.105190 status: local 1/20 remote 0/30 948992397.122186 starting delivery 155: msg 232595 to local [EMAIL PROTECTED] 948992397.122200 status: local 2/20 remote 0/30 948992397.122207 delivery 154: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.122219 status: local 1/20 remote 0/30 948992397.140408 starting delivery 156: msg 232599 to local [EMAIL PROTECTED] 948992397.140421 status: local 2/20 remote 0/30 948992397.140428 delivery 155: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.140439 status: local 1/20 remote 0/30 948992397.154104 starting delivery 157: msg 232566 to local [EMAIL PROTECTED] 948992397.154117 status: local 2/20 remote 0/30 948992397.154124 delivery 156: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.154136 status: local 1/20 remote 0/30 948992397.168191 starting delivery 158: msg 232578 to local [EMAIL PROTECTED] 948992397.168204 status: local 2/20 remote 0/30 948992397.168211 delivery 157: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.168223 status: local 1/20 remote 0/30 948992397.186982 starting delivery 159: msg 232585 to local [EMAIL PROTECTED] 948992397.186994 status: local 2/20 remote 0/30 948992397.187001 delivery 158: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.187013 status: local 1/20 remote 0/30 948992397.221952 starting delivery 160: msg 232596 to local [EMAIL PROTECTED] 948992397.221965 status: local 2/20 remote 0/30 948992397.221972 delivery 159: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.221983 status: local 1/20 remote 0/30 948992397.236801 starting delivery 161: msg 230530 to local [EMAIL PROTECTED] 948992397.236814 status: local 2/20 remote 0/30 948992397.236821 delivery 160: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.236833 status: local 1/20 remote 0/30 948992397.237616 starting delivery 162: msg 230526 to local [EMAIL PROTECTED] 948992397.237629 status: local 2/20 remote 0/30 948992397.237636 delivery 161: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.237648 status: local 1/20 remote 0/30 948992397.248445 starting delivery 163: msg 232607 to local [EMAIL PROTECTED] 948992397.248458 status: local 2/20 remote 0/30 948992397.248465 delivery 162: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.248477 status: local 1/20 remote 0/30 948992397.248483 starting delivery 164: msg 230534 to local [EMAIL PROTECTED] 948992397.248495 status: local 2/20 remote 0/30 948992397.248775 delivery 163: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.248788 status: local 1/20 remote 0/30 948992397.268167 starting delivery 165: msg 232597 to local [EMAIL PROTECTED] 948992397.268180 status: local 2/20 remote 0/30 948992397.268187 delivery 164: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992397.268201 status: local 1/20 remote 0/30 948992397.280813 starting delivery 166: msg 232580 to local [EMAIL PROTECTED] 948992397.280826 status: local 2/20 remote 0/30 948992397.280833 delivery 165: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.280844 status: local 1/20 remote 0/30 948992397.299656 starting delivery 167: msg 232586 to local [EMAIL PROTECTED] 948992397.299669 status: local 2/20 remote 0/30 948992397.299676 delivery 166: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.299687 status: local 1/20 remote 0/30 948992397.300495 starting delivery 168: msg 230527 to local [EMAIL PROTECTED] 948992397.300508 status: local 2/20 remote 0/30 948992397.300515 delivery 167: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.300527 status: local 1/20 remote 0/30 948992397.314387 starting delivery 169: msg 232598 to local [EMAIL PROTECTED] 948992397.314400 status: local 2/20 remote 0/30 948992397.314407 delivery 168: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.314419 status: local 1/20 remote 0/30 948992397.333688 starting delivery 170: msg 232567 to local [EMAIL PROTECTED] 948992397.333701 status: local 2/20 remote 0/30 948992397.333708 delivery 169: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.333720 status: local 1/20 remote 0/30 948992397.348671 starting delivery 171: msg 232576 to local [EMAIL PROTECTED] 948992397.348684 status: local 2/20 remote 0/30 948992397.348691 delivery 170: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.348703 status: local 1/20 remote 0/30 948992397.349472 starting delivery 172: msg 230529 to local [EMAIL PROTECTED] 948992397.349485 status: local 2/20 remote 0/30 948992397.349492 delivery 171: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.349504 status: local 1/20 remote 0/30 948992397.366075 starting delivery 173: msg 232588 to local [EMAIL PROTECTED] 948992397.366088 status: local 2/20 remote 0/30 948992397.366095 delivery 172: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.366107 status: local 1/20 remote 0/30 948992397.379157 starting delivery 174: msg 232589 to local [EMAIL PROTECTED] 948992397.379170 status: local 2/20 remote 0/30 948992397.379177 delivery 173: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.379189 status: local 1/20 remote 0/30 948992397.397490 starting delivery 175: msg 232603 to local [EMAIL PROTECTED] 948992397.397503 status: local 2/20 remote 0/30 948992397.397510 delivery 174: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.397522 status: local 1/20 remote 0/30 948992397.403897 starting delivery 176: msg 230523 to local [EMAIL PROTECTED] 948992397.403910 status: local 2/20 remote 0/30 948992397.403916 delivery 175: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992397.403928 status: local 1/20 remote 0/30 948992397.406512 delivery 176: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992397.406527 status: local 0/20 remote 0/30
Chris Readle wrote: > > Faried Nawaz wrote: > > > > Chris Readle <[EMAIL PROTECTED]> writes: > > > > Chris Readle wrote: > > > > > > I'm having a bit of strand queue behaviour. Basically I've got 50+ (I > > > think 54, without looking) local-bound messages in the queue that I > > > cannot get to flush no matter what I try. I've tried sending an ALRM, a > > > HUP, stopping and restarting qmail and rebooting the server. The > > > messages are still there. Everything else seems to be running great and > > > new messages are going in and out with no problems, but these message > > > justs won't deliver. Any ideas? > > > > > > chris > > > > Show us what the logs say when you try to flush the queue. > > I think I see the problem, now....I'm getting message has wrong owner > and unable to switch to directory....I'll attach the relevant log > portion. > > chris I think I should also mention that new messages to these email addresses go through with nary a problem. One of them is the address that I use to send and receive to the list from! :) chris > > ------------------------------------------------------------------------ > 948992273.168662 starting delivery 121: msg 230524 to local [EMAIL PROTECTED] > 948992273.168675 status: local 1/20 remote 0/30 > 948992273.171009 delivery 121: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992273.171024 status: local 0/20 remote 0/30 > 948992396.674129 starting delivery 122: msg 230525 to local [EMAIL PROTECTED] > 948992396.674143 status: local 1/20 remote 0/30 > 948992396.674150 starting delivery 123: msg 230524 to local [EMAIL PROTECTED] > 948992396.674162 status: local 2/20 remote 0/30 > 948992396.693089 starting delivery 124: msg 230532 to local [EMAIL PROTECTED] > 948992396.693103 status: local 3/20 remote 0/30 > 948992396.693110 delivery 122: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992396.693124 status: local 2/20 remote 0/30 > 948992396.693131 delivery 123: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992396.693145 status: local 1/20 remote 0/30 > 948992396.693152 starting delivery 125: msg 230522 to local [EMAIL PROTECTED] > 948992396.693164 status: local 2/20 remote 0/30 > 948992396.709790 starting delivery 126: msg 232574 to local [EMAIL PROTECTED] > 948992396.709803 status: local 3/20 remote 0/30 > 948992396.709811 delivery 124: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992396.709825 status: local 2/20 remote 0/30 > 948992396.709832 delivery 125: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992396.709846 status: local 1/20 remote 0/30 > 948992396.728920 starting delivery 127: msg 232568 to local [EMAIL PROTECTED] > 948992396.728933 status: local 2/20 remote 0/30 > 948992396.728940 delivery 126: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.728952 status: local 1/20 remote 0/30 > 948992396.750439 starting delivery 128: msg 232590 to local [EMAIL PROTECTED] > 948992396.750452 status: local 2/20 remote 0/30 > 948992396.750459 delivery 127: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.750471 status: local 1/20 remote 0/30 > 948992396.768174 starting delivery 129: msg 232601 to local [EMAIL PROTECTED] > 948992396.768187 status: local 2/20 remote 0/30 > 948992396.768194 delivery 128: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.768206 status: local 1/20 remote 0/30 > 948992396.772692 starting delivery 130: msg 230533 to local [EMAIL PROTECTED] > 948992396.772705 status: local 2/20 remote 0/30 > 948992396.772712 delivery 129: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.772724 status: local 1/20 remote 0/30 > 948992396.786670 starting delivery 131: msg 232600 to local [EMAIL PROTECTED] > 948992396.786683 status: local 2/20 remote 0/30 > 948992396.786690 delivery 130: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992396.786704 status: local 1/20 remote 0/30 > 948992396.787520 starting delivery 132: msg 232577 to local [EMAIL PROTECTED] > 948992396.787533 status: local 2/20 remote 0/30 > 948992396.787540 delivery 131: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.787551 status: local 1/20 remote 0/30 > 948992396.802177 starting delivery 133: msg 232604 to local [EMAIL PROTECTED] > 948992396.802190 status: local 2/20 remote 0/30 > 948992396.802197 delivery 132: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.802208 status: local 1/20 remote 0/30 > 948992396.820684 starting delivery 134: msg 232591 to local [EMAIL PROTECTED] > 948992396.820697 status: local 2/20 remote 0/30 > 948992396.820704 delivery 133: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.820716 status: local 1/20 remote 0/30 > 948992396.839303 starting delivery 135: msg 232575 to local [EMAIL PROTECTED] > 948992396.839316 status: local 2/20 remote 0/30 > 948992396.839323 delivery 134: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.839335 status: local 1/20 remote 0/30 > 948992396.840144 starting delivery 136: msg 232581 to local [EMAIL PROTECTED] > 948992396.840157 status: local 2/20 remote 0/30 > 948992396.840164 delivery 135: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.840176 status: local 1/20 remote 0/30 > 948992396.859953 starting delivery 137: msg 230531 to local >[EMAIL PROTECTED] > 948992396.859967 status: local 2/20 remote 0/30 > 948992396.859974 delivery 136: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.859985 status: local 1/20 remote 0/30 > 948992396.875262 starting delivery 138: msg 232592 to local [EMAIL PROTECTED] > 948992396.875274 status: local 2/20 remote 0/30 > 948992396.875281 delivery 137: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.875293 status: local 1/20 remote 0/30 > 948992396.876087 starting delivery 139: msg 232569 to local [EMAIL PROTECTED] > 948992396.876100 status: local 2/20 remote 0/30 > 948992396.876106 delivery 138: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.876118 status: local 1/20 remote 0/30 > 948992396.890123 starting delivery 140: msg 232582 to local [EMAIL PROTECTED] > 948992396.890136 status: local 2/20 remote 0/30 > 948992396.890143 delivery 139: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.890155 status: local 1/20 remote 0/30 > 948992396.904920 starting delivery 141: msg 232570 to local [EMAIL PROTECTED] > 948992396.904933 status: local 2/20 remote 0/30 > 948992396.904939 delivery 140: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.904951 status: local 1/20 remote 0/30 > 948992396.925058 starting delivery 142: msg 232571 to local [EMAIL PROTECTED] > 948992396.925071 status: local 2/20 remote 0/30 > 948992396.925078 delivery 141: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.925090 status: local 1/20 remote 0/30 > 948992396.944740 starting delivery 143: msg 232587 to local [EMAIL PROTECTED] > 948992396.944753 status: local 2/20 remote 0/30 > 948992396.944760 delivery 142: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.944771 status: local 1/20 remote 0/30 > 948992396.960305 starting delivery 144: msg 232583 to local [EMAIL PROTECTED] > 948992396.960318 status: local 2/20 remote 0/30 > 948992396.960325 delivery 143: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.960337 status: local 1/20 remote 0/30 > 948992396.961138 starting delivery 145: msg 232593 to local [EMAIL PROTECTED] > 948992396.961151 status: local 2/20 remote 0/30 > 948992396.961158 delivery 144: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.961170 status: local 1/20 remote 0/30 > 948992396.981837 starting delivery 146: msg 232605 to local [EMAIL PROTECTED] > 948992396.981850 status: local 2/20 remote 0/30 > 948992396.981857 delivery 145: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992396.981869 status: local 1/20 remote 0/30 > 948992397.001238 starting delivery 147: msg 232579 to local [EMAIL PROTECTED] > 948992397.001251 status: local 2/20 remote 0/30 > 948992397.001258 delivery 146: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.001270 status: local 1/20 remote 0/30 > 948992397.002055 starting delivery 148: msg 232602 to local [EMAIL PROTECTED] > 948992397.002068 status: local 2/20 remote 0/30 > 948992397.002075 delivery 147: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.002087 status: local 1/20 remote 0/30 > 948992397.016799 starting delivery 149: msg 232594 to local [EMAIL PROTECTED] > 948992397.016811 status: local 2/20 remote 0/30 > 948992397.016818 delivery 148: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.016830 status: local 1/20 remote 0/30 > 948992397.030390 starting delivery 150: msg 232572 to local [EMAIL PROTECTED] > 948992397.030403 status: local 2/20 remote 0/30 > 948992397.030410 delivery 149: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.030422 status: local 1/20 remote 0/30 > 948992397.048259 starting delivery 151: msg 232584 to local [EMAIL PROTECTED] > 948992397.048271 status: local 2/20 remote 0/30 > 948992397.048278 delivery 150: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.048290 status: local 1/20 remote 0/30 > 948992397.068683 starting delivery 152: msg 232606 to local [EMAIL PROTECTED] > 948992397.068695 status: local 2/20 remote 0/30 > 948992397.068702 delivery 151: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.068714 status: local 1/20 remote 0/30 > 948992397.089426 starting delivery 153: msg 230528 to local [EMAIL PROTECTED] > 948992397.089439 status: local 2/20 remote 0/30 > 948992397.089446 delivery 152: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.089457 status: local 1/20 remote 0/30 > 948992397.105158 starting delivery 154: msg 232573 to local [EMAIL PROTECTED] > 948992397.105172 status: local 2/20 remote 0/30 > 948992397.105178 delivery 153: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.105190 status: local 1/20 remote 0/30 > 948992397.122186 starting delivery 155: msg 232595 to local [EMAIL PROTECTED] > 948992397.122200 status: local 2/20 remote 0/30 > 948992397.122207 delivery 154: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.122219 status: local 1/20 remote 0/30 > 948992397.140408 starting delivery 156: msg 232599 to local [EMAIL PROTECTED] > 948992397.140421 status: local 2/20 remote 0/30 > 948992397.140428 delivery 155: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.140439 status: local 1/20 remote 0/30 > 948992397.154104 starting delivery 157: msg 232566 to local [EMAIL PROTECTED] > 948992397.154117 status: local 2/20 remote 0/30 > 948992397.154124 delivery 156: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.154136 status: local 1/20 remote 0/30 > 948992397.168191 starting delivery 158: msg 232578 to local [EMAIL PROTECTED] > 948992397.168204 status: local 2/20 remote 0/30 > 948992397.168211 delivery 157: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.168223 status: local 1/20 remote 0/30 > 948992397.186982 starting delivery 159: msg 232585 to local [EMAIL PROTECTED] > 948992397.186994 status: local 2/20 remote 0/30 > 948992397.187001 delivery 158: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.187013 status: local 1/20 remote 0/30 > 948992397.221952 starting delivery 160: msg 232596 to local [EMAIL PROTECTED] > 948992397.221965 status: local 2/20 remote 0/30 > 948992397.221972 delivery 159: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.221983 status: local 1/20 remote 0/30 > 948992397.236801 starting delivery 161: msg 230530 to local [EMAIL PROTECTED] > 948992397.236814 status: local 2/20 remote 0/30 > 948992397.236821 delivery 160: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.236833 status: local 1/20 remote 0/30 > 948992397.237616 starting delivery 162: msg 230526 to local [EMAIL PROTECTED] > 948992397.237629 status: local 2/20 remote 0/30 > 948992397.237636 delivery 161: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.237648 status: local 1/20 remote 0/30 > 948992397.248445 starting delivery 163: msg 232607 to local [EMAIL PROTECTED] > 948992397.248458 status: local 2/20 remote 0/30 > 948992397.248465 delivery 162: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.248477 status: local 1/20 remote 0/30 > 948992397.248483 starting delivery 164: msg 230534 to local [EMAIL PROTECTED] > 948992397.248495 status: local 2/20 remote 0/30 > 948992397.248775 delivery 163: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.248788 status: local 1/20 remote 0/30 > 948992397.268167 starting delivery 165: msg 232597 to local [EMAIL PROTECTED] > 948992397.268180 status: local 2/20 remote 0/30 > 948992397.268187 delivery 164: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992397.268201 status: local 1/20 remote 0/30 > 948992397.280813 starting delivery 166: msg 232580 to local [EMAIL PROTECTED] > 948992397.280826 status: local 2/20 remote 0/30 > 948992397.280833 delivery 165: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.280844 status: local 1/20 remote 0/30 > 948992397.299656 starting delivery 167: msg 232586 to local [EMAIL PROTECTED] > 948992397.299669 status: local 2/20 remote 0/30 > 948992397.299676 delivery 166: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.299687 status: local 1/20 remote 0/30 > 948992397.300495 starting delivery 168: msg 230527 to local [EMAIL PROTECTED] > 948992397.300508 status: local 2/20 remote 0/30 > 948992397.300515 delivery 167: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.300527 status: local 1/20 remote 0/30 > 948992397.314387 starting delivery 169: msg 232598 to local [EMAIL PROTECTED] > 948992397.314400 status: local 2/20 remote 0/30 > 948992397.314407 delivery 168: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.314419 status: local 1/20 remote 0/30 > 948992397.333688 starting delivery 170: msg 232567 to local [EMAIL PROTECTED] > 948992397.333701 status: local 2/20 remote 0/30 > 948992397.333708 delivery 169: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.333720 status: local 1/20 remote 0/30 > 948992397.348671 starting delivery 171: msg 232576 to local [EMAIL PROTECTED] > 948992397.348684 status: local 2/20 remote 0/30 > 948992397.348691 delivery 170: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.348703 status: local 1/20 remote 0/30 > 948992397.349472 starting delivery 172: msg 230529 to local [EMAIL PROTECTED] > 948992397.349485 status: local 2/20 remote 0/30 > 948992397.349492 delivery 171: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.349504 status: local 1/20 remote 0/30 > 948992397.366075 starting delivery 173: msg 232588 to local [EMAIL PROTECTED] > 948992397.366088 status: local 2/20 remote 0/30 > 948992397.366095 delivery 172: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.366107 status: local 1/20 remote 0/30 > 948992397.379157 starting delivery 174: msg 232589 to local [EMAIL PROTECTED] > 948992397.379170 status: local 2/20 remote 0/30 > 948992397.379177 delivery 173: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.379189 status: local 1/20 remote 0/30 > 948992397.397490 starting delivery 175: msg 232603 to local [EMAIL PROTECTED] > 948992397.397503 status: local 2/20 remote 0/30 > 948992397.397510 delivery 174: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.397522 status: local 1/20 remote 0/30 > 948992397.403897 starting delivery 176: msg 230523 to local [EMAIL PROTECTED] > 948992397.403910 status: local 2/20 remote 0/30 > 948992397.403916 delivery 175: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ > 948992397.403928 status: local 1/20 remote 0/30 > 948992397.406512 delivery 176: deferral: >Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ > 948992397.406527 status: local 0/20 remote 0/30
Greetings! I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/<user>/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? Thanks for your help!
On Thu, Jan 27, 2000 at 09:12:44AM -0800, Scott Schappell wrote: > Greetings! > > I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or > login from a terminal, it does not tell them they have new mail, when they > do (in the case of ssh, it says "no mail" regardless). I am using > /home/<user>/Mailbox for delivery. For telnet, I'm using telnetd via inetd, > and sshd2 for ssh connections. I RTFAQ, and didn't see anything that > specifically addressed that issue. What do I need to change? This is a Unix issue more than a qmail issue. Firstly you need to work out what it is that tells you whether you have mail or not. Can I suggest you look at the characteristics of the shell you are running - especially wrt anything to do with email? Once you've done that work, you might explore whether that characteristic can be modified to look at your Mailbox. If you do that work and find out what to do, you might want to post your results here to help future people with the same question. Regards.
Scott Schappell <[EMAIL PROTECTED]> wrote: > > I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or > login from a terminal, it does not tell them they have new mail, when they > do (in the case of ssh, it says "no mail" regardless). I am using > /home/<user>/Mailbox for delivery. For telnet, I'm using telnetd via inetd, > and sshd2 for ssh connections. I RTFAQ, and didn't see anything that > specifically addressed that issue. What do I need to change? Write a script for your system-wide .bashrc which does something like "Check the contents of $HOME/Mailbox for new messages and print 'You have new mail' if there is any". If you deliver to $HOME/Maildir/, all you have to do is check whether there are any files in $HOME/Maildir/new/ . Charles -- ---------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> Any opinions expressed are just that -- my opinions. ----------------------------------------------------
On Thu, 27 Jan 2000, Scott Schappell wrote: > Greetings! > > I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or > login from a terminal, it does not tell them they have new mail, when they > do (in the case of ssh, it says "no mail" regardless). I am using > /home/<user>/Mailbox for delivery. For telnet, I'm using telnetd via inetd, > and sshd2 for ssh connections. I RTFAQ, and didn't see anything that > specifically addressed that issue. What do I need to change? It's shell specific. In tcsh I added set mail = (~$USER/Mailbox) to my .cshrc and get notifications all the time. You may need to set the MAIL env variable to ~/Mailbox in your case. It all depends on what shell you use. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net 128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
"Scott Schappell" <[EMAIL PROTECTED]> writes: I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/<user>/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? In /etc/profile, add MAIL=$HOME/Mailbox export MAIL Add something similar to /etc/csh.cshrc. (Be sure and educate the users, too!)
> From: "Mark E. Drummond" <[EMAIL PROTECTED]> > Date: Wed, 26 Jan 2000 23:16:20 -0500 > > Wrong-o! Want to send a nicely formatted proposal (with appropriate > highlights etc) to the department director so you can get funding for > that million dollar server upgrade project? Good luck doing it in plain > text. And tables? Sounds like a job for PDF. It'll even look the same everywhere. Chris -- Chris Garrigues virCIO http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com +1 512 432 4046 +1 512 374 0500 4314 Avenue C O- Austin, TX 78751-3709 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft.
PGP signature
"Chris Garrigues" <[EMAIL PROTECTED]> wrote: >Sounds like a job for PDF. It'll even look the same everywhere. Or a URL pointing to HTML on a local web server. -Dave
Mark E. Drummond wrote: > Wrong-o! Want to send a nicely formatted proposal (with appropriate > highlights etc) to the department director so you can get funding for > that million dollar server upgrade project? Good luck doing > it in plain text. And tables? Actually, I've never seen anyone do anything USEFUL like that with it. Real business stuff like that either gets sent as an attached Word or Excel doc, or a PDF. Or paper. You don't just knock up a million dollar proposal on the fly in an email editor, y'know. -Matt -- Matt Brown ---- UNIX Administrator ---- tickets.com Phone: (714) 327-5571 --- Email: [EMAIL PROTECTED]
Chris Garrigues wrote: > > Sounds like a job for PDF. It'll even look the same everywhere. PDF is very nice, I'd love to see it as a defacto standard, if not PS, but Acrobat costs $$$ and I refuse to spend $$$ on something when a perfectly good (free) alternative is available. Not only do I work at a cash strapped educational institution, it's a government cash strapped educational instituion! We have standardised (for better or worse) on Netscape Communicator so there is generally no problem with the content being rendered wrong. -- ___________________________________________________ Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED] Gang Warily|http://signals.rmc.ca/
"Jeff Russell" <[EMAIL PROTECTED]> wrote: >This account is not on the list, but if you could respond to this I'd >appreciate it. >I'm not sure if this is qmail or not, but I can't send messages outside of >our firewall, nor can I get messages in. What happens when you try? They disappear? They bounce? >However, I am able to email >interoffice. So qmail is functioning, but only partially. > >I have checked our firewall processes, and the web server and SMTP mail is >running. I then checked var/qmail/bin for any messages, and there are >sixty-two preprocessed messages. ( I am not sure if these are the messages >from outside). Look at them. >I have also gone directly to my Maildir and tried to list >messages from there, but it doesn't list anything. In fact no ones does. > >Clearly, I am able to get on the net, so I don't believe that this is a >firewall problem. If anyone has any clue, I'd appreciate it. Thanks! One obvious thing to do would be to look at your qmail-send logs. You might also run qmail-showctl and post the results. -Dave
Thomas Schachner <[EMAIL PROTECTED]> wrote: >Is it possible to set qmail to only allow authenticated smtp session to >send messages ?? > >RFC 2554 I don't know if it's RFC 2554, but there are patches on www.qmail.org that implement SMTP authentication. -Dave
On Tue, 25 Jan 2000, Andras Tudos - Computronic, C3 wrote: > At 2000.01.24 20:58, Monday, you wrote: > >On 24/01 19:28, Andras Tudos - Computronic, C3 wrote: > > > > > I have an operational theory question: when the load in a qmail setup > > > [...snip...] > > > not occur in a sendmail or other MTA based system. > > > >What operating system? Are you using Maildir or mailbox? > > Solaris 2.6 and Maildir. > > But I think the answer was given already: the problem is the flat > queue/todo folder and the solution is the big-todo patch. Of course > the most important is to have enough I/O to be able to deliver without > filling up the queue: the disk subsystem was the real bottleneck, > which is being upgraded now. If you use online disk-suite to create a logging file-system you will find the write-performance of Maildir will increase significantly as directory write operations no-longer become synchronous. This will speedup local delivery under high loads. RjL ================================================================== You know that. I know that. But when || Austin, Texas you talk to a monkey you have to || Email: [EMAIL PROTECTED] grunt and wave your arms -ck ||
Joe Millay <[EMAIL PROTECTED]> wrote: >QUESTION #1: >The [LWQ] instructions say there should be a file named INSTALL.ids in the >source directory. I couldn't find it, so per the instructions I added: > >alias:*:7790:2108::/var/qmail/alias:/bin/true > qmaild:*:7791:2108::/var/qmail:/bin/true > qmaill:*:7792:2108::/var/qmail:/bin/true > qmailp:*:7793:2108::/var/qmail:/bin/true > qmailq:*:7794:2107::/var/qmail:/bin/true > qmailr:*:7795:2107::/var/qmail:/bin/true > qmails:*:7796:2107::/var/qmail:/bin/true > >to the /etc/passwd file. > >I did the "make setup check" command and the "./config-fast >the.full.hostname" command. Both seemed to work fine. > >NOW, I have a file named INSTALL.ids in the >/usr/local/src/qmail/qmail-1.03/ directory. So, should I edit that file >now? No. It's documentation, not a config file. >QUESTION #2: >I am getting ready to install ucspi-tcp and daemontools, but I am not >sure what they do, or if I really need to do so. Can anyone help with >this? You don't need to be sure of what they do to install them. If you want to follow the LWQ directions, they're absolutely mandatory. If you want to satisfy your curiosity about what they do, it's right there in LWQ, specifically at: http://Web.InfoAve.Net/~dsill/lwq.html#daemontools http://Web.InfoAve.Net/~dsill/lwq.html#ucspi-tcp >QUESTION #3: >I've read forward in the instructions and I see that I will add users >like the following: >=address:user:uid:gid:directory:dash:extension: You *could* do that, but if you think you *must*, you're mistaken. You don't need to use qmail-users to allow normal users to receive mail. >The instructions say that the directory /var/qmail/users contains a >series of configuration files, but mine is empty (the directory contains >no files). Am I to create the config files, or will they be setup later? >I am extremely confused about this portion of the setup. qmail-users is optional. *If* you want to use it, you'll need to populate /var/qmail/users. -Dave
Scott Beck <[EMAIL PROTECTED]> wrote: >How do I set *.domain as a local delivery in >/var/qmail/control/locals or do I need to do something entirly >different? There's no wildcard mechanism for control/locals. You'll need to list all of the domains. -Dave
On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: > Scott Beck <[EMAIL PROTECTED]> wrote: > >How do I set *.domain as a local delivery in > >/var/qmail/control/locals or do I need to do something entirly > >different? > There's no wildcard mechanism for control/locals. You'll need to list > all of the domains. You could give my patch a try, which adds regular expressions to control/locals. But I have no numbers on performance issues. Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ Greetings -- Robert Sander
I sent this separately to Robert, then realized he wasn't the original questioner :). From what I noticed, in my locals file all it says is: localhost silvertree.org And any mail addressed to <user>@<sub>.silvertree.org gets delivered as a local. As an example, I have the following hosts: tintagel mordred arthur ygraine and mail sent to [EMAIL PROTECTED] still gets delivered to the qmail box, and tintagel's machine is still being built :). My understanding is that the entry "silvertree.org" equates to "*.silvertree.org", at least that's I gleaned from the brief FAQ entry. Of course, I also may not be understanding his question. That also has to assume the MX entry is correct for his domain, that all mail goes to that machine. In my example: silvertree.org IN MX 10 arthur.silvertree.org. The FAQ I am referencing is: http://cr.yp.to/qmail/faq/incominghost.html#local Hope that helps. Scott ----- Original Message ----- From: "Robert Sander" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 27, 2000 10:53 AM Subject: Re: subdomain qmail locals > On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: > > Scott Beck <[EMAIL PROTECTED]> wrote: > > >How do I set *.domain as a local delivery in > > >/var/qmail/control/locals or do I need to do something entirly > > >different? > > There's no wildcard mechanism for control/locals. You'll need to list > > all of the domains. > > You could give my patch a try, which adds regular expressions to > control/locals. But I have no numbers on performance issues. > > Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ > > Greetings > -- > Robert Sander >
On 27-Jan-00 Scott Schappell wrote: <SNIP> > That also has to assume the MX entry is correct > for his domain, that all mail goes to that machine. > In my example: silvertree.org IN MX 10 arthur.silvertree.org. > > The FAQ I am referencing is: > http://cr.yp.to/qmail/faq/incominghost.html#local > <SNIP> I have read this FAQ but failed to understand it because I did not know what they meant by DNS entry. Maybe I should explain the situation a little better. I am not the server administrator. I am just a Perl programmer trying to make things work correctly for a program I wrote. The server administrator told me the only way to get mail from <anyone>@<sub>.domain was to add an entry in /var/qmail/control/locals for each <sub>.domain. I did not believe him because the amount of entries in that file could be over 3000 (eek) so I tested it and my test email was bounced. I sent an email to [EMAIL PROTECTED] domain was entered in /var/qmail/control/locals but sub.domain was not. There was a line in /etc/aliases.cdb for [EMAIL PROTECTED] to be delivered to me@domain and the email bounced. The log said that qmail was not trying to deliver it locally. The program I am writting will just need to set up forwards for people that do not have an actual local email account just a subdomain account. I guess what my question should have been was where do I need to make entries when someone signs up for an email forward account? The forwards will be done with fastforward and I have already made the script that writes them to /etc/aliases.cdb. Sorry for the confusion Scott ----------------------------------------------------------------- E-Mail: Scott Beck <[EMAIL PROTECTED]> Address: 3542 Pine Bettle Ln. Sulphur La. 70663 Phone: (318) 527-9518 Date: 27-Jan-00 Time: 23:40:16 -----------------------------------------------------------------
On 27-Jan-00 Robert Sander wrote: > On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: >> Scott Beck <[EMAIL PROTECTED]> wrote: >> >How do I set *.domain as a local delivery in >> >/var/qmail/control/locals or do I need to do something entirly >> >different? >> There's no wildcard mechanism for control/locals. You'll need to list >> all of the domains. > > You could give my patch a try, which adds regular expressions to > control/locals. But I have no numbers on performance issues. > > Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ > > Greetings > -- > Robert Sander I just downloaded that patch. You said you do not have any benchmark results from it but do you think is will be faster to do ^([^\.]+\.)?domain$ or list 3000 sub.domain. Both at this point are an option. Thanks Scott ----------------------------------------------------------------- E-Mail: Scott Beck <[EMAIL PROTECTED]> Address: 3542 Pine Bettle Ln. Sulphur La. 70663 Phone: (318) 527-9518 Date: 28-Jan-00 Time: 00:19:34 -----------------------------------------------------------------
[EMAIL PROTECTED] wrote: >Question: How can i configure same name for two different domains. As alias >in QMAIL directory forwards the mail only through the user name and it >doesn't see the domain name. I feel the problem can be sorted out by " >Virtual Domain " concept. > > Kindly suggest is this the right solution if yes, how it can be >implemented. Yes, this is what virtual domains are used for. See: http://Web.InfoAve.Net/~dsill/lwq.html#virtual-domains -Dave
Hi Is it possible to stop qmail sending or receiving email if the from: and to: fields contain incomplete addresses i.e. username and not [EMAIL PROTECTED] Your help is really appreciated.
"Adil Tahiri" <[EMAIL PROTECTED]> wrote: >Is it possible to stop qmail sending or receiving email if the from: and to: >fields contain incomplete addresses i.e. username and not >[EMAIL PROTECTED] qmail doesn't look at the From: or To: fields. It uses the SMTP envelope addresses. There's no easy way to filter them for incomplete specifications. Perhaps the SPAMCONTROL patch posted recently does. Dr. Hoffman? -Dave
Recently saw a short thread on procmail with qmail, but I'm having another error... I used the patch on the qmail webpage to patch procmail for Maildirs. I got the qmail-procmail script from the archives to change the exit codes in procmail to something qmail can understand, and in the user directory, .qmail contains: ./Maildir/ |/usr/sbin/qmail-procmail procmail seems to be working, but it is annoying to see the following error in my /var/log/qmail/current log file: biglongnumber starting delivery 337: msg 2087 to local [EMAIL PROTECTED] biglongnumber status: local 1/10 remote 1/20 biglongnumber delivery 337: success: procmail:_Couldn't_chdir_to_""/procmail:_Skipped_"$HOME/Mail"/did_1+0+1/ biglongnumber status: local 1/10 remote 1/20 Also, relating to my logs, I sometimes see deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/ Thanks for any clues you can give me! -Jennifer
Thanks for all the suggestions and answers. In the end, though, I tried the simple fix of: # ln -s /home/<user>/Mailbox <user> # chown <user> <file> # chgrp <group> <user> # chmod 500 <user> and it worked just fine, whether connecting via telnet, ssh or a term. Only odd thing I noticed was that the owner of the symlinks was changed to root and group mail, and the permissions were changed to u=rx g=rx o=rx, however, as long as the Mailbox file in the users home directory is set properly, it still can't be viewed by others were someone to try to % cat /var/mail/archon. Sure, it's not elegant, but it worked :) Thanks again!
Using the straight script out of LWQ a: script stop will kill smtpd and pop3 supervise, but not the underlying tcpserver and then restarting doesn't work becasue the port is bound. Here's the run files: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 2000000 \ /usr/local/bin/tcpserver -v -p -x /etc/tcprules.d/qmail-smtpd.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 \ |/usr/local/bin/tai64n |/usr/local/bin/tai64nlocal and #!/bin/sh exec env PATH="/var/qmail/bin:$PATH" \ /usr/local/bin/softlimit -m 2000000 \ /usr/local/bin/tcpserver -v -R 0 pop-3 qmail-popup famvid.com \ checkpassword qmail-pop3d Maildir 2>&1 \ |/usr/local/bin/tai64n |/usr/local/bin/tai64nlocal Thanks in advance, Bill ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
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. qmail-qstat reports:- messages in queue: 36 messages in queue but not yet preprocessed: 0 qmail-qread reports:- 26 Jan 2000 21:31:44 GMT #20516 1597 <[EMAIL PROTECTED]> remote [EMAIL PROTECTED] 26 Jan 2000 21:31:44 GMT #20517 1612 <[EMAIL PROTECTED]> remote [EMAIL PROTECTED] 26 Jan 2000 21:31:45 GMT #20518 2339 <[EMAIL PROTECTED]> remote [EMAIL PROTECTED] 26 Jan 2000 21:31:45 GMT #20519 3708 <[EMAIL PROTECTED]> remote [EMAIL PROTECTED] [plus lots more similar] I have tried 'kill -ALRM <qmail-send>' but that doesn't seem to encourage anything to happen. What do I have to do to get rid of these messages? It doesn't matter too much if there lost even. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
On Thu, Jan 27, 2000 at 08:31:09PM +0000, 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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27 Jan 00, at 20:31, Chris Green wrote: > I have tried 'kill -ALRM <qmail-send>' 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]
On Thu, Jan 27, 2000 at 09:39:58PM -0000, Petr Novotny wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 27 Jan 00, at 20:31, Chris Green wrote: > > I have tried 'kill -ALRM <qmail-send>' 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/
On Thu, Jan 27, 2000 at 12:39:11PM -0800, Mark Delany wrote: > On Thu, Jan 27, 2000 at 08:31:09PM +0000, 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/
Hi All! How can I get the MX record for my domain? I don't have direct access to the DNS. Thanks JES
On Thu, Jan 27, 2000 at 06:49:49PM -0500, Juan E Suris wrote: > How can I get the MX record for my domain? I don't have direct access to the > DNS. Get or Set? Get is: nslookup -q=mx megsinet.net Which gives: megsinet.net preference = 10, mail exchanger = mail.corecomm.net megsinet.net nameserver = ns1.megsinet.net megsinet.net nameserver = ns2.megsinet.net megsinet.net nameserver = ns3.megsinet.net megsinet.net nameserver = ns4.megsinet.net mail.corecomm.net internet address = 216.214.150.16 ns1.megsinet.net internet address = 208.150.60.2 ns2.megsinet.net internet address = 208.133.80.2 ns3.megsinet.net internet address = 208.133.72.2 ns4.megsinet.net internet address = 208.133.80.8 To set a mx-pointer, you need to contact your DNS-admin. -- Ruben
* Juan E Suris ([EMAIL PROTECTED]) [27 Jan 2000 18:47]: > How can I get the MX record for my domain? I don't have direct access to the > DNS. If you mean: How do I register the MX record for my domain: When you registered the domain, there were at least two DNS entries. Get the person(s) who operate/own these machines to add a MX record for your domain that points to the _name_ of your machine. If you mean: What machine does the MX record for my domain point to: Use either of the following two commands: % host -t mx domain.name or if this fails: % host -t a domain.name -- Quist Consulting Email: [EMAIL PROTECTED] 219 Donlea Drive Voice: +1.416.696.7600 Toronto ON M4G 2N1 Fax: +1.416.978.6620 CANADA WWW: http://www.quist.on.ca
Thanks. My problems is that remote mail is not arriving. The qmail logs shows no SMTP acitivity what so ever, so this lead me to think that the MX is wrong, but to my untrained eye it seems right. [suris@domain qmail]# host -t mx domain.com domain.com.domain.com is a nickname for www.domain.com www.domain.com mail is handled (pri=10) by mail.domain.com where mail.domain.com has same IP as domain.com. All TEST.local tests passed. Any suggestions. JES >> How can I get the MX record for my domain? I don't have direct access to the >> DNS. > >If you mean: How do I register the MX record for my domain: > > When you registered the domain, there were at least two > DNS entries. Get the person(s) who operate/own these machines > to add a MX record for your domain that points to the _name_ > of your machine. > >If you mean: What machine does the MX record for my domain point to: > > Use either of the following two commands: > > % host -t mx domain.name > > or if this fails: > > % host -t a domain.name > >-- >Quist Consulting Email: [EMAIL PROTECTED] >219 Donlea Drive Voice: +1.416.696.7600 >Toronto ON M4G 2N1 Fax: +1.416.978.6620 >CANADA WWW: http://www.quist.on.ca
On Thu, Jan 27, 2000 at 07:25:09PM -0500, Juan E Suris wrote: > Thanks. > > My problems is that remote mail is not arriving. The qmail logs shows no > SMTP acitivity what so ever, so this lead me to think that the MX is wrong, > but to my untrained eye it seems right. > > [suris@domain qmail]# host -t mx domain.com > domain.com.domain.com is a nickname for www.domain.com > www.domain.com mail is handled (pri=10) by mail.domain.com > > where mail.domain.com has same IP as domain.com. It is *really* annoying when someone asks a question about suspected DNS problems, and then disguises his domain name with a phoney one. Anyway, in your case it looks like you have your MX record pointing at a CNAME. Don't do that. Chris
> Anyway, in your case it looks like you have your MX record pointing at a CNAME. > Don't do that. And, of course, fire your DNS admin. BIND will complain very clearly in the logs if you're pointing MX at a CNAME. If they haven't been watching the logs, then they are asking for very large problems. steve
I am sorry if I was annoying, but my server has not been security tested yet so I don't want to make it public until it is. When the time is right I will not be so _annoying_. CNAME? JES >On Thu, Jan 27, 2000 at 07:25:09PM -0500, Juan E Suris wrote: >> Thanks. >> >> My problems is that remote mail is not arriving. The qmail logs shows no >> SMTP acitivity what so ever, so this lead me to think that the MX is wrong, >> but to my untrained eye it seems right. >> >> [suris@domain qmail]# host -t mx domain.com >> domain.com.domain.com is a nickname for www.domain.com >> www.domain.com mail is handled (pri=10) by mail.domain.com >> >> where mail.domain.com has same IP as domain.com. > >It is *really* annoying when someone asks a question about suspected DNS >problems, and then disguises his domain name with a phoney one. > >Anyway, in your case it looks like you have your MX record pointing at a CNAME. >Don't do that. > >Chris
> so I don't want to make it public until it is. Bullshit. When you expect to get mail there through a mx record your server IS public known. Simple question: is your SMTP server running? YOu can test it by telnetting to port 25 on your machine. Does your successful test connection show up in the logs? If not, you logging is broken. You SHOULD read a DNS book (DNS and BIND by O'Reilly f.e.) or get the qmail and DNS training by Russel Nelson in Oslo :) Regards, Frank
Title: RE: FLUSH QUEUEproperly reading the documentation will reveil that if you send an ALRM to qmail-send daemon, it will then start flushing the queue, although qmail will do this automatically after a while of idling
--Stephen
-----Original Message-----
From: root [mailto:root]On Behalf Of TAG
Sent: Thursday, January 27, 2000 7:52 PM
To: [EMAIL PROTECTED]
Subject: FLUSH QUEUE
HI ALL,
IS there a way of flushing the qmail queue - PLEASE HELP!!!
Many thanks
_Tonino
On Wed, Jan 26, 2000 at 09:23:39PM -0800, Faried Nawaz wrote: > Stig Hackv�n wrote: > > qmail invokes commands with /bin/sh regardless of the user's login shell, so even >if a user has /bin/false for a shell, that user's .qmail file can be used to gain >shell access. > > And how does someone with /bin/false as their shell put commands in their > .qmail files? ftp is one way. > i consider this to be a qmail bug. > > I consider it a site-specific administrative problem. is it reasonable to use the shell field of the password database to permit or deny shell access to a username. qmail should respect this. stig -- Stig ... Friend of Hacking ... 707-987-3236 work@home Hackv�n ... http://hackvan.com ... 415-264-8754 mobile We are {b}Org ... http://brainofstig.AI ... [EMAIL PROTECTED]
It's probably not a good idea to be using an ftp config that allows users with non-real shells to log in. That's generally considered a Bad Thing (tm). If you really want something that supports virtual-style users well, look into NcFTPd. It's (mostly) commercial, and closed-soruce, but it does the job very well. At 11:07 PM 1/27/00 , you wrote: >On Wed, Jan 26, 2000 at 09:23:39PM -0800, Faried Nawaz wrote: >> Stig Hackv�n wrote: >> >> qmail invokes commands with /bin/sh regardless of the user's login >shell, so even if a user has /bin/false for a shell, that user's .qmail file >can be used to gain shell access. >> >> And how does someone with /bin/false as their shell put commands in their >> .qmail files? > >ftp is one way. > >> i consider this to be a qmail bug. >> >> I consider it a site-specific administrative problem. > >is it reasonable to use the shell field of the password database to permit >or deny >shell access to a username. qmail should respect this. > > stig > > >-- >Stig ... Friend of Hacking ... 707-987-3236 work@home >Hackv�n ... http://hackvan.com ... 415-264-8754 mobile >We are {b}Org ... http://brainofstig.AI ... [EMAIL PROTECTED] --- Phil Genera <[EMAIL PROTECTED]> Sysadmin, http://www.troop474.org/
On Thu, Jan 27, 2000 at 08:07:28PM -0800, Stig Hackv�n wrote: > > is it reasonable to use the shell field of the password database to permit or deny > shell access to a username. qmail should respect this. The problem, as I see it, is that qmail is more flexible than e.g. sendmail and not only uses the regular passwd db /etc/passwd to get the users homedir. This means that all users may not even have an regular "account" on the machine which is actually does the receiving/delivering pert of the MT process. What could be done is, however is to patch qmail-local to honour (i.e. let them override the default "/bin/sh") the shells in /etc/passwd for those users that actually _have_ regular accounts. For really paranoid implementations, this patch could be made to DENY (default to /bin/false) shell for those who lack shell in /etc/passwd. One question arise: Is there ANY security issues WHATSOEVER to use the shell defined in /etc/passwd? Only root should be able to change /etc/passwd. So if root assignes a cracked shell to a user, then this is not a problem in qmail-land? I leave the patching as an exercise to the reader. /magnus -- http://x42.com/
I recently "upgraded" to the latest versions of ucspi-tcp and daemontools on my qmail based MX. Although it seems to be operating just fine, I get the following messages on the console: supervise: fatal: unable to acquire qmail-send/supervise/lock: temporary failure supervise: fatal: unable to acquire log/supervise/lock: temporary failure supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: temporary failure supervise: fatal: unable to acquire log/supervise/lock: temporary failure Here is one of the directories in question: ls -l /var/qmail/supervise/qmail-send/supervise total 2 prw------- 1 root other 0 Jan 27 23:34 control| -rw------- 1 root other 0 Jan 27 23:30 lock prw------- 1 root other 0 Jan 27 23:30 ok| -rw-r--r-- 1 root other 18 Jan 27 23:35 status This is on Solaris 7. Compared against my Slackware Linux box, everything looks the same. The 2 are set up identically. -- ___________________________________________________ Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED] Gang Warily|http://signals.rmc.ca/
Hi, I am working on qmail-1.03 on red-hat linux 6.1. I accidently deleted files named 1, 2, 3, etc from /var/qmail/queue/local and mess. now qmail shows: Jan 28 12:09:57 alok qmail: 949041597.388541 alert: unable to opendir mess/0, sleeping... Jan 28 12:10:07 alok qmail: 949041607.398535 alert: unable to opendir mess/0, sleeping... and does not accept any messages for delivery. I re-created the files and folders in above directories, but they were of no use. Is there a way to solve this problem. thanks Alok
The DNScache package includes a dnstrace tool that's designed to debug these problems. ``dnstrace 15 briefme.com 192.5.5.241'' shows that * one of the briefme.com servers is down; * one of the servers says briefme.com MX remove-it.com; * the other three servers listed by the parent say briefme.com MX mail.remove-it.com and briefme.com MX 209.191.19.113; and * yet another server, not listed by the parent but listed by some of the children, also says briefme.com MX mail.remove-it.com and briefme.com MX 209.191.19.113. There are, by the way, many subscribers to the qmail list whose domains show similar inconsistencies between DNS servers. Mark Delany writes: > I get different results when querying that domain with dnscache and bind. Random in both cases. An initial query to an empty cache is more likely to get the mail.remove-it.com and 209.191.19.113 results, because that's available from three out of the four immediately accessible servers; but a query to an active cache is more likely to get the other result, which has a much larger TTL. ---Dan
On the qmail list [EMAIL PROTECTED] wrote: > >I am using Qmail and I want to receive mail for "mynet.com.pk" and want = >to forward it to our another mailserver=20 >"welcome.mynet.com.pk" for relaying. OK. >But I want to make the Qmail an = >open relay too. Umm, no. Trust me, you do not want to do that. What makes you think you want to do that? What agreeable things do you think will happen to your server if you run an open relay on it? I can think of several extremely *dis*agreeable things, that's not difficult. >So i deleted recpthosts to make open relay. I=20 Bad idea. >put "mynet.com.pk" in locals but not in rcpthosts. I put = You want to relay mail addressed to mynet.com.pk to welcome.mynet.com.pk, right? Then mynet.com.pk should be in rcpthosts, but not in locals. >":welcome.mynet.com.pk" in smtproutes. Now what i get problem is that,=20 You want mynet.com.pk:welcome.mynet.com.pk in smtproutes. The rest depends on whether you are using the qmail machine as an Internet gateway or not. >whenever I receive mail for "mynet.com.pk" Qmail tries to deliver it = >locally and doeasn't forward it to "welcome.mynet.com.pk". With ":welcome.mynet.com.pk" in smtproutes, *all* mail will be transmitted to welcome.mynet.com.pk. *Except* that addressed to mynet.com.pk, since you had mynet.com.pk in locals. Exactly the opposite of what you want, if I understand you correctly.
Hello, I wanted to stop sending males and I delete qmail/queue/mess and others. But I can never remove files in qmail/queue/pid. If I do, it happens Segmentetion Fault (Core dumpped.). How can I do? [EMAIL PROTECTED]
Ok, I know, this sounds quite controversial, and it's probably not even qmail's fault, but I'm curious if anyone else has had the same sort of problem. A user just sent 2 subsequent mails to a mailing list, both including quite large attachments (looking in ~user/list/archive, the files are 1,2Mb and 730kb respectively) to 21 users. This is quite heavy on a 128kbit line, esp. since concurrencyremote is 20, so I expect that each qmail-remote takes its share of the bandwidth, leaving 128/20 kbit per delivery. So, naturally, I'll get a few defferals due to dead connections, but eventually all the mail should get sent, so I don't worry about that. What I do worry about is that I can't login because bash can't fork (due to lack of memory,) that the load peaks around 2.40 and averages at 1.20 and that the TCP/IP stack is dead. (I can't get a ping reply from our local network and all connections seem dead.) What could be the cause of this? Could it be qmail or just an instable linux kernel? Thanks for any comments. System information: PPro 180MHz 64Mb RAM 100Mb Swap 3Com 3c905B (Running in 100Mbit to the router) Slackware 4.0 Linux 2.2.12 (egcs-1.1.2) Using syslogd for logging (I know, I know.. I need to change. How about syslog-ng btw?) On the same server, I also run proftpd apache bind but it's on quite a small scale, and shouldn't matter much. Thanks, Henrik.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28 Jan 00, at 11:29, Henrik Öhman wrote: > A user just sent 2 subsequent mails to a mailing list, both including quite > large attachments (looking in ~user/list/archive, the files are 1,2Mb and > 730kb respectively) to 21 users. This is quite heavy on a 128kbit line, esp. > since concurrencyremote is 20, so I expect that each qmail-remote takes its > share of the bandwidth, leaving 128/20 kbit per delivery. Well, TCP/IP doesn't work this way. Each connection is trying to steal as much as possible - only if the replies from the opposite sides have (roughly) identical delays, the bandwidth is shared evenly; otherwise, the more responsive hosts get larger share of bandwidth. But anyway... > So, naturally, I'll get a few defferals due to dead connections, but > eventually all the mail should get sent, so I don't worry about that. What I > do worry about is that I can't login because bash can't fork (due to lack of > memory,) that the load peaks around 2.40 and averages at 1.20 Which processes are running (ie. actively working)? > and that the > TCP/IP stack is dead. (I can't get a ping reply from our local network and all > connections seem dead.) > > What could be the cause of this? Could it be qmail or just an instable linux > kernel? Unstable kernel. What you describe looks like memory leak somewhere in kernel (network part probably). Simply, by calling normal functions, you CAN'T crash anything in the kernel. qmail is a userspace program, not a kernel program. End of story. > 3Com 3c905B (Running in 100Mbit to the router) Do you use Becker's driver, or 3Com's one? > Linux 2.2.12 (egcs-1.1.2) If it were 2.2.11, I'd know where the leak is... :-) -----BEGIN PGP SIGNATURE----- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOJF97lMwP8g7qbw/EQJ3+QCg41B/o5bAqxdHupOBYo+Muc5x+vwAoJnu I+X7+MDDQXvo/+PK8xxWUtuD =yh56 -----END PGP SIGNATURE-----
Petr Novotny wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 28 Jan 00, at 11:29, Henrik �hman wrote: > > A user just sent 2 subsequent mails to a mailing list, both including quite > > large attachments (looking in ~user/list/archive, the files are 1,2Mb and > > 730kb respectively) to 21 users. This is quite heavy on a 128kbit line, esp. > > since concurrencyremote is 20, so I expect that each qmail-remote takes its > > share of the bandwidth, leaving 128/20 kbit per delivery. > > Well, TCP/IP doesn't work this way. Each connection is trying to > steal as much as possible - only if the replies from the opposite > sides have (roughly) identical delays, the bandwidth is shared > evenly; otherwise, the more responsive hosts get larger share of > bandwidth. But anyway... > Ok, yeah, I was being a little brief there, but anyway. ;) > > So, naturally, I'll get a few defferals due to dead connections, but > > eventually all the mail should get sent, so I don't worry about that. What I > > do worry about is that I can't login because bash can't fork (due to lack of > > memory,) that the load peaks around 2.40 and averages at 1.20 > > Which processes are running (ie. actively working)? > The curious thing is, when I started top, the CPU was 98% idle, so the heavy load must have come during a very short peak. Also, memory usage had sunk to more normal levels after just a few seconds (next time I tried to log into a virtual console, I did not recieve an error message about memory shortage.) As I ran top, all the 20 qmail-remotes were S, as were all other processes (except for top.) The only difference from normal behaviour was that I could not establish any TCP/IP-connection whatsoever. > Unstable kernel. What you describe looks like memory leak > somewhere in kernel (network part probably). Ok, an upgrade is due anyway. Too bad the kernel didn't say anything about it. > Simply, by calling normal functions, you CAN'T crash anything in > the kernel. qmail is a userspace program, not a kernel program. > End of story. Okay, then it should definitely be a kernel level error. > > 3Com 3c905B (Running in 100Mbit to the router) > > Do you use Becker's driver, or 3Com's one? > Becker's. Any differences? Is 3Com's better? Oh, and sorry if I seemed to unrighteously accuse qmail of something. ;) Thanks, Henrik.
