[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Exim problem mails stucks in /var/spool/exim/input/



Thx, for the tip y will be working on it.

Cheers,
	rak

On Tue, Sep 16, 2003 at 11:39:45PM -0500, Rod Rodolico wrote:
> On a mail server with any kind of traffic, this directory should have some files in it most of
> the time. There should be a file with a -H at the end that matches the -D. Look in
> /etc/cron.d/exim and see when the incoming messages are processed (standard install is every
> 15 minutes). If I understand correctly, exim is called when an incoming message is received,
> and it puts the message in /var/spool/exim/input. Then, every 15 minutes, another copy is
> started which processes the files and delivers them. So, this directory should have files in
> it most of the time.
> 
> However, if the files stay there for a while, they may be frozen. Try the following:
> 
> exim -bp | grep "*** frozen ***"
> 
> I get a lot of frozen messages on my server and, after looking at them, simply delete them. I
> do this with the following Perl script. THIS SCRIPT DOES NO ERROR CHECKING. Do not use it
> unless you know you want to delete all frozen messages.
> 
> Rod
> 
> #! /usr/bin/perl -w
> `exim -bp | grep "*** frozen ***" > unfreeze.txt`;
> my $badmessages;
> open BADMAIL, "<unfreeze.txt" or die "Could not open unfreeze.txt";
> while ( $line = <BADMAIL> ) {
>    my ( $time, $size, $messagenumber, $sender, $status ) = split( ' ', $line );
>    print "Time on queue => $time\tSize=>$size\tMessage #=>$messagenumber\n";
>    $badmessages .= ' ' . $messagenumber;
> }
> close BADMAIL;
> `exim -Mrm $badmessages`;
> 1;
> 
> > Hi people,
> > 	Got some problems here im runing a Debian Woody, the system is up to
> > date and the mail server is exim with amavis and McAfee uvscan antivirus.
> > 	For some reason that I couldn't find out the mail is beeing stored
> > in the /var/spool/exim/input directory and not deliver to its destinated
> > users on the system. The amavis config has been double check and its ok and
> > the exim it self has no special configuration it is the MX server on the
> > domain and has a couple of secondary names...
> > 	The problem is that the input dir is fill with file of the tipe
> > 19yvpW-0001Fz-00-D and we try to reproces the queue with exim -fq but with
> > no success.
> > 	If anyone got a clue of what is happening or can point me to some
> > "good" reading I would be thanks.
> >
> > 	Cheers,
> > 		rak
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
> >
> 
> 
> -- 
> BRITANNUS(shocked): Caesar, this is not proper.
> THEODOTUS(outraged): How?
> CAESAR (recovering his self-possession): Pardon him, Theodotus: he is a barbarian, and thinks
> that the customs of his tribe and island are the laws of nature.
>                                 Caesar and Cleopatra, Act II
>                                   --George Bernard Shaw



Reply to: