Mailscanner in mem

[Lindsay Snider]

On Thursday 27 March 2003 10:11, you wrote:
> Hi Julien
> I use redhat 7.3 with the latest MailScanner
> I just setup tmpfs and I have /var/spool/MailScanner/incoming mounted(I use
> fstab)
> Now I Just sent myself a message and all looks fine the message was 
> accepted and got delivered.
>
Have you tried sending a virus through it yet?  That's where I saw the 
problem.  There were no errrors, f-prot would simply not catch viruses. 

> Mar 27 17:04:04 mailscanner sendmail[4430]: h2RF44H04430:
> to=<test at ans.nom.za>, delay=00:00:00, mailer=smtp, pri=30556, stat=queued
> Mar 27 17:04:07 mailscanner MailScanner[4331]: New Batch: Scanning 1
> messages, 1000 bytes
> Mar 27 17:04:12 mailscanner MailScanner[4331]: Virus and Content Scanning:
> Starting
> Mar 27 17:04:12 mailscanner MailScanner[4331]: Uninfected: Delivered 1
> messages
> Mar 27 17:04:12 mailscanner sendmail[4435]: h2RF44H04430:
> to=<test at ans.nom.za>, delay=00:00:08, xdelay=00:00:00, mailer=smtp,
> pri=120556, relay=[196.25.84.194] [196.25.84.194], dsn=2.0.0, stat=Sent
> (h2RF4Muc003419 Message accepted for delivery)
>
> I havn't tested it under load but it looks like it wil work
>
>
> Mozzi
>
> On Monday 24 March 2003 13:51, you wrote:
> > Try scanning a directory structure in tmpfs with the latest F-Prot code,
> > it's possible they have fixed it.
> > Let me know what you find.
> >
> > At 11:20 24/03/2003, you wrote:
> > >Tnx
> > >I use fprot so there goes that idea
> > >
> > >Mozzi
> > >
> > >On Monday 24 March 2003 12:55, you wrote:
> > > > At 09:26 24/03/2003, you wrote:
> > > > >Hallo all
> > > > >
> > > > >Can anyone remeber the subject for the thrad on running mailscanner
> > > > > in memory?
> > > > >
> > > > >I have a box with 3Gig ram here and I need the performance.
> > > >
> > > > You can safely run with the MailScanner/incoming directory in RAM
> > > > (just use tmpfs) as long as you aren't using F-Prot (which for some
> > > > reason doesn't like tmpfs and won't recurse directories properly).
> > > > Putting your mqueue.in and mqueue in RAM is very dodgy unless your
> > > > RAM is battery-backed and your system is never rebooted with anything
> > > > in its mail queues.
> > > >
> > > > If you are running Linux, then add a "-" in front of the log filename
> > > > in syslog.conf. So instead of it logging to
> > > >          /var/log/maillog
> > > > make it
> > > >          -/var/log/maillog
> > > > That will stop syslogd from fsync-ing after every log entry, which
> > > > can make quite a difference to your disk traffic.
> > > >
> > > > Running with MailScanner/incoming in tmpfs can add up to 30% to your
> > > > max throughput.
> > > > --
> > > > Julian Field
> > > > www.MailScanner.info
> > > > Professional Support Services at www.MailScanner.biz
> > > > MailScanner thanks transtec Computers for their support
> >
> > --
> > Julian Field
> > www.MailScanner.info
> > Professional Support Services at www.MailScanner.biz
> > MailScanner thanks transtec Computers for their support