qmail-smtpd on tcpserver again :(
I tried to run so many different configs and still no luck. basic script for launching smtp looks like this: tcpserver -v -u 508 -g 509 0 smtp /var/qmail/bin/qmail-smtpd \ 2>&1 | /var/qmail/bin/splogger smtpd 3 & But I cannot send message form any external host - I found in logs: 937900864.859093 tcpserver: warning: dropping connection, unable to run qmail-smtpd: file does not exist (of course qmail-smtpd exists in /var/qmail/bin/) Any idea? Thx in advance! Piotr Wanat -- mailto:[EMAIL PROTECTED] | UIN:15871058
Re: qmail-smtpd on tcpserver again :(
On Tue, Sep 21, 1999 at 10:12:42AM +0200, Piotr Wanat wrote: > I tried to run so many different configs and still no luck. > basic script for launching smtp looks like this: > > tcpserver -v -u 508 -g 509 0 smtp /var/qmail/bin/qmail-smtpd \ > 2>&1 | /var/qmail/bin/splogger smtpd 3 & > > But I cannot send message form any external host - I found in logs: > 937900864.859093 tcpserver: warning: dropping connection, unable to run > qmail-smtpd: file does not exist > > (of course qmail-smtpd exists in /var/qmail/bin/) Any idea? The file may exist, but if /var/qmail/bin has the wrong permissions, the qmaild user may not be able to look at the files. The usual mode is 755 for /var/qmail and /var/qmail/bin. -- See complete headers for more info
Re: ETRN
On Tue, Sep 21, 1999 at 09:47:07AM +0200, Dimitri SZAJMAN wrote: > Please can Qmail use the ETRN protocol as described in RFC 1985 ? (see > http://rfc.fh-koeln.de/rfc/html/rfc1985.html). > > As I think no :-/, I installed maildir2smtp but I get troubles getting the > dynamic IP adress from my clients with custommers when their SMTP want to > check mails... If you're assigning dynamic addresses to your customers, look at http://www.qmail.org/turnmail -- See complete headers for more info
qmail Digest 21 Sep 1999 10:00:00 -0000 Issue 766
qmail Digest 21 Sep 1999 10:00:00 - Issue 766 Topics (messages 30513 through 30591): Pop Server 30513 by: Qmail-User 30518 by: Anand Buddhdev Re: qmail-smtpd-wrapper error. 30514 by: Chris Johnson 30515 by: Lorens Kockum 30517 by: Mark Thomas 30520 by: Lorens Kockum 30521 by: Dave Sill 30526 by: Mark Thomas 30543 by: Dave Sill 30585 by: Mark Thomas Re: When will qmail back off to the next MX? 30516 by: David Dyer-Bennet 30551 by: phil.ipal.net Can't find message after received 30519 by: Eric Davis 30535 by: Dave Sill Re: Having trouble with pop 30522 by: Tim Hunter 30524 by: Mikko Hänninen 30532 by: Aaron L. Meehan 30533 by: Rick Erlandson 30537 by: Tim Hunter 30539 by: Gregory J. Forkiin (Rhawn) 30546 by: Rick Erlandson 30555 by: Racer X 30558 by: Gregory J. Forkiin (Rhawn) Re: qmail-smtp fails on RedHat 6.0 30523 by: mw.wierdlmpc.msci.memphis.edu 30534 by: Richard George 30540 by: Dave Sill 30553 by: Mate Wierdl big Messages with POP3 30525 by: martin.sintesoft.net Re: Main server = qmail, destination = ms exchange 30527 by: Dave Sill 30548 by: Olivier M. Re: (Clarification) Installation Quesiton on Qmail. 30528 by: Serban Udrea 30545 by: Dave Sill 30552 by: Mark Thomas Re: How to remove a (botched) qmail installation to start over? 30529 by: Dave Sill Re: <> question 30530 by: Aaron L. Meehan Qmail and HP Openmail 30531 by: Stephan Hadan (E-Mail) Re: maildir structure 30536 by: qmail.col7.metta.lk imapd with tcpserver? 30538 by: Piotr Wanat 30541 by: Dave Sill 30542 by: Piotr Wanat 30544 by: Dave Sill 30549 by: Piotr Wanat 30550 by: Dave Sill 30554 by: Piotr Wanat 30565 by: Dave Sill Re: auto-forward email and hierarchical email account 30547 by: Dave Sill Weird Message... 30556 by: Andy Walden How good is RBL at filtering spam? 30557 by: David Harris 30559 by: James J. Lippard 30560 by: schinder.leprss.gsfc.nasa.gov 30562 by: David Harris 30569 by: Nathan J. Mehl 30570 by: David Harris 30571 by: James Smallacombe 30573 by: Fabrice Scemama 30574 by: Vern Hart 30576 by: James Smallacombe 30580 by: schinder.leprss.gsfc.nasa.gov "550 rejected: cannot route to sender" problem 30561 by: Graham Higgins Re: Sqwebmail and IMAP 30563 by: Randy Harmon 30566 by: Racer X 30567 by: Randy Harmon 30568 by: Asmodeus 30572 by: Racer X 30575 by: Sam 30584 by: Randy Harmon usage of qmail-local 30564 by: Joe Chan Virtual email for non virtual host 30577 by: James How to Rewrite Message-ID using ofmipd 30578 by: x how to using maildrop 30579 by: x HOw to send more with qmail-inject? 30581 by: Hawke 30583 by: Peter Samuel qmail-start (qmail 1.03) under RedHat 6.0 30582 by: Vladimir Berezniker Re: race condition in qmail-popbull 30586 by: Michael Boyiazis Re: ANNOUNCE: /var/qmail/control/locals and regex 30587 by: Robert Sander ETRN 30588 by: Dimitri SZAJMAN 30591 by: Anand Buddhdev qmail-smtpd on tcpserver again :( 30589 by: Piotr Wanat 30590 by: Anand Buddhdev Administrivia: To subscribe to the digest, e-mail: [EMAIL PROTECTED] To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To bug my human owner, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- I am having some difficulty starting my pop server. Could someone give me an example of what type of syntax they use to start the qmail pop service? Regards Vivian Lal On Mon, Sep 20, 1999 at 09:09:04PM +1000, Qmail-User wrote: tcpserver -RHlmy.host.name 0 110 /usr/local/qmail/bin/qmail-popup \ my.host.name /usr/local/bin/checkpassword \ /usr/local/qmail/bin/qmail-pop3d Maildir & Replace my.host.name with your host's name, and change the path to the programs to /var/qmail. That's where you most likely installed qmail. > I am having some difficulty starting my pop server. Could someone give me > an example of what type of syntax they use to start the qmail pop service? > > Regards > > Vivian Lal > -- See complete headers for more info On Sun, Sep 19, 1999 at 10:46:11PM -0500, Mark Thomas wrote: > 937728523.256241 tcpserver: warning: dropping connection, unable to run > /var/qmail/bin/qmail-smtpd-wrapper: access denied > 937728523.256449 tcpserver: end 16854 status 28416 > 937728523.25
Redirecting outgoing mails
Dear All ! I use Redhat6 with Qmail as the MTA. I just want to know if we can redirect outgoing mails as well. For exmple I want to redirect mails from [EMAIL PROTECTED] to [EMAIL PROTECTED] Shashi
Qmail and ANTI-SPAM
Hi folks, i'm using qmail with rblsmtpd to block Mail from known spamers. But it doesn't seem to work, some free test from the web detect, that my site accepts mail from spamers, but it shouldn't ?! i call qmail that way : supervise /var/lock/qmail-smtpd tcpserver -c400 -v -x/etc/tcp.smtp.cdb -u$USERID -g$GROUPID 0 25 \ rblsmtpd qmail-smtpd 2>&1 | setuser qmaill accustamp | \ setuser qmaill cyclog -s500 -n5 /var/log/qmail/qmail-smtpd & It doesn't work .. :-( Thanks, Thomas
Re: ETRN
Thank you for your answer. With some help, I wrote a script that looks like that with commands like 'tr', 'cut', 'sed' and so on. But I am looking for the real ETRN as described in the RFC. Thanks ! -- Xon-Xoff - http://www.Xon-Xoff.fr Publication et Commerce electronique sur le Web Messagerie d'entreprise, Interconnexion et Securite des reseaux - Message d'origine - De : Anand Buddhdev <[EMAIL PROTECTED]> À : Dimitri SZAJMAN <[EMAIL PROTECTED]> Cc : <[EMAIL PROTECTED]> Envoyé : mardi 21 septembre 1999 10:43 Objet : Re: ETRN > On Tue, Sep 21, 1999 at 09:47:07AM +0200, Dimitri SZAJMAN wrote: > > > Please can Qmail use the ETRN protocol as described in RFC 1985 ? (see > > http://rfc.fh-koeln.de/rfc/html/rfc1985.html). > > > > As I think no :-/, I installed maildir2smtp but I get troubles getting the > > dynamic IP adress from my clients with custommers when their SMTP want to > > check mails... > > If you're assigning dynamic addresses to your customers, look at > http://www.qmail.org/turnmail > > -- > See complete headers for more info >
Re: qmail-start (qmail 1.03) under RedHat 6.0
* Vladimir Berezniker ([EMAIL PROTECTED]) [20 Sep 1999 21:59]: > Hi, > First of all I am a newbie to the *nix. I use supervise from deamon tools 0.61. >To run the following run file: > * Go back and read the html man pages for daemontools 0.61 again. In order to get logging and control to work one has to put the script for the logging portion (the stuff after the pipeline (|) symbol) in the log subdirectory of the directory that contains the run script for the qmail-start command and then use svscan to connect the two: For example: /services/qmail/run <-- contains the commands to start qmail /services/qmail/log/run <-- contains multilog et. al. with svscan being started (in the background) from the /services directory. -- Quist ConsultingEmail: [EMAIL PROTECTED] 219 Donlea DriveVoice: +1.416.696.7600 Toronto ON M4G 2N1 Fax: +1.416.978.6620 CANADA WWW: http://www.quist.on.ca
rcpthosts - did i miss something?!
Hi there .. i want qmail to only accept mail form an email-adress/domain that is listet in /var/qmail/control/rcpthosts, but it accepts very mail , even from foo@bar. What's wrong?! Thomas
Re: rcpthosts - did i miss something?!
rcpthosts accepts all FROM messages but not all TO messages : I.e. if rcpthosts contains "foo.com", it will only accept messages adressed TO: [EMAIL PROTECTED] but any SENDER (FROM) will be accepted. -- Xon-Xoff - http://www.Xon-Xoff.fr Publication et Commerce electronique sur le Web Messagerie d'entreprise, Interconnexion et Securite des reseaux - Message d'origine - De : Thomas Foerster <[EMAIL PROTECTED]> À : qmail <[EMAIL PROTECTED]> Envoyé : mardi 21 septembre 1999 13:50 Objet : rcpthosts - did i miss something?! | Hi there .. | | i want qmail to only accept mail form an email-adress/domain that is | listet in /var/qmail/control/rcpthosts, but it accepts very mail , | even from foo@bar. | | | What's wrong?! | | Thomas |
Re: rcpthosts - did i miss something?!
Thomas Foerster <[EMAIL PROTECTED]> writes on 21 September 1999 at 13:50:30 +0200 > i want qmail to only accept mail form an email-adress/domain that is > listet in /var/qmail/control/rcpthosts, but it accepts very mail , > even from foo@bar. rcpthosts controls addresses for which mail will be *received* (hence the name). It has nothing to do with sender addresses. -- David Dyer-Bennet ***NOTE ADDRESS CHANGES*** [EMAIL PROTECTED] http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms Join the 20th century before it's too late!
Re: Weird Message...
Andy Walden Wrote thus: > I searched the archives for this, and saw it mention several times, but I > couldn't find a definitive answer. I'm getting: > > Sep 20 13:40:09 leviathan qmail: 937852809.494540 warning: trouble injecting bounce message, will try later > Sep 20 13:40:09 leviathan qmail: 937852809.524814 warning: trouble injecting bounce message, will try later > Sep 20 13:40:09 leviathan qmail: 937852809.555087 warning: trouble injecting bounce message, will try later > Sep 20 13:40:09 leviathan qmail: 937852809.583407 warning: trouble injecting bounce message, will try later > > I haven't changed anything (that I know of). The server has been up > without incident now for 196 days. I did a qmail-qread and didn't see > anything really weird. I have plenty of disk space, did an ls -laR of the > entire /var/qmail/queue directory looking for anything large and didn't > see anything. Any thoughts on this? Thanks. > > > -- > --- > Andy WaldenWork Email: [EMAIL PROTECTED] > Network Administrator,Pers Email: [EMAIL PROTECTED] > MTCO CommunicationsPhone: (800) 859-6826 > "A little nonsense now and then, is relished by the wisest men." > -Willi Wonka I'm having the same problem. I posted it to this list, but with no response so far. If anyone understands this problem, I hope they'll share their wisdom. Good luck! -Carlos
Re: Weird Message...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21 Sep 99, at 3:47, D. Carlos Knowlton wrote: > > Sep 20 13:40:09 leviathan qmail: 937852809.494540 warning: trouble > injecting bounce message, will try later > > Sep 20 13:40:09 leviathan qmail: 937852809.524814 warning: trouble > injecting bounce message, will try later > > Sep 20 13:40:09 leviathan qmail: 937852809.555087 warning: trouble > injecting bounce message, will try later > > Sep 20 13:40:09 leviathan qmail: 937852809.583407 warning: trouble > injecting bounce message, will try later > > [snip] > > I'm having the same problem. I posted it to this list, but with no > response so far. If anyone understands this problem, I hope they'll share > their wisdom. There may be two reasons: 1. Somehow, the queue structure (or access rights) got damaged. Use a tool which shows that, like "make setup check" or "queue-fix" from www.qmail.org. 2. Besides being out of free space, you may be out of inodes. Check not only "df", but also "df -i". -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBN+ePvFMwP8g7qbw/EQLWawCgjD1uw0W9hXUoQaFSesroikxkTt0An1Q7 Qf9QjyKiU5gSfYfRm2vtdor4 =QbFd -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Weird Message...
On Tue, 21 Sep 1999, Petr Novotny wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 21 Sep 99, at 3:47, D. Carlos Knowlton wrote: > > > Sep 20 13:40:09 leviathan qmail: 937852809.494540 warning: trouble > > injecting bounce message, will try later > > > Sep 20 13:40:09 leviathan qmail: 937852809.524814 warning: trouble > > injecting bounce message, will try later > > > Sep 20 13:40:09 leviathan qmail: 937852809.555087 warning: trouble > > injecting bounce message, will try later > > > Sep 20 13:40:09 leviathan qmail: 937852809.583407 warning: trouble > > injecting bounce message, will try later > > > > [snip] > > > > I'm having the same problem. I posted it to this list, but with no > > response so far. If anyone understands this problem, I hope they'll share > > their wisdom. > > There may be two reasons: > 1. Somehow, the queue structure (or access rights) got damaged. > Use a tool which shows that, like "make setup check" or > "queue-fix" from www.qmail.org. This fixed it for me. Thank you. -- --- Andy WaldenWork Email: [EMAIL PROTECTED] Network Administrator, Pers Email: [EMAIL PROTECTED] MTCO CommunicationsPhone: (800) 859-6826 "A little nonsense now and then, is relished by the wisest men." -Willi Wonka
Re: How good is RBL at filtering spam?
[EMAIL PROTECTED] wrote: >(My pobox.com address, on the other hand, gets plenty of spam, because >pobox's antispam methods are very poor. I only wish they used DUL, >which would get rid of most of the spam from that direction.) It's not good enough for an antispam method to simply be effective, it should also be selective. The DUL blocks non-relaying, nonspammers, just because it doesn't like the looks of their domain name...the baby/bathwater scenario. But the War on Spam, like the War on Drugs and the War on Terrorism cares little about collateral damage like me. Want to stop spam dead in its tracks? Turn off your smtp daemon. -Dave
Re: ANNOUNCE: /var/qmail/control/locals and regex
On Tue, Sep 21, 1999 at 08:56:54AM +0200, Robert Sander wrote: > [EMAIL PROTECTED] (Claus Färber) wrote: > > > Much of work? > > All you have to do is (untested): > > controls/virtualdomains: > > .example.com:alias-piffle > > alias/.qmail-default: > > |forward "$DEFAULT" > > (Yes, that's less work than applying a patch!) > > Inconsistent? > > Maybe. > > I see, but is that documented anywhere? You mean like, say, the man pages for example? http://www.qmail.org/man/man8/qmail-command.html > And I still think this is the "territory" auf control/locals because I do > not have a "virtual"domain, but a real one ;-) Don't reject a solution because you don't like the semantics. --Adam
Mail in queue - qmail won't quit
HI !
I have a mail in my queue to [EMAIL PROTECTED]
qmail trys to deliver it since 10 minutes without an error..
if i try to connect to the mailer of intracen.org (do a nslookup on the
MX),
i can connect but there is no response.
qmail can't quit, he waits until the mail is delivered.
How can i set a timeout?
How can i delete this ("/§"= message?!? (i tried qmHandle ..)
Thomas
Re: How good is RBL at filtering spam?
On Tue, Sep 21, 1999 at 09:31:27AM -0400, Dave Sill wrote: } [EMAIL PROTECTED] wrote: } } >(My pobox.com address, on the other hand, gets plenty of spam, because } >pobox's antispam methods are very poor. I only wish they used DUL, } >which would get rid of most of the spam from that direction.) } } It's not good enough for an antispam method to simply be effective, it } should also be selective. The DUL blocks non-relaying, nonspammers, } just because it doesn't like the looks of their domain name...the No, it blocks people who could easily send mail out through the mail servers of their ISP. If pobox used DUL (or more accurately, if pobox allowed its customers to choose which antispam services they wanted their mail filtered through, since that is what I really want), it would be both effective and wouldn't drop any mail that I want to get. People who use variable IP dialups and are too stubborn to use their providers SMTP servers to relay won't be able to reach me. Big deal. But this has been discussed on this list before. } baby/bathwater scenario. But the War on Spam, like the War on Drugs } and the War on Terrorism cares little about collateral damage like } me. } } Want to stop spam dead in its tracks? Turn off your smtp daemon. } } -Dave -- Paul J. Schinder NASA Goddard Space Flight Center [EMAIL PROTECTED]
Re: Mail in queue - qmail won't quit
Thomas Foerster <[EMAIL PROTECTED]> wrote:
>I have a mail in my queue to [EMAIL PROTECTED] qmail trys to
>deliver it since 10 minutes without an error.. if i try to connect
>to the mailer of intracen.org (do a nslookup on the MX), i can
>connect but there is no response.
>
>qmail can't quit, he waits until the mail is delivered.
>
>How can i set a timeout?
http://Web.InfoAve.Net/~dsill/lwq.html#queuelifetime
>How can i delete this ("/§"= message?!? (i tried qmHandle ..)
1) stop qmail
2) remove the /var/qmail/queue files associated with the message
3) restart qmail
or:
1) "touch" queue files sufficiently into the future to make qmail-send
think they've been around longer than queuelifetime. It'll bounce
on the next delivery attempt.
or:
1) Relax and let qmail do its job.
-Dave
Re: Redirecting outgoing mails
[EMAIL PROTECTED] wrote: >I use Redhat6 with Qmail as the MTA. I just want to know if we can >redirect outgoing mails as well. For exmple I want to redirect mails >from [EMAIL PROTECTED] to [EMAIL PROTECTED] You mean that on "some.domain.com", you want mail from "anybody" to go to "[EMAIL PROTECTED]", regardless of the intended recipient? I don't see an easy way to accomplish this. You could hack a wrapper around qmail-inject that would redirect messages from "anybody", but redirecting SMTP-injected messages would be a lot harder. -Dave
Re: Qmail and ANTI-SPAM
Thomas Foerster <[EMAIL PROTECTED]> wrote: >i'm using qmail with rblsmtpd to block Mail from known spamers. >But it doesn't seem to work, some free test from the web detect, that my >site accepts mail from spamers, but it shouldn't ?! Is that a RBL test, or a relay test? What's the URL? >supervise /var/lock/qmail-smtpd tcpserver -c400 -v -x/etc/tcp.smtp.cdb >-u$USERID -g$GROUPID 0 25 \ >rblsmtpd qmail-smtpd 2>&1 | setuser qmaill accustamp | \ >setuser qmaill cyclog -s500 -n5 /var/log/qmail/qmail-smtpd & > >It doesn't work .. :-( You mean RBL doesn't work, or nothing's listening to port 25? -Dave
Re: Virtual email for non virtual host
James <[EMAIL PROTECTED]> wrote: >I want to create a number of emails for one server (example, >[EMAIL PROTECTED], [EMAIL PROTECTED]), but I am at a loss as to how to do >this. I have created virtual email accounts for my other virtual domains >without a problem, they work great. How did you set them up? Add the "virtual" hosts to rcpthosts and locals? If so, they're not really virtual, they're host aliases. >But now I don't want to have to >create an "info" user just so I can have an "info" email for the server. >The "info" mail isn't for a virtual domain, it's for THE domain on my >server. > >I've tried adding domain.com:info in the virtual domain file but that >didn't work. What do I need to do? Thanks for any help. That virtualdomains entry causes mail sent to [EMAIL PROTECTED] to be delivered to info-user, which would be handled by ~info/.qmail-user or ~alias/.qmail-info-user. See: http://Web.InfoAve.Net/~dsill/lwq.html#multiple-hostnames http://Web.InfoAve.Net/~dsill/lwq.html#virtual-domains -Dave
cannot start: unable to switch to queue directory
This was ruhnnning fine for weeks, then all of a sudden it's givintg this errror when I try to start it: "qmail: 937928346.622853 alert: cannot start: unable to switch to queue directory" Anyone have any idea? Thanks, -Hawke
Re: cannot start: unable to switch to queue directory
It's qmail 1.03, on Solaris 2.6 (+ patches). Thanks, -Hawke - Original Message - From: Hawke <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 21, 1999 9:44 AM Subject: cannot start: unable to switch to queue directory > This was ruhnnning fine for weeks, then all of a sudden it's givintg this > errror when I try to start it: > "qmail: 937928346.622853 alert: cannot start: unable to switch to queue > directory" > Anyone have any idea? > Thanks, > -Hawke >
Re: cannot start: unable to switch to queue directory
: This was ruhnnning fine for weeks, then all of a sudden it's givintg this : errror when I try to start it: : "qmail: 937928346.622853 alert: cannot start: unable to switch to queue : directory" I'm sure it's something like a permissions problem. Try downloading queue-fix from www.qmail.org and run that on your queue directory. It should detect and fix any permission problems. -- Matthew Harrell You're just jealous because the Bit Twiddlers, Inc. voices only talk to me. [EMAIL PROTECTED]
RE: qmail-smtpd-wrapper error. -Reply
"Mark Thomas" <[EMAIL PROTECTED]> wrote: >Well, dad, I hate it when your right! You sound like a man who has much >patience. I've got three children, I worked the help desk at the computer center while I was in college, and I've been a tech support engineer for ten years, so I'm either very patient or brain dead. :-) >>Hmm, that "502 unimplemented (#5.5.1)" message came from qmail-smtpd >>when you entered and unrecognized command. So your SMTP service was >>working fine. > >))) I thought it was going to tell me "helo dude"! No, that's what you're supposed to say to it. >>I used the INSTALL directions, but, then, I'm an experienced system >>administrator. > >- Ouch!, Well, the INSTALL document looked alot different after >going >- through your LWQ. I felt like I could give it a run for the money. I wasn't trying to denigrate your newbieness. Back when I started doing qmail, there was no choice: the INSTALL document was *it*. qmail was a place where newbies feared to tread. Now there are various RPM's, HOWTO's, web sites, and LWQ, and qmail is a kind of newbie "attractive nuisance". Some of us old timers are scrambling around with files trying to soften the corners, but there's still a sharp spot or two. >>You say you need to compile your own instructions/fixes to get it to >>work. I'd be happy to work with you to incorporate any changes >>necessary into LWQ. > >- Thanks, I'll be happy to add comments that I would feel would >make LWQ - more newbie proof. > >- I'll take another shot at it in a nite or two, Until then, stay >tuned for - part deux.. I think I'll have a beer! I already know I need to improve the coverage of startup files for Slackware and *BSD. Comments and suggestions for other improvements are eagerly solicited. -Dave
Newbie install help
Hello, I have recently set up qmail on my machine. The installation wentbeautifully! When i attempted to send mail from my local network,i got this error: ``sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)''for messages to any domain not listed in /var/qmail/control/rcpthosts. So, i check the FAQ, and sure enough, there's a fix. So i setup andrun TCP-SERVER without any problems. when i go to set the rules perthe FAQ and man pages i get: unable to parse command 192.168.0.:allow,RELAYCLIENT="" error line 1 What the heck? So i go check the FAQ for more problems. It says torun INSTCHECK among other things. So i do the rest of the fixes andthen run the INSTCHECK It kicks back three errors: permissions for alias are wrongpermissions for sendmail are wronggroup for sendmail is wrong I manage to fix the permissions for sendmail and am then left withone error, the permissions for alias are wrong.I set them to 644, and nada! I set .qmail* under them to 644 (per directions) and nada! So i try every combination (yes, i really did, and it took some time) and nada! Does anyone know what i've missed or have any suggestions to what to look for to fix the alias permissions and the parse problem? Please help!!! Ryan L
Re: qmail LWQ installation problem - qmail doesn't seem executable
"Warren 'Llama' Ernst" <[EMAIL PROTECTED]> wrote: >So I'm installing qmail on my RedHat 6 distrubution a la the "Life with >qmail" document, and its going great (I've been doing a little each day all >week) until section 2.8.2 when I am suppposed to type "/usr/local/sbin/qmail >cdb" > >Well, I do this, and I get "bash: /usr/local/sbin/qmail: No such file or >directory" > >So I do an ls -l and see the qmail entry in /usr/local/sbin is the link to: >"qmail -> /etc/rc.d/init.d/qmail" and its permission is "lrwxrwxrwx" > >In checking /etc/rc.d/init.d/, i see that qmail is the executable script >"qmail" frmom the beginning of section 2.8.2, but I can't execute it here >either. It looks like: >[root@lllama init.d]# qmail >bash: qmail: command not found >[root@lllama init.d]# ./qmail >bash: ./qmail: No such file or directory OK, these are classic symptoms of a bad "magic number". The top line of the qmail script should look like: #!/bin/sh That tells the exec() system call that the file is a script, and the interpreter is /bin/sh. 1) Verify that the first line of your script is correct: head -1 /usr/local/sbin/qmail |od -c 000 # ! / b i n / s h \n 012 If you get the following: 000 # ! / b i n / s h \r \n 013 The problem is that your browser or the InfoAve web server "helpfully" converted the UNIX text file format (newline) into DOS text format (CRLF). If that's the case, you can convert it back by doing: tr -d '\012' /tmp/foo cp /tmp/foo /usr/local/sbin/qmail If you get anything else, edit the file, delete the first line, and re-enter it. Or re-download the script. 2) Verify that /bin/sh is a working shell: /bin/sh You should get no error messages, and a "$ ", "bash$ ", or similar prompt. Commands like "ls" and "ps" should work. Hit ^D to exit the shell. If this fails, you've got serious problems. 3) Try "bash /usr/local/sbin/qmail cdb". If that works, the problem is definitely in the "magic number". -Dave
Re: Newbie install help
"Ryan" <[EMAIL PROTECTED]> wrote: >So, i check the FAQ, and sure enough, there's a fix. So i setup and >run TCP-SERVER without any problems. when i go to set the rules per >the FAQ and man pages i get: > >unable to parse command 192.168.0.:allow,RELAYCLIENT="" error line 1 That's supposed to be an entry in /etc/tcp.smtp. You didn't type that on the command line, did you? >What the heck? So i go check the FAQ for more problems. It says to >run INSTCHECK among other things. So i do the rest of the fixes and >then run the INSTCHECK > >It kicks back three errors: > >permissions for alias are wrong >permissions for sendmail are wrong >group for sendmail is wrong Red herrings. -Dave
me file
Hi there. I aked this a while ago but in the wrong context. I intend to set up an ISP style smtp and pop server using qmail. I need full relaying to any host from dialup users on my network. What do I put in the me file? As I can't get the ./config script to find my dns name and As my machine runs a lot of virtual hosts(over 50) I need to know what to put in the file. I've found a nice article on relaying which I am sure will be a lot of help but it doesn't mention this file. If anyone has any thoughts let me know. Incidently the hostname of the machine is not a dns name. -- Marek Narkiewicz, Webmaster Intercreations Reply to <-marek @ intercreations . com-> "People in glass houses seldom throw parties" David Devant and his Spirit Wife Miscellaneous
Re: Newbie install help
Glad to hear that they are red herrings... no, it didn't use the command line. I followed the directions and made a file called /etc/tcp.smtp and filled it with: 192.168.0:allow,RELAYCLIENT="" 127.:allow,RELAYCLIENT="" I then went to the command line and typed in (per directions) /usr/local/bin/tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp and it promply laughs in my face with the unable to parse error!!! I'm currently looking on E-bay for a very large hammer! Ryan - Original Message - From: Dave Sill <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 21, 1999 10:44 AM Subject: Re: Newbie install help > "Ryan" <[EMAIL PROTECTED]> wrote: > > >So, i check the FAQ, and sure enough, there's a fix. So i setup and > >run TCP-SERVER without any problems. when i go to set the rules per > >the FAQ and man pages i get: > > > >unable to parse command 192.168.0.:allow,RELAYCLIENT="" error line 1 > > That's supposed to be an entry in /etc/tcp.smtp. You didn't type that > on the command line, did you? > > >What the heck? So i go check the FAQ for more problems. It says to > >run INSTCHECK among other things. So i do the rest of the fixes and > >then run the INSTCHECK > > > >It kicks back three errors: > > > >permissions for alias are wrong > >permissions for sendmail are wrong > >group for sendmail is wrong > > Red herrings. > > -Dave >
Re: me file
The me file should contain the DNS name for you mail server. On Tue, 21 Sep 1999, Marek Narkiewicz wrote: > Hi there. I aked this a while ago but in the wrong context. I intend to set up an >ISP style > smtp and pop server using qmail. I need full relaying to any host from dialup users >on my > network. What do I put in the me file? As I can't get the ./config script to find >my dns > name and As my machine runs a lot of virtual hosts(over 50) I need to know what to >put in > the file. I've found a nice article on relaying which I am sure will be a lot of >help but it > doesn't mention this file. If anyone has any thoughts let me know. > Incidently the hostname of the machine is not a dns name. > -- > Marek Narkiewicz, Webmaster Intercreations > Reply to <-marek @ intercreations . com-> > "People in glass houses seldom throw parties" > David Devant and his Spirit Wife > Miscellaneous > > - Timothy L. Mayo mailto:[EMAIL PROTECTED] Senior Systems Administrator localconnect(sm) http://www.localconnect.net/ The National Business Network Inc. http://www.nb.net/ One Monroeville Center, Suite 850 Monroeville, PA 15146 (412) 810- Phone (412) 810-8886 Fax
Logging denied relaying attempts
My apologies if this has been asked before. I searched the archives and found nothing. I read several of the relaying documents referenced from qmail.org, and successfully have a selective relay set up where you have to authenticate through POP before relaying mail to external domains. How do I log refused relay attempts (ie spammers, people who forgot to authenticate first, etc.) My log right now pretty much just logs whether a delivery was local or remote. As a quick question since I'm already here, how do you change the "relaying refused" message? I know it's in the docs somewhere, but since I'm already sending an email, I figured I ask real quick-like. ;-) Thanks, ~Patrick
Re: me file
Marek Narkiewicz wrote:
>
> Hi there. I aked this a while ago but in the wrong context. I intend to set up an
>ISP style
> smtp and pop server using qmail. I need full relaying to any host from dialup users
>on my
> network. What do I put in the me file? As I can't get the ./config script to find
>my dns
> name and As my machine runs a lot of virtual hosts(over 50) I need to know what to
>put in
> the file. I've found a nice article on relaying which I am sure will be a lot of
>help but it
> doesn't mention this file. If anyone has any thoughts let me know.
> Incidently the hostname of the machine is not a dns name.
I'm new to qmail and not entirely sure what you are asking, but as
for allowing relaying only on your network, as I understand it you
can use tcpserver to limit relaying to hosts on your network only,
or you can do what I did which is to roll your own script which
allows or denies relaying based upon IP address of the SMTP peer.
Here is the script that I use to allow relaying only for hosts
on our network (I called it /var/qmail/bin/selectiverelay.sh):
--
#! /usr/local/bin/bash
ADDR=${TCPREMOTEIP##209.116.169.}
if [ -z $ADDR ]; then
unset RELAYCLIENT
elif [ $ADDR = 127.0.0.1 ]; then
export RELAYCLIENT=""
elif [ $ADDR = $TCPREMOTEIP ]; then
unset RELAYCLIENT
elif [ $ADDR -lt 66 -o $ADDR -gt 126 ]; then
unset RELAYCLIENT
else
export RELAYCLIENT=""
fi
/var/qmail/bin/qmail-smtpd
---
My inetd.conf entry for qmail looks like this:
smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env
/var/qmail/bin/selectiverelay.sh
As you can see, you can set up any number of rules and tests to
see if relaying should be accepted for the host in question. This
gives you all the power in the world to determine who to relay for.
The script above first sets the variable ADDR to be the last octal
of the remote peer's IP address using some bash string magic. The
variable TCPREMOTEIP will have been set by tcp-env, whose job is
to set such variables. If the remote peer is not in the
209.116.169. network (which is our network) ADDR will remain
whatever it was, otherwise it will only be the last octal.
Then, if ADDR is nothing (which should never happen anyway), or
ADDR is the same as the remote peer's IP (which means that the
remote peer was not in the 209.116.169. network) the variable
RELAYCLIENT is unset. If the last octal is in the range 66 - 126
or the IP is 127.0.0.1 (which are all of the valid hosts in our
network and the localhost IP, respectively), RELAYCLIENT is set.
qmail-smtpd will ignore the rcpthosts file if RELAYCLIENT is set,
so for the hosts we have allowed RELAYCLIENT, relaying happens,
otherwise relaying only to the hosts in our network (which are
listed in our rcpthosts file) is allowed.
The only drawback I can see to a script like the above is that it
runs yet another process (a bash process) every time an email is
received. But it's working well for us so far, and it's easy
to change and to even add a "trusted" remote IP address.
You can also selectively relay using the tcpserver program, if
memory serves correctly. You may want to check into that as well,
especially if you are using tcpserver already, because the selective
relaying will then essentially be "free".
I don't know if this addresses your problem in any way, but I
posted it in hopes that if it doesn't, it might help someone
else sometime.
Any comments or suggestions (or reports of any problems with
my approach to selective relaying) are welcome.
Best wishes,
Bryan
--
Bryan Ischop l u m b d e s i g n
[EMAIL PROTECTED]http://www.plumbdesign.com
Re: Newbie install help
On Tue, Sep 21, 1999 at 10:59:40AM -0700, Ryan wrote: > 192.168.0:allow,RELAYCLIENT="" try 192.168.0. --Adam
Re: Having trouble with pop
Tim,
I think you've sent me in the right direction... (at least it's somewhere to
start)
The RPM install-setup thing I ran entered a line like this (Ive substituted
the values for all the variables it used) in a file
/etc/rc.d/init.d/qmail-pop3d.init
supervise /var/lock/qmail-pop3d \
tcpserver -v -c40 -x/etc/tcprules.d/qmail-pop3d.cdb -u'id -u root' -g'id -u
root' 0 pop-3 \
qmail-popup grow.sd27.bc.ca checkpassword qmail-pop3d Maildir \
2>&1 | setuser qmaill accustamp \
| setuser qmaill cyclog ${FILESIZE="-s 100"} ${FILENO=-n 10"}
/var/log/qmail-pop3d &
That last line was a little confusing to me, but what I wrote (the ${FILE..
stuff) above is what was on the right of the equal sign in the variable
assignments.
When I start or stop or start qmail-pop3d (qmail-pop3d.init start) I get a
single line that says 'hard error', the next line says 'starting
qmail-pop3d done' (or stopping). I noticed too that your line doesn't
seem to have the -u -g stuff (should it really be root?) Maybe if I could
figure out what 'hard error' means.
> I had a similar problem when I first setup qmail with maildir support.
> Make sure in your qmail-pop3d startup script you have Maildir (not
maildir)
> e.g.
> echo -n "Starting qmail: qmail-pop3d"
> supervise /var/supervise/qmail/pop3d \
> tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup mail.cimx.com \
> /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 2>&1
| \
> setuser qmaill cyclog /var/log/qmail/pop3d &
>
Re: How good is RBL at filtering spam?
[EMAIL PROTECTED] writes: > My guess has always been that they stay away from .gov because the > .gov is the one entity that can effectively shut them down. I think you give spammers too much credit for thinking. They spam anti-spam lists all the time. Talk about smart. --Michael
Regular expression anti-spam filtering
Here are my latest diffs to try to block spam based on regular expression filtering in headers. Enjoy. :) http://www.flame.org/qmail/flame-patches-1.03-1.6.3.diff I also added a "badrcptto" hack that will do the same thing as "badmailfrom" but on the other envelope address. This was done since I have a lot of pseudo-users which are there simply as spam traps. :) --Michael
Re: Newbie install help
"Ryan" <[EMAIL PROTECTED]> wrote: >I followed the directions and made a file >called /etc/tcp.smtp >and filled it with: > >192.168.0:allow,RELAYCLIENT="" >127.:allow,RELAYCLIENT="" > >I then went to the command line and typed in (per directions) > >/usr/local/bin/tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp > >and it promply laughs in my face with the unable to parse error!!! OK, as Adam McKenna pointed out, that should be "192.168.0.:allow...". But what you wrote here doesn't match what you wrote in your first message: >unable to parse command 192.168.0.:allow,RELAYCLIENT="" error line 1 Do you have "192.168.0" or "192.168.0."? Also, I grepped the source for "unable to parse" and the only match I found was "unable to parse this line: ". Was that an exact copy of the message? Please don't paraphrase error messages. -Dave
Re: me file
Marek Narkiewicz <[EMAIL PROTECTED]> wrote: >Hi there. I aked this a while ago but in the wrong context. I >intend to set up an ISP style smtp and pop server using qmail. I >need full relaying to any host from dialup users on my network. What >do I put in the me file? As I can't get the ./config script to find >my dns name and As my machine runs a lot of virtual hosts(over 50) I >need to know what to put in the file. control/me is the system's FQDN. If you couldn't run ./config, you should have run ./config-fast. See: http://Web.InfoAve.Net/~dsill/lwq.html#do-build For details. -Dave
Further me file and smtp
Ok Thanks for the replys re: the me file. I still have a query though. If I use my machines host name for the me file then what happens when users from other domains need to send e-mai? Does the hostname in the mefile become appended to their address? Cheers,
Re: Further me file and smtp
karen Narkiewicz <[EMAIL PROTECTED]> wrote: >Ok Thanks for the replys re: the me file. I still have a query >though. If I use my machines host name for the me file then what >happens when users from other domains need to send e-mai? Does the >hostname in the mefile become appended to their address? Cheers, The "me" file is used to supply the default value for several other configuration settings. Examine this chart: http://Web.InfoAve.Net/~dsill/lwq.html#config-files and if you don't want the non-DNS'd "me" supplied for these variables, either use a DNS'd name in "me" or set the variables explicitly. -Dave
Re: ANNOUNCE: /var/qmail/control/locals and regex
On Tue, Sep 21, 1999 at 10:13:28AM -0400, Adam D . McKenna wrote: > > And I still think this is the "territory" auf control/locals because I do > > not have a "virtual"domain, but a real one ;-) > > Don't reject a solution because you don't like the semantics. I do not reject it, I just offer another solution. Let the people decide. And the performance. (Could anybody test my patch?) Greetings -- Robert Sander "Is it Friday yet?" @Home http://home.pages.de/~gurubert pgp available there
Re: Newbie install help
Sorry, error message says: tcprules:fatal error: unable to parse 192.168.0.:allow,RELAYCLIENT="" in line 1 I have tried adding a blank line to the end...no luck. I tried changing the command to use rules.cdb rules.tmp instead of tcp.smtp as the example had. no luck! I cannot find any file named tcp.smtp.cdb or rules.cdb should there already be one? What directory should these files be in? they are currently in /etc I tried cp /etc/tcp.smtp.tmp /etc.tcp.smtp.cdb and also cp /etc/rules.tmp /etc/rules.cdb no luck eitherI must me missing something. I really appreciate all your help. My hammer should be here shortly =) Ryan - Original Message - From: Dave Sill <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 21, 1999 12:00 PM Subject: Re: Newbie install help > "Ryan" <[EMAIL PROTECTED]> wrote: > > >I followed the directions and made a file > >called /etc/tcp.smtp > >and filled it with: > > > >192.168.0:allow,RELAYCLIENT="" > >127.:allow,RELAYCLIENT="" > > > >I then went to the command line and typed in (per directions) > > > >/usr/local/bin/tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp > > > >and it promply laughs in my face with the unable to parse error!!! > > OK, as Adam McKenna pointed out, that should be > "192.168.0.:allow...". But what you wrote here doesn't match what you > wrote in your first message: > > >unable to parse command 192.168.0.:allow,RELAYCLIENT="" error line 1 > > Do you have "192.168.0" or "192.168.0."? > > Also, I grepped the source for "unable to parse" and the only match I > found was "unable to parse this line: ". Was that an exact copy of the > message? > > Please don't paraphrase error messages. > > -Dave >
SMTP problems
Hi, qmail is running on a SuSE-Linux Server 5.3 with nameserver bind8. In the local network qmail is working fine. When i send a Email to a remote address then i get in the logfile the message: "Deferral: Sorry, i wasn´t able to establish a SMTP-connection." Is this a qmail-problem or a routing problem? What can i do? Thanks for help Ulrich Butzer Email: [EMAIL PROTECTED]
Re: SMTP problems
On Tue, Sep 21, 1999 at 09:41:05PM +0100, U. Butzer wrote: } Hi, } } qmail is running on a SuSE-Linux Server 5.3 with nameserver bind8. } In the local network qmail is working fine. When i send a Email to a remote } address then i get in the logfile the message: } "Deferral: Sorry, i wasn´t able to establish a SMTP-connection." } } Is this a qmail-problem or a routing problem? What can i do? There's a simple way to find out. Try telnetting to port 25 of the remote server (telnet fqdn.of.remote 25). Some systems have a command named mconnect to do just that (mconnect fqdn.of.remote). If you get a response from the remote, it's not a routing or network problem. } } Thanks for help } } Ulrich Butzer } } Email: [EMAIL PROTECTED] } } -- Paul J. Schinder NASA Goddard Space Flight Center [EMAIL PROTECTED]
Re: SMTP problems
Can you ping the remote host? "U. Butzer" wrote: > > Hi, > > qmail is running on a SuSE-Linux Server 5.3 with nameserver bind8. > In the local network qmail is working fine. When i send a Email to a remote > address then i get in the logfile the message: > "Deferral: Sorry, i wasn´t able to establish a SMTP-connection." > > Is this a qmail-problem or a routing problem? What can i do? > > Thanks for help > > Ulrich Butzer > > Email: [EMAIL PROTECTED] -- +---+ + Thomas M. Sasala, Electrical Engineer [EMAIL PROTECTED] + + MRJ Technology Solutionshttp://www.mrj.com + + 10461 White Granite Drive, Suite 102(W)(703)277-1714 + + Oakton, VA 22124 (F)(703)277-1702 + +---+
IMAP with Qmail (encripted)
Hello Sirs, First of all I want to thank everyone that helped me every time I needed some help of this list... I want to setup an IMAP server with Qmail so that it rejects any message that doesn't use criptografy for the login and pass fields... I want to use IMAP with Qmail too, in the Maildir mode. I noticed some patches in the Home Page, it is the only way? ... Well, it is it by now. Regards... Pirolla
Re: Virtual email for non virtual host
> But now I don't want to have to >create an "info" user just so I can have an "info" email for the server. >The "info" mail isn't for a virtual domain, it's for THE domain on my >server. >I've tried adding domain.com:info in the virtual domain file but that >didn't work. What do I need to do? Thanks for any help. Ever tried a ~alias/.qmail-info File with forwarding to the existent User on your Domain or an user on one of your virtual domains? Or using qmail/user/assign if you don't want to set up more fieles ind the ~alias directory? And have you set domain.com in you local and rcpthosts file? Ciao, Cyril
Re: Qmail and HP Openmail
On Mon, 20 Sep 1999 17:51:43 +0200 "Stephan Hadan (E-Mail)" wrote: > is there anybody who has Qmail working together with HP Openmail 6.0 for > Linux ? Please tell me if it works and how it works. qmai interacts with Openmail just like it does with any other SMTP mail transport: it speaks SMTP. For what it is worth I've not heard of any problems, nor experienced any. I have not bothered to chase down which of the Openmail hosts I send mail to are using Linux and which are using HP-UX. Regards, Giles
Recording the envelope-from in Received: line
With sendmail and Postfix (or so I've heard) it is possible to record the envelope-from address in the Received: line. This is deemed useful by my colleagues for tracing mails trough broken e-mail gateways. For example, consider the following line: Received: from dfw7-1.relay.mail.uu.net (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id XAA04842 for <[EMAIL PROTECTED]>; Tue, 21 Sep 1999 23:09:42 +0200 (MEST) (envelope-from [EMAIL PROTECTED]) Note the envelope-from comment. Is there any way to achieve the same effect with qmail? [Side note: I'm asking because we are currently reevaluating our use of sendmail. Postfix is a strong contender; Wietse Venema is a personal friend of a couple of my colleagues.] Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer;
isocor the fastest?
Currently, we are successfully using qmail 1.03 in a production environment. I recently came across a press release from Isocor stating: "ISOCOR's Internet messaging product has the capability to deliver more than 800 messages per second, making it the fastest Internet messaging server in the world. As it is also extremely hardware efficient, ISPs would need to spend up to 50 percent more on hardware resources to achieve the same performance from alternative messaging software" I know that qmail is really fast. Does anyone know/guess what makes Isocor's products "the fastest Internet messaging server in the world" while remaining "extremely hardware efficient"? Any idea of their messaging server's structure? Anything we can learn for future versions of qmail? --vt
Re: Problems with qpop and Solaris
[EMAIL PROTECTED] writes: > Now if you look where it is stat'ing the files in new and cur, you will > see that they have actually been truncated, as the 93 has been chopped > off the filename. This is one of many serious bugs in the Solaris ucb libraries. Do not use /usr/ucb/cc. One way to prevent mistakes is to move /usr/ucbinclude to /usr/ucbinclude-broken. ---Dan
Re: qmail-start (qmail 1.03) under RedHat 6.0
I am sorry for late reply, but pop3 server I use was down. I am not sure what "the
html man pages for daemontools 0.61"
you are referring to. The only documentation on daemontools 0.61 I could find is the
web page for these tools. I based
my script on LWQ, which does not use svscan. Should I modify my scripts to use svscan
( as soon as I get this one working
I plan to use supervise to run qmail-pop3d and qmail-smtpd ). I include all the files
this time (I did not want to send
them since I did not get a chance to clean them up).
* qmail ***
the generic script which is called from another one
#!/bin/sh
#chkconfig: 345 70 30
#description: qmail-send deamon
action=$1
service="qmail/mail"
description="qmail-send"
. /etc/rc.d/init.d/qmail-all
exit 0
qmail-all *
the generic script which is called from another one
#!/bin/sh
#
. /etc/rc.d/init.d/functions
is_running()
{
tries=0
while [ $tries -lt 10 ]
do
sleep 1
if svok $SUPERVISE_DIR$service
then
return 0
fi
tries=`expr $tries + 1`
done
return 1
}
is_stopped()
{
tries=0
while [ $tries -lt 10 ]
do
sleep 1
if ! svok $SUPERVISE_DIR$service
then
return 0
fi
tries=`expr $tries + 1`
done
return 1
}
script="qmail"
PATH=/var/qmail/bin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
export PATH
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
SUPERVISE_DIR="/var/supervise/"
if ! [ -d $SUPERVISE_DIR$service ]
then
echo
echo "$script: $SUPERVISE_DIR$service is not a directory" >&2
exit 2
fi
case "$action" in
start)
echo -n "starting $description: "
if ! [ -f $SUPERVISE_DIR$service/run ]
then
echo
echo "$script: file $SUPERVISE_DIR$service/run does not exist" >&2
exit 3
fi
if ! [ -x $SUPERVISE_DIR$service/run ]
then
echo
echo "$script: file $SUPERVISE_DIR$service/run is not executable" >&2
exit 4
fi
if svok $SUPERVISE_DIR$service
then
echo
echo -n "$script: $description already running"
echo_failure
echo
exit 5
fi
#Make sure we don't have any down files
#that will prevent us from starting this service
rm -f $SUPERVISE_DIR$service/down
#logging will be started in the run file
supervise $SUPERVISE_DIR$service &
#wait for a while, until it starts or doesn't.
if is_running
then
echo_success
echo
exit 0
else
echo_failure
echo
exit 5
fi
;;
stop)
echo -n "stopping service $description: "
if ! svok $SUPERVISE_DIR$service
then
echo
echo -n "$script: $description is not running"
echo_failure
echo
exit 5
fi
svc -dx $SUPERVISE_DIR$service
#wait until it stops or timesout
if is_stopped
then
echo_success
echo
exit 0
else
echo_failure
echo
exit 5
fi
;;
status)
echo "checking status of $description service: "
svstat $SUPERVISE_DIR$service
;;
restart)
echo "restarting service $description: "
qmail stop $2 $3
qmail start $2 $3
;;
reload)
echo "reloading (-HUP) service $description: "
svc -h $SUPERVISE_DIR$service
;;
pause)
echo "pausing service $description: "
svc -p $SUPERVISE_DIR$service
;;
cont)
echo "resuming service $description: "
svc -c $SUPERVISE_DIR$service
;;
help)
cat <&2
echo "Usage: $script {start|stop|restart|reload|stat|pause|cont|help}"
exit 99
esac
exit 0
"Russell P. Sutherland" wrote:
> * Vladimir Berezniker ([EMAIL PROTECTED]) [20 Sep 1999 21:59]:
>
> > Hi,
> > First of all I am a newbie to the *nix. I use supervise from deamon tools
>0.61. To run the following run file:
> > *
>
> Go back and read the html man pages for daemontools 0.61 again.
> In order to get logging and control to work one
> has to put the script for the logging portion (the stuff after
> the pipeline (|) symbol) in the log subdirectory
> of the directory that contains the run script for the
> qmail-start command and then use svscan to connect
> the two:
>
> For example:
>
> /services/qmail/run <-- contains the commands to start qmail
> /services/qmail/log/run <-- contains multilog et. al.
>
> with svscan being started (in the background) from the /services
> directory.
>
> --
> Quist ConsultingEmail: [EMAIL PROTECTED]
> 219 Donlea DriveVoice: +1.416.696.7600
> Toronto ON M4G 2N1 Fax: +1.416.978.6620
> CANADA WWW: http://www.quist.on.ca
tcpserver error
I can't find this in the archive so here goes. Sending mail to my machine which has processes running under tcpserver returns this error: tcpserver: warning: dropping connection, unable to run /var/qmail/bin/qmail-smtpd: file does not exist All on one line. tcpserver is invoked with this call as an alias in my rc file: alias qsmtp='/usr/local/bin/tcpserver -R -x/etc/tcp.smtp.cdb -c100 -u504 -g504 0 smtp \ /var/qmail/bin/qmail-smtpd &' Also all on one line. I have checked the directory path and the filename and they match exactly. The tcpserver process is running as qmaild and the dirs have the correct ownership. What can be going wrong? -- Marek Narkiewicz, Webmaster Intercreations Reply to <-marek @ intercreations . com-> "People in glass houses seldom throw parties" David Devant and his Spirit Wife Miscellaneous
Qmail with LDAP Auth
OK. I posted my earlier problems to this list, and was told in a nice friendly manner that there was a Qmail-LDAP mailing list to send to. So I subscribed, and posted all my current findings to it. I got all my messages back, but not a single soul has responded (nor even posted queries of their own), so I'm forced to bring my problem back here, hoping that a qmail guru somewhere will have some idea of what to change. I have applied the Qmail-LDAP patch to the vanilla qmail source code. My LDAP server is up and running. When I compile the new checkpassword with debugging turned on, it appears to get the username and password from the command line, and when I provide them, it connects to the server, checks my password, and returns my home directory perfectly. When I turn debugging off, and it tries to get the USER and PASS from qmail-popup, it appears to stop working. I modified the checkpassword code to display debugging output without expecting the username and password on the command line (basically just a quick commenting out of the #ifdef section that grabs the parameters from argv[]) and when I run qmail-popup localhost checkpassword it complains that no username is being provided. Surely the patched checkpassword couldn't be so broken, or noone else would be able to use it (??!?) Basically, how does qmail-popup present the username and password to the checkpassword program, and how should checkpassword get these arguments? I'd love to sit down and go through the qmail code enough to figure it out, but I'm leaving this job at the end of the year, and I need to get the system working in such a way that it can be easily administered by someone with no knowledge of qmail or linux (some might say the same way I've done so far! =) ). Anyway, any help or pointers in the right direction would be greatly appreciated...
Maildir setup problem (newbie!)
I'm just setting up qmail on a server and am not able to successfully deliver anything to users! I'm attempting to use the Maildir mailbox. I have user/Maildir (permissions 775) and user/.qmail (permissions 664). I have changed /var/qmail/rc to indicate "./Maildir/" instead of "./Mailbox" . The file .qmail contains "./Maildir". I have run qmail-pw2u and qmail-newu and the cdb file gets set up appropriately. Doing a "ps -Af|grep qm*" indicates "qmail-lspawn ./Maildir/" is running. I tested the configuration by doing an "echo to: mls |/var/qmail/bin/qmail-inject". However, looking at the log file in /var/log/qmail indicates a delivery problem - typically-- 937942327.372385 delivery 22: deferral: Temporary_error_on_maildir_delivery._(#4.3.0)/ 937942327.372463 status: local 0/10 remote 0/20 937942631.370107 starting delivery 23: msg 475224 to local [EMAIL PROTECTED] 937942631.370180 status: local 1/10 remote 0/20 937942631.382713 delivery 23: deferral: Temporary_error_on_maildir_delivery._(#4.3.0)/ 937942631.382792 status: local 0/10 remote 0/20 937942691.380091 starting delivery 24: msg 475226 to local [EMAIL PROTECTED] 937942691.380163 status: local 1/10 remote 0/20 937942691.392589 delivery 24: deferral: Temporary_error_on_maildir_delivery._(#4.3.0)/ 937942691.392672 status: local 0/10 remote 0/20 --- sam2.ggg.com is the local machine I'm testing on and mls is the correct user account that has Maildir and .qmail set up. Similarly, attempting to test by telneting to sam2.ggg.com port 25 and sending a message to [EMAIL PROTECTED] seems to generate a similar set of log entries. Any suggestions as to what I've likely done wrong and/or should check out? Similarly, attempting to test by telneting to sam2.ggg.com port 25 and sending a message to [EMAIL PROTECTED] seems to generate a similar set of log entries. In addition to the list, please reply directly to [EMAIL PROTECTED] Thanks Michael Slade
Re: ETRN
On Tue, Sep 21, 1999 at 12:15:03PM +0200, Dimitri SZAJMAN wrote: > that with commands like 'tr', 'cut', 'sed' and so on. But I am looking for > the real ETRN as described in the RFC. Not without names that resolve. You say ETRN myhostname, but the server thinks you want to spool waiting mail for myhostname. It looks up myhostname's IP, and starts delivering. If you have a dynamic IP, that won't work because there's no way to let the mailserver's DNS know your IP without the usual hours to days delay of DNS updates. ETRN is for fixed IP's. -- Ruben -- Eat more memory!
Re: Qmail dies over and over
Gustavo V G C Rios writes: > syscall read(0x2,0x8054090,0x800) > returns 0 (0x0) > 937023957.591990 alert: oh no! lost spawn connection! dying... Evidently qmail-lspawn is exiting. Trace it to find out why. Note that a URL for a complete trace is more useful than an abbreviated trace. ---Dan
Re: isocor the fastest?
On Tue, Sep 21, 1999 at 05:32:20PM -0400, Victor Tavares wrote: > Anything we can learn for future versions of qmail? Yup. Start saving for multiple 655Mbit lines and a couple of 1 GHZ Athlon's. Apart from that, there's nothing special about being the fastest. Being fastest *on a given hardware-platform* is the challenge, and qmail does a fine job. And being secure is a nice feature too. -- Ruben -- Eat more memory!
Re: POP3: premature NOOP OK, NOT an RFC 1939 Compliant server
Olivier M. writes: > Is qpop3d really "NOT an RFC 1939 > Compliant server", or is the php program buggy ? The phpop program is buggy. It is sending NOOP in the A state. RFC 1939 prohibits sending NOOP except in the T state. ---Dan
RE: Qmail with LDAP Auth
RGH! Ok, my mistake... I missed a bit of code that needed commenting, and I can now get debugging info. It is definitely checking the LDAP server correctly, and it acknowledges that it can set its UID and GID to mine, change to my $HOME/Mailbox directory correctly, so now it appears that qmail-pop3d is the problem, claiming that "this user has no $HOME/Maildir". I'm really going nuts over this, but I'll have to follow the pop3d code for a while now... Sorry all, and thanks again to Jeffrey Skelton for his help.
Re: Return Receipts
Russell Nelson writes: > What's wrong with having a program which acts on Netscape's > "Disposition-Notification-To: RFC822-address" ? Same problem as Return-Receipt-To. If everybody on a mailing list is using that program, the address is flooded with mail. ---Dan
Qmail book
Is there a qmail book? Kevin
Re: How good is RBL at filtering spam?
On Tue, 21 Sep 1999, Dave Sill wrote: > [EMAIL PROTECTED] wrote: > > >(My pobox.com address, on the other hand, gets plenty of spam, because > >pobox's antispam methods are very poor. I only wish they used DUL, > >which would get rid of most of the spam from that direction.) > > It's not good enough for an antispam method to simply be effective, it > should also be selective. The DUL blocks non-relaying, nonspammers, > just because it doesn't like the looks of their domain name...the I thought it blocked known IP blocks of dialup ports? > baby/bathwater scenario. But the War on Spam, like the War on Drugs > and the War on Terrorism cares little about collateral damage like > me. I cannot imagine what damage is done by asking a dialup user to send email out through his provider's internal relay.
RE: Qmail with LDAP Auth patches
> > A small sample from the ldif file before I ldbm it: > > > > dn: cn=John Smith > > cn: John Smith > > sn: Smith > > objectClass: qmailUser > > objectClass: person > > mail: [EMAIL PROTECTED] > > mailHost: mail.budget.co.nz > > mailMessageStore: /home/jsmith/Mailbox/ > > qmailUser: jsmith > > qmailUID: 666 > > qmailGID: 666 > > uid: jsmith > > userPassword: xxx After hours and hours of messing around with source code and inserting all sorts of debugging info that was never meant to be, I've found the problem, and there's a small problem with the Qmail-LDAP documentation on the web page. In the example LDIF file, is says that mailMessageStore should be /usr/home/opi/maildir/. In my case, this appears to be wrong, as qmail-pop3d attempts to chdir to the maildir provided on the command line, which it is already in, courtesy of checkpassword. I fixed the problem completely by undoing all my changes and changing every occurrence of mailMessageStore to exclude the Mailbox portion. I'm a little disappointed that noone on the qmail-ldap list was even able to reply to my query, much less help with this obviously minor screwup... but perhaps someone can benefit from my frustration.
Re: Qmail book
On Wed, 22 Sep 1999, Kevin Waterson wrote: > Is there a qmail book? There answer is on http://www.qmail.org, along with answers to tons of other questions about qmail. jms
Re: Sqwebmail and IMAP
Say you have a bunch of mboxes. You choose filenames for them. Of course, some filenames are prohibited: * You can't use the name .., because that's a directory. * You can't use the name /Mail, because you don't have permission. * You can't use the name Mailbox/2, because Mailbox is a file. But the complete list of restrictions is reasonably simple, and people don't seem to have much trouble dealing with a few special characters. Now change each mbox to a maildir. Whatever filenames worked with mbox will continue to work with maildir. You now have a bunch of maildirs. What exactly is the problem? ---Dan
Re: Sqwebmail and IMAP
Sam writes: > A filename named "cur" will not work. Of course it will. There's nothing wrong with a mailbox named cur. As I said, whatever filenames worked with mbox format will continue to work with maildir format. So what exactly is the problem? ---Dan
Re: Sqwebmail and IMAP
D. J. Bernstein writes: > Say you have a bunch of mboxes. You choose filenames for them. Of > course, some filenames are prohibited: > >* You can't use the name .., because that's a directory. >* You can't use the name /Mail, because you don't have permission. >* You can't use the name Mailbox/2, because Mailbox is a file. > > But the complete list of restrictions is reasonably simple, and people > don't seem to have much trouble dealing with a few special characters. > > Now change each mbox to a maildir. Whatever filenames worked with mbox > will continue to work with maildir. You now have a bunch of maildirs. > What exactly is the problem? A filename named "cur" will not work. -- Sam
Re: Sqwebmail and IMAP
D. J. Bernstein writes: > Sam writes: > > A filename named "cur" will not work. > > Of course it will. There's nothing wrong with a mailbox named cur. As I > said, whatever filenames worked with mbox format will continue to work > with maildir format. So what exactly is the problem? Creating a maildir folder explicitly named "cur" will not work, for the obvious reason that the cur is already being used to store messages in the INBOX. -- Sam
Re: Sqwebmail and IMAP
I think Dan is assuming that additional mail folders won't be in the INBOX maildir (even though that was the question that was originally asked), but rather that you stick maildir mail folders in the same places you'd stick mailbox-format maildirs. I.e., not in the incoming maildir. Jim Lippard [EMAIL PROTECTED] http://www.discord.org/ Unsolicited bulk email charge: $500/message. Don't send me any. PGP Fingerprint: 0C1F FE18 D311 1792 5EA8 43C8 7AD2 B485 DE75 841C On Wed, 22 Sep 1999, Sam wrote: > D. J. Bernstein writes: > > > Sam writes: > > > A filename named "cur" will not work. > > > > Of course it will. There's nothing wrong with a mailbox named cur. As I > > said, whatever filenames worked with mbox format will continue to work > > with maildir format. So what exactly is the problem? > > Creating a maildir folder explicitly named "cur" will not work, for the > obvious reason that the cur is already being used to store messages in the > INBOX. > > -- > Sam > >
Re: Sqwebmail and IMAP
James J. Lippard writes: > I think Dan is assuming that additional mail folders won't be in the INBOX > maildir (even though that was the question that was originally asked), but > rather that you stick maildir mail folders in the same places you'd stick > mailbox-format maildirs. I.e., not in the incoming maildir. Then what you will have to ask yourself is whether you want all your folders shared by every one of your incoming maildirs. I could consider the proposal of storing all folders in ../Mail, however what I don't like about this approach is that you're now in conflict with your mail apps who use $HOME/Mail to store traditional mailbox-file folders. Additionally, the approach of storing folders in the INBOX maildir allows the implementation of a voluntary quota, which I've done, and I know that people are using it, so I'm not going to abandon that. -- Sam
Re: Sqwebmail and IMAP
adam@spotted:~$ ls -l Mail drwx-- 5 adam adam 1024 Aug 18 01:37 billing drwx-- 5 adam adam 1024 Jul 2 11:59 bugtraq drwx-- 5 adam adam 1024 Jul 2 01:43 default drwx-- 5 adam adam 1024 Jul 2 02:28 idt drwx-- 5 adam adam 1024 Jul 2 01:36 inbox drwx-- 5 adam adam 1024 Jul 2 02:27 inet drwx-- 5 adam adam 1024 Jul 2 01:43 mailer-daemon drwx-- 5 adam adam 1024 Jul 2 01:41 nanog drwx-- 5 adam adam 1024 Jul 8 10:52 nic drwx-- 5 adam adam 1024 Jul 2 01:46 old drwx-- 5 adam adam 1024 Jul 2 01:35 qmail drwx-- 5 adam adam 1024 Jul 29 21:26 raid drwx-- 5 adam adam 1024 Jul 2 01:43 root drwx-- 5 adam adam 1024 Jul 2 01:42 smp drwx-- 5 adam adam 1024 Aug 13 20:13 themes.org drwx-- 5 adam adam 1024 Jul 2 16:05 tx drwx-- 5 adam adam 1024 Aug 18 01:33 virtual This is the way my folders are organized. This makes sense to me. Everything that's not caught by a specific .qmail file or procmail rule is sent to ~/Mail/inbox/ > Then what you will have to ask yourself is whether you want all your > folders shared by every one of your incoming maildirs. I could consider > the proposal of storing all folders in ../Mail, however what I don't like > about this approach is that you're now in conflict with your mail apps who > use $HOME/Mail to store traditional mailbox-file folders. If we're really that concerned about this, we could decide upon a new, "standard" directory (such as Maildirs/ or Mailboxes/ etc). In any case, mutt has no problem with my method of keeping my mail folders, and as far as I know, most mailers allow you to specify this as a variable or config option. > Additionally, the approach of storing folders in the INBOX maildir allows > the implementation of a voluntary quota, which I've done, and I know that > people are using it, so I'm not going to abandon that. Fixing this up only involves the addition of a single directory inside ~/Mail. --Adam
Qmail sending multiple messages...is there a fix?
I am new to this list and probably asking what has been covered, but please indulge me. I checked the archives, faq, and google.com, but didn't find an answer. We have qmail (latest version) running and it is sending out multiple messages when we use the mail command in php3. sendmail wasn't doing this before we converted. Has anyone else seen this? Is there a fix? Thanks, --- Scott A. Cole Senior Vice President, Engineering & CTO OneSight, Inc. http://onesight.com OneSight - "Connecting Companies with Consumers" ---
Re: Sqwebmail and IMAP
On Wed, Sep 22, 1999 at 03:31:42AM -, D. J. Bernstein wrote: > Say you have a bunch of mboxes. You choose filenames for them. Of > course, some filenames are prohibited: > >* You can't use the name .., because that's a directory. >* You can't use the name /Mail, because you don't have permission. >* You can't use the name Mailbox/2, because Mailbox is a file. > > But the complete list of restrictions is reasonably simple, and people > don't seem to have much trouble dealing with a few special characters. > > Now change each mbox to a maildir. Whatever filenames worked with mbox > will continue to work with maildir. You now have a bunch of maildirs. With Maildir, the third restriction is no longer true - Maildir isn't a file, it's a directory. > What exactly is the problem? 1. Multiple folders, which I feel you handle by implication quite nicely: Multiple mailboxes translates to multiple Maildirs. (a) But some MUAs (sqwebmail) won't see such multiple maildirs as multiple folders. They'd rather create Maildir/.foo, for instance, as another folder 'foo' in the UA. This '.foo' is a Maildir in and of itself. 2. Subfolders: Mailboxes can't do sub-folders within themselves. But Maildir's structure is capable of that because it's a dir. The Maildir spec is unclear whether the other files shown as allowed in a maildir is all that's allowed or whether they are 'examples-without-limitation'. We know that clueful extensions won't break Maildir's purpose. But random extensions may (will!) produce a fractured non-standard. Statement of problem: nobody has a standard, a spec, or even recommendations from which to implement subfolders to Maildirs. It seems clear to me that with #1 solved with multiple Maildirs in user's home directory, that the application demonstrated in 1(a) could be applied effectively to the #2 problem: Maildir/.foo is subfolder 'foo' in Maildir. But that's less clear to others. An alternative view is that cluttering ~ with Maildir-foo and Maildir-bar, etc., is undesireable - hence the 1(a) solution to problem 1 (but what of subfolders? I'm unclear on that). Other views manufacture creative solutions, making compatibility more difficult, not easier. Will you recommend a specific approach that UA's should use for implementing folders and subfolders with Maildirs? Perhaps as part of the Maildir spec? That would help switch the debate from "what do we do since Maildir's spec doesn't specify?" to "do we resist or do we go along with the author's recommendation?" Thanks for your responses. Randy
vmailmgr / ~alias
Hi there, as in the RFCs, every maildomain should have a postmaster, right? So, i set up one user "postmaster" for each virtual domain. So, the FAQ/Howto says, that i should create a ~alias/.qmail-default, .qmail-root with "postmaster@" in it. Will mail then be delivered to postmaster@CURRENTDOMAIN or to postmaster@LOCALHOST ? Thanks, Thomas
