Search results for query: *

thanks for the tips...I think I found a work around. I think the reason the proocess kept bailing out was because the load average was hitting the default limit of either 8 or 12. ( not sure which one did it), but I upped the following from the default of 8 and 12 respectively: # load average...

another wierd thing that I think is related: I tried to sendmail -q each of the queues manually and they go away after a few minutes. here is my output after a few moments. it still has q1 running: ps -efww |grep run root 1647 1 0 Mar26 ? 00:00:00 xinetd -stayalive -pidfile...

I got the same thing you did for hotmail and I get responses for the others too, so I think DNS is ok. unless I'm missing something... I see what you meant about aliases, but I am not really using that. this is just a mail gateway that passes everything off to an Exchange environment. the owner...

here are a few lines of maillog after doing sendmail -q. I've replaced my domain with mydomain, my internal server with myInternalServer, and my external server (which is the one in question) with my server. there is nothing in messages that coresponds to this time period, so I ommited it. top...

I think so...another server we have seems fine with the same dns servers...with only one queue. it's a beefier machine, but I don't think processing is the issue because sar shows about 90% idle.

thanks for the tip, however, I am still having trouble clearing out the 3 queues I created. My server is set to try to deliver for 4 days. I have over 5 days worth in my queue. new mail seems to be coming and going within each queue, but I'm not convinced the queue runner is ever going through...

I have it set to run once an hour in cron, but it doesn't seem to be doing it, or at least doesn't seem to finish. that's why I tried the -v option and sure enough it cuts out well before its done.

does anyone know what this means? I am trying to run a huge queue with sendmail -q -v and it gets through about 1000 meaages and quits with: "Skipping /var/spool/mqueue/i2NIbfHI004544 (sequence 731 of 10303) and flushing rest of queue". It doesn't seem to be the same message each time. thanks.

As a follow up to my own question, the queue has grown to about 55,000 files or (I guess) 25,000 messages. Could it be that the queue runner can't keep up with the messages to process the messages older than 4 days? in other words, could my queue runner be working fine, but working for days...

I am running 8.12. My /var/spool/mqueue directory doesn't seem to be cleaning up after itself. Mail seems to be working fine, but the mqueue dir has messages in it from several weeks ago. I know I can move the queue and run it as a seperate process, but I thought it was supposed to regularly...