RE: Problems using qmail
hi, I'm alessandro from Italy ... This problem doesn't exist if i send a mail trough qmail-inject.. Then it's probably not a problem with qmail. From your attachment: X-Mailer: Evolution/0.10 (Preview Release) Have you tried another client, perhaps one that has been declared stable?
Re: Problems using qmail
I'm going crazy to understand why This problem doesn't exist if i send a mail trough qmail-inject.. The curious thing is that if I put in the FROM field an external address, qmail is able to send-out the error message whitout any problem!!! it must be a problem of the local delivery. Check the deliverymethod and the granted rights for the mailbox / maildir. The lowest right for the maildir must set to 701 or higher. Regards, Ruprecht
Re: Problems using qmail
Now it works... My hosts.allow was ' tcp-env : 127.0.0.1 : setenv RELAYCLIENT ' but this syntax is wrong... it put in the RELAYCLIENT the value and qmail add this variable at the end of the address... Now my hosts.allow is: 'tcp-env : 127.0.0.1 : setenv RELAYCLIENT ' so it set the RELAYCLIENT variable without any value.. and it works!!! thanks to all!! p.s. Qmail on Xinetd is possible!!!
Re: Problems using qmail
Alle[EMAIL PROTECTED] wrote: hi, I'm alessandro from Italy Welcome. I'm Dave from Tennessee, USA. I'm using Qmail with XINETD, and it *works* Are you sure? :-) When I send a mail to someone, qmail appends a to the end of the TO field, so if the the recipients' email is [EMAIL PROTECTED], qmail try to connect to [EMAIL PROTECTED] and fails.. Right away I'm thinking RELAYCLIENT... This problem doesn't exist if i send a mail trough qmail-inject.. And this nearly clinches it. I suspect you're using xinetd to set RELAYCLIENT to enable selective relaying. What you want is for RELAYCLIENT to be set to the null string for hosts allowed to relay. You're probably saying something like: RELAYCLIENT= But apparently xinetd is not setting RELAYCLIENT to the null string, it's setting it to, literally, . And according to the qmail-smtpd man page: Exception: If the environment variable RELAYCLIENT is set, qmail-smtpd will ignore rcpthosts, and will append the value of RELAYCLIENT to each incoming recipient address. So, perhaps setting RELAYCLIENT like: RELAYCLIENT= in your xinetd config will do the trick. The curious thing is that if I put in the FROM field an external address, qmail is able to send-out the error message whitout any problem!!! Not sure what's going on there, though. -Dave
Re: Problems using qmail on very large site
Hi Mark, They stay running forever and the parent process is qmail-queue. Now I have 162 defunct process. Today I will try to alter rlim_fd_cur to 64 (the number of file descriptors - Today the value is 1024. 64 was the original value) and keep the rlim_fd_max to 2048, like it is today and I will reboot the machines. I read somewhere that isn't a good idea change the default current limit of file descriptors like I did. They suggest only change the max number of file descriptor. Well, is just a guess, but I think that won't cause any damage to try ;-) Thanks for your attention ! Regards. The problem is the fact that I'm having too much defunct process. Usually I have between 350-500 process running by machine. From that, normally I have between 90-120 defunct process per machine. Do they stay forever, or do they go away? Which qmail process is the parent? I have seen Solaris 2.x systems where processes do stay around forever, but I have not seen in on, eg, FreeBSD. Regards.
Re: Problems using qmail on very large site
Yuan, For change the current and max number of file descriptors in Solaris 2.6 (in 2.7 I think is the same but I'm not sure), you need add two entries in your /etc/system file: set rlim_fd_cur=1024 set rlim_fd_max=2048 and you MUST reboot your machine in order to changes take effect. To see if everythings works, try to use the command ulimit -a before and after the modifications. Unfortanately the max number of file descriptors wouldn't be showed, just the current will (open files parameter). Hope this helps. Regards, Claudio Hi, Excuse me for asking a silly question. In Solaris 2.6 or 2.7, how do you change rlim_fd_max etc? I cannot find it in the Answer Books. Thank you very much. Yuan Hi Mark, They stay running forever and the parent process is qmail-queue. Now I have 162 defunct process. Today I will try to alter rlim_fd_cur to 64 (the number of file descriptors - Today the value is 1024. 64 was the original value) and keep the rlim_fd_max to 2048, like it is today and I will reboot the machines. I read somewhere that isn't a good idea change the default current limit of file descriptors like I did. They suggest only change the max number of file descriptor. Well, is just a guess, but I think that won't cause any damage to try ;-) Thanks for your attention ! Regards. The problem is the fact that I'm having too much defunct process. Usually I have between 350-500 process running by machine. From that, normally I have between 90-120 defunct process per machine. Do they stay forever, or do they go away? Which qmail process is the parent? I have seen Solaris 2.x systems where processes do stay around forever, but I have not seen in on, eg, FreeBSD. Regards.
RE: Problems using qmail on very large site
Claudio, I looked at my record just now. I have a Sun Ultra 5 running Solaris 2.7. When I increased the number of concurrent remote processes to 50, the log file shows "cannot open pipe" error for a lot of the processes. Is this caused by rlim_fd_max too small? Sincerely, Yuan Yuan, For change the current and max number of file descriptors in Solaris 2.6 (in 2.7 I think is the same but I'm not sure), you need add two entries in your /etc/system file: set rlim_fd_cur=1024 set rlim_fd_max=2048 and you MUST reboot your machine in order to changes take effect. To see if everythings works, try to use the command ulimit -a before and after the modifications. Unfortanately the max number of file descriptors wouldn't be showed, just the current will (open files parameter). Hope this helps. Regards, Claudio
Re: Problems using qmail on very large site
Yuan, In my case, I changed both (rlim_fd_max and rlim_fd_cur to 2048 and 1024 respectively). After reboot my machines I don't received more messages like that. By the way, my concurrency remote is set to 255. So, I believe that for your case (50) this set (2048) should work fine too. I suggest that you try change just the rlim_fd_max, because I think that change rlim_fd_cur is unnecessary or, even (I still couldn't try decrease it like I said that I will), cause that problem that originate all this discussion: a lot of defunct process running in my machine ! But in my case, like I said, I'm using Solaris 2.6 and not 2.7 like you Regards, Claudio Is this caused by rlim_fd_max too small? Sincerely, Yuan Yuan, For change the current and max number of file descriptors in Solaris 2.6 (in 2.7 I think is the same but I'm not sure), you need add two entries in your /etc/system file: set rlim_fd_cur=1024 set rlim_fd_max=2048 and you MUST reboot your machine in order to changes take effect. To see if everythings works, try to use the command ulimit -a before and after the modifications. Unfortanately the max number of file descriptors wouldn't be showed, just the current will (open files parameter). Hope this helps. Regards, Claudio
Re: Problems using qmail on very large site
The problem is the fact that I'm having too much defunct process. Usually I have between 350-500 process running by machine. From that, normally I have between 90-120 defunct process per machine. Do they stay forever, or do they go away? Which qmail process is the parent? I have seen Solaris 2.x systems where processes do stay around forever, but I have not seen in on, eg, FreeBSD. Regards.
