RE: tcpserver problems? or is it qmail? or BOTH! Help? (fwd)
How do you get tcpserver to run the qmail-smtpd daemon? When I run it as in the faq, it runs and I see the process running, but it doesn't accept connections. I then changed it to use inetd using tcp-env and qmail-smtpd accepts connections. Could someone get me starting in the right direction? Charlie Chrisman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 04, 2001 6:04 AM To: [EMAIL PROTECTED] Subject: Re: tcpserver problems? or is it qmail? or BOTH! Help? (fwd) Possibly the reason you were blasted is that this is incorrect. You _cannot_ make inetd or xinetd use tcpserver. Your xinetd script doesn't use tcpserver; it uses tcp-env. tcp-env was originally designed to allow you to do tcpserver-like operations from inetd, but is now deprecated. There are precisely zero advantages to using inetd/xinetd in this manner, and several disadvantages (when compared to a simple tcpserver installation). Charles -- What are the disadvantages of using xinetd? Rob...
Re: tcpserver problems? or is it qmail? or BOTH! Help?
Scott Zielsdorf [EMAIL PROTECTED] wrote: My thanks to Lukas Beeler who asked me to run 'ps auxf' and behold! I found errors coming from readproctile telling me it couldn't find /usr/local/bin/setguidid. [...] So did I 'fat finger' setguidid somewhere in a script or did my daemontools install fail and I just didn't realize it? Or is there another problem? It's setuidgid, not setguidgid. So aside from me telling the Canadian guy how to use xinetd to *maybe* get around his problem (I hadn't considered a fire wall issue)instead of tcpserver, can you give me some guidance into where to look to solve this? Sorry; I delete inetd/xinetd from all the boxes I administer and can offer you no advice other than use tcpserver instead. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: tcpserver problems? or is it qmail? or BOTH! Help? (fwd)
Please quote properly; your original text was after a sig delimiter, and you had no attribution for my text. I wrote: There are precisely zero advantages to using inetd/xinetd in this manner, and several disadvantages (when compared to a simple tcpserver installation). [EMAIL PROTECTED] wrote: What are the disadvantages of using xinetd? Security and concurrency limits, mostly. But it's not qmail, and doesn't belong on this list. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: tcpserver problems? or is it qmail? or BOTH! Help? (fwd)
Charlie Chrisman [EMAIL PROTECTED] wrote: How do you get tcpserver to run the qmail-smtpd daemon? When I run it as in the faq, it runs and I see the process running, but it doesn't accept connections. I then changed it to use inetd using tcp-env and qmail-smtpd accepts connections. Could someone get me starting in the right direction? Not without some real information. Post the script you use to start tcpserver/qmail-smtpd, along with copies of any tcprules files. The output of qmail-showctl is always good too. Chances are this is FAQ #1. But you didn't even clarify the problem; doesn't accept connections? Describe exactly what you did, what you expected to happen, and what did happen. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: tcpserver problems? or is it qmail? or BOTH! Help?
-Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] So did I 'fat finger' setguidid somewhere in a script or did my daemontools install fail and I just didn't realize it? Or is there another problem? It's setuidgid, not setguidgid. Yeah, people keep telling me that *I* spelled it wrong but after an hour and a half of looking at EVERY script I had edited, setuidgid or setguidgid was no where to be found in any text file. Turns out I didn't fat finger anywhere. I tracked the problem to the /service/qmail-smtp/run script. I haven't isolated the problem in the script yet but I must have mis-set a flag, misplaced a line break or something. I gave up after a couple of hours on trying to diagnose my faux paux. Here's what I did to get tcpserver to run: 1. I removed the smtp file from the xinetd.d directory which was invoking tcpwrappers through xinetd and HUP'd xinetd. (BTW, simply removing the smtp file and rebooting...and yeah...I know, didn't have to reboot, could have HUP'd, etc did NOT allow tcpserver to run free. I was still getting the errors about setguidgid not being found in the readproctitle log. It was only after replacing the run file with the one from the LWQ install docs that I was able to eliminate the the readproctitle errors.) 2. I stopped qmail. 3. I went back to the LWQ /service/qmail-smtpd/run script and put it into play. (I was using a script sent to me by Robin but I had modified it - hence, my fault not his) 4. I started qmail. 5. I ran `ps auxwf | grep readp` and saw there were no readproctitle errors. 6. I ran `netstat -lp | grep smtp` and saw that tcpserver was the daemon. (Previous invocations of the command either showed that xinetd was running smtp or that NO smtp was running. 7. I put a blank rcpthosts file in the /var/qmail/control directory. 8. I checked the /etc/tcp.smtp file and made sure I had my IP addresses set in the rules the way I wanted them. 9. Restarted qmail. 10. Tested by sending a message from the allowable IP range - success. Tested by sending a message from an outside IP range - failure. 11. Happiness Again, my thanks to you and Lukas for pointing me in the right direction. I'm not enough of a linux wizard yet (going on 5 days now, woohoo!) to know how to delete xinetd. Hell, I didn't even know what xinetd was. Scott Zielsdorf Senior Technical Support Consultant Computer Instruments IVR Solutions Support Group Voice: 913.492.1888 x8862 Fax: 913.492.1483
Re: tcpserver problems? or is it qmail? or BOTH! Help?
First of all, I'm on the list, and I set Mail-Followup-To: appropriately. Please don't cc: me on your list messages; I hate duplicates and get 500-1000 messages a day already. Scott Zielsdorf [EMAIL PROTECTED] wrote: It's setuidgid, not setguidgid. Yeah, people keep telling me that *I* spelled it wrong but after an hour and a half of looking at EVERY script I had edited, setuidgid or setguidgid was no where to be found in any text file. Hmmm. 7. I put a blank rcpthosts file in the /var/qmail/control directory. Bad. Bad. Bad. Go directly to jail, do not pass Go, do not collect $200. 8. I checked the /etc/tcp.smtp file and made sure I had my IP addresses set in the rules the way I wanted them. [...] 10. Tested by sending a message from the allowable IP range - success. Tested by sending a message from an outside IP range - failure. Define failure -- no connection, or no relay? 11. Happiness Except that you're either: 1) An open relay, or 2) Not accepting any mail from outside your local network Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: tcpserver problems? or is it qmail? or BOTH! Help?
-Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 04, 2001 1:52 PM First of all, I'm on the list, and I set Mail-Followup-To: appropriately. Please don't cc: me on your list messages; I hate duplicates and get 500-1000 messages a day already. While learning anything necessarily about linux or qmail from you may be dubious, I will definitely learn perfection :) My humblest apologies that I failed to remove your personal address. But only a 1000 a day? Really? Damn. Can I swap email accounts with you? I've got you beat by at least 600. Automated reports from a half dozen RS6000's plus the 14 UNIXWARE boxes sucking data from the RS6000's plus email from their associated staffs plus all the 25 or 30 messages I get from this list plus... well, like you, I am extremely put upon. How do gods like us do it? 7. I put a blank rcpthosts file in the /var/qmail/control directory. Bad. Bad. Bad. Go directly to jail, do not pass Go, do not collect $200. And this is bad, bad, bad because why? I don't want any traffic coming back to the box. It does not have an MX record for the domain and I don't want it to. 8. I checked the /etc/tcp.smtp file and made sure I had my IP addresses set in the rules the way I wanted them. [...] 10. Tested by sending a message from the allowable IP range - success. Tested by sending a message from an outside IP range - failure. Define failure -- no connection, or no relay? Failure from an outside domain/IP address to relay. 11. Happiness Except that you're either: 1) An open relay, or 2) Not accepting any mail from outside your local network You got it big guy. I have closed the open relay state - which is the only state I could run qmail in and get it to relay when I started posting to this group seeking the accumulated wisdom of the 'umma'. Now, I have accepted the orthodoxy of the priests of tcpserver, vanquished the satanic xinetd, and can selective relay! Hallelujah I only want this box to accept internal traffic and relay internal traffic outbound. After 4 or 5 days of vexing frustration, I have accomplished what someone else set out to do and I had to take over, learned Linux by crash course and, quite spectacularly, proved myself a fool. All in all, a good week. I think the problem with the run script may be that I was subbing zero for oh or vice versa in the command line. My telnet client and my eyes don't work so well differentiating between the two. Thanks, Scott
RE: tcpserver problems? or is it qmail? or BOTH! Help?
Gadzooks In my previous reply to Charles Cazabon I was IMPRECISE. My rcpthosts file is NOT blank, it has localhost in it. Just wanted to clear that up before Charles could retort :) Scott Zielsdorf Senior Technical Support Consultant Computer Instruments 9901 W. 87th St. Overland Park, KS 66212 (913) 492-1888 ext. 402 [EMAIL PROTECTED]
Re: tcpserver problems? or is it qmail? or BOTH! Help?
Scott Zielsdorf [EMAIL PROTECTED] wrote: Please don't cc: me on your list messages [...] While learning anything necessarily about linux or qmail from you may be dubious, I will definitely learn perfection :) My humblest apologies that I failed to remove your personal address. But only a 1000 a day? Really? Despite the smiley, that first paragraph sounds supiciously insulting. And why are you trying to turn this into a dicksize war? 7. I put a blank rcpthosts file in the /var/qmail/control directory. Bad. Bad. Bad. Go directly to jail, do not pass Go, do not collect $200. And this is bad, bad, bad because why? I don't want any traffic coming back to the box. It does not have an MX record for the domain and I don't want it to. Big question: if you don't want the box to receive mail over the network, why run an SMTP daemon in the first place? Oh, I see -- later on, you state you _do_ want it to receive mail over the network. [...] I have closed the open relay state - which is the only state I could run qmail in and get it to relay when I started posting to this group seeking the accumulated wisdom of the 'umma'. Now, I have accepted the orthodoxy of the priests of tcpserver, vanquished the satanic xinetd, and can selective relay! Hallelujah I think you've made things much more complex than necessary. There is lots of documentation on selective relaying with qmail and tcpserver. I think the problem with the run script may be that I was subbing zero for oh or vice versa in the command line. My telnet client and my eyes don't work so well differentiating between the two. Yes, this will bite you. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: tcpserver problems? or is it qmail? or BOTH! Help?
-Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 04, 2001 6:26 PM Despite the smiley, that first paragraph sounds supiciously insulting. And why are you trying to turn this into a dicksize war? Oh, Charles...I'm feeling impetuous. Please believe me, it wasn't an insult and I'm not into dicksize wars...Just got carried away. Sorry. I just took slight offense with you stating your email stats. We're all busy, eh? Big question: if you don't want the box to receive mail over the network, why run an SMTP daemon in the first place? Oh, I see -- later on, you state you _do_ want it to receive mail over the network. U, not precisely. I don't want outside world mail coming in. I simply want to relay internal traffic out. With the exception of me and the guy who is *supposed* to be sysadmin'ing this box, no one inside on the LAN has an account on the box. I think you've made things much more complex than necessary. There is lots of documentation on selective relaying with qmail and tcpserver. Charles, in all seriousness, no BS'ing, no being snide, anything, I am a newbie. A very new newbie to qmail and linux. When the consultant hired to do all this work bailed, I got tagged for the job. I read a ton of stuff on the web. I joined this list. I couldn't get selective relaying to work. Period. So the advice, I think from Robin, was to reinstall and follow the LWQ directions to a T - which I did with the exceptions of installing daemontools. The daemontools that I installed are 0.76 and not 0.70 as in the LWQ doc. Still could not get selective relaying to go. I was frantic and guessing. Thought maybe it was a DNS problem but when I brought that to the list and DNS got ruled out. Long story short: If Lukas Beeler hadn't told me to do a command I have NEVER in 6 years of working with SCO UNIX used or even knew existed and you hadn't explained to me about xinetd and wrappers I would still be begging for assistance. So yes, there are good docs on the web. But none that I was able to find addressed the possibility that if you screwed up your run file either a) xinetd might take over (because someone before you had tinkered with it) and make qmail mail an open relay or b) smtp would not run as a daemon at all. And not knowing sh*t about what I was really doing on a new OS with a new product I really think that maybe there is a bit of a gap in documentation - unless I really balled up and missed it somewhere. I was doing everything the docs and faqs had told me to do but selective relaying didn't work. Maybe I missed it when I didn't read the testing docs?? That's my two cents worth. I think maybe I should stop wasting everyone's time and bandwidth and call this closed unless someone wants to do rebuttal. Thanks, Scott
Re: tcpserver problems? or is it qmail? or BOTH! Help?
Scott Zielsdorf [EMAIL PROTECTED] wrote: By searching on the keywords xinetd and qmail on the web I was able to find a script that allowed xinetd to use tcpserver as its daemon and then the relaying rules in /etc/tcp.smtp.cdb worked. [...] Possibly the reason you were blasted is that this is incorrect. You _cannot_ make inetd or xinetd use tcpserver. Your xinetd script doesn't use tcpserver; it uses tcp-env. tcp-env was originally designed to allow you to do tcpserver-like operations from inetd, but is now deprecated. There are precisely zero advantages to using inetd/xinetd in this manner, and several disadvantages (when compared to a simple tcpserver installation). Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: tcpserver problems? or is it qmail? or BOTH! Help?
-Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Subject: Re: tcpserver problems? or is it qmail? or BOTH! Help? Possibly the reason you were blasted is that this is incorrect. LOL...You think? You_cannot_ make inetd or xinetd use tcpserver. Your xinetd script doesn't use tcpserver; it uses tcp-env. tcp-env was originally designed to allow you to do tcpserver-like operations from inetd, but is now deprecated. There are precisely zero advantages to using inetd/xinetd in this manner, and several disadvantages (when compared to a simple tcpserver installation). My thanks to Lukas Beeler who asked me to run 'ps auxf' and behold! I found errors coming from readproctile telling me it couldn't find /usr/local/bin/setguidid. Here's the specific error message: root 686 0.8 0.0 1252 16 ?SAug02 14:19 \_ readproctitle service errors: ...xec: /usr/local/bin/setguidgid: cannot execute: No such file or directory?tcpserver: usage: tcpserver [ -1UXpPhHrRoOdDqQv ] [ -c limit ] [ - x rules.cdb ] [ -B banner ] [ -g gid ] [ -u uid ] [ -b backlog ] [ -l localname ] [ -t timeout ] host port program?./run: /usr/local/bin/setguidgid: No such fil e or directory?./run: exec: /usr/local/bin/setguidgid: cannot execute: No such f ile or directory? And, sure 'nuf, their ain't a setguidgid anywhere on the box. So did I 'fat finger' setguidid somewhere in a script or did my daemontools install fail and I just didn't realize it? Or is there another problem? Lukas also had me run 'netstat -lp | grep smtp' and, like there was a doubt smile, the owner came back as xinetd. So aside from me telling the Canadian guy how to use xinetd to *maybe* get around his problem (I hadn't considered a fire wall issue)instead of tcpserver, can you give me some guidance into where to look to solve this? Thanks Scott
Re: tcpserver: end xxxx status 256
On Fri, Jul 06, 2001 at 10:07:11PM -0700, Lists Servers Email wrote: Does any know what causes this error: Server: tcpserver: end status 256 A program that was called by tcpserver exited non-zero. What you obscured is a pid. Client: user xxx +OK pass xx -ERR unable to write pipe Connection to host lost. I'm guessing (since you haven't shown us your tcpserver command-line) that qmail-popup has a problem with whatever problem it's trying to call. Vince.
Re: tcpserver: end xxxx status 256
I found the problem, tcpserver for pop3 was not running as root. But I have another problem!!! there is mail in the queue but it's not get deliver local. Thanks Kevin. - Original Message - From: Vincent Schonau [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, July 07, 2001 12:43 AM Subject: Re: tcpserver: end status 256 On Fri, Jul 06, 2001 at 10:07:11PM -0700, Lists Servers Email wrote: Does any know what causes this error: Server: tcpserver: end status 256 A program that was called by tcpserver exited non-zero. What you obscured is a pid. Client: user xxx +OK pass xx -ERR unable to write pipe Connection to host lost. I'm guessing (since you haven't shown us your tcpserver command-line) that qmail-popup has a problem with whatever problem it's trying to call. Vince.
Re: tcpserver: end xxxx status 256
Please don't Cc: me, I'm on the list. On Sat, Jul 07, 2001 at 01:16:31AM -0700, Lists Servers Email wrote: [...] But I have another problem!!! there is mail in the queue but it's not get deliver local. That sucks. What do the logs say[tm]? Vince.
Re: tcpserver / queue cleaning
On Wed, Jul 04, 2001 at 08:26:45PM +0200, Moritz Schmitt wrote: 2. I'm using tcpserver to start qmail and it seems to work. But there is a little thing I don't understand. On my FreeBSD 4.2 RELEASE machine I added the follwing configuration file into /etc/rc: That's not the right place to start services, but that's beyond the scope of this list. /usr/local/bin/tcpserver -p -x /etc/tcp.smtp.cdb -u 82 -g 81 0 smtp \ /var/qmail/bin/smtpd After I added this line I rebooted the machine and it stopped right at the point where it was supposed to excute the line above. It didn't crash and I was able to talk to my server on port 25 it just didn't proccess the rest of the startup scripts. Because it looked the way that /var/qmail/bin/qmail-smtpd was waiting on stdin I added an ampersand at the and of the line so /bin/sh would start it as a background process. It seems to work that way but I'm confused because I read twice in two different docs that no ampersand is needed. At least it wasn't printed there. Can anyone enlighten me? In this case you do need the ampersand, but again this is not a qmail question, but a general Unix question. I'd suggest you read http://www.lifewithqmail.org. Set things up as outlined there, and start svscan from a script in /usr/local/etc/rc.d Chris PGP signature
Re: tcpserver / queue cleaning
On Wed, Jul 04, 2001 at 08:26:45PM +0200, Moritz Schmitt wrote: Hello, I got too questions about qmail and tcpserver. If the tcpserver program is off topic here, please advise me to the right list. 1. How can I delete every message existing in the queue? If this isn't a FAQ, it should be. Stop all qmail processes. Have the compile qmail source handy. 'rm -rf /var/qmail/queue', and 'make setup check' in the qmail source directory. (There are other ways, but this way is, IMHO, the simplest for someone who doesn't understand the architecture of qmail.) 2. I'm using tcpserver to start qmail and it seems to work. But there is a little thing I don't understand. On my FreeBSD 4.2 RELEASE machine I added the follwing configuration file into /etc/rc: /usr/local/bin/tcpserver -p -x /etc/tcp.smtp.cdb -u 82 -g 81 0 smtp \ /var/qmail/bin/smtpd Wow. It's strongly recommended, even in the file itself, not to play with /etc/rc. If you want to stick with files in /etc, use rc.local. I personally am now a big fan of /usr/local/etc/rc.d/*.sh -- FreeBSD now runs any files matching that specification at boot time. I use this method to start svscan, which then starts all the tcpserver processes (qmail-smtpd, qmail-pop3d, et al) for me* -- see Life With qmail: http://www.lifewithqmail.org/ and modify the 'run' scripts to taste. * Of course, it also starts dnscache, tinydns, axfrdns, and publicfile. I love DJBware. ;) After I added this line I rebooted the machine and it stopped right at the point where it was supposed to excute the line above. It didn't crash and I was able to talk to my server on port 25 it just didn't proccess the rest of the startup scripts. Because it looked the way that /var/qmail/bin/qmail-smtpd was waiting on stdin I added an ampersand at the and of the line so /bin/sh would start it as a background process. It seems to work that way but I'm confused because I read twice in two different docs that no ampersand is needed. At least it wasn't printed there. Can anyone enlighten me? -Moritz See above -- if you're going to run tcpserver, I highly recommend that you go whole hog and use daemontools to bring stuff up as well. Can't wait until openssh has an option that runs under daemontools without too much extra overhead! -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy
[OT] RE: tcpserver / queue cleaning
I'm using /etc/rc to start the tcpserver process because I read it in Running qmail; Richard Blum. To quote him on that: Once the qmail-smtpd boot script is created, it must be run from a system boot script. On a FreeBSD system this can be the /etc/rc script. Because the qmail-smtpd script just contained the tcpserver line I thought it's no big deal to write it directly into /etc/rc. Anyways, I or the book, one of us sucks. Maybe both. But thanks for the hint I'm going to read Life with qmail and I'm removing my entries from /etc/rc. -Moritz -Original Message- From: Greg White [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 04, 2001 8:47 PM To: qmail Subject: Re: tcpserver / queue cleaning On Wed, Jul 04, 2001 at 08:26:45PM +0200, Moritz Schmitt wrote: Hello, I got too questions about qmail and tcpserver. If the tcpserver program is off topic here, please advise me to the right list. 1. How can I delete every message existing in the queue? If this isn't a FAQ, it should be. Stop all qmail processes. Have the compile qmail source handy. 'rm -rf /var/qmail/queue', and 'make setup check' in the qmail source directory. (There are other ways, but this way is, IMHO, the simplest for someone who doesn't understand the architecture of qmail.) 2. I'm using tcpserver to start qmail and it seems to work. But there is a little thing I don't understand. On my FreeBSD 4.2 RELEASE machine I added the follwing configuration file into /etc/rc: /usr/local/bin/tcpserver -p -x /etc/tcp.smtp.cdb -u 82 -g 81 0 smtp \ /var/qmail/bin/smtpd Wow. It's strongly recommended, even in the file itself, not to play with /etc/rc. If you want to stick with files in /etc, use rc.local. I personally am now a big fan of /usr/local/etc/rc.d/*.sh -- FreeBSD now runs any files matching that specification at boot time. I use this method to start svscan, which then starts all the tcpserver processes (qmail-smtpd, qmail-pop3d, et al) for me* -- see Life With qmail: http://www.lifewithqmail.org/ and modify the 'run' scripts to taste. * Of course, it also starts dnscache, tinydns, axfrdns, and publicfile. I love DJBware. ;) After I added this line I rebooted the machine and it stopped right at the point where it was supposed to excute the line above. It didn't crash and I was able to talk to my server on port 25 it just didn't proccess the rest of the startup scripts. Because it looked the way that /var/qmail/bin/qmail-smtpd was waiting on stdin I added an ampersand at the and of the line so /bin/sh would start it as a background process. It seems to work that way but I'm confused because I read twice in two different docs that no ampersand is needed. At least it wasn't printed there. Can anyone enlighten me? -Moritz See above -- if you're going to run tcpserver, I highly recommend that you go whole hog and use daemontools to bring stuff up as well. Can't wait until openssh has an option that runs under daemontools without too much extra overhead! -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy
Re: [OT] RE: tcpserver / queue cleaning
Moritz Schmitt [EMAIL PROTECTED] wrote: I'm using /etc/rc to start the tcpserver process because I read it in Running qmail; Richard Blum. To quote him on that: Once the qmail-smtpd boot script is created, it must be run from a system boot script. On a FreeBSD system this can be the /etc/rc script. Because the qmail-smtpd script just contained the tcpserver line I thought it's no big deal to write it directly into /etc/rc. It is a big deal, if you don't understand what you're putting in there. Anyways, I or the book, one of us sucks. Maybe both. No. You're a newbie. You don't suck. The book, from the opinions of knowledgable qmail experts on this list, appears to suck quite badly. The advice you quote above is further evidence of this. But thanks for the hint I'm going to read Life with qmail and I'm removing my entries from /etc/rc. Yes, Life with qmail is definitely the way to go for most novices. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: tcpserver: relay iface question
GARGIULO Eduardo INGDESI [EMAIL PROTECTED] wrote: How can I tell tcpserver to relay clients connected from an interface instead of ip addresses? You can wildcard IP addresses on byte boundaries -- i.e., the following entry: 10.10.:allow,RELAYCLIENT= would allow the 16-bit subnet 10.10.x.x to relay. This should probably be good enough. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: tcpserver: relay iface question
Thus spake GARGIULO Eduardo INGDESI ([EMAIL PROTECTED]): How can I tell tcpserver to relay clients connected from an interface instead of ip addresses? You bind one tcpserver on each interface and give the one on the relay-enabled interface a rule set that always matches. It's that easy.
Re: tcpserver: relay iface question
On Mon, Jun 25, 2001 at 09:50:07PM +0200, Felix von Leitner wrote: Thus spake GARGIULO Eduardo INGDESI ([EMAIL PROTECTED]): How can I tell tcpserver to relay clients connected from an interface instead of ip addresses? You bind one tcpserver on each interface and give the one on the relay-enabled interface a rule set that always matches. If, and only if, you make sure no traffic for this interface can come in through the other interface. I think charles suggestion is easier. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: tcpserver: fatal: unable to bind: address already used ???
Hello, Thanks for the great help! I really really apreciate this! I found the following line in my /etc/inetd.conf file in the section Pop and imap mail services et al pop-3 stream tcp nowait root/usr/sbin/tcpd ipop3d The advice seems to suggest that I should comment out this line. I am currently running qmail-pop3d. Is commenting out this line the correct way to go? I am quite a newbie and don't want to do something stupid or comment out something I shouldn't be. Best. --- Frank Tegtmeyer [EMAIL PROTECTED] wrote: A A [EMAIL PROTECTED] writes: I think this is probably the cause for the high cpu load from qmail. Can anyone give me a pointer on how I can fix this? I'll admit that I am a complete newbie to linux and qmail, so any help and/or detailed instructions is greatly appreciated. Did you remove the line beginning with pop3 from the /etc/inetd.conf file? If not, that's the reason. In that case comment this line out (a # sign at the begin of the line) and restart inetd. To do this look at the process id of inetd: ps ax | grep inetd | grep -v grep The number at the front is the process id. Then do a kill -HUP 1234 (replace 1234 with the found process id of inetd). Regards, Frank __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: tcpserver: fatal: unable to bind: address already used ???
On Thu, Jun 21, 2001 at 09:44:02PM -0700, A A wrote: I found the following line in my /etc/inetd.conf file in the section Pop and imap mail services et al pop-3 stream tcp nowait root/usr/sbin/tcpd ipop3d The advice seems to suggest that I should comment out this line. I am currently running qmail-pop3d. Is commenting out this line the correct way to go? I am quite a newbie and don't want to do something stupid or comment out something I shouldn't be. Yes comment out that line, i.e. put a ''#'' in the beginning of the line and reload inetd. How to reload inetd depends on it's installation but try ''/etc/init.d/inetd reload''. Jörgen
Re: tcpserver: fatal: unable to bind: address already used ???
A A [EMAIL PROTECTED] writes: pop-3 stream tcp nowait root/usr/sbin/tcpd ipop3d The advice seems to suggest that I should comment out this line. I am currently running qmail-pop3d. Is commenting out this line the correct way to go? Yes, that's all to do. Don't forget to send the inetd process the HUP signal. The safest way for you may be to shutdown your system after commenting out the line. When it is turned on again all should be fine. Regards, Frank
Re: tcpserver: fatal: unable to bind: address already used ???
On Tue, Jun 19, 2001 at 09:15:50PM -0700, A A wrote: [snip] The line 23359 root 20 0 324 324 264 R 0 5.1 0.0 65:51 supervise seems to suggest something called supervise is taking up most of the cpu (5.1%)? There's most probably two (or more) processes of the same supervise. You can verify this with ''ps axw | grep supervise''. Jörgen
Re: tcpserver: fatal: unable to bind: address already used ???
A A [EMAIL PROTECTED] writes: I think this is probably the cause for the high cpu load from qmail. Can anyone give me a pointer on how I can fix this? I'll admit that I am a complete newbie to linux and qmail, so any help and/or detailed instructions is greatly appreciated. Did you remove the line beginning with pop3 from the /etc/inetd.conf file? If not, that's the reason. In that case comment this line out (a # sign at the begin of the line) and restart inetd. To do this look at the process id of inetd: ps ax | grep inetd | grep -v grep The number at the front is the process id. Then do a kill -HUP 1234 (replace 1234 with the found process id of inetd). Regards, Frank
Re: tcpserver: fatal: unable to bind: address already used
On Mon, Jun 18, 2001 at 12:32:51AM +0800, Alex Tsang wrote: When I start the qmail-pop3d service, the log files log ¡¥tcpserver: fatal: unable to bind: address already used¡¦ errors but I can still use the pop3 server. So what¡¦s this error mean? It means that something is already bound to your POP3 port. Since your POP service works, it's likely that you already started your POP3 service once and now you're trying to start it again. Chris PGP signature
Re: tcpserver: Return 553 instead of 451?
On Wed, May 30, 2001 at 10:34:29PM -0700, Bruce Lane wrote: 63.102.43.25:allow,RBLSMTPD=Access denied due to spamming. 63.102.43.25:allow,RBLSMTPD=-Access denied due to spamming. should do the trick. From http://cr.yp.to/ucspi-tcp/rblsmtpd.html: However, if $RBLSMTPD begins with a hyphen, rblsmtpd removes the hyphen and uses a 553 error code. This tells legitimate clients to bounce the message immediately. -- Jos Backus _/ _/_/_/Modularity is not a hack. _/ _/ _/-- D. J. Bernstein _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer;
Re: tcpserver: Return 553 instead of 451?
Bruce Lane writes: I'm using tcpserver with qmail and a local blacklist in the form of tcp.smtp and tcp.smtp.cdb. In order to provide local logging, and a brief description to a rejected source of why their connection attempt was rejected, a typical line from my tcp.smtp file may look something like this: 63.102.43.25:allow,RBLSMTPD=Access denied due to spamming. My question: Is there any way to make tcpserver return a 553 error instead of a 451? I've dug around in the source code files, but I don't speak enough C to be able to find and change what I want. In http://cr.yp.to/ucspi-tcp/rblsmtpd.html, look for Temporary errors. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Microsoft rivets everything. 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Linux has some loose screws. Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | You own a screwdriver.
Re: TCPSERVER status 256
Nathaniel L. Keeling III [EMAIL PROTECTED] wrote: How can I verify if this is a bare line problem or not? Use recordio to record the complete SMTP dialogue. See the faq. My rc file contains 'qmail-start '|dot-forward .forward ./Maildir/' and nothing is showing up in the qmail-send log file. That's not nothing to do with your SMTP problems. If you're not running qmail using svscan, a la Life with qmail, you probably should splogger qmail to the end of your qmail-start command. -Dave
Re: TCPSERVER status 256
On Tue, May 29, 2001 at 08:44:20AM -0400, Dave Sill wrote: Nathaniel L. Keeling III [EMAIL PROTECTED] wrote: How can I verify if this is a bare line problem or not? Use recordio to record the complete SMTP dialogue. See the faq. A nice trick: - create /service/qmail-smtpd as you would normally - create /service/qmail-smtpd-recordio as a copy with recordio inserted, and logging to a separate space (be sure to chmod this logdir tight because recordio records complete emails). The switchover is then simply: # svc -u /service/qmail-smtpd-recordio ; svc -d /var/service/qmail-smtpd and viceversa. We have this on all our mailservers now, and for pop3 too. It's a great diagnostic tool. Greetz, Peter.
RE: TCPSERVER status 256
Search the archive for 256 or the like. I posted details about the same question last year sometime. Dave NetCarrier, Software Engineering -Original Message-From: Nathaniel L. Keeling III [mailto:[EMAIL PROTECTED]]Sent: Saturday, May 26, 2001 2:12 PMTo: [EMAIL PROTECTED]Subject: TCPSERVER status 256I am getting a status 256 in the qmail-smtpd log files when one of our other servers try to connect to the mail server to send mail. The log files from the other server is getting good response, the helo and response, and sends the data but the messages are not getting to the users and there are no entries in the qmail-send log file. Can anybody help? Here are the entries from qmail-smtpd log file. @40003b0fba66381db324 tcpserver: status: 1/40 @40003b0fba6638bd8d04 tcpserver: pid 8871 from 207.227.131.194 @40003b0fba663ac86894 tcpserver: ok 8871 kweku.akan.net:207.227.131.131:25 akim.akan.net:207.227.131.194::3191 @40003b0fba671a5dfe0c tcpserver: end 8871 status 256 @40003b0fba671a6725cc tcpserver: status: 0/40 thanks
Re: TCPSERVER status 256
How can I verify if this is a bare line problem or not? My rc file contains 'qmail-start '|dot-forward .forward ./Maildir/' and nothing is showing up in the qmail-send log file. Chris Johnson wrote: On Sat, May 26, 2001 at 01:12:09PM -0500, Nathaniel L. Keeling III wrote: I am getting a status 256 in the qmail-smtpd log files when one of our other servers try to connect to the mail server to send mail. The log files from the other server is getting good response, the helo and response, and sends the data but the messages are not getting to the users and there are no entries in the qmail-send log file. Can anybody help? Here are the entries from qmail-smtpd log file. @40003b0fba66381db324 tcpserver: status: 1/40 @40003b0fba6638bd8d04 tcpserver: pid 8871 from 207.227.131.194 @40003b0fba663ac86894 tcpserver: ok 8871 kweku.akan.net:207.227.131.131:25 akim.akan.net:207.227.131.194::3191 @40003b0fba671a5dfe0c tcpserver: end 8871 status 256 @40003b0fba671a6725cc tcpserver: status: 0/40 Though it doesn't necessarily mean this, every time I've seen the above it was because the other end was sending me a message with a bare linefeed in it. See http://cr.yp.to/docs/smtplf.html Chris Part 1.2Type: application/pgp-signature
Re: TCPSERVER status 256
On Sat, May 26, 2001 at 01:12:09PM -0500, Nathaniel L. Keeling III wrote: I am getting a status 256 in the qmail-smtpd log files when one of our other servers try to connect to the mail server to send mail. The log files from the other server is getting good response, the helo and response, and sends the data but the messages are not getting to the users and there are no entries in the qmail-send log file. Can anybody help? Here are the entries from qmail-smtpd log file. @40003b0fba66381db324 tcpserver: status: 1/40 @40003b0fba6638bd8d04 tcpserver: pid 8871 from 207.227.131.194 @40003b0fba663ac86894 tcpserver: ok 8871 kweku.akan.net:207.227.131.131:25 akim.akan.net:207.227.131.194::3191 @40003b0fba671a5dfe0c tcpserver: end 8871 status 256 @40003b0fba671a6725cc tcpserver: status: 0/40 Though it doesn't necessarily mean this, every time I've seen the above it was because the other end was sending me a message with a bare linefeed in it. See http://cr.yp.to/docs/smtplf.html Chris PGP signature
RE: TCPSERVER status 256
I am getting a status 256 in the qmail-smtpd log files when one of our other servers try to connect to the mail server to send mail. The log files from the other server is getting good response, the helo and response, and sends the data but the messages are not getting to the users and there are no entries in the qmail-send log file. Can anybody help? Here are the entries from qmail-smtpd log file. If /var/qmail/rc has splogger qmail at the end, remove it and restart qmail-send and it will start logging correctly.
RE: tcpserver blues
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Joerg Lenneis
Sent: Friday, May 11, 2001 4:31 AM
To: Nick (Keith) Fish
Cc: Chris Ochap; Qmail Mailing List
Subject: Re: tcpserver blues
Nick (Keith) Fish:
Chris Ochap wrote:
start() {
# Start daemons.
echo -n $Starting $prog:
daemon /var/qmail/rc
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd
RETVAL=$?
[ $RETVAL -eq 0 ] touch /var/lock/subsys/qmail
echo
return $RETVAL
}
Try adding 21 to the end of the tcpserver line, so:
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u 51 -g 50 0
smtp
/var/qmail/bin/qmail-smtpd 21
[...]
That is not correct, that will just redirect stderr to stdout.
You need to put a single at the end of the line that starts up
tcpserver to put the process into the background.
regards,
--
Joerg Lenneis
email: [EMAIL PROTECTED]
RE: tcpserver blues
Hi Chris
You put this query up on the 10th. and tc lewis replied? I would endorse his
answer to you, look into supervise from the daemontools toolkit.
If you are starting off with qmail and want to get it up and going then go
with one of the established methods of setting it up - Life with qmail
and/or Tetsu Ushijima's excellent qmail-conf which has complete
configuration scripts for setting up qmail.
http://www.din.or.jp/~ushijima/qmail-conf.html
I believe that it is not recommended to run qmail in the background, and
with tcpserver it is not necessary. The DJB suite has a special way of
working together with tcpserver, the relevant executable (qmail, smtpd,
pop3d) and multilog. tcpserver listens for connections to a port (e.g. 25)
and kicks off the relevant program (smtpd) as required. It is correct that
21 redirects stderr to stdout but this is actually used (I believe, one
of the regular guys can confirm this) as a special pipe for multilog to pipe
the output to the multilog log for the service.
This is my machines run script for smptd generated by Ushijima's qmail-conf.
You'll see that smtpd is called without the background option. It works
:-)
Cheers
Patrick
#!/bin/sh
exec 21 \
envdir ./env \
sh -c '
case $REMOTENAME in h) H=;; p) H=p;; *) H=H;; esac
case $REMOTEINFO in r) R=;; [0-9]*) R=t$REMOTEINFO;; *) R=R;; esac
exec \
envuidgid qmaild \
softlimit ${DATALIMIT+-d$DATALIMIT} \
/usr/local/bin/tcpserver \
-vDU$H$R \
${LOCALNAME+-l$LOCALNAME} \
${BACKLOG+-b$BACKLOG} \
${CONCURRENCY+-c$CONCURRENCY} \
-xtcp.cdb \
-- ${IP-0} ${PORT-25} \
/var/qmail/bin/qmail-smtpd
'
From: Chris Ochap [EMAIL PROTECTED]
=
That is not correct, that will just redirect stderr to stdout.
You need to put a single at the end of the line that starts up
tcpserver to put the process into the background.
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: tcpserver -p and smtpd and DNS
On Mon, May 14, 2001 at 06:30:44AM -, David Killingsworth wrote: I have been running qmail for about 8 months, It works great. So far I have not been able to resolve on problem. When an smtp connection comes in we only want to connect with servers who have forward and reverse DNS that match. I allready anwered your question in alt.comp.mail.qmail some days ago. What is wrong with my answer? Gerrit. -- [EMAIL PROTECTED] innominate AG the linux architects tel: +49.30.308806-0 fax: -77 http://www.innominate.com
Re: tcpserver -p and smtpd and DNS
I have narrowed this to one simple item. Could someone, possibly you Gerrit I know you have answered one way to get around this I just wanna understand why I have to get around it, explain to me why qmail has delivered an email to me that contains the following header: Received: from unknown (HELO dali.onevision.de) (@212.77.172.50) by mail.myweb.net with SMTP; 14 May 2001 08:59:56 - I have tcpserver -DUvp wrapping smtpd for qmail. Shouldn't tcpserver drop the connection when $TCPREMOTEIP is DNS'd to a hostname and $TCPREMOTEHOST is DNS'd to an IP. if $TCPREMOTEIP can't be resolved or if $TCPREMOTEHOST can't be resolved, shouldn't this cause a FATAL in tcpserver? and it will drop the incoming connection? David. On Mon, 14 May 2001 10:51:33 +0200, Gerrit Pape [EMAIL PROTECTED] wrote : On Mon, May 14, 2001 at 06:30:44AM -, David Killingsworth wrote: I have been running qmail for about 8 months, It works great. So far I have not been able to resolve on problem. When an smtp connection comes in we only want to connect with servers who have forward and reverse DNS that match. I allready anwered your question in alt.comp.mail.qmail some days ago. What is wrong with my answer? Gerrit. -- [EMAIL PROTECTED] innominate AG the linux architects tel: +49.30.308806-0 fax: -77 http://www.innominate.com
Re: tcpserver -p and smtpd and DNS
On Mon, May 14, 2001 at 10:10:21AM -, David Killingsworth wrote: I have narrowed this to one simple item. Could someone, possibly you Gerrit I know you have answered one way to get around this I just wanna understand why I have to get around it, explain to me why qmail has delivered an email to me that contains the following header: Received: from unknown (HELO dali.onevision.de) (@212.77.172.50) by mail.myweb.net with SMTP; 14 May 2001 08:59:56 - I have tcpserver -DUvp wrapping smtpd for qmail. Shouldn't tcpserver drop the connection when $TCPREMOTEIP is DNS'd to a hostname and $TCPREMOTEHOST is DNS'd to an IP. if $TCPREMOTEIP can't be resolved or if $TCPREMOTEHOST can't be resolved, shouldn't this cause a FATAL in tcpserver? and it will drop the incoming connection? tcpserver *only* rejects connections if told to do so by the rules supplied with -x or -X. What rules have you tried? You should be able to get tcpserver to drop connections that do not have TCPREMOTEHOST set by putting these entries in your rules: =.:allow :deny Regards. David. On Mon, 14 May 2001 10:51:33 +0200, Gerrit Pape [EMAIL PROTECTED] wrote : On Mon, May 14, 2001 at 06:30:44AM -, David Killingsworth wrote: I have been running qmail for about 8 months, It works great. So far I have not been able to resolve on problem. When an smtp connection comes in we only want to connect with servers who have forward and reverse DNS that match. I allready anwered your question in alt.comp.mail.qmail some days ago. What is wrong with my answer? Gerrit. -- [EMAIL PROTECTED] innominate AG the linux architects tel: +49.30.308806-0 fax: -77 http://www.innominate.com
Re: tcpserver -p and smtpd and DNS
On Mon, May 14, 2001 at 10:10:21AM -, David Killingsworth wrote: Shouldn't tcpserver drop the connection when $TCPREMOTEIP is DNS'd to a hostname and $TCPREMOTEHOST is DNS'd to an IP. if $TCPREMOTEIP can't be resolved or if $TCPREMOTEHOST can't be resolved, shouldn't this cause a FATAL in tcpserver? and it will drop the incoming connection? No. The docs say, tcpserver will remove $TCPREMOTEHOST in that case. it is on You (your proc tcpserver is running) to decide to drop the connection. Gerrit. -- [EMAIL PROTECTED] innominate AG the linux architects tel: +49.30.308806-0 fax: -77 http://www.innominate.com
Re: tcpserver -p and smtpd and DNS
On Mon, May 14, 2001 at 12:35:32PM +, Mark Delany wrote: =.:allow :deny Close. To achieve this, the tcp.smtp file should actually contain: =:allow :deny I just experimented with both forms. With the dot, nothing matched, including hosts with good forward/reverse resolvability. Without it, only sites for which tcpserver didn't unset TCPREMOTEHOST matched. This, of course, is exactly the desired behavior. As already mentioned in this thread, tcpserver -p unsets TCPREMOTEHOST when the name obtained by reverse lookup can't be resolved to the original IP. Consequently, for such an (arguably) undesirable client IP, no match occurs at the =:allow line in the above tcp.smtp settings, since the = token only matches when TCPREMOTEHOST is defined. The :deny line then rejects those undesirable clients as they fall through. Just to be thorough, even if obvious, I'll also mention that these two lines must appear LAST in your tcp.smtp file.
Re: tcpserver blues
Nick (Keith) Fish:
Chris Ochap wrote:
start() {
# Start daemons.
echo -n $Starting $prog:
daemon /var/qmail/rc
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd
RETVAL=$?
[ $RETVAL -eq 0 ] touch /var/lock/subsys/qmail
echo
return $RETVAL
}
Try adding 21 to the end of the tcpserver line, so:
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u 51 -g 50 0 smtp
/var/qmail/bin/qmail-smtpd 21
[...]
That is not correct, that will just redirect stderr to stdout.
You need to put a single at the end of the line that starts up
tcpserver to put the process into the background.
regards,
--
Joerg Lenneis
email: [EMAIL PROTECTED]
Re: tcpserver blues
tcpserver runs in the foreground. that line:
tcpserver: status: 0/40
is its [logging] output. when it accepts a new connection, it will output
more.
just run it in the background.
maybe pipe stdout and stderr to a file for logging.
or be elegant and use supervise and svscan (see daemontools
documentation on cr.yp.to).
-tcl.
On Thu, 10 May 2001, Chris Ochap wrote:
can anyone help me figure out why qmail-smtpd will not start. i have been
following multiple peices of literature to complete the install...although
they all differ slightly...i have had no trouble with any stage of the
install except getting qmail to start listening for remote deliveries.
whenever i enter the tcpserver command to start qmail-smtpd whether it be in
a startup script or command line...i get
tcpserver: status: 0/40
and the prompt just sits there like it is waiting for me to enter another
parameter. i am fairly confident that the command line options are all
correct:
tcpserver executable and switches -v = verbose -p = accept comm w/o remote
host dns lookup -x = use rules database
location of rules database with a very simple set of rules
user and group ids for qmail users...define whether tcpserver is on
localhost...use smtp...ok sorry im going over what most of you probably know
already. does anyone have any suggestions or need more info? here is a
copy of my little script...i am running rh 7.1. thanx all.
---
# Source function library.
. /etc/rc.d/init.d/functions
# Source networking configuration.
. /etc/sysconfig/network
# Check that qmail is loaded
[ -f /var/qmail/bin/qmail-start ] || exit 0
RETVAL=0
prog=qmail
start() {
# Start daemons.
echo -n $Starting $prog:
daemon /var/qmail/rc
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd
RETVAL=$?
[ $RETVAL -eq 0 ] touch /var/lock/subsys/qmail
echo
return $RETVAL
}
stop() {
# Stop daemons.
echo -n $Stopping $prog:
killproc qmail-send
RETVAL=$?
[ $RETVAL -eq 0 ] rm -f /var/lock/subsys/qmail
echo
return $RETVAL
}
restart() {
stop
start
}
# See how we were called.
case $1 in
start)
start
;;
stop)
stop
;;
restart)
restart
;;
*)
echo $Usage: $0 {start|stop|restart}
exit 1
esac
exit $?
Re: tcpserver blues
Chris Ochap wrote:
start() {
# Start daemons.
echo -n $Starting $prog:
daemon /var/qmail/rc
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd
RETVAL=$?
[ $RETVAL -eq 0 ] touch /var/lock/subsys/qmail
echo
return $RETVAL
}
Try adding 21 to the end of the tcpserver line, so:
/usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u 51 -g 50 0 smtp
/var/qmail/bin/qmail-smtpd 21
This should cause qmail-smtpd to run in the background instead of directly on
whatever tty you are attached to. To test rather it is running or not, tail it
the log file it outputs while telnetting into port 25 of your machine.
--
Keith
Network Engineer
Triton Technologies, Inc.
RE: TCPserver; ucspi-tcp; inetd
Joe,
I had the same problem.
I was (and still am) totally confused with daemontools, inetd, ucspi,
xinitd, blah, blah, blah:)! I was reading a bunch of FAQ and install notes
and added an SMTP to my /etc/xinetd.d directory. Here is what I added:
{
flags = REUSE NAMEINARGS
socket_type = stream
protocol= tcp
wait= no
user= qmaild
server = /usr/sbin/tcpd
server_args = /var/qmail/bin/tcp-env -R
/var/qmail/bin/qmail-smtpd
disable =no
}
I did this because one of the FAQs said that I needed to use this with
xinetd. Of course, you don't need this if you are under control (in terms
of managing services) of ucspi. I changed disable =no to disable =yes
and it took care of this error messages. This caused the conflict with the
address in use.
I still don't have everything working yet, but I am still trying!
Thanks,
Ted
-Original Message-
From: jx001 [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 9:21 PM
To: [EMAIL PROTECTED]
Subject: TCPserver; ucspi-tcp; inetd
When I did install the ucspi-tcp package I receive the following
error-message (var/log/qmail/qmail-smtpd):
tcpserver: fatal: unable to bind: adress already use
I did install ucspi-tcp as described (http://cr.yp.to/ucspi-tcp.html)
There must be some problems with inetd...
How can I solve this problem?
THX
Joe
Re: TCPserver; ucspi-tcp; inetd
you already have a service listening on port 25. a likely culprit is sendmail. make sure that it's shut off, and make sure that you check /etc/inetd.conf. if there's something in there listening on the smtp port, comment it out, and kill -HUP inetd's pid. dan On Fri, 27 Apr 2001, jx001 wrote: When I did install the ucspi-tcp package I receive the following error-message (var/log/qmail/qmail-smtpd): tcpserver: fatal: unable to bind: adress already use I did install ucspi-tcp as described (http://cr.yp.to/ucspi-tcp.html) There must be some problems with inetd... How can I solve this problem? THX Joe
Re: TCPserver; ucspi-tcp; inetd
At 27.04.2001 02:20, you wrote: When I did install the ucspi-tcp package I receive the following error-message (var/log/qmail/qmail-smtpd): tcpserver: fatal: unable to bind: adress already use I did install ucspi-tcp as described (http://cr.yp.to/ucspi-tcp.html) There must be some problems with inetd... How can I solve this problem? remove/comment out the line in /etc/inetd.conf that starts a smtpserver. The line should resemble something like this: smtp stream tcp nowait root/usr/sbin/tcpd sendmail -bs place a # (hash) infront of that line and give inetd a HUP and then try to restart your qmail-smtpd... -- andreas landmark / noXtension [EMAIL PROTECTED] #distributed : 20001003 [23:27:04] froggie_ I like the feeling of a TCP socket you get in a DCC chat..
VIRUS TROUVE : Re: tcpserver help
Panda Antivirus a trouvé les virus suivants dans le message : Envoyé par :Forrest Sutton Adresse : [EMAIL PROTECTED] Pour : [EMAIL PROTECTED] Sujet : Re: tcpserver help Date : 24/04/2001 04:57:09 THIS MESSAGE CONTENT VIRUS !!! Fichier : Emanuel.exe Virus : W32/Navidad.B Renommé http://www.pandasoftware.com winmail.dat
Re: tcpserver help
On Fri, Apr 06, 2001 at 03:34:18PM -0400, Todd Kennedy wrote: I'm trying to run qmail with tcpserver, and running this command: 17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp /var/qmail/bin/qmail-smtpd gives the following error messsage: tcpserver: fatal: unable to bind: address already used Something is already listening to your SMTP port. Find out what it is and kill it. Chris Emanuel.exe
RE: tcpserver help
Take me off list please. no longer work at x-tant. Viruses attatched to mails. Thank you. -Original Message- From: jessica [mailto:[EMAIL PROTECTED]] Sent: 23 April 2001 15:07 To: Todd Kennedy Cc: [EMAIL PROTECTED] Subject: Re: tcpserver help On Fri, Apr 06, 2001 at 03:34:18PM -0400, Todd Kennedy wrote: I'm trying to run qmail with tcpserver, and running this command: 17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp /var/qmail/bin/qmail-smtpd gives the following error messsage: tcpserver: fatal: unable to bind: address already used Something is already listening to your SMTP port. Find out what it is and kill it. Chris
VIRUS TROUVE : Re: tcpserver help
Panda Antivirus a trouvé les virus suivants dans le message : Envoyé par :jessica Adresse : [EMAIL PROTECTED] Pour : [EMAIL PROTECTED] Sujet : Re: tcpserver help Date : 23/04/2001 16:49:41 THIS MESSAGE CONTENT VIRUS !!! Fichier : Emanuel.exe Virus : W32/Navidad.B Renommé http://www.pandasoftware.com winmail.dat
Re: tcpserver help
On Tue, Apr 24, 2001 at 05:01:57PM +0200, NDSoftware wrote: PLEASE USE A ANTIVIRUS !!! stop doubling this !@%%# The blabla found Virus blbla Messages are more annoying... -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: tcpserver help
On Tue, 24 Apr 2001 17:01:57 +0200, NDSoftware wrote: PLEASE USE A ANTIVIRUS !!! Please don't send lame messages like this to the list. If you have already blocked the virus with your software then what are you worried about?
Re: tcpserver help
On Tue, Apr 24, 2001 at 05:01:35PM +0200, NDSoftware wrote: PLEASE USE A ANTIVIRUS !!! [snip virus] It's bad enough that a dozen other mail hosts (including yours) are spamming the list with their thoughts on the matter for each of jessica's messages. Please stop adding to the noise.
Re: tcpserver help
On Fri, Apr 06, 2001 at 03:34:18PM -0400, Todd Kennedy wrote: I'm trying to run qmail with tcpserver, and running this command: 17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp /var/qmail/bin/qmail-smtpd gives the following error messsage: tcpserver: fatal: unable to bind: address already used Something is already listening to your SMTP port. Find out what it is and kill it. Chris Emanuel.exe
Re: TCPServer Error
On Tue, Apr 17, 2001 at 03:43:48AM -0300, Martin Marconcini wrote: Hello: I have followed www.lifewithqmail.org instructions. The server is OpenBSD 2.8. This was my first qmail installation. At the office I installed OpenBSD and Qmail and followed instructions and have had no problem. I installed pop/smtp stuff. At home I have another obsd box w/qmail. But I can't make tcpserver work. /var/log/qmail/smtpd/current shows the following error everytime I telnet localhost 25. @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error The error message seems pretty obvious to me. There is some problem with the qmail-smtpd executable. Perhaps it was compiled on a different system, perhaps it was compiled on a later version of the same system. Whatever the problem, your OS doesn't like that executable file for some reason. To confirm this, I'd run qmail-smtpd from a command line prompt thusly: $ /var/qmail/bin/qmail-smtpd Please do this and show us the output. To fix it you probably need to rebuild and reinstall the program. I don't really know whether LWQ does this in the standard way. I have no inetd running. tcpserver is working fine. The problem is that the program it wants to run (qmail-smtpd) is not running for some reason. Regards.
Re: TCPServer Error
From: Martin Marconcini [EMAIL PROTECTED] warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error That would imply to me that the syntax of the "exec" command in your run script is wrong. If I run /var/qmail/supervise/run manually it seems to start w/no error. Do you mean /var/qmail/supervise/qmail-smtpd/run? Can you show us that file?
Re: TCPServer Error
The error message seems pretty obvious to me. There is some problem with the qmail-smtpd executable. Perhaps it was compiled on a different system, perhaps it was compiled on a later version of the same system. Whatever the problem, your OS doesn't like that executable file for some reason. To confirm this, I'd run qmail-smtpd from a command line prompt thusly: $ /var/qmail/bin/qmail-smtpd Please do this and show us the output. Here it goes... bash-2.04# cd /var/qmail/bin/ bash-2.04# ls bouncesaying maildirwatch qmail-getpw qmail-pw2uqmail-rspawn qsmhook condredirect mailsubj qmail-inject qmail-qmqpc qmail-sendsendmail datemail pinq qmail-local qmail-qmqpd qmail-showctl splogger elq predate qmail-lspawn qmail-qmtpd qmail-smtpd tcp-env exceptpreline qmail-newmrh qmail-qread qmail-start forward qail qmail-newuqmail-qstat qmail-tcpok maildir2mbox qbiff qmail-pop3d qmail-queue qmail-tcpto maildirmake qmail-clean qmail-popup qmail-remote qreceipt bash-2.04# ./qmail-smtpd bash-2.04# NOthing happened... whether the entire qmail is stopped or started... no process nothing. What should It print? To fix it you probably need to rebuild and reinstall the program. I don't really know whether LWQ does this in the standard way. I have no inetd running. tcpserver is working fine. The problem is that the program it wants to run (qmail-smtpd) is not running for some reason. Okey... Thanks!! Martin
Re: TCPServer Error
On Tuesday 17 April 2001 07:45, David Young wrote: From: Martin Marconcini [EMAIL PROTECTED] warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error That would imply to me that the syntax of the "exec" command in your run script is wrong. If I run /var/qmail/supervise/run manually it seems to start w/no error. Do you mean /var/qmail/supervise/qmail-smtpd/run? Can you show us that file? Mkey! Here it goes.. bash-2.04# cat /var/qmail/supervise/qmail-smtpd/run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd 2 bash-2.04# Just in case here goes the rest of the four... bash-2.04# cat /var/qmail/supervise/qmail-smtpd/log/run #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/smtpd bash-2.04# bash-2.04# cat /var/qmail/supervise/qmail-send/run #!/bin/sh exec /var/qmail/rc bash-2.04# bash-2.04# cat /var/qmail/supervise/qmail-send/log/run #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail bash-2.04# Any ideas? Thanks! Martin.
Re: TCPServer Error
it would be interesting if you could provide the output of the following commands: uname -a file /bin/ls file /var/qmail/bin/qmail-smtpd file /var/qmail/bin/qmail-start and the contents of your "run" file you start tcpserver and smtpd with /k Martin Marconcini([EMAIL PROTECTED])@2001.04.17 03:43:48 +: Hello: I have followed www.lifewithqmail.org instructions. The server is OpenBSD 2.8. This was my first qmail installation. At the office I installed OpenBSD and Qmail and followed instructions and have had no problem. I installed pop/smtp stuff. At home I have another obsd box w/qmail. But I can't make tcpserver work. /var/log/qmail/smtpd/current shows the following error everytime I telnet localhost 25. @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error @40003ada6c2f392520a4 tcpserver: end 22092 status 28416 @40003ada6c2f394a6f6c tcpserver: status: 0/20 And that everytime i try a telnet. I have no inetd running. If I run /var/qmail/supervise/run manually it seems to start w/no error. I have make the lifewqmail steps again.. but can't find the error. And the works is I did it a few hours ago at the office!!! :( I use Maildir and have /var/qmail/rc properly configured. Everything worked pretty well until i decided to switch from inetd to tcpserver. I installed tcpserver from ports/packages. Also daemontools. Any ideas??? I run Bash2.04... Thanks in advance. -- Martin Marconcini | Unix, MS-DOS, Windows. | Also known as The Good, The Bad | And the Ugly... -- -- Hackers do it with bugs. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
RE: TCPServer Error
Hi Here goes the info. bash-2.04# uname -a OpenBSD jupiter 2.8 GENERIC#399 i386 bash-2.04# file /bin/ls /bin/ls: OpenBSD/i386 demand paged executable bash-2.04# file /var/qmail/bin/qmail-smtpd /var/qmail/bin/qmail-smtpd: empty WHAT'S THIS? bash-2.04# file /var/qmail/bin/qmail-start /var/qmail/bin/qmail-start: OpenBSD/i386 demand paged dynamically linked executable bash-2.04# cat /var/qmail/supervise/qmail-smtpd/run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd 21 Thanks!! Martin -Original Message- From: Karsten W. Rohrbach [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 17, 2001 9:54 AM To: Martin Marconcini Cc: [EMAIL PROTECTED] Subject: Re: TCPServer Error it would be interesting if you could provide the output of the following commands: uname -a file /bin/ls file /var/qmail/bin/qmail-smtpd file /var/qmail/bin/qmail-start and the contents of your "run" file you start tcpserver and smtpd with /k Martin Marconcini([EMAIL PROTECTED])@2001.04.17 03:43:48 +: Hello: I have followed www.lifewithqmail.org instructions. The server is OpenBSD 2.8. This was my first qmail installation. At the office I installed OpenBSD and Qmail and followed instructions and have had no problem. I installed pop/smtp stuff. At home I have another obsd box w/qmail. But I can't make tcpserver work. /var/log/qmail/smtpd/current shows the following error everytime I telnet localhost 25. @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error @40003ada6c2f392520a4 tcpserver: end 22092 status 28416 @40003ada6c2f394a6f6c tcpserver: status: 0/20 And that everytime i try a telnet. I have no inetd running. If I run /var/qmail/supervise/run manually it seems to start w/no error. I have make the lifewqmail steps again.. but can't find the error. And the works is I did it a few hours ago at the office!!! I use Maildir and have /var/qmail/rc properly configured. Everything worked pretty well until i decided to switch from inetd to tcpserver. I installed tcpserver from ports/packages. Also daemontools. Any ideas??? I run Bash2.04... Thanks in advance. -- Martin Marconcini | Unix, MS-DOS, Windows. | Also known as The Good, The Bad | And the Ugly... -- -- Hackers do it with bugs. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
RE: TCPServer Error (SOLVED)
Well.. thanks to Karsten and everybody. I managed to discover that qmail-smtpd was toasted! (By using file /var/qmail/bin/qmail-smtpd) I copied the bin from another similar openbsd box and it works now. Thanks!!! Martin. -Original Message- From: Karsten W. Rohrbach [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 17, 2001 9:54 AM To: Martin Marconcini Cc: [EMAIL PROTECTED] Subject: Re: TCPServer Error it would be interesting if you could provide the output of the following commands: uname -a file /bin/ls file /var/qmail/bin/qmail-smtpd file /var/qmail/bin/qmail-start and the contents of your "run" file you start tcpserver and smtpd with /k Martin Marconcini([EMAIL PROTECTED])@2001.04.17 03:43:48 +: Hello: I have followed www.lifewithqmail.org instructions. The server is OpenBSD 2.8. This was my first qmail installation. At the office I installed OpenBSD and Qmail and followed instructions and have had no problem. I installed pop/smtp stuff. At home I have another obsd box w/qmail. But I can't make tcpserver work. /var/log/qmail/smtpd/current shows the following error everytime I telnet localhost 25. @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error @40003ada6c2f392520a4 tcpserver: end 22092 status 28416 @40003ada6c2f394a6f6c tcpserver: status: 0/20 And that everytime i try a telnet. I have no inetd running. If I run /var/qmail/supervise/run manually it seems to start w/no error. I have make the lifewqmail steps again.. but can't find the error. And the works is I did it a few hours ago at the office!!! I use Maildir and have /var/qmail/rc properly configured. Everything worked pretty well until i decided to switch from inetd to tcpserver. I installed tcpserver from ports/packages. Also daemontools. Any ideas??? I run Bash2.04... Thanks in advance. -- Martin Marconcini | Unix, MS-DOS, Windows. | Also known as The Good, The Bad | And the Ugly... -- -- Hackers do it with bugs. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
Re: TCPServer Error
Martin Marconcini([EMAIL PROTECTED])@2001.04.17 10:54:27 +: Hi Here goes the info. bash-2.04# uname -a OpenBSD jupiter 2.8 GENERIC#399 i386 bash-2.04# file /bin/ls /bin/ls: OpenBSD/i386 demand paged executable bash-2.04# file /var/qmail/bin/qmail-smtpd /var/qmail/bin/qmail-smtpd: empty WHAT'S THIS? here we go, your binary is not correctly installed. unpack the qmail source somewhere, cd into the dir and "make qmail-smtpd". check for any error messages from the compiler during building. check the qmail-smtpd binary in the build directory. it should not be empty. bash-2.04# file /var/qmail/bin/qmail-start /var/qmail/bin/qmail-start: OpenBSD/i386 demand paged dynamically linked executable bash-2.04# cat /var/qmail/supervise/qmail-smtpd/run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd 21 Thanks!! Martin -Original Message- From: Karsten W. Rohrbach [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 17, 2001 9:54 AM To: Martin Marconcini Cc: [EMAIL PROTECTED] Subject: Re: TCPServer Error it would be interesting if you could provide the output of the following commands: uname -a file /bin/ls file /var/qmail/bin/qmail-smtpd file /var/qmail/bin/qmail-start and the contents of your "run" file you start tcpserver and smtpd with /k Martin Marconcini([EMAIL PROTECTED])@2001.04.17 03:43:48 +: Hello: I have followed www.lifewithqmail.org instructions. The server is OpenBSD 2.8. This was my first qmail installation. At the office I installed OpenBSD and Qmail and followed instructions and have had no problem. I installed pop/smtp stuff. At home I have another obsd box w/qmail. But I can't make tcpserver work. /var/log/qmail/smtpd/current shows the following error everytime I telnet localhost 25. @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error @40003ada6c2f392520a4 tcpserver: end 22092 status 28416 @40003ada6c2f394a6f6c tcpserver: status: 0/20 And that everytime i try a telnet. I have no inetd running. If I run /var/qmail/supervise/run manually it seems to start w/no error. I have make the lifewqmail steps again.. but can't find the error. And the works is I did it a few hours ago at the office!!! I use Maildir and have /var/qmail/rc properly configured. Everything worked pretty well until i decided to switch from inetd to tcpserver. I installed tcpserver from ports/packages. Also daemontools. Any ideas??? I run Bash2.04... Thanks in advance. -- Martin Marconcini | Unix, MS-DOS, Windows. | Also known as The Good, The Bad | And the Ugly... -- -- Hackers do it with bugs. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46 -- Motto of the Electrical Engineer: Working computer hardware is a lot like an erect penis: it stays up as long as you don't fuck with it. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
Re: TCPServer Error
On Tue, Apr 17, 2001 at 03:43:48AM -0300, Martin Marconcini wrote: @40003ada6c2f381c5b64 tcpserver: status: 1/20 @40003ada6c2f384a0ab4 tcpserver: pid 22092 from 127.0.0.1 @40003ada6c2f38fae424 tcpserver: ok 22092 localhost.marconcini.com.ar:127.0.0.1:25 :127.0.0.1::17948 @40003ada6c2f39080b54 tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: exec format error @40003ada6c2f392520a4 tcpserver: end 22092 status 28416 @40003ada6c2f394a6f6c tcpserver: status: 0/20 A week ago I told you, on this list, that "your qmail-smtpd executable is hosed". It still is. Tim
RE: tcpserver - pop3d logging
kurth, I wrote a logging patch to do just that. see http://www.quint.be/projects/ -Willy On Thursday, April 12, 2001 02:20, Kurth Bemis [SMTP:[EMAIL PROTECTED]] wrote: i know that its been asked on the list before.but i can't remember when or the answer for that matter. i'd like to log the usernames from my pop users...to see who is getting their mail and whose not :-) i thought that there was a tcpserver or multilog switch for it...but i can't remember...can someone help me out :-) ~kurth
Re: tcpserver help
well duh..
either you running another tcpserver already
or your sendmail still running
kill sendmail or tcpserver and try again
- Original Message -
From: "Todd Kennedy" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 06, 2001 3:34 PM
Subject: tcpserver help
I'm trying to run qmail with tcpserver, and running this command:
17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp
/var/qmail/bin/qmail-smtpd
gives the following error messsage:
tcpserver: fatal: unable to bind: address already used
i'm not sure what do here. any help would be appreciated.
thanks
todd
--
#!/bin/sh
for DVDs in Linux screw the MPAA and ; do dig $DVDs.z.zoy.org ; done
| perl -ne 's/\.//g; print pack("H224",$1) if(/^x([^z]*)/)' | gunzip.
Re: tcpserver help
Todd Kennedy [EMAIL PROTECTED] writes: gives the following error messsage: tcpserver: fatal: unable to bind: address already used Comment out the line beginning with "smtp" in your /etc/inetd.conf file and send the inetd process a HUP signal (kill -HUP pid of inetd). Inetd is still waiting for connections to this port. Regards, Frank
Re: tcpserver help
On Fri, Apr 06, 2001 at 03:34:18PM -0400, Todd Kennedy wrote: I'm trying to run qmail with tcpserver, and running this command: 17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp /var/qmail/bin/qmail-smtpd gives the following error messsage: tcpserver: fatal: unable to bind: address already used Something is already listening to your SMTP port. Find out what it is and kill it. Chris PGP signature
RE: tcpserver help
On 06-Apr-2001 Todd Kennedy wrote:
I'm trying to run qmail with tcpserver, and running this command:
17:31:44 root:/etc/usr/local/bin/tcpserver -u 518 -g 521 0 smtp
/var/qmail/bin/qmail-smtpd
gives the following error messsage:
tcpserver: fatal: unable to bind: address already used
i'm not sure what do here. any help would be appreciated.
thanks
todd
I get the same at my first attempt with tcpserver:
comment the smtp line into your /etc/inetd.conf!
--
Regards,: Marco Calistri [EMAIL PROTECTED]
gpg key available on http://www.qsl.net/ik5bcu
Xfmail 1.4.7p2 on linux RedHat 6.2
--
#!/bin/sh
for DVDs in Linux screw the MPAA and ; do dig $DVDs.z.zoy.org ; done
| perl -ne 's/\.//g; print pack("H224",$1) if(/^x([^z]*)/)' | gunzip.
Re: Tcpserver - GONE A BIT FAR ...
Has anyone seen my umbrella? I think I left it here somewhere
Re: tcpserver
At 10:44 AM 3/27/01 -0500, you wrote: Scrap telnet for ssh. Scrap ftpd for ssh (authenticated) and/or publicfile (anonymous). telnet or ftpd is not the main issue, starting any system services through tcpserver is the point. (Using tcpserver.conf) What's tcpserver.conf? It is a file like inetd.conf. May be you are familiar with writing long tcpserver commands to monitor the port and corresponding services to start, upon incoming request, in some startup file like rc.conf, or through rc.d/init.d directory --- Also it starts multiple instances of tcpserver for each port / service to monitor. Compare with inetd.conf Where just a single entry suffices. tcpserver.conf gives you the best of both worlds. The ease of configuration of inetd speed (sustaining quite high no of connections), security (tunable through .cdb files). See attachment for tcpserver.conf See also the man O/P (use more or less pager for proper viewing). What's tcpserver-control? This is an added goodie of the bunch. It Actually parses the tcpserver.conf with a help of daemon-tools starts tcpserver to monitor the ports given in tcpserver.conf (like inetd.conf) (Thats What I Think, How ? I still have to figure out, that's the reason for my first mail !!) All Options that can be given to tcpserver can be given in tcpserver.conf (Looks like It) And in a more structured manageable way. It also allows to start / stop status monitoring of the services handled by tcpserver. See tcpserver-control man page. (use more or less pager to view correctly) Regards Mustafa M -- VeetVision Communications (P) Ltd. Bungalow C-3, Moghul Gardens, 411001 Pune, India Tel. 91-20-6113056, 6051597, 6051598 / Fax 91-20-6050652 tcpserver.conf man.tcpserver-control man.tcpserver.conf
Re: Tcpserver
* Sumith [EMAIL PROTECTED] [010327 04:16]: Side note: would you *PLEASE* turn off HTML in your mail and fix your line width - you're wasting other people's resources and make your messages unnecessarily hard to read. http://learn.to/edit_messages Qmail FAQ states that tcpserver allows only 40 simultaneous qmail-smtpd connections and to increase it to 400, I need to run tcpserver -c 400 Would this number sustain after a reboot... That depends on how you start tcpserver. How to do this for qmail-pop3d as well The same way? I mean, what do you expect us to do? Grab a crystal ball and try to find out how you invoke your stuff? Why don't you *read* the available documentation? Like: Step 1: http://www.google.com/search?hl=enlr=safe=offq=%22tcpserver+-c%22+qmail-send Step 2: http://qmail.3va.net/qmailfaq.html#smtpd Step 3: verify that this is correct: http://cr.yp.to/ucspi-tcp/tcpserver.html Keep in mind that a) this is not a support forum and b) helping you each time you have a problem will 1) get on a *lot* of people's nerves and 2) make you prone to not reading the documentation. Neither alternative is desirable. -- Robin S. Socha http://mail.socha.net/
Re: Tcpserver
On Tue, Mar 27, 2001 at 04:34:04AM -0500, Robin S. Socha wrote: Keep in mind that a) this is not a support forum Huh? URL:http://cr.yp.to/djb.html * qmail support questions. Send them to the qmail mailing list instead. Maybe you're getting carried away a bit. If this list is not a support forum for qmail, what _is_? Vince.
Re: Tcpserver
Thanks Vincent! Mr. Robin is trying to discourage newbies like me from asking for help. Seems like this wise guy has a problem in life. Its really a bad habit to reply rudely. So, Mr. Robin if you dont want to help just *ignore* and DONT attempt to spoil someone's day. And regarding the question I posted, I figured it outthere is -c40 number specified in my qmail-smtpd run script (qmail installed from memphis rpm's) So, What would be the right number to increase this to, for a qmail server which would handle around 30,000 mails per day. Also it would help me to know if there is any know limitation on number of tcpserver connections for qmail-pop3d. Regards Sumith On Tue, Mar 27, 2001 at 04:34:04AM -0500, Robin S. Socha wrote: Keep in mind that a) this is not a support forum Huh? URL:http://cr.yp.to/djb.html * qmail support questions. Send them to the qmail mailing list instead. Maybe you're getting carried away a bit. If this list is not a support forum for qmail, what _is_? Vince.
Re: Tcpserver
rpm's) So, What would be the right number to increase this to, for a qmail server which would handle around 30,000 mails per day. Watch your logs and your memory use to see what number is appropriate for your system. If your tcpserver/smtpds use too much memory the number is too high. Set the number lower then. Beware that this would defer many connection attempts - if you are always at the limit of parallel connections and hyve no more memory to spend invest in your hardware. For 3 mails a day -c 10 should be enough. Give it more if your machine is able to do it (it should :) - this handles peaks well then. Regards, Frank
Re: Tcpserver
Sumith writes: Mr. Robin is trying to discourage newbies like me from asking for help. No, he's trying to get you to try to help yourself FIRST. And regarding the question I posted, I figured it out See? You wasted our time because with a little more work, you answered your own question. -- -russ nelson will be speaking at http://www.osdn.com/conferences/brie/ Crynwr sells support for free software | PGPok | Watch out! He's got an 521 Pleasant Valley Rd. | +1 315 268 1925 voice | opinion, and he's not Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | afraid to share it!
Re: Tcpserver - GONE A BIT FAR ...
HI ALL, I am shocked and appalled at the absolute lack of courtesy, help and sympathy that is on this list. I have been here a while and while there comes a few newbies that can really ask some dumb questions - we were all there once... Have some patience and help those less experienced than yourselves. If you do not like this - BUGGER OFF... Those that do not RTFM (read the F'ing manual) sometimes do not have the time or the knowhow on where to find it - and that is why we have a mailing list - so we can ask others that know - and stop this needless bickering and band together. Sorry to those who are offended - but thats tough ... Thanks Tonino Russell Nelson wrote: Sumith writes: Mr. Robin is trying to discourage newbies like me from asking for help. No, he's trying to get you to try to help yourself FIRST. And regarding the question I posted, I figured it out See? You wasted our time because with a little more work, you answered your own question.
Re: Tcpserver - GONE A BIT FAR ...
TAG [EMAIL PROTECTED] wrote: Those that do not RTFM (read the F'ing manual) sometimes do not have the time or the knowhow on where to find it - and that is why we have a mailing list - so we can ask others that know - and stop this needless bickering and band together. No. Those that do not have the "knowhow" on where to find the fucking manual (in the tarball with the source code! what an idea!) shouldn't be running computers at all, let alone an MTA on the internet. We have a mailing list so that we can investigate trouble reports from users who have already read (and understood) the documentation, but are running into situations not covered in it, and so that we can discuss possible solutions to complicated problems. Basic guide for newbies: if for some reason you think it is easier to just post your FAQ to the mailing list, rather than reading the documentation, where it is clearly answered, you need to a) grow up, and b) get a clue. 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: Tcpserver
On Tue, Mar 27, 2001 at 06:22:58PM +0530, Sumith wrote: Thanks Vincent! Mr. Robin is trying to discourage newbies like me from asking for help. No, he's not. FWIW: I agreed with most of what Robin wrote, but to claim that this is not a support forum for qmail is simply wrong. Vince.
Re: Tcpserver - GONE A BIT FAR ...
Charles Cazabon [EMAIL PROTECTED] wrote: No. Those that do not have the "knowhow" on where to find the fucking manual (in the tarball with the source code! what an idea!) shouldn't be running computers at all, let alone an MTA on the internet. Welcome to the second millenium where clueless folks abound on the internet. And it is a good thing too. Without them we'd be back in the days when only .edu's and .gov's existed on the 'net. Sure, it was a nice little community and we were all able to keep our noses glued to the overhead, but who cared?
Re: Tcpserver
* Vincent Schonau [EMAIL PROTECTED] [010327 09:37]: On Tue, Mar 27, 2001 at 06:22:58PM +0530, Sumith wrote: Mr. Robin is trying to discourage newbies like me from asking for help. No, he's not. Yes he is. I would very much like for newbies who don't read the FAQ or otherwise try to help themselves to disappear. FWIW: I agreed with most of what Robin wrote, but to claim that this is not a support forum for qmail is simply wrong. Vince, we've been there before. This ML is kept alive by a handful of people to whom I'm greatly indebted because they have helped *me* lot. OTOH, *I* would have said "I'm running the Memphis RPMs version #123" in the first place. And yes, I believe that someone who cannot do that should *not* be running a mailserver in the first place. Just for the record (reply-to set, this is way OT): |qmail: For discussion of the qmail package, the qmailanalog package, the |dot-forward package, and the fastforward package. [...] | |Please read FAQ, PIC.*, and the other documentation in the qmail package |before sending your question to the qmail mailing list. -- Robin S. Socha http://mail.socha.net/
Re: Tcpserver
On Tue, Mar 27, 2001 at 10:00:04AM -0500, Robin S. Socha wrote: * Vincent Schonau [EMAIL PROTECTED] [010327 09:37]: On Tue, Mar 27, 2001 at 06:22:58PM +0530, Sumith wrote: Mr. Robin is trying to discourage newbies like me from asking for help. No, he's not. Yes he is. I would very much like for newbies who don't read the FAQ or otherwise try to help themselves to disappear. FWIW: I agreed with most of what Robin wrote, but to claim that this is not a support forum for qmail is simply wrong. Vince, we've been there before. This ML is kept alive by a handful of people to whom I'm greatly indebted because they have helped *me* lot. OTOH, *I* would have said "I'm running the Memphis RPMs version #123" in the first place. And yes, I believe that someone who cannot do that should *not* be running a mailserver in the first place. Just for the record (reply-to set, this is way OT): |qmail: For discussion of the qmail package, the qmailanalog package, the |dot-forward package, and the fastforward package. [...] | |Please read FAQ, PIC.*, and the other documentation in the qmail package |before sending your question to the qmail mailing list. -- Robin S. Socha http://mail.socha.net/ now i know tcpserver a lot -- MOkondo i am an atheist, thank god !
Re: tcpserver
Mustafa Mahudhawala [EMAIL PROTECTED] wrote: Has anybody used tcpserver for Qmail other services out there -- Of course. I am using FreeBSD 4.2 and want to start my basic services like telnetd, ftpd along with smtp pop3 etc using tcpserver (and tcpserver.conf) instead of plain tcpserver or inetd (and inetd.conf). Scrap telnet for ssh. Scrap ftpd for ssh (authenticated) and/or publicfile (anonymous). What's tcpserver.conf? I have succesfully installed tcpserver, daemontools tcpserver-control (latest versions) What's tcpserver-control? But I am pretty confused about the whole lot and their ineraction. i.e. tcpserver - daemontools - tcpserver-control. tcpserver listens to a specified port, accepts connections on that port, and forks a daemon to handle the connection. daemontools provides a set of utilities for controlling daemons (services)--starting them, stopping them, signalling them, logging their output, etc. tcpserver-control I've never heard of. also /services tcpserver.conf (why both) Beats me. -Dave
Re: Tcpserver - GONE A BIT FAR ...
At 08:56 AM 3/27/2001, TAG wrote: HI ALL, Greetings, I am shocked and appalled at the absolute lack of courtesy, help and sympathy that is on this list. I have been here a while and while there comes a few newbies that can really ask some dumb questions - we were all there once... There is a distinct difference between someone who genuine doesn't know and someone that just doesn't read documentation. "How do i get qmail to start at boot?" is a classic example of someone not reading LFQ. Have some patience and help those less experienced than yourselves. If you do not like this - BUGGER OFF... It gets tiring to see the same 5 questions..recently someone asked me off list that LFQ didn't cover apache with PHP installation. I said that there was reason for this. APACHE AND PHP AREN'T EVEN RE MOTLEY RELATED TO QMAIL!! Those that do not RTFM (read the F'ing manual) sometimes do not have the time or the knowhow on where to find it - and that is why we have a mailing list - so we can ask others that know - and stop this needless bickering and band together. If you can't find a web site i'm surprised if you can boot lilo. Chances you got qmail from qmail.org...and what else is on qmail.org?...a whole section for documentation. Its very hard to miss...theres only about 30 links there :-) If you don't know how to read man pages use ./configure or make or learn to find documentation then you shouldn't even be looking at LINUX or other UNIX. (And for all those of you that are wondering, NO! Qmail will NOT run on Windows. :-)) It comes down to laziness and i think that a newbie qmail list would be good. I wouldn't subscribe...but it give the newbies a chance to work together and figure out how to read documentation. :-) Sorry to those who are offended - but thats tough ... I don't feel that its offensive...I have posted much worse to the misc@openbsd list. :-) Thanks Tonino ~kurth Russell Nelson wrote: Sumith writes: Mr. Robin is trying to discourage newbies like me from asking for help. No, he's trying to get you to try to help yourself FIRST. And regarding the question I posted, I figured it out See? You wasted our time because with a little more work, you answered your own question.
Re: Tcpserver
Dear All Seems like it's all my fault for starting this WAR.. It had become a habit for me, whenever I see a problem, I panic and first thing send a mail to the list. My Sincere apologies for all thisI *promise* to read, study and try to do things myself before posting to the list (In Plain TEXT and without any lines in between). And if I do post *will* include all the relevant details. Regards Sumith
Re: Tcpserver
Dear All Seems like it's all my fault for starting this WAR.. It had become a habit for me, whenever I see a problem, I panic and first thing send a mail to the list. My Sincere apologies for all thisI *promise* to read, study and try to do things myself before posting to the list (In Plain TEXT and without any lines in between). And if I do post *will* include all the relevant details. Regards Sumith Don't loose any sleep over it. Face it, some people are grouches... That's why they invented Prozac! Personally, maybe the qmail list would benefit from a Qmail-Newbies list. This way the ones who don't mind helping the newbies (like myself) can actually get some work done instead of having to read whining / vulgar emails!. Yes I can use the F-word just as easily as everyone else but THIS LIST is *NOT* the place for it. AND before anyone flames me about not posting here, you are 100% correct! I don't post here, I answer emails to the newbies personally and individually so the problem or question GETS answered instead of being ignored which has happened on this list. Regards, Richard
Re: Tcpserver
Richard Zimmerman [EMAIL PROTECTED] wrote: Personally, maybe the qmail list would benefit from a Qmail-Newbies list. It's been proposed before. There are various problems with the idea, the main one being that newbies who won't read documentation also won't post to the correct list. Also, the idea itself is flawed -- why go to any trouble at all to help someone who won't even read basic documentation? This way the ones who don't mind helping the newbies (like myself) can actually get some work done instead of having to read whining / vulgar emails!. Yes I can use the F-word just as easily as everyone else but THIS LIST is *NOT* the place for it. On the contrary; djb himself has used it many times on this list. I have the archive entries to prove it. You're not the language police; if you don't care for the occasional blue word, please don't read this list. AND before anyone flames me about not posting here, you are 100% correct! I don't post here, I answer emails to the newbies personally and individually so the problem or question GETS answered instead of being ignored which has happened on this list. This compounds the problem; answers should go to the list, so that people searching the list archives for answers will actually find them, rather than finding only questions, and re-posting the question again. Ad infinitum. 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: Tcpserver
Richard Zimmerman [EMAIL PROTECTED] wrote: This way the ones who don't mind helping the newbies (like myself) can actually get some work done instead of having to read whining / vulgar emails!. Yes I can use the F-word just as easily as everyone else but THIS LIST is *NOT* the place for it. Charles Cazabon wrote: On the contrary; djb himself has used it many times on this list. I have the archive entries to prove it. You're not the language police; if you don't care for the occasional blue word, please don't read this list. Well, if djb used the F-word, THAT makes it all OK! Why don't we start calling it F***Mail then? I'm sure Dan Bernstein would love to be known as the creator of F***Mail... don't you? You can debate whether rude, foul language is appropriate for a list all you want. I personally don't really care to see it, but I acknowledge it's up to the individual to choose their own words. As you said, I can choose not to subscribe and/or read the messages. However, as any educated individual will tell you. Your choice of words is a direct reflection of your intellect. Shallow people use shallow words. Choose any words you care to use, it will only gives us a better insite of the validity of all your comments.
Re: Tcpserver
Bill Andersen [EMAIL PROTECTED] wrote:
However, as any educated individual will tell you. Your choice of
words is a direct reflection of your intellect. Shallow people use
shallow words.
You are correct; I could have used longer terminology to communicate my
intentions, possibly substituting "intercourse" for the shorter epithet.
Instead, I chose to use the term you alluded to ("the F-word") to make
my point. You appear to have missed the point; I'll repeat it for clarity's
sake: please do not try to force your opinions about what language should
or should not be used on the list down the esophogi of the rest of us.
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: Tcpserver
Robin S. Socha wrote: * Sumith [EMAIL PROTECTED] [010327 04:16]: Side note: would you *PLEASE* turn off HTML in your mail and fix your line width - you're wasting other people's resources and make your messages unnecessarily hard to read. http://learn.to/edit_messages Further side note: To improve the s/n ratio around here, would you cease responding to people whose comments you don't like, whose editors tweak you the wrong way or who have funny haircuts? Your "side notes" have been going on for _years_ on this list and they aren't terribly profitable from the looks of the archives.
Re: Tcpserver - GONE A BIT FAR ...
On Tue, Mar 27, 2001 at 03:56:03PM +0200, TAG wrote: Those that do not RTFM (read the F'ing manual) sometimes do not have the time Huh? This should be a legitimation to waste listmembers time??? That's not the way things work. and that is why we have a mailing list We have this mailinglist for discussing problems NOT covered by the manuals, for discussing patches and technical details. - so we can ask others that know - and stop this needless bickering and band together. Go an get a life. -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: Tcpserver - GONE A BIT FAR ...
On Tue, Mar 27, 2001 at 10:54:26AM -0500, Kurth Bemis wrote: I am shocked and appalled at the absolute lack of courtesy, help and sympathy that is on this list. I have been here a while and while there comes a few newbies that can really ask some dumb questions - we were all there once... There is a distinct difference between someone who genuine doesn't know and someone that just doesn't read documentation. "How do i get qmail to start at boot?" is a classic example of someone not reading LFQ. LFQ should be LWQ... But it is even covered by the documentation in the source tarball... I have posted much worse to the misc@openbsd list. :-) Yes, that's true ;-)) But you learned your lesson - I don't think this guy here will... -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: Tcpserver
On Tue, Mar 27, 2001 at 01:03:12PM -0600, Charles Cazabon wrote:
Bill Andersen [EMAIL PROTECTED] wrote:
However, as any educated individual will tell you. Your choice of
words is a direct reflection of your intellect. Shallow people use
shallow words.
You are correct; I could have used longer terminology to communicate my
intentions, possibly substituting "intercourse" for the shorter epithet.
Instead, I chose to use the term you alluded to ("the F-word") to make
my point. You appear to have missed the point; I'll repeat it for clarity's
sake: please do not try to force your opinions about what language should
or should not be used on the list down the esophogi of the rest of us.
And don't forget that there are many non-native english speakers on this
list (like muself), their selection of words may be influenced by a
different culture or - simply not knowing the "shallow" word.
--
Henning Brauer | BS Web Services
Hostmaster BSWS| Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Re: Tcpserver
* Bill Andersen [EMAIL PROTECTED] writes: Charles Cazabon wrote: Richard Zimmerman [EMAIL PROTECTED] wrote: [quoting corrected] This way the ones who don't mind helping the newbies (like myself) can actually get some work done instead of having to read whining / vulgar emails!. Yes I can use the F-word just as easily as everyone else but THIS LIST is *NOT* the place for it. On the contrary; djb himself has used it many times on this list. I have the archive entries to prove it. You're not the language police; if you don't care for the occasional blue word, please don't read this list. Well, if djb used the F-word, THAT makes it all OK! Yup. His suite of programs, his list. He God. You luser. Easy. The gang of lusers you're trying to protect here *has* *not* provided sufficient information. They were pointed at the correct links from google. They were shown how to use their mailtoys correctly (you don't give a toss about what your mail looks like, eh? Tell you what: there is a reason why people use quote strings). Do they care? No. Do the people who devote their time to trying to help people with problems get paid for this? No. So you don't care - tough luck. Contribute nothing, expect nothing. However, as any educated individual will tell you. Parse error. Your choice of words is a direct reflection of your intellect. Tell me, Bill, how would you know? Choose any words you care to use, it will only gives us a better insite of the validity of all your comments. You are so full of yourself your eyeballs must be brown. In case you haven't noticed: this is a technical mailing list. Take your political correctness and shove it. This is not a "I'm a pathetic luser with limited reading abilities and gosh! it would be, like, rillyrilly nice if you guys could read out the docs to me." list. This a mailing list where - in good times - some people get some real problems solved and others benefit from the answers. If you cannot grasp this concept, you are *in* *the* *wrong* *place* -- Robin S. Socha http://mail.socha.net/ Note to experienced users: Please don't encourage anti-support behavior. Don't try to answer questions from users who don't provide the necessary information. Guessing what they did is an incredible waste of time. (DJB)
RE: Tcpserver
Kuhl. In that case who do I talk to to get unsubscribed from this group? I already tried unsubscribing from the web page and it acted like it took it, but I'm still getting emails a day later. Garrett Johnson SFGH, Dean's Office, School of Medicine -Original Message- From: Robin S. Socha [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 27, 2001 12:02 PM To: [EMAIL PROTECTED] Subject: Re: Tcpserver * Bill Andersen [EMAIL PROTECTED] writes: Charles Cazabon wrote: Richard Zimmerman [EMAIL PROTECTED] wrote: [quoting corrected] This way the ones who don't mind helping the newbies (like myself) can actually get some work done instead of having to read whining / vulgar emails!. Yes I can use the F-word just as easily as everyone else but THIS LIST is *NOT* the place for it. On the contrary; djb himself has used it many times on this list. I have the archive entries to prove it. You're not the language police; if you don't care for the occasional blue word, please don't read this list. Well, if djb used the F-word, THAT makes it all OK! Yup. His suite of programs, his list. He God. You luser. Easy.
Re: Tcpserver
Johnson, Garrett [EMAIL PROTECTED] wrote: In that case who do I talk to to get unsubscribed from this group? I already tried unsubscribing from the web page and it acted like it took it, but I'm still getting emails a day later. Removal instructions are included in the confirmation mail you got from ezmlm when you signed up. They're also in the headers of every message. Hint: use the -help address for extra removal instructions. 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: Tcpserver
[EMAIL PROTECTED] wrote: Kuhl. In that case who do I talk to to get unsubscribed from this group? I already tried unsubscribing from the web page and it acted like it took it, but I'm still getting emails a day later. Look at the headers of the mail you recieve from the list and look at the return path. There you will find the address you have subscribed under. For example: Return-Path: [EMAIL PROTECTED] would indicate [EMAIL PROTECTED] was subscribed. To unsubscribe [EMAIL PROTECTED] from the list, send a mail to: [EMAIL PROTECTED] Then reply to the confirmation request and you will be removed from the list.
RE: Tcpserver - GONE A BIT FAR ...
"Basic guide for newbies: if for some reason you think it is easier to just post your FAQ to the mailing list, rather than reading the documentation, where it is clearly answered, you need to a) grow up, and b) get a clue." I think the most important thing is this write-up is " where it is clearly answered... ". I have read most document 20-30 times and seldom find them " clearly answered ". Some of you who are annoyed, please consider: (1) someone who is starting NEW needs little bit extra help then "f'ing" in response (2) I have seen posting from Spain, Germany, etc. Such individuals has English as their second language. I was going to add few more.. but decided to leave it only to above. Kirt -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 27, 2001 9:14 AM To: [EMAIL PROTECTED] Subject: Re: Tcpserver - GONE A BIT FAR ... TAG [EMAIL PROTECTED] wrote: Those that do not RTFM (read the F'ing manual) sometimes do not have the time or the knowhow on where to find it - and that is why we have a mailing list - so we can ask others that know - and stop this needless bickering and band together. No. Those that do not have the "knowhow" on where to find the fucking manual (in the tarball with the source code! what an idea!) shouldn't be running computers at all, let alone an MTA on the internet. We have a mailing list so that we can investigate trouble reports from users who have already read (and understood) the documentation, but are running into situations not covered in it, and so that we can discuss possible solutions to complicated problems. Basic guide for newbies: if for some reason you think it is easier to just post your FAQ to the mailing list, rather than reading the documentation, where it is clearly answered, you need to a) grow up, and b) get a clue. 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. ---
