writing to /var/spool/MailScanner/incoming

[Rick Cooper]

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Richard Frovarp
> Sent: Tuesday, May 08, 2007 10:51 AM
> To: MailScanner discussion
> Subject: Re: writing to /var/spool/MailScanner/incoming
> 
> Ugo Bellavance wrote:
> > Richard Frovarp wrote:
> >>
> >> Isn't this really dangerous? If you lose power or reboot 
> the machine 
> >> without an empty incoming queue, you will lose messages. To reboot 
> >> you would have to stop the incoming mail process, let MailScanner 
> >> clean out the queue, then reboot. Or am I missing something that 
> >> would prevent you from losing messages?
> >
> > Messages stays in the MTA inbound queue until processed.  They are 
> > copied to /var/spool/MailScanner/incoming, processed and it 
> is copied 
> > to the outbound MTA queue once processed.  Once copied in 
> the outbount 
> > queue, it is deleted from the inbound queue.
> >
> > I think this is in the MAQ...
> >
> > ugo
> >
> Right and if /var/spool/MailScanner/incoming is in tempfs, the only 
> place it exists is in RAM. The state of RAM goes away during 
> reboot or 
> power loss. Hence it is really dangerous to have incoming in 
> tempfs. If 
> that queue isn't empty when the state is lost, messages will be lost.
> -- 

Only half correct. The MailScanner queue is lost but the MTA queue is still
intact. When MailScanner restarts it will process all the MTA's queue again
so everything lost in the MailScanner working dir is rebuilt anyway. Nothing
in the MTA queue is touched until it's in the MTA outbound queue.

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.