Re: [Mimedefang] resending mail sent to /var/spool/mail

2006-01-05 Thread James Ebright
Move the mqueue directory to something like mqueue-temp and make a new one with same permissions/owners (do this with sendmail stopped) then start sendmail, once load is low enough you can start a new sendmail process to process that mqueue-temp like this: sendmail -q -oQ/full/path/to/mqueue-temp

Re: [Mimedefang] resending mail sent to /var/spool/mail

2006-01-05 Thread Dave O'Neill
On Thu, Jan 05, 2006 at 02:23:32PM -0800, Kelson Vibber wrote: > > sendmail -q -O QueueDirectory=/path/to/queue > > That starts a sendmail process that will run through the queue once. > If your queue is large (and the concept of "large" really depends on your hardware -- it could mean 1000 ent

Re: [Mimedefang] resending mail sent to /var/spool/mail

2006-01-05 Thread Kelson Vibber
Stephen Ford wrote: We had one of our internal mail servers die for a little while today and when I run mailq (I'm on a Solaris 9 system) there are 1600 messages waiting with connection refused errors in /var/spool/mqueue. This should do it: sendmail -q -O QueueDirectory=/path/to/queue That

RE: [Mimedefang] resending mail sent to /var/spool/mail

2006-01-05 Thread Jason Bertoch
Sent: Thursday, January 05, 2006 4:50 PM To: mimedefang@lists.roaringpenguin.com Subject: [Mimedefang] resending mail sent to /var/spool/mail We had one of our internal mail servers die for a little while today and when I run mailq (I'm on a Solaris 9 system) there are 1600 messages waiting

[Mimedefang] resending mail sent to /var/spool/mail

2006-01-05 Thread Stephen Ford
We had one of our internal mail servers die for a little while today and when I run mailq (I'm on a Solaris 9 system) there are 1600 messages waiting with connection refused errors in /var/spool/mqueue. However, since I'm using mimedefang with sendmail as a gateway, my sendmail processes are only