Re: qmail + Courrier-IMAP vs just Courrier-IMAP server (newbie)
#include imho.h On Tue, Aug 14 2001, Jean-Christian Imbeault [EMAIL PROTECTED] wrote: My original plan was to install qmail - VMailMgr - Courrier-IMAP. But after a little reading I find out that Courrier-IMAP has it own email server implementation. So it seems that qmail is not needed? Yeah, it seams so. Am I right? If so what are the advantages/disadvantages to either using qmail with the Courrier-IMAP engine or just using Courrier as the mail and IMAP server? No, you're wrong. There're some nifty features like userauth and tlsauth in courier, but just look into the source code. I don't say that's a mess but there're some design flaws in that what are missing from qmail. ---jul
Re: qmail + Courrier-IMAP vs just Courrier-IMAP server (newbie)
-BEGIN PGP SIGNED MESSAGE- Hello Jean-Christian, Tuesday, August 14, 2001, 5:13:34 AM, you wrote: My original plan was to install qmail - VMailMgr - Courrier-IMAP. But after a little reading I find out that Courrier-IMAP has it own email server implementation. So it seems that qmail is not needed? Am I right? If so what are the advantages/disadvantages to either using qmail with the Courrier-IMAP engine or just using Courrier as the mail and IMAP server? AFAIK, Mr. Sam doesn't consider courier-mta as being production quality and I know of nobody that actually uses it. But if you want to use qmail and courier-imap in a virtual domain environment, I suggest you take a look at http://inter7.com/vpopmail as courier-imap got direct integration of vpopmail. Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.5i iQEVAwUBO3kHDMZa2WpymlDxAQHuYQf9F3NM69LzTG9hNimFk2B72FaTf047jzVy PH+C7+MuGvU+2CnI9jiavsIm9w6ChC+Eeq0VNps4UvYIwU1PJ09yP16Dtjh7xzXH c/EIHEAmGMV3+g40JkXGQdOIwSIfj2lg2HFCtEM4g2nuVL5tUiJuPXBPajEtfXYs rloUUurepslsIUyKhoIBmmpx28FNOtRhKnnF/pW8yI7pESdHwumi3gxZ5Hflk8oT NDrmDvsShrMC5Kvg8b/hdw6vktAlqdnor/vjoFtHx2EkESVRLPoQI6mjKv3VtmMK IJk/QwqbgVphrMGSb2At4i9L0QE7N5PWCjwlRYqHXu7AL1KsOrOozA== =TnrE -END PGP SIGNATURE-
Re: QMAIL-SMTPD and INETD
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: QMAIL-SMPTD doesnt work with INETD. I installed it as the INSTALL filedasaid to, but to no avail. I rebooted the box and Qmail-SMTPD didnt start.dadaAny help would be appreciated.dadaThis is the most current verision and is installed into the defaultdadirectories.dadaThanks!daAndy You didn't post what you did, so nobody can help you. However, as you've noted, use of inetd/xinetd with qmail is deprecated. It's much simpler to set up with tcpserver (from ucspi-tcp). See djb's documentation on his website at cr.yp.to, or do a Life with qmail installation (see http://lifewithqmail.org). Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmail Without Inetd
suryadi writes: Can Qmail Works without inetd (in FreeBSD 3.5) and without others (such as tcpserver, etc) ? CMIIW. No, qmail (spesifically qmail-smtpd) needs a 'server' (tcpserver, (x)inetd, etc) to listen to SMTP connection. Regards, Ahmad Ridha
Re: qmail, avoid spam mail
On Mon, 13 Aug 2001 14:28:53 +0800, KY Lui [EMAIL PROTECTED] said: Hello recently, i found that someone using my qmail server to send mail. how can i avoid this? 1. Include logs in your mail 2. Tell us how they used your qmail server to send mail 3. Reinstall using www.lifewithqmail.org -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Re: Qmail, tcpserver, environment variables, and qmail-smtpd
Bill Arlofski [EMAIL PROTECTED] wrote: I am trying to understand the purpose of being able to set environment variables like $TCPREMOTEHOST with tcpserver for incoming connections (ie: using the -h option or -p 'paranoid' option to perform reverse DNS lookups) and set or unset the $TCPREMOTEHOST variable based on DNS information. when qmail-smtpd does not seem to care, or make any use of it. Is a shell script to be called in place of qmail-smtpd to check environment variables, then pass control back onto qmail-smtpd? Yes. Write a small wrapper that checks either for the presence of the appropriate environment variable, or checks that the given variable is non-empty, and either execs the rest of its commandline (if the variable meets your criteria) or exits otherwise. Then insert this wrapper in the tcpserver commandline before qmail-smtpd. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmail deferred messages..
Leonardo [EMAIL PROTECTED] wrote: I need to change the time of deferred messages in qmail. My server is = very busy and I need retry to send every 15 minutes the messages. How and where I can change in the source code to make this? Don't. qmail doesn't try every 10 minutes or every five minutes. It retries with a quadratic backoff algorithm, less frequently as the message ages. What problem are you trying to solve? Perhaps your hardware is under-spec'ed for the amount of mail you're trying to handle. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmail-Scanner
On 14 Aug 2001 02:47:18 +0200, Craig Spiers [EMAIL PROTECTED] wrote: is there any way to make qmail-scanner leave an email it has been scanned allready? You do not want to do this, because between two runs of the qmail-scanner is one .qmail file, where it is very simple to add a virus... Greetings -- Robert Sander Computer Scientist Epigenomics AG Bioinformatics RDwww.epigenomics.com Kastanienallee 24 +493024345330 10435 Berlin
Re: qmail-lspawn patch for hosting multiple local domains
On Fri, Aug 10, 2001 at 08:26:43PM +, MarkD wrote:
argument, the name of the local user to verify. This patch makes
qmail-lspawn call qmail-getpw with two arguments; the name and the domain
of the local user to verify. This, together with a modified qmail-getpw,
will enable qmail to differentiate between the local domains that the
server is hosting.
I have never checked, but I wonder whether the qmail-ldap guys have
had to do the same thing?
No. You need to forget aboy some qmail stuff when using qmail-ldap. We just
have user accounts and assigned mail addresses. VEry straightforward. A
simple (simplyfied) user entry looks like
dn: cn=brahe, ou=intern, dc=bsws, dc=de
cn: brahe
userPassword: {crypt}censored
uid: brahe
mail: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
and so on.
Basically, in qmail-lspawn a search using the filter
(|(mail=address)(mailalternateaddress=address))
is done, where address is the full rcpt address.
For auth'ing the uid and userPassword attributes count. There is no need in
qmail-ldap to distinguisch between local part and domain part in an address,
and there is no relation between email addresses and uids except that they
belong to an user account.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg, Germany *
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
Re: qmail anti-virii
Averroes [EMAIL PROTECTED] wrote: I am new in qmail and want to migrate qmail with security purposes but I want to know how to deal with virus, worms, etc. It is possible to configure qmail with some tools which check the contents of mail, attached docs, etc. All my server are Linux powered and all clients are Win2k. This is why of my mail. I encourage you to take a look at the AMaViS project at http://www.amavis.org. Totally qmail compatible. Best Regards, -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Eduardo Augusto Alvarenga - Analista de Suporte - #179653 Blumenau - Santa Catarina. Tel. (47) 9102-3303 http://www.netron.com.br/~eduardo -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: qmail anti-virii
You can also try this script; http://www.ornl.gov/its/archives/mailing-lists/qmail/2001/03/msg01041.html don't forget to use the -i flag on all grep commands so that you won't miss the upper case characters. cheers Eduardo Augusto Alvarenga wrote: Averroes [EMAIL PROTECTED] wrote: I am new in qmail and want to migrate qmail with security purposes but I want to know how to deal with virus, worms, etc. It is possible to configure qmail with some tools which check the contents of mail, attached docs, etc. All my server are Linux powered and all clients are Win2k. This is why of my mail. I encourage you to take a look at the AMaViS project at http://www.amavis.org. Totally qmail compatible. Best Regards, -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Eduardo Augusto Alvarenga - Analista de Suporte - #179653 Blumenau - Santa Catarina. Tel. (47) 9102-3303 http://www.netron.com.br/~eduardo -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- Noel G. Mistula Network Systems Administrator Meriton Apartments Pty Ltd
Re: qmail anti-virii
I am working through a few last minor issues, but Kaspersky Antivirus for Linux servers has a nice qmail integration piece. http://www.kaspersky.com (You'll want at least the August 1st 3.5 build 136 version - mime problems with earlier versions) Basically, you start the antivirus daemon, rename the original qmail-queue file, drop Kaspersky's qmail-queue in it's place. qmail-smtpd passes inbound mail to the Kaspersky qmail-queue which performs the scan via the running daemon process, then passes off virus-free email to the original qmail-queue program. Logging is to syslog, or a file, or both. You have options of emailing the offending users that they have sent infected email (most of these I am finding are getting bounced for all the obvious reasons). You can also send an administrative mail to your network admins to keep you up to date on incoming (or outgoing) email virus activity. I am pretty happy with it. I'd be glad to comment more, show configs, or help in any way.. I just don't want to clog up the list on my first day here. grin Averroes wrote: Hi There, I am new in qmail and want to migrate qmail with security purposes but I want to know how to deal with virus, worms, etc. It is possible to configure qmail with some tools which check the contents of mail, attached docs, etc. All my server are Linux powered and all clients are Win2k. This is why of my mail. Docs, Tutorials, etc. will be helpful. In advance Thanks! #-- # Averroes A. Aysha http://www.keyserver.net/en/ # Think Linux, Think Slackware! # Network Security Auditor (NSA) # [EMAIL PROTECTED] # Fingerprint = 73B7 2559 2968 5094 3B95 5C70 4E85 5F94 6068 1DD8 #--
Re: qmail-pop3d
On Mon, Aug 13, 2001 at 11:42:25AM -0400, qmail wrote: After I test the qmail-smtpd and qmail-send is ok,it seems to me ok. I try to install qmail-pop3d and start this service. I add the run script in /var/qmail/supervise/qmail-pop3d I use the method to test the checkpasswd program, the response is ok. #!/bin/sh exec /usr/local/bin/softlimit -m 200 /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup sbs01.helka.com.hk /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 but I find a process: root 8461 0.0 0.0 00 ?Z11:17 0:00 [supervise defunction is it ok? I can't check the pop3 with email client. anything that I should install after enable qmail-pop3d? I have two questions for you: 1. What is the output of 'svstat /service/*' ? 2. Is it just linewrap issues, or is 'run' really multilined without escape characters like that? -- Greg White
Re: qmail on AFS
Got a solution for this; thanks for all your help. The problem was qmail was unable to deliver mail if the Maildir is stored on AFS. Andrea mentioned that AFS is very similar to CODA, and the CODA solution is to use rename() as I was planning on doing. Peter had cautioned that rename will overwrite existing files whereas hard links will not lose any existing files. Archived discussion threads indicate that renaming is still relatively safe because the email file name is composed of the current date/time, PID and host name and it is unlikely that the PID would recycle within 1 second. The extended explanation of the problem is that AFS implements its own ACL, so that even the Unix root user may have no access to a users ~home directory; the holds true also that a user who has managed to log in to the Linux/Unix box may have no access to his own ~home directory. Access to AFS files are granted by tokens issued by the AFS/Kerberos authentication server. So during mail delivery, qmail-lspawn will setuid to become the email receipient, except that in most cases, this user will not have a valid token. So before we can even come to the problem of link() versus rename(), qmail is stymied by a lack to access to the Maildir. My solution of choice is to make qmail-local.c setuid to a mail delivery user (I picked qmaill) and make the qmail-local binary be setuid and owned by qmaill. The Maildir/tmp directory will grant allow lookup, insert, and delete privileges to qmaill, and Maildir/new will grant lookup, and insert to qmaill. The lack of a delete privilege on Maildir/new means that if a rename() is going to overwrite an existing file, AFS fails this operation because it implies a delete of the existing file, which privilege has not been granted to qmaill. (This scenario was tested by me by making qmail-local.c always generate the same email file name; on the first delivery it succeeds; on subsequent deliveries qmail defers the delivery as long as a file of the same name exists in Maildir/new.) In conjunction with all of the above, I will need a cron job to periodically refresh qmaill's AFS/Kerberos token so that qmaill will always have a valid token in order to make use of the ACL privileges that have been given to qmaill. The unified diff of my patch to qmail-local.c appears below for whatever you want to do with it. -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 123 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160 --- qmail-local.c.orig Wed Aug 8 14:34:18 2001 +++ qmail-local.c Thu Aug 9 01:05:42 2001 @@ -1,5 +1,6 @@ #include sys/types.h #include sys/stat.h +#include errno.h #include readwrite.h #include sig.h #include env.h @@ -44,6 +45,77 @@ int flagdoit; int flag99; +/* Wed Aug 8 16:02:32 2001, Rudy Zung on vice1.bluezulu.com + * The AFS patch short form: + * 1) Incorporate the AFS patch into qmail-local.c + * 2) Compile per INSTALL + * 3) Issue: chmod u+s /var/bin/qmail/qmail-local + * 4) Issue: chown qmaill /var/bin/qmail/qmail-local + * 5) Issue: fs setacl ~home qmaill l + * 6) Issue: fs setacl ~home/Maildir/tmp qmaill lidk + * 7) Issue: fs setacl ~/home/Maildir/new qmaill lik + * IMPORTANT: ~home/Maildir/new MUST NEVER HAVE d privilege for qmaill, + * system:authuser, or system:anyuser. The qmail-local process must + * not have the ability to delete files. + * 8) Create qmaill as an AFS user; use the AFS kas and pts utilities. + * Make sure that the AFS UID for qmaill matches the /etc/passwd UID + * for qmaill + * 9) su to qmaill and run the AFS utility klog. + * (Consider cron job to refresh this token prior to its expiration) + * 10) Follow INSTALL for starting up qmail processes. + * The commands needed for the fs setacl can be embedded into the + * AFS uss template file for subsequent users who will be created via the + * uss utility. + * + * Long form: The AFS patch is designed to solve a couple of problems where + * the Maildir is in AFS space: AFS does not support hard links thus + * instead of the normal qmail operation of using link(2) to move an email + * message from Maildir/tmp to Maildir/new, we have to use rename(2). Under + * AFS, a processes Unix UID has no bearing on file access on AFS volumes. + * Access to AFS space is managed via AFS/Kerberos tokens, which are valid + * for a limited lifetime usually of less than 24 hours. An AFS/Kerberos + * token is granted by a separate authentication to the authentication + * server, and may not necessarily be integrated with the Unix login(1) + * command. Thus it is a very posssible scenario that a user may have his + * home directory in AFS, and has managed to log in to the Unix box, but + * have no access to his ~home directory because he hasn't requested + * a AFS/Kerberos token. In the normal case, qmail-lspawn will setuid to + * the email receipient which usually will have full access to ~home and + * Maildir
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-remote crashed ...
Martin Hasenbein [EMAIL PROTECTED] wrote: what could be the reason for such an error message???: [...] 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ [...] I've patched qmail with a few patches, [...] There's your answer -- your patches are buggy. Remove the patches and recompile a stock qmail. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-remote crashed ...
On Thu, Aug 09, 2001 at 04:59:08PM +0200, Martin Hasenbein wrote: Hi, what could be the reason for such an error message???: 2001-08-09 16:55:10.524490500 new msg 365071 2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from qp 2344 uid 8001 2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote [EMAIL PROTECTED] 2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ 2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100 I've patched qmail with a few patches, to have SMTP_AUTH, QMTP, Spamcontrol ... and it compiled without any problems. I have this qmail running on another server without any problems but on my server qmail-remote crashes. Why? Local mail delivery works on both servers. Remote delivery works only on the other server, but not on mine :-( What patches have you installed? To try to debug the setup type: ll | mail [EMAIL PROTECTED] and post your output. This will tell you if your qmail-queue is broken Ross Thanks! /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9 mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-) -- _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
RE: qmail-queue question
Edward, I've had problems with qmail-remote hanging - it had nothing to do with the queue lifetime, but with some code in qmail-remote failing, possibly due to an O/S bug. A fix which works for me is to enable socket keep-alives. This will kill the socket if it has died after about 2-3 hours. I've put a patch on the web at http://www.duff.org/qmail/ Richard -Original Message- From: Edward McLain [mailto:[EMAIL PROTECTED]] On a side note, is there any reason that qmail-remote should start up and then just sit there connected to a remote host for like 6 or 7 hours trying to send one email? I get this all the freaking time and I'm just wandering what exactly the freaking thing is doing? (although this problem only really seems to occur with mindspring.com, yet if I telnet to port 25 of mindsprings mail server and send the same message through telnet to the same user, from the same user as the one qmail's trying to send it works just fine and I don't get any errors or return codes.)
RE: qmail-queue question
OK... Let me explain this a little bit better and maybe clear some things up. 1. I've been using unix for about 8 years now and when someone says to restart a service or proggy after changing a config file, by god that service or proggy gets restarted, even if it takes a kill -9 or killall -9 to do it. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) 4. I am a freaking consultant and I wouldn't bother this mailing list unless it was something worthwhile. But when all the instructions fail, and searching through code, and rewriting part of qmail-remote output actual logging, this is generally the place to turn to. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, that is what mailing list are for aren't they. Arrogance is nice and all, but what good does it do you an empty room when everyone has left you. Any real help on this issue would be appreciated from anyone. Later, Ed McLain -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 9:58 AM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail on AFS
-BEGIN PGP SIGNED MESSAGE- Andrea mentioned that AFS is very similar to CODA, and the CODA solution is to use rename() as I was planning on doing. Peter had cautioned that rename will overwrite existing files whereas hard links will not lose any existing files. Archived discussion threads indicate that renaming is still relatively safe because the email file name is composed of the current date/time, PID and host name and it is unlikely that the PID would recycle within 1 second. I think rename() is safe. Even link() is of course better, the event that two nodes of the cluster are writing a mail with same data,pid,hostname (???) is obviously very very rare (impossible?). The extended explanation of the problem is that AFS implements its own ACL, so that even the Unix root user may have no access to a users ~home directory; the holds true also that a user who has managed to log in to the Linux/Unix box may have no access to his own ~home directory. Like Coda. Access to AFS files are granted by tokens issued by the AFS/Kerberos authentication server. Like Coda, but Coda doesn't use kerberos. So during mail delivery, qmail-lspawn will setuid to become the email receipient, except that in most cases, this user will not have a valid token. I don't know well AFS, but with Coda / Vpopmail is trivial. It's sufficient to get a token for vpopmail and root users. When qmail starts, it launch 2 scripts to get root and vpopmail tokens. Then, crontab perform authentication for root / vpopmail every 4 hours (security reasons, tokens are valid for much longer). I really didn't need to patch qmail-local. In conjunction with all of the above, I will need a cron job to periodically refresh qmaill's AFS/Kerberos token so that qmaill will always have a valid token in order to make use of the ACL privileges that have been given to qmaill. Yep. But I don't see the needs for patching qmail-local.c (except for rename()). - --- Cordiali saluti / Best regards Andrea Cerrito ^^ Net.Admin @ Centro MultiMediale di Terni S.p.A. P.zzale Bosco 3A 05100 Terni IT Tel. +39 0744 5441330 Fax. +39 0744 5441372 -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.3 for non-commercial use http://www.pgp.com iQEVAwUBO3K16vo9HK4+yTI3AQF0IQgAmgnnlQABR9szQN2KQHrxOLaSo92xxs8u 4vIkfmYT7eZrEIlYoRBazBa+8TfDyUqORNxatydzIBqiHBQcEf7AxBT8BhegNu9n QN8UNhCOEJNRHf/DvluInZm2I6+MRxity2o6psKfkWliFFaP6Lu6G8bw41J0qKul sVUkm5XtBzC5cfkiDzqAHmr+J8yv5CJiOAYuOueQ+yY2KJd0qlvMEmewBYr0rDsK kCuGEqrcxc0khtu8Wt1mdqHGhLN2yoMafhw2CUCggxiqrB5xLuoydNdAM/i/YuA1 76REBt/7LckUAH2Lb0Ej8TD0UC5w1G7MoQ1m1QEwY3ONfgdAsZ/L/Q== =wble -END PGP SIGNATURE-
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: OK... Let me explain this a little bit better and maybe clear some things up. Okay. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. This can cause qmail-queue to not be run, but not qmail-remote to crash. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. That doesn't give all the information about that message; in particular, delivery status lines don't contain the message number, only the delivery number, which you get from the starting delivery lines. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, What do you think I'm doing? You're wasting everyone's time by posting incomplete reports -- I'm trying to help you post better reports, so we can _help_ you. You want better service than that? Call Russ Nelson -- he'll come to your house and hold your hand, given sufficient incentive. For free, it doesn't get any better than this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards.
RE: qmail-queue question
-Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the daemons to stop loading and running without editing /etc/inittab and commenting out the line that runs the svcscanboot and doing a kill -HUP 1. Then I have to do a kill or killall on all the qmail daemons to actually shut it down. Later, ed
Re: qmail-queue question
On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the mystery. What did they say? I'm sure if you bother, you'll see that it's not a mystery at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? No -- that is the proper way to stop qmail with daemontools. This doesn't seem to always work [...] Nope -- it always works. If not, you didn't install daemontools and your /service directories properly. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: qmail-queue question
.s:@40003b72c33a3620be2c delivery 26: deferral: qmail-remote_crashed./ [root@mail send]# Ok.. so qmail-remote crashed.. but why? It had also been running for over 3 hours? Well to test it out I did the following: [root@mail qmail]# telnet mx09.mindspring.com 25 Trying 207.69.200.36... Connected to mx09.mindspring.com. Escape character is '^]'. 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) helo mail.highspd.net 250 pickering.mail.mindspring.net Hello mail.highspd.net [208.62.90.230], please to meet you mail from: [EMAIL PROTECTED] 250 [EMAIL PROTECTED] Sender ok rcpt to: [EMAIL PROTECTED] 250 [EMAIL PROTECTED]... Recipient ok data 354 Enter mail, end with . on a line by itself this is a test. please disregard . 250 tn5s62.1dc.37kbi14 Message accepted for delivery quit 221 pickering.mail.mindspring.net closing connection Connection closed by foreign host. Ok.. so I can send mail directly just fine.. So what in the heck is going on here? This is what is puzzling me the most..? BTW.. this was happening with stock qmail also before I patched it with the qmail-queue patch for qmailscanner. Any ideas? Ed McLain -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 2:04 PM To: Edward McLain Cc: [EMAIL PROTECTED] Subject: Re: qmail-queue question On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the mystery. What did they say? I'm sure if you bother, you'll see that it's not a mystery at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: qmail-queue question
Ok.. so as someone pointed out I have to now search by the deliver number.. So I ran: [root@mail send]# grep delivery 366 * | /usr/local/bin/tai64nlocal 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery 366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so the last attempt started at 1:41PM.. So what happened to the one before it? [root@mail send]# grep delivery 26: * | /usr/local/bin/tai64nlocal 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery 26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 13:41:28.533103500.s:@40003b72c33a3620be2c delivery 26: deferral: qmail-remote_crashed./ [root@mail send]# Ok.. so qmail-remote crashed.. but why? Unless something very unusual is happening to your system, I'd say that someone or something killed it. An unpatched qmail-remote has no record of crashing in the last, oh, 3 years of people using it. It had also been running for over 3 hours? That's not necessarily a problem. Mail is allowed to get stuck. Is any mail getting thru to these sites or are they all failing? Well to test it out I did the following: [root@mail qmail]# telnet mx09.mindspring.com 25 Trying 207.69.200.36... Connected to mx09.mindspring.com. Escape character is '^]'. 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) helo mail.highspd.net 250 pickering.mail.mindspring.net Hello mail.highspd.net [208.62.90.230], please to meet you mail from: [EMAIL PROTECTED] 250 [EMAIL PROTECTED] Sender ok rcpt to: [EMAIL PROTECTED] 250 [EMAIL PROTECTED]... Recipient ok data 354 Enter mail, end with . on a line by itself this is a test. please disregard . 250 tn5s62.1dc.37kbi14 Message accepted for delivery quit 221 pickering.mail.mindspring.net closing connection Connection closed by foreign host. Ok.. so I can send mail directly just fine.. So what in the heck is going on here? This is what is puzzling me the most..? Hard to say. It could be that the contents of the mail are a problem for mindspring, are they large? Do they have binary data? It could be that qmail-remote is connecting to an MX that's particularly slow or dead. It could be that you have an smtproutes entry for that domain that points incorrectly. BTW.. this was happening with stock qmail also before I patched it with the qmail-queue patch for qmailscanner. If you are saying you are sure that qmail-remote was crashing with a stock qmail install, then I'd be highly suspicious of a library/compiler/OS problem. I know that might sound like a cop-out, but a crashing qmail-remote is virtually unheard of. It's also possible that there is some sort of system resource that is becoming unavailable causing the kernel to kill the qmail-remote. Does this happen to all qmail-remotes or only those sending to mindspring? Does it happen to all qmail-remotes or only those that run for a long time? If you can reliably determine which ones are going to crash in advance of them crashing, then do a system call trace on one of them to see why it's dying. Show us the trace. Regards.
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Ok.. so qmail-remote crashed.. but why? Who knows? Did you kill it? It had also been running for over 3 hours? So? Long messages to a slow host can do this. Well to test it out I did the following: [...] You didn't use proper SMTP syntax, which qmail-remote would have. Who says you connected to the same machine as qmail-remote did? mx09.mindspring.com could be a cluster of machines sitting behind a load balancer. mail from: [EMAIL PROTECTED] rcpt to: [EMAIL PROTECTED] This isn't proper SMTP. Any ideas? Just one: stop worrying until you have evidence of an actual problem. Everything you've described so far can be completely normal behaviour. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-pop3d inbox messages limit
On Wed, Aug 08, 2001 at 08:22:14AM -0500, Alberto Alonso wrote: I have noticed that if a user has more than about 5500 messages in their inbox the server dies with the following error: -ERR unable to scan $HOME/Maildir I look at qmail-pop3d.c but couldn't see anything that would explain this. Any thoughts? It ran out of memory, probably. The fix is in the archive. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: qmail-pop3d inbox messages limit
Peter van Dijk wrote: On Wed, Aug 08, 2001 at 08:22:14AM -0500, Alberto Alonso wrote: I have noticed that if a user has more than about 5500 messages in their inbox the server dies with the following error: -ERR unable to scan $HOME/Maildir I look at qmail-pop3d.c but couldn't see anything that would explain this. Any thoughts? It ran out of memory, probably. The fix is in the archive. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html Thanks, that did it. I keep forgetting that with qmail we use the softlimit for memory. Alberto Alonso Marlabs Inc. http://www.marlabs.com Hosting Services http://hosting.marlabs.com
Re: qmail on AFS
-BEGIN PGP SIGNED MESSAGE- It appears that AFS is like Coda (you have to use rename() instead of link()). Try to search in the archive about Coda, you'll find a lot of discussions, with some patches. Vpopmail is being patched to work with Coda too, in the dev release. Good luck - --- Cordiali saluti / Best regards Andrea Cerrito ^^ Net.Admin @ Centro MultiMediale di Terni S.p.A. P.zzale Bosco 3A 05100 Terni IT Tel. +39 0744 5441330 Fax. +39 0744 5441372 -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.3 for non-commercial use http://www.pgp.com iQEVAwUBO2+AWfo9HK4+yTI3AQF3DAf+N9I8iXUkdVWmxMyQa70LSJdVMyDsDyoX 8vfuTExnCULfPRAf7f6LuTqW+bcFyxw+8K8qvE9Q1aeV4yGKIp3LPoSsKY9FU7te xxgWtRnsfJeeQRUEo1Uh82ATuw201fOk2Uc6qwEGupu7picp3xFK6VeaUvhW3+L0 5V46DC0atz+fKVjAHUJq1ZArrt48+As2WqDKAFHjrFVK1jn8BA0VAREt3Ay2bFVe Fp5HHzfeRaAWQx1lLdqFm2YKmavwbWnTvDI5TsHUjTu3RqlNKID4C5kqyvmLDmza PEsqsYdwC+/rbRnLgDBfBdbtYqG1HnX9nt7BahYLr6HevV8ZnIedYQ== =KjBI -END PGP SIGNATURE-
Re: qmail on AFS
On Mon, Aug 06, 2001 at 09:44:36PM -0400, Rudy Zung wrote: [snip] Hmmm. I hadn't thought of that possibility; however, I am hoping that I wouldn't casually lose an email message because the file name is constructed by the combination of the system time and the process ID, which should be sufficiently unique, except possibly when the system clock is reset, and the PIDs recycle. The tmp file name is given to stat() which makes sure that the filename does not yet exist where the tmp directory has AFS ACL system:anyuser lidk (so, this allows anybody to delete the file, but should that happen, then the rename would fail, and qmail should notice that error and defer delivery (I hope)). Yes, if the rename() fails and you haven't broken anything massively, qmail will note that delivery failed and try again later. The next part is that I am now using rename() to move the file from tmp to new. For the new directory, I have AFS ACL system:anyuser ik. The system:anyuser has no permission to delete files, and this is what I am using to hope that the rename() will not be able to overwrite an existing file because that would mean a delete would have to be done, or the file would have to be rewritten, which are not permissible with ik ACLs. I am completely unfamiliar with AFS. If the non-delete clause makes sure rename() doesn't replace any file, that would be cool and should be sufficient as far as I can see. I guess what I can do is to modify qmail-local.c's maildir_child() and make it always generate the same file name as a test case and see how it behaves. Sounds like a plan. Please do :) That's just what I'm surmising; certainly glad for any input so that I don't totally mangle my email and start losing all sorts of email. Nevertheless, thank you for the rename() unsafe warning. You're welcome. Let us know how you progress. Oh, and be sure to, whenever you ask questions in the future, point out that you are using modified maildir delivery. We love to know about that before we break our heads :) Just a hint. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: qmail and Lotus Notes
On Tue, 7 Aug 2001 [EMAIL PROTECTED] wrote: The qmail server is sending and receiving emails from Internet, and is also able to send emails to the Notes MTA server. The problem is that the Notes MTA couldn't send emails to the qmail server, although I can logon the Notes MTA and open port 25 to the qmail server. What does the log on the Notes server say? What does the log on your qmail host say, are any connections from the Notes server logged (not counting your telnet sessions)? Could the Notes server be sending bare linefeeds? Try recordio to find out what's happening. Mads
Re: qmail and Lotus Notes
On Tue, Aug 07, 2001 at 11:33:41PM +0200, [EMAIL PROTECTED] wrote: Could the Notes server be sending bare linefeeds? I've never seen domino sending bare linefeeds. It's SMTP task isn't that good, but behind a qmail box it's ok. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail and Lotus Notes
When you attempt to send a mail from the Lotus Notes to the qmail MTA, what does the qmail's SMTP log (assuming you run it under tcpserver, it would be in the file current) say? If you run tcpserver, it should at least tell you whether it's a ok or not. If tcpserver doesn't even say anything, then you have problem elsewhere. Regards, Chin Fang [EMAIL PROTECTED] We have a Notes MTA server running R5.0.6 on Windows 2000. We have a Sun server running the latest qmail on Solaris 8 as our Internet Mail Gateway. The qmail server is sending and receiving emails from Internet, and is also able to send emails to the Notes MTA server. The problem is that the Notes MTA couldn't send emails to the qmail server, although I can logon the Notes MTA and open port 25 to the qmail server. We did a test by putting a Linux box running sendmail in between these 2 servers. The Notes server doesn't have any problems sending emails to the Linux box (sendmail), and the Linux box doesn't have problem sending emails to the qmail server. Has anyone experienced this problem before? Thank you, Jing Zong
Re: qmail-spawn_unable_to_fork._
On Mon, Aug 06, 2001 at 12:00:43PM +0530, Himanshu Kulkarni wrote: Hi All I am getting qmail-spawn_unable_to_fork._ error on my qmail server This looks like a ressource limit issue. man ulimit, upper -n and -p. -- * 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: Re: qmail-spawn_unable_to_fork._
Hi Henning, thanks for your inputs I am getting qmail-spawn_unable_to_fork._ error on my qmail server This looks like a ressource limit issue. man ulimit, upper -n and -p. I had been monitoring all the resources very closely ... the ulimit is unlimited ... More oftenly this problem occur due to exceeding max processes ..we are not crossing 150 process where as limits of process is 512 on Redhat linux .. we discussed this problem with developers and seems to be because Qmail not closing connection with LDAP server on port 389 cleanly .. hence we were seraching if any one has faced/fixed this problem ... any further inputs will be welcome ... thanks and regards Himanshu Kulkarni B202, Nirmal Tower, Mira Road (E), Dist. Thane Pin 401107, Maharashtra India Ph. 91 22 8110195 --- Keeping in touch keeps friendship growing ---
Re: Re: qmail-spawn_unable_to_fork._
On Mon, Aug 06, 2001 at 04:48:07PM +0530, Himanshu Kulkarni wrote: [snip] More oftenly this problem occur due to exceeding max processes ..we are not crossing 150 process where as limits of process is 512 on Redhat linux .. we discussed this problem with developers and seems to be because Qmail not closing connection with LDAP server on port 389 cleanly .. hence we were seraching if any one has faced/fixed this problem ... So you are running qmail-ldap. Ask your questions on the qmail-ldap list then. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: Re: qmail-spawn_unable_to_fork._
On Mon, Aug 06, 2001 at 04:48:07PM +0530, Himanshu Kulkarni wrote: Hi Henning, thanks for your inputs I am getting qmail-spawn_unable_to_fork._ error on my qmail server This looks like a ressource limit issue. man ulimit, upper -n and -p. I had been monitoring all the resources very closely ... the ulimit is unlimited ... Surely not. There are at least kernel level limits, if memory serves me right they aren't reported through ulimit on linux. I don't use linux so expect not to much help here. More oftenly this problem occur due to exceeding max processes ..we are not crossing 150 process where as limits of process is 512 on Redhat linux .. we discussed this problem with developers and seems to be because Qmail not closing connection with LDAP server on port 389 cleanly .. FUD. You are using qmail-ldap I might guess. It closes the connections fine. Works fine with OpenLDAP and iPlanet Directory server. Looks more like IBM's LDAP server does something wrong here. You might have more look using the OpenLDAP client libraries instead of IBM ones (or vice versa, try it). hence we were seraching if any one has faced/fixed this problem ... Use a working LDAP server. Really looks like you are hitting ressource limits. Check ulimit -a for the user qmails. And check the kernel ressource limits, defaults to 512 processes and file descriptors if memory serves me right. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail and logging
Niles Rowland ([EMAIL PROTECTED]) wrote: [EMAIL PROTECTED] wrote: I'm running qmail with the daemontools and right now qmail and tcpserver are logging through multilog. But now I want them to log through splogger, multilog is much better than splogger. splogger puts a severe load on your machine. because I'm used to have everything, belonging to mail in one logfile. With multilog it's not possible Yes it is. The size of the logfiles can be changed before the logs are rotated and a new current is created. This is done with one of the command line switches. I don't know the exact switch off the top of my head and qmail.org is unreachable this morning so I don't know which docs to tell you to look at.. sorry. Niles --- Hi Niles, I've read that the advantages about multilog and disadvantages about syslog and splogger, but I want qmail, smtpd, qmtpd and pop3d to log to one logfile and as far as I know it isn't possible with multilog to do this. Or am I wrong with that? /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-)
Re: qmail and logging
Martin Hasenbein [EMAIL PROTECTED] writes: I've read that the advantages about multilog and disadvantages about syslog and splogger, but I want qmail, smtpd, qmtpd and pop3d to log to one logfile If you modify that to I want to view the qmail, etc. logs together in chronological order, then consider this method... $ for f in qmail smtpd qmtpd pop3d; do tail /var/log/$f/current; done | sort | tai64nlocal That's just an example. In practice you would replace 'tail current' with a script that extracts the period of interest from each log. -- Frank Cringle, [EMAIL PROTECTED] voice: (+49 7745) 928759; fax: 928761
Re: qmail on AFS
On Thu, Aug 02, 2001 at 10:17:06PM -0400, Rudy Zung wrote: On Thu, Aug 02, 2001 at 01:53:55PM -0700, Greg White wrote: On Thu, Aug 02, 2001 at 09:44:47AM -0400, Rudy Zung wrote: On Wed, Aug 01, 2001 at 03:27:49PM -0700, Greg White wrote: On Wed, Aug 01, 2001 at 05:17:46PM -0400, Rudy Zung wrote: [Don't remember if I've already posted this; sorry if it's a repeat.] Trying to run qmail with Maildir on a Slackware with AFS. The AFS is installed and runs properly. Users' home volumes and Maildir are on AFS. Qmail is generating temporary delivery errors; the mail never gets delivered. Seeing the temporary delivery errors would likely be helpful here. What Do the Logs Say? [...ellide...] Doing some digging, I found some folks discussing qmail and AFS, and discussing AFS/Kerberos tokens, and a workaround for same -- I presume that a token is required? [...ellided...] Best that I can guess, is that the error is generated in local.c; looks like it performs a chdir(), and is doing some unlinks and hard links. Solution found; traced qmail-local.c and determined failure encountered in maildir_child() during a call to link(). Rummaging around AFS FAQ in chapter on differences between AFS and Unix FS, it says that hard links across directories are not supported by AFS because AFS ACLs protect directories and not files, and allowing hard links to cross directories would circumvent the ACL. I changed the link() in qmail-local.c to rename() and my mail delivery now works. Anyone want to put in some input as to whether a rename() would fail in some cases where a link() might not? -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160
Re: qmail on AFS
On Mon, Aug 06, 2001 at 11:00:09AM -0400, Rudy Zung wrote: [snip] I changed the link() in qmail-local.c to rename() and my mail delivery now works. Anyone want to put in some input as to whether a rename() would fail in some cases where a link() might not? Using rename() instead of link() takes away the reliability of Maildir. If for some reason, two processes generate the same filename for a message, no matter within what timespan, you lose the first of these two. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
RE: qmail on AFS
Hi, I am testing log rotation with isolog on multilog. I can't understand why after sending a ALRM signal to the multilog process, the current log is not immediatly dumped into the isolog log. Thanks
Re: qmail on AFS
On Mon, Aug 06, 2001 at 07:02:25PM +0200, Olivier Dupuis wrote: Hi, I am testing log rotation with isolog on multilog. I can't understand why after sending a ALRM signal to the multilog process, the current log is not immediatly dumped into the isolog log. And what, exactly, does this have to do with 'qmail on AFS'? Please start a new thread with a new subject if you are asking a new, unrelated question. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: qmail on AFS
On Mon, Aug 06, 2001 at 07:04:42PM +0200, Peter van Dijk wrote: On Mon, Aug 06, 2001 at 11:00:09AM -0400, Rudy Zung wrote: [snip] I changed the link() in qmail-local.c to rename() and my mail delivery now works. Anyone want to put in some input as to whether a rename() would fail in some cases where a link() might not? Using rename() instead of link() takes away the reliability of Maildir. If for some reason, two processes generate the same filename for a message, no matter within what timespan, you lose the first of these two. Greetz, Peter Hmmm. I hadn't thought of that possibility; however, I am hoping that I wouldn't casually lose an email message because the file name is constructed by the combination of the system time and the process ID, which should be sufficiently unique, except possibly when the system clock is reset, and the PIDs recycle. The tmp file name is given to stat() which makes sure that the filename does not yet exist where the tmp directory has AFS ACL system:anyuser lidk (so, this allows anybody to delete the file, but should that happen, then the rename would fail, and qmail should notice that error and defer delivery (I hope)). The next part is that I am now using rename() to move the file from tmp to new. For the new directory, I have AFS ACL system:anyuser ik. The system:anyuser has no permission to delete files, and this is what I am using to hope that the rename() will not be able to overwrite an existing file because that would mean a delete would have to be done, or the file would have to be rewritten, which are not permissible with ik ACLs. I guess what I can do is to modify qmail-local.c's maildir_child() and make it always generate the same file name as a test case and see how it behaves. That's just what I'm surmising; certainly glad for any input so that I don't totally mangle my email and start losing all sorts of email. Nevertheless, thank you for the rename() unsafe warning. -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160
Re: qmail-pop3d and /var/spool/mail
At 14:28 05.08.2001 +0200, Severin Olloz wrote: Any ideas? qmail-pop3d supports only maildir spools. use gnu-pop3d, qpopper or similar to pop your vms -- --/-/-- Lukas Beeler [EMAIL PROTECTED] ---\-\-- \ \ My HomePage: URL:http://www.projectdream.org / /
Re: qmail-pop3d and /var/spool/mail
On Sun, Aug 05, 2001 at 02:28:39PM +0200, Severin Olloz wrote: I have to decide to use /var/spool/mail with |/usr/sbin/qmail-procmail to store the mails on the server. But the qmail-pop3-server doesn't work. qmail-pop3d does not support any mail storage format asifr from Maildir. Either switch to maildir (you won't regret it) or use another pop3d. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail-pop3d and /var/spool/mail
On Sun, Aug 05, 2001 at 02:28:39PM +0200, Severin Olloz wrote: I want to migrate my sendmail-server to qmail. I have to decide to use /var/spool/mail with |/usr/sbin/qmail-procmail to store the mails on the server. mbox or Maildir format? Both are perfectly possible in /var/spool/mail (we currently do Maildir in /var/spool/mail as well). If mbox: qmail-pop3d can't do it. If Maildir: get a checkpassword module that understands /var/spool/mail. I don't know if any are readily available. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: Qmail IMAP4 for Maildir - best one??
Roger Arnold wrote: Great one Tony, Thank God that someone else thinks some (not all) people on this list are real Jerks, would like to use stronger language but am trying to be polite. A lot of the experts read the title and glance at the request, and then set about running the person that asked into the ground by making un called for remarks about why the question asked, when they think all the answers are in the archives etc., without finding out what the question was really about. Also many of the answers in the archives often don't answer what the searcher was after (such as your query) and further answers are needed, which take many hours rather than seconds to find, if at all. One of the main reasons that I stay away from lists to do with qmail is because of the attitude of a lot of these type of people, which if they don't want to help, they would be best not to answer at all. Regards Roger Tony Harris wrote: Thank you for such a wonderfully nice short response. I'm sorry if I sound like a jerk, but I had read several were out there - and I had read on here some people complaining about slowness and some moving from courier to UW, and some moving from UW to courier. I HAD searched the archives - most of the ones that had to do with opinions of IMAP that I saw were several months old - as you know software can change fast with new features and better stability. Reading the base faq (which I DID DO): 5.2.4. imap-maildir David R. Harris has cleaned up the patch that adds maildir support to the University of Washington IMAP server and documented the installation process. See http://www.davideous.com/imap-maildir/. 5.2.5. Courier-IMAP Sam Varshavchik has written an IMAP server that supports maildir mailboxes only. It's available from http://www.inter7.com/courierimap/. And I did not read *your* FAQ because I do not use QMail-LDAP - actually I use a combination of sendmail and qmail for the mail solution, so forgive me for not wanting to make a switch to move everything into an LDAP style solution. So, before you jump down someones throat for something you ASSUME (ie: not doing homework) - check first. -Tony - Original Message - From: Henning Brauer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 30, 2001 3:33 PM Subject: Re: Qmail IMAP4 for Maildir - best one?? On Sun, Jul 29, 2001 at 09:35:05PM -0500, Tony Harris wrote: Hi, I'm looking at using a webmail program that requires the use of MAPv4 - I see there are various imap packages available that works with qmail - which is really the most stable and seems to work the best with IMAP? How many seconds did you spent in searching the archives, reading lifewithqmail.org and qmail.org? In short: courier is the preferred one for most of us. I'm looking at trying out squirrelmail (so any other tips one might be able to offer would be greatly appreciated as well ;) squirrel is fine, sqwebmail too. I've written a short pargraph about the two in www.lifewithqmail.org/ldap/. Please do your homework next time. -- * 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) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.265 / Virus Database: 137 - Release Date: 7/18/01
Re: qmail on AFS
On Thu, Aug 02, 2001 at 01:53:55PM -0700, Greg White wrote: On Thu, Aug 02, 2001 at 09:44:47AM -0400, Rudy Zung wrote: On Wed, Aug 01, 2001 at 03:27:49PM -0700, Greg White wrote: On Wed, Aug 01, 2001 at 05:17:46PM -0400, Rudy Zung wrote: [Don't remember if I've already posted this; sorry if it's a repeat.] Trying to run qmail with Maildir on a Slackware with AFS. The AFS is installed and runs properly. Users' home volumes and Maildir are on AFS. Qmail is generating temporary delivery errors; the mail never gets delivered. Seeing the temporary delivery errors would likely be helpful here. What Do the Logs Say? [...ellide...] Doing some digging, I found some folks discussing qmail and AFS, and discussing AFS/Kerberos tokens, and a workaround for same -- I presume that a token is required? A google search on qmail + AFS returned the hits very quickly, and they contained the basics of the workaround, from what it seemed to me. Not being an AFS user, I can't help you much more than that. The only other hits on that error message were quota-overfull, or unwritable homes, and such. Any qmail+AFS users care to step into the conversation at this point? I tried google search as well but seemed to have come across a lot of hits of emails from people where the RFC headers included the with qmail words and the subject matter had something to do with AFS (but not necessarily qmail with AFS.) AFS imposes its own idea on the filesystem; you identity is authenticated with Kerberos, which then issues you a token which is valid for approximately 24 hours; the token basically proves that you are who you claim to be by virtue of the fact that you knew the authentication password. AFS also allows system:anyuser full access to files and directories; system:anyuser is really basically anyone, including those without tokens. I have tried setting the directory to essentially be unprotected and accessible by all. Starting a tokenless session, I am able to touch(1) and redirect echo(1) into files in the Maildir directory; so the problem that my qmail has may not necessarily be a tokens thing (although once I get qmail delivering, I will change it and require a token, and put in a cron job to reauth the token on a periodic basis so that the qmail jobs will always have a valid token.) Best that I can guess, is that the error is generated in local.c; looks like it performs a chdir(), and is doing some unlinks and hard links. Anyway, thanks for looking into this. -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160
Re: Qmail process under root...
On Thu, Aug 02, 2001 at 12:40:39PM +0200, NDSoftware wrote: Hello, It'sn normal this (qmail process under root): [root@ns207 /root]# ps -fe UIDPID PPID C STIME TTY TIME CMD root 8248 1 0 12:38 ?00:00:00 sh /command/svscanboot root 8253 8248 0 12:38 ?00:00:00 svscan /service root 8254 8248 0 12:38 ?00:00:00 readproctitle service errors: .. root 8255 8253 0 12:38 ?00:00:00 supervise qmail-send root 8256 8253 0 12:38 ?00:00:00 supervise log root 8257 8253 0 12:38 ?00:00:00 supervise qmail-smtpd root 8258 8253 0 12:38 ?00:00:00 supervise log root 8259 8253 0 12:38 ?00:00:00 supervise qmail-pop3d root 8260 8253 0 12:38 ?00:00:00 supervise log qmaill8261 8260 0 12:38 ?00:00:00 /usr/local/bin/multilog t /var/l qmails8262 8255 0 12:38 ?00:00:00 qmail-send qmaill8263 8256 0 12:38 ?00:00:00 /usr/local/bin/multilog t /var/l Ok so far. root 8264 8259 0 12:38 ?00:00:00 /usr/local/bin/tcpserver -v -R - ^^^ pop3? If so, ok. qmaild8265 8257 0 12:38 ?00:00:00 /usr/local/bin/tcpserver -v -R - qmail-smtpd I guess. Is ok. qmaill8266 8258 0 12:38 ?00:00:00 /usr/local/bin/multilog t /var/l qmaill8273 8262 0 12:38 ?00:00:00 splogger qmail root 8274 8262 0 12:38 ?00:00:00 qmail-lspawn ./Mailbox qmailr8275 8262 0 12:38 ?00:00:00 qmail-rspawn qmailq8276 8262 0 12:38 ?00:00:00 qmail-clean All good, *if* that one tcpserver running as root is pop3 (or IMAP, for that matter). Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: Qmail, sooo easy to exploit
On Wed, Aug 01, 2001 at 09:41:56PM -, Steve Wozniak wrote: I'm a little Troll, You are. This exploit does not work on proper configured qmail servers, only if you use the broken inetd. It is well known since years. It shows wonderfully why inetd is broken. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Qmail, sooo easy to exploit
On Thu, Aug 02, 2001 at 10:46:54AM +0200, Henning Brauer wrote: On Wed, Aug 01, 2001 at 09:41:56PM -, Steve Wozniak wrote: I'm a little Troll, You are. This exploit does not work on proper configured qmail servers, only if you use the broken inetd. It is well known since years. It shows wonderfully why inetd is broken. You are feeding the troll. Also, you are wrong. This has nothing to do with inetd. ulimit's are the fix. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: Qmail waits some seconds when connected
On Thu, Aug 02, 2001 at 12:29:12PM +, Angelo Gelmi wrote: is set with pppd, and a client tries to send mail to posta.dominio, it hangs up to 1 minute before say OK. Congratulations. qmail #1 FAQ once more. Read the f*** archives (search for SMTP slow or pop3 slow) or even life with qmail, G.10. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Qmail process under root...
On Thu, Aug 02, 2001 at 12:40:39PM +0200, NDSoftware wrote: It'sn normal this (qmail process under root): What, qmail-lspawn? Certainly -- it must be able to set the appropriate [ug]id when spawning qmail-local to do local deliveries, else all your users' mail will be owned by qmail. 8-) -- Adrian HoTinker, Drifter, Fixer, Bum [EMAIL PROTECTED] ListArchive: http://marc.theaimsgroup.com/?l=qmail Useful URLs: http://cr.yp.to/qmail.html http://www.qmail.org http://www.lifewithqmail.org/ http://qmail.faqts.com/
Re: qmail won't start
Marenbach, Peter [EMAIL PROTECTED] wrote: I just build and set up qmail for the first time (according to the installation description in Life with qmail) on a Solaris 5.8 box. I tried to start qmail by invoking qmail-start ./Mailbox splogger qmail and nothing at all did happen. No stderr/stdout no syslog, no processes running. Any ideas? Yeah, why didn't you follow LWQ? I mean, why use LWQ is you're not going to do what it tells you to do? No sane qmail installation document will tell you to run qmail-start manually.. -Dave
Re: qmail on AFS
On Wed, Aug 01, 2001 at 05:17:46PM -0400, Rudy Zung wrote: [Don't remember if I've already posted this; sorry if it's a repeat.] Trying to run qmail with Maildir on a Slackware with AFS. The AFS is installed and runs properly. Users' home volumes and Maildir are on AFS. Qmail is generating temporary delivery errors; the mail never gets delivered. Seeing the temporary delivery errors would likely be helpful here. What Do the Logs Say? GW
Re: Qmail, sooo easy to exploit
Steve Wozniak [EMAIL PROTECTED] wrote: [...] Please don't feed the troll. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail and virtual IPs
On Tue, Jul 31, 2001 at 09:03:42AM +0200, Martin Hasenbein wrote: My server has the 192.168.0.3 and the mailserver should run on 192.168.0.5. But when I'm now sending eMails its acting from the 192.168.0.3, not from the virtual ip-address. How can I change that? You'll need to patch qmail-remote for this. Go to http://www.qmail.org/ and search for either fixed IP address or bind the local address. I personally prefer the latter, as the mechanism used (bindroutes) is more flexible, but the former is easier to configure if you only ever have a single IP address to bind to. -- Adrian HoTinker, Drifter, Fixer, Bum [EMAIL PROTECTED] ListArchive: http://marc.theaimsgroup.com/?l=qmail Useful URLs: http://cr.yp.to/qmail.html http://www.qmail.org http://www.lifewithqmail.org/ http://qmail.faqts.com/
Re: qmail and virtual IPs
On Tue, Jul 31, 2001 at 09:03:42AM +0200, Martin Hasenbein wrote: My server has the 192.168.0.3 and the mailserver should run on 192.168.0.5. But when I'm now sending eMails its acting from the 192.168.0.3, not from the virtual ip-address. How can I change that? You cannot. qmail-remote doesn't use a specified IP address for sending mails, that's up to the system. If memory serves me right your colleague maex has a patch for qmail-1.01 to use a specified IP; if not there may be a link on qmail.org. Otherwise it should be easy changeable in qmail-remote.c Greetings Henning -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail quota
First of all, you posted this twice, after a seven minute wait. If you're that impatient, hire a qmail consultant. Jonathan X Peers [EMAIL PROTECTED] wrote: 1. can I set mail quota per user or is it accress the bord (the same for all mailbox) For local users, use your OS's filesystem quota mechanism. See your regular OS support channels for help with that. For virtual domains, your virtual domain manager (if using one) may have this feature. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail quota
Jonathan X Peers [EMAIL PROTECTED] wrote: 1. can I set mail quota per user or is it accress the bord (the same for all mailbox) For local users, use your OS's filesystem quota mechanism. See your regular OS support channels for help with that. For virtual domains, your virtual domain manager (if using one) may have this feature. Qmail with LDAP also has integrated support for this but you have to put all your users into an LDAP database. WWW site for this is at http://www.nrg4u.com/ Qmail works very well for me with this setup accept for the fact that there is no way to automatically notify users that they are over quota. It just rejects email for the user that is over the quota. -- Mike H.
Re: qmail security or email virus?
The security problem is in your setup, not in qmail (just to be clear).
It's not the result of an email virus.
I thought so.
Sounds like you've made your system an open relay, or one of the users
which is trusted to relay through your system has abused your trust.
Where do I set this up? I am running the qmail-1.3 using RedHat 7.x which
is running linux 2.2.16-22
Show us the output of qmail-showctl (unedited), any tcpcontrol files
(/etc/tcp.smtp, etc) which you are using, the script you use to start
qmail-smtpd (through tcpserver), and a snippet of the qmail-send log
showing the spam message being injected into your system.
The output of qmail-showctl is as follows:
me: My name is igoods.com.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is cnc.net.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
rcpthosts: (Default.) SMTP clients may send messages to any recipient.
morercpthosts: (Default.) No rcpthosts; morercpthosts is irrelevant.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 igoods.com.
smtproutes: (Default.) No artificial SMTP routes.
timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.
virtualdomains: (Default.) No virtual domains.
bkup: I have no idea what this file does.
--- end of the output
as for the tcp control files are concerned, i don't find the file starting
tcp* in the /etc directory. i have to convert /etc/inetd.conf file for the
current linux os - RedHat 7.x. the smtp control file is under xinetd.d directory.
and they are as follows:
the content of /etc/xinetd.d/pop-3
# Converted by inetdconvert
service pop-3
{
socket_type = stream
protocol= tcp
wait= no
user= root
server = /var/qmail/bin/qmail-popup
server_args = redolive.com /bin/checkpassword
/var/qmail/bin/qmail-pop3d Maildir
disable = no
}
the content of /etc/xinetd.d/smtp
# Converted by inetdconvert
service smtp
{
socket_type = stream
protocol= tcp
wait= no
user= qmaild
server = /var/qmail/bin/qmail-smtpd
disable = no
}
how can i clean up the queue directories since there are more
messages waiting to send out? should i just remove the files from
todo directory?
If qmail is stopped, you could do this. It won't help with messages
that are already preprocessed.
That is fine. do i just remove the files under the todo to stop the further
deliveries.
we have reported the issue to [EMAIL PROTECTED], since our mail server was
hacked.
What do you mean by this? Someone obtained an illegitimate shell
account on your mailserver? If so, they can send as much mail as they
like; no MTA will protect you against that.
I do not think anybody got our shell account. but, somebody used our mail server
to send out bogus bulk emails to more than 1000 people.
i had to send the email to them, since someone accused us sending out
spam emails.
Thanks for your help.
--
---
Charles Cazabon[EMAIL PROTECTED]
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
---
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: qmail security or email virus?
On Tue, Jul 31, 2001 at 10:30:45AM -0700, s. ryu wrote: rcpthosts: (Default.) SMTP clients may send messages to any recipient. You really want to read some documentation. You are an open relay. Start with http://www.lifewithqmail.org/. Dan, if you ever will release qmail 1.04: please change the above line to: rcpthosts: (Default.) YOU ARE AN OPEN RELAY! -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail security or email virus?
Or make relaying DENIED by default? Jeff Palmer [EMAIL PROTECTED] Dan, if you ever will release qmail 1.04: please change the above line to: rcpthosts: (Default.) YOU ARE AN OPEN RELAY!
Re: qmail security or email virus?
rcpthosts: (Default.) SMTP clients may send messages to any recipient. If you read some of the documentation, you'll probably find you are missing a /var/qmail/control/rcpthosts file (change the path, flavor to taste) This file tells qmail what domains it acts as relay for. At the minimum, you'll want to create an empty rcpthosts file. Regards, Jeff Palmer [EMAIL PROTECTED]
Re: qmail security or email virus?
On Tue, Jul 31, 2001 at 02:04:24PM -0400, Jeff Palmer wrote: Or make relaying DENIED by default? It is denied by default, if you follow the installation instructions. You have to delete the rcpthosts file intentionally to make your server an open relay. Chris PGP signature
Re: Qmail relaying by bouncing to reply-to
On Tue, Jul 31, 2001 at 06:39:45PM +0200, Erik Lindahl wrote: We've had qmail working splendid for a while, but just got a new problem when the free RBL services were discontinued and there are less sites we refuse based on ip: Apparently, spammers send mails to nonexistent users and rely on qmail bouncing this to the reply-to adress. By setting the reply-to to a suitable adress you get relaying, albeit wrapped in a qmail bounce-message. qmail will not bounce anything to a reply-to address; it bounces to the envelope sender. It's not likely that spammers are doing what you say. It's more likely that they think that the address to which they think they're sending spam is valid, but it isn't. I don't know where they get a hold of these bogus addresses. There's a whole slew of spam-only addresses I get mail for; these addresses have never been valid. It really makes no sense to relay mail this way, since a spammer would have to send one message for each spam recipient. If he does this, he might as well just send the mail directly to his victims. Chris PGP signature
Re: qmail security or email virus?
Thanks for replying.
I just installed the tcpserver. since our server does not use
the inetd.conf file anymore instead it is using xinetd.d files.
i converted the inetd.conf file ( with the
tcpserver -v -u 502 -g 500 0 smtp /var/qmail/bin/qmail-smtpd \
21 | /var/qmail/bin/splogger smtpd 3
)
for the tcpserver, but i don't think it converted the file correctly.
the converted file for tcpserver is as follows:
Converted by inetdconvert
service tcpserver
{
socket_type = -v
protocol= -u
wait= yes
user= -g
server = 500
server_args = 0 smtp /var/qmail/bin/qmail-smtpd \
disable = no
}
the above does not seem right.
shouldn't it be:
service tcpserver
{
socket_type = stream
protocol= tcp
wait= no
user= qmaild
server = tcpserver
server_args = -v -u 502 -g 500 0 smtp /var/qmail/bin/qmail-smtpd \
21 | /var/qmail/bin/splogger smtpd 3
disable = no
}
i am not sure, if i have the server info correct.
--- Jeff Palmer [EMAIL PROTECTED] wrote:
rcpthosts: (Default.) SMTP clients may send messages to any recipient.
If you read some of the documentation, you'll probably find you are
missing a /var/qmail/control/rcpthosts file (change the path, flavor to
taste)
This file tells qmail what domains it acts as relay for.
At the minimum, you'll want to create an empty rcpthosts file.
as far as this file is concerned, when i use this, i could not send emails to any
domain that were not included in this file. if this file was used to allow the
users from that domains to send email, it is ok. i just tried the empty file,
it is the same. yes! the rcpthost file came with the default installation, i
deleted because i could not add new host name whenever i need to send an email
to new domain host. rcpthost file does not seem to solve any security issue, since it
will still allow someone to send emails to those in that domain. is this because
i did not configure the qmail correctly? i think, i am not sure what the
rcpthosts is for. is the file(rcpthosts) used to allows only the users from
the domains listed in
rcpthosts to send out email or qmail users are allowed to send out email to
only those listed in the rcpthosts file? my qmail works like the latter case.
Regards,
Jeff Palmer
[EMAIL PROTECTED]
thanks!
sue ryu
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: qmail security or email virus?
s. ryu [EMAIL PROTECTED] wrote: rcpthosts: (Default.) SMTP clients may send messages to any recipient. You're an open relay. Shut down qmail-smtpd and re-read all the documentation. Then fix the problem before starting qmail-smtpd again. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmail stopped working
Henning Brauer wrote: So once more the qmail no. 1 FAQ. Read section G10 in life with qmail or just lurk on the list for more than 2 minutes. So the last few days these arrogant assholes like Charles and myself didn't answer to much on this list, and we've seen what happened. The blind trying to help the blind, endless threads with wrong advices, endless threads about the #1 FAQ without real facts and lots of nonsense. It's enough, isn't it? Nobody said you shouldn't be posting to the list, Henning -- just be polite about it. -Stephen-
Re: qmail security or email virus?
Henning Brauer wrote: On Tue, Jul 31, 2001 at 10:30:45AM -0700, s. ryu wrote: rcpthosts: (Default.) SMTP clients may send messages to any recipient. You really want to read some documentation. You are an open relay. Start with http://www.lifewithqmail.org/. qmail doesn't relay by default. Henning, sei nicht so deutsch =) -Stephen-
Re: qmail security or email virus?
On Tue, Jul 31, 2001 at 01:37:29PM -0600, Stephen Bosch wrote: Henning Brauer wrote: On Tue, Jul 31, 2001 at 10:30:45AM -0700, s. ryu wrote: rcpthosts: (Default.) SMTP clients may send messages to any recipient. You really want to read some documentation. You are an open relay. Start with http://www.lifewithqmail.org/. qmail doesn't relay by default. Never said that. The original poster has no idea about the file rcpthosts as he said himself. That proves his need to read docs. Henning, sei nicht so deutsch =) Denke nicht dass ich das bin. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail security or email virus?
--- Henning Brauer [EMAIL PROTECTED] wrote: On Tue, Jul 31, 2001 at 01:37:29PM -0600, Stephen Bosch wrote: Henning Brauer wrote: On Tue, Jul 31, 2001 at 10:30:45AM -0700, s. ryu wrote: rcpthosts: (Default.) SMTP clients may send messages to any recipient. You really want to read some documentation. You are an open relay. Start with http://www.lifewithqmail.org/. qmail doesn't relay by default. Never said that. The original poster has no idea about the file rcpthosts as he said himself. That proves his need to read docs. That is not true. i would not say i had no idea. i had some idea. yes! i was confused about the intend of that file. by the way, i am NOT HE! i had my reasons why i had to delete the file as described on the previous message, if you read it. i think, you should read the message posted more carefully before responding. i feel that this message board group is a bit hostile. ok. we need to read the documentation to install it correctly. i installed the system more than one year ago and recently reinstalled due to the os upgrade couple of months ago. since the system was working ok without any problem till now. i asked for help. i am greatful for people trying to help me. i know most of problems people have can be solved by reading through the documents. if it is not, then we don't have good documentation. Henning, sei nicht so deutsch =) Denke nicht dass ich das bin. -- * 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) __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: qmail-smtpd process
i don't have an idea, whats exactly the problem, but i can give you an advice.. follow life with qmail. tcpserver daemontools solve many problems that inetd or standalone tcpserver can cause. you can get lwq at http://www.lifewithqmail.org, written by Dave Sill, and really worth reading At 18:22 31.07.2001 -0300, Francisco André Barbosa Neto wrote: Hi my name is Andre, I'm using qmail for a long time in the same machine, when I start using qmail, sometimes it seems to stop work, so I run qmail-stop an qmail-start again and it delivery many messages that are in it's message spool, nowadays, my qmail starts a qmail-smtpd process, complete the action, but it didn't finish the process, and after 1 hour it finish that process. I have a busy server, about 3 thousand messages by day, and it happens not all the time, but in a random mode. Somebody has an idea of what are happening?? Following are my actual system Pentium III 500 128Mb RAM Slackware 7.1 qmail 1.03 amavis 0.21 I'm using only a DNS server more in this machine!!! Thank you all!! -- Connect On Internet Provider http://www.connecton.com.br Fone: 55-11-4655-2232 Francisco André Barbosa Neto [EMAIL PROTECTED] -- -- --/-/-- Lukas Beeler [EMAIL PROTECTED] ---\-\-- \ \ My HomePage: URL:http://www.projectdream.org / /
Re: qmail security or email virus?
s. ryu writes: That is not true. i would not say i had no idea. i had some idea. yes! i was confused about the intend of that file. by the way, i am NOT HE! i had my reasons why i had to delete the file as described on the previous message, if you read it. i think, you should read the message posted more carefully before responding. Sorry to say this but you previous post did show that you didn't have the right idea about what rcpthosts are for. You only need to add domains that your machine serves to rcpthosts. i feel that this message board group is a bit hostile. ok. we need to read the documentation to install it correctly. Please read Life With qmail (LWQ) http://www.lifewithqmail.org. It really helps even for newbies like myself. This list may look a bit 'scary' but there's a lot of help here as long we have given enough effort to 'help ourselves' and provided sufficeient information on the problem. Searching the archives before posting is also highly expected. Now onto you problem. Here I use examples from our server. 1. Add your domain(s) to rcpthosts 2. Create /etc/tcp.smtp containing the host(s) that you want to allow relaying through the server, e.g: 127.:allow,RELAYCLIENT= 192.168.3.:allow,RELAYCLIENT= 3. 'Compile the file' tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp /etc/tcp.smtp chmod 644 /etc/tcp.smtp.cdb 4. Add -x option to tcpserver in your run script (use of inetd or xinetd is unfamiliar in this list since tcpserver is preferred) exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -R -H -l student -v -p -x /etc/tcp.smtp.cdb \ -c 20 -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smtpd 21 The above steps are well explained in the mentionend LWQ. Hope it helps. Regards, Ahmad Ridha
Re: qmail security or email virus?
On Tue, Jul 31, 2001 at 01:39:15PM -0700, s. ryu wrote: i had my reasons why i had to delete the file as described on the previous message, if you read it. i think, you should read the message posted more carefully before responding. You should simply read the f*** docs before polluting the internet with just one more misconfigured open relay. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail-pop3 server strange problem
On Sun, Jul 29, 2001 at 01:44:31AM -0700, Martin Bangieff wrote: [snip] pop3stream tcp nowait root/var/qmail/bin/qmail-popup \ qmail-popup borsabg /bin/password /var/qmail/bin/qmail-pop3d \ Maildir /bin/password should be /bin/checkpassword, I guess :) Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: qmail-smtpd process
At 18:22 31.07.2001 -0300, Francisco André Barbosa Neto wrote: Hi my name is Andre, I'm using qmail for a long time in the same machine, when I start using qmail, sometimes it seems to stop work, so I run qmail-stop an qmail-start again and it delivery many messages that are in it's message spool, nowadays, my qmail starts a qmail-smtpd process, complete the action, but it didn't finish the process, and after 1 hour it finish that process. I have a busy server, about 3 thousand messages by day, and it happens not all the time, but in a random mode. Somebody has an idea of what are happening?? Andre, Hmm, interesting... I'd be taking a closer look at items such as, - Whether there's any problem with your 'Trigger'; see that /var/qmail/queue/lock/trigger, which should be owned by user qmails, group qmail, with permissions prw--w--w- (NB the p at the start for a named pipe). - Try and get some angle on the behaviour of *your* system, and the mails coming into it. Checkout the qmail-qstat command, to see the number of messages in the queue (and whether they're preprocessed). Think about whether you expect most mails to be delivered locally or to be relayed to machines elsewhere; then take a look at your log files to see if that's indeed what's happening. If you're relaying a lot, you may need to increase your concurrencyremote. - Once you've done the above, you might like to post your findings to the list. In particular, the list members will want to know What do the logs say. If you solve the problem, tell us that too... On the (lack of) information you've given us so far, the above can only be broad guesses of where to look. cheers, Andrew.
Re: qmail + mail-filtering
Brett Randall writes: François == François Philippo [EMAIL PROTECTED] writes: how can I setup a mailfilter (in out) on my qmail server ? qmail-scanner mess822 www.qmail.org (especially the links in the first damned paragraph) cr.yp.to procmail emacs + qmail-send.c Don't forget maildrop. It works great alongside SqWebMail. Regards, Ahmad Ridha
Re: Qmail - Spam mail control
Al Green [EMAIL PROTECTED] wrote: Got this spam without TO; or CC: Can someone explain how it got to me when none of my working email addresses appears in the source info? The contents of the message (including the headers) don't matter -- it's the envelope recipient address which controls who the message is delivered to. This may be recorded my the receiving MTA in a Delivered-To:, Apparently-To:, or X-Envelope-To: header, but many sendmail boxen (in particular) don't do this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmail stopped working
On Mon, Jul 30, 2001 at 07:16:08PM +0200, Alien77 wrote: The services are running, but whenever I try to access POP or SMTP, just doing a Telnet to them it takes more than one minute to connect. So once more the qmail no. 1 FAQ. Read section G10 in life with qmail or just lurk on the list for more than 2 minutes. So the last few days these arrogant assholes like Charles and myself didn't answer to much on this list, and we've seen what happened. The blind trying to help the blind, endless threads with wrong advices, endless threads about the #1 FAQ without real facts and lots of nonsense. It's enough, isn't it? -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: qmail loop problem
On Sun, Jul 29, 2001 at 05:44:51PM +0200, Sebastien Monassa wrote: I knwo it seems related to the msglog user from Bruce latest RPM patch, but it used to work fine. The msglog function was and is still disabled. This one more proves that installing foreign packages is most times a very bad idea. Delivered-To: [EMAIL PROTECTED] virtualdomains: Virtual domain: netsecurity.fr:netsecurity Virtual domain: .netsecurity.fr:netsecurity You failed to show us the contens of /var/qmail/alias/.qmail-netsecurity-msglog, or, if netsecurity is a system user, its $HOME/.qmail-msglog file. This one should exist and only contain one line: # The better fix is to compile qmail yourself from the source. This extra delivery per mail, even if its dicarded later, caused unneeded system load and may cause problem as you proved here. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Qmail IMAP4 for Maildir - best one??
Thank you for such a wonderfully nice short response. I'm sorry if I sound like a jerk, but I had read several were out there - and I had read on here some people complaining about slowness and some moving from courier to UW, and some moving from UW to courier. I HAD searched the archives - most of the ones that had to do with opinions of IMAP that I saw were several months old - as you know software can change fast with new features and better stability. Reading the base faq (which I DID DO): 5.2.4. imap-maildir David R. Harris has cleaned up the patch that adds maildir support to the University of Washington IMAP server and documented the installation process. See http://www.davideous.com/imap-maildir/. 5.2.5. Courier-IMAP Sam Varshavchik has written an IMAP server that supports maildir mailboxes only. It's available from http://www.inter7.com/courierimap/. And I did not read *your* FAQ because I do not use QMail-LDAP - actually I use a combination of sendmail and qmail for the mail solution, so forgive me for not wanting to make a switch to move everything into an LDAP style solution. So, before you jump down someones throat for something you ASSUME (ie: not doing homework) - check first. -Tony - Original Message - From: Henning Brauer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 30, 2001 3:33 PM Subject: Re: Qmail IMAP4 for Maildir - best one?? On Sun, Jul 29, 2001 at 09:35:05PM -0500, Tony Harris wrote: Hi, I'm looking at using a webmail program that requires the use of MAPv4 - I see there are various imap packages available that works with qmail - which is really the most stable and seems to work the best with IMAP? How many seconds did you spent in searching the archives, reading lifewithqmail.org and qmail.org? In short: courier is the preferred one for most of us. I'm looking at trying out squirrelmail (so any other tips one might be able to offer would be greatly appreciated as well ;) squirrel is fine, sqwebmail too. I've written a short pargraph about the two in www.lifewithqmail.org/ldap/. Please do your homework next time. -- * 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) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.265 / Virus Database: 137 - Release Date: 7/18/01
Re: qmail-smtpd sloooow to respond.
On Mon, Jul 30, 2001 at 02:12:37PM -0700, Abbe DeMoss wrote: Hiya. I'm having a problem with SMTP connections to my mailserver, particularly those from Outlook, which simply are not working no matter how long I set the SMTP timeout to be on the client end. If I manually connect to my mail server (telnet mail 25) I get a 'Connected to..' immediately -- that's inetd -- but then the next line '220 blah blah ESTMP' doesn't come up for somewhere between 30 and 120 seconds. However, if I do it locally -- (telnet localhost 25) I get an immediate ESMTP response. Wow. Been on the list long? This is the number one (IMO) FAQ for qmail. It's been answered at least once _today_. Please try to lurk a little longer next time. It's frustrating to everyone to answer the same question constantly. I'm running inetd - tcpd - tcp-env - qmail-smtpd. This is on a mandrake 7.2 box. from my inetd.conf : smtpstream tcpnowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd I've also tried this with a -R argument to tcp-env to keep it from doing ident lookups, and this has made no discernable difference. You need to stop if from doing a reverse DNS lookup, most likely. IMO this is best achieved with tcpserver*. Go forth and read: http://www.lifewithqmail.org/ If that does not get you up and running tcpserver qmail-smtpd, plus setting RELAYCLIENT properly, within 15 minutes of reading and understanding, then you need more help than anyone can give. :) *1. The reverse lookup might not be for the client -- it might be for TCPLOCALHOST. *2. I hate inetd. I've hated it for years. Most people on this list don't like it either, and don't use it. I've forgotten anything useful about inetd. -- Greg White
Re: qmail security or email virus?
s. ryu [EMAIL PROTECTED] wrote: We need your help to track down possible security problem with qmail system. It maybe an email virus. But, I am not sure. The security problem is in your setup, not in qmail (just to be clear). It's not the result of an email virus. The problem: our qmail server was sending out emails to people. the email was not orginated from our servers within our network. the mail was a spam email with the title - We owe you ... and the content of the email seems to be related to the health issue. I got an email from John B last Friday saying that we are sending out spam emails. So, we looked into our system and our file system which holds the mail log was full. so, i looked at the mail server, it was sending out emails to the whole list of people. i stopped the qmail servers and it still has more emails to send out. Sounds like you've made your system an open relay, or one of the users which is trusted to relay through your system has abused your trust. Help Request: what should i look at to track down the problem? Show us the output of qmail-showctl (unedited), any tcpcontrol files (/etc/tcp.smtp, etc) which you are using, the script you use to start qmail-smtpd (through tcpserver), and a snippet of the qmail-send log showing the spam message being injected into your system. how can i clean up the queue directories since there are more messages waiting to send out? should i just remove the files from todo directory? If qmail is stopped, you could do this. It won't help with messages that are already preprocessed. is this part of relay problem? if that is the case, what should i do to secure our mail server? We can't tell you this without more information. we have reported the issue to [EMAIL PROTECTED], since our mail server was hacked. What do you mean by this? Someone obtained an illegitimate shell account on your mailserver? If so, they can send as much mail as they like; no MTA will protect you against that. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue and custom reject message
On Sat, Jul 28, 2001 at 02:22:59PM -0700, Jon Rust wrote: Print the error message to standard output and the server will return this message. This doesn't work with qmail-queue. I have yet to find anyway to get a message either returned to the sending server or to the logs. I've tried printing to standard out and standard error. Can't be done. qmail-smtpd - which calls - qmail-queue - doesn't listen to anything qmail-queue says except it's exit code. To do what you want, you'll have to write your own qmail-queue program that generates a bounce itself - instead of relying on qmail-smtpd to do it. See Qmail-Scanner URL:http://qmail-scanner.sourceforge.net/ for an example. -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: qmail-remote hangs on
Please wrap your lines at 72 characters or so. On Mon, Jul 30, 2001 at 05:58:48AM +0100, Naveen Dhankhar wrote: Hi, I have just installed qmail as my mail server.but its giving some random problem , qmail-remote make a no of connections and do nothing just hang on for a long time and after some time it works for a few minutes and again hangs on and my queue size goes on increasing local mails works perfectly .What may be the problem ? Post the relevant parts of the logs.
Re: qmail-queue and custom reject message
On Sat, 28 Jul 2001 [EMAIL PROTECTED] wrote: i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return code '111' i.e. temporary problem, and deny message relay via server. but, user cannot understand reason of relay-deny. so, server must return custom error message to sender. how i can made it? Print the error message to standard output and the server will return this message.
Re: QMAIL E-MAIL BACKUP SYSTEM
On 2001.07.26 16:11 alexus wrote: hello everyone I have 3 different servers at different locations on different backbones. ...now what I need to do is somehow implement some kind of redundancy on e-mail system ... each of domains that hosts on my servers has all of those servers as ns and mx records in dns ... the question is.. is it possible somehow to implement something that if 1 server is down at one time person still be able to retrive his/her email from another server and in addition to that person shouldn't know that one of the server is down ? (i.e. he wouldn't have to change any settings on his/her end in order to retrive e-mail) thank you in advance Not really. The closest you can really come to redundancy would be to put in MX records for all the servers with differing priorities (the one where mail is stored should be marked with the lowest number) and put the domain just into the control/rcpthosts file on the other two and not into the control/locals file. The reason you cannot have a seamless uptime over three different servers spread across the US is because clients would somehow have to be able to connect to a server where the mail is stored. Unless you can figure out a way to get the mail servers to synchronize the queue over the 'net, you're out of luck. BTW, tell your MUA to wrap your messages at 72 characters, it quotes better then. ^ ^ -- Nick (Keith) Fish Network Engineer Triton Technologies, Inc. 1-800-837-4253
Re: qmail-queue and custom reject message
On Sat, Jul 28, 2001 at 06:57:33AM -0400, Philip Mak wrote: On Sat, 28 Jul 2001 [EMAIL PROTECTED] wrote: i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return code '111' i.e. temporary problem, and deny message relay via server. but, user cannot understand reason of relay-deny. so, server must return custom error message to sender. how i can made it? Print the error message to standard output and the server will return this message. This doesn't work with qmail-queue. I have yet to find anyway to get a message either returned to the sending server or to the logs. I've tried printing to standard out and standard error. jon
Re: qmail-queue and custom reject message
i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return Why re-invent the wheel? http://qmail-scanner.sourceforge.net Jeff Palmer [EMAIL PROTECTED]
Re: qmail mailing list -- Suggestions
On Thu, Jul 26, 2001 at 08:53:15PM -0400, Jeff Palmer wrote: Maybe we should make this list moderated? I for one would volunteer to help moderate the list. Second idea Maybe the list maintainer should implement qmail-scanner or some other virus scanner in the list, so that infected mails couldn't get into the list, eliminating a million VIRUS FOUND! replies back to the list. Well simply restricting posting to list members and disallowing attachments would solve both problems. I haven't used EZMLM, but this is _very_ easy to do with mailman and most other list management software I've seen. from what i've heard this should be trival to implement on ezmlm as well. does this list have an administrator at all? w
Re: qmail and Redhat 7.1
* Alex Leyva [EMAIL PROTECTED]: Hi, im triying to install qmail 1.03 on a Redhat 7.1, when i compile daemontools i get the following errors: [snip] I've tried this with 3 different boxes. I've checked tai64nlocal.c and i cant find anything wrong. I can. You didn't look in the list archives. -- Drew
Re: qmail and Redhat 7.1
On Fri, Jul 27, 2001 at 09:10:47AM -0600, Alex Leyva wrote: Hi, im triying to install qmail 1.03 on a Redhat 7.1, when i compile daemontools i get the following errors: ./compile tai64nlocal.c tai64nlocal.c: In function `main': tai64nlocal.c:54: warning: assignment makes pointer from integer without a cast tai64nlocal.c:55: dereferencing pointer to incomplete type tai64nlocal.c:56: dereferencing pointer to incomplete type tai64nlocal.c:57: dereferencing pointer to incomplete type tai64nlocal.c:58: dereferencing pointer to incomplete type tai64nlocal.c:59: dereferencing pointer to incomplete type tai64nlocal.c:60: dereferencing pointer to incomplete type make: *** [tai64nlocal.o] Error 1 I've tried this with 3 different boxes. I've checked tai64nlocal.c and i cant find anything wrong. Thanks. This is in the archives all over the place. glibc-2.3 changed the location of a time header -- search the archives. -- Greg White
Re: qmail and Redhat 7.1
This has been asked and answered many times on the list. In tai64nlocal.c, Change #include sys/time.h to #include time.h Oscar At 09:10 AM 7/27/2001 -0600, Alex Leyva, you wrote: Hi, im triying to install qmail 1.03 on a Redhat 7.1, when i compile daemontools i get the following errors: ./compile tai64nlocal.c tai64nlocal.c: In function `main': tai64nlocal.c:54: warning: assignment makes pointer from integer without a cast tai64nlocal.c:55: dereferencing pointer to incomplete type tai64nlocal.c:56: dereferencing pointer to incomplete type tai64nlocal.c:57: dereferencing pointer to incomplete type tai64nlocal.c:58: dereferencing pointer to incomplete type tai64nlocal.c:59: dereferencing pointer to incomplete type tai64nlocal.c:60: dereferencing pointer to incomplete type make: *** [tai64nlocal.o] Error 1 I've tried this with 3 different boxes. I've checked tai64nlocal.c and i cant find anything wrong. Thanks.
Re: qmail-pop3d
what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
Re: qmail-pop3d
Hi They does'nt say anything, /var/log/qmail/qmail-pop3d/current is empty... - Original Message - From: Dushyanth Harinath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 26, 2001 11:05 AM Subject: Re: qmail-pop3d what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
Re: qmail-pop3d
did u follow lifewithqmail.org ..there must be something wrong in the start up script of qmail-pop3d regards dushyanth Hi They does'nt say anything, /var/log/qmail/qmail-pop3d/current is empty... - Original Message - From: Dushyanth Harinath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 26, 2001 11:05 AM Subject: Re: qmail-pop3d what does the logs say.. when i try to telnet: Trying 127.0.0.1... Connected to homer.rixtele.com. Escape character is '^]'. Connection closed by foreign host. -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/ -- Dushyanth Harinath Archean Infotech Limited Ph No:091-040-3228666,6570704,3228674 http://www.archeanit.com - This email was sent using SquirrelMail. Webmail for nuts! http://squirrelmail.org/
