Search results for query: *

First, this problem can be due to either qmail, either Yahoo (which maybe waits before sending your second mail). Try to send mail from another account to be sure that this problem always occurs.

I'll check this website. About the .qmail-personnel, it doesn't begin with a pipe character, it is just a list of the persons with an ampersand to ask for a redirection. So this file is just something like : &user1 &user2 ... &usern

About GUI/UID, I never paid attention to the readproctitle but there's an error "setuidgid: qmaill unknown account". I know this error was here before, but as all was right, I never had a look at this. I tested the setuidgid command with several accounts ('root', admin account, user account...

I moved the queue and created a new one with queue-fix but it didn't sort out the problem. Actually, I think the problem isn't with qmail-lspawn but rather with qmail-local which I suspect not to say its father its job is done, so that lspawn just wait and nothing can wake it up. I'll...

Thanks for the idea, alas I already tried the queue-fix utility, with no result. Anyway, I'll purge the queue, move it and create a new one as soon as I can. Maybe queue-fix can't detect a problem and to create a new queue can solve it...

I checked this but it's correct. I followed the LWQ web site to install Qmail and it reads that usually the qmail-lspawn is running as user root. If it can help, I used qmail-remove to remove a blocked message from the queue and it appeared that it makes the qmail-lspawn process end. By the...

Hello all I have installed qmail 1.03 on a Mac OS X.2.8. I have no HFS+ partition so I set the concurrencylocal to 1 to avoid locks. Since I installed the latest security update from Apple, I have a problem. the qmail-lspawn owned by the root is ok but the child owned by a user sometimes...