Common SQL Backend for several MailScanner clients.
MailScanner at ecs.soton.ac.uk
Sat May 2 01:13:03 IST 2009
That sounds mostly like SpamAssassin and MailWatch issues, not directly
MailScanner related. Am I correct or not? MailScanner's use of SQL is
strictly limited and not much can be gained by sharing its SQL databases
(there are only about 2 tables).
On 01/05/2009 07:16, Kasper Sacharias Eenberg wrote:
> Good morning.
> Can you have several MailScanner clients, that all run on a single SQL
> That includes a bayesian filter, but afaik that shouldn't cause any
> problems, as it's already shared between users on some servers.
> The logging is through SQL ofcourse, as we use the mailwatch front-end.
> Will this create any problems that anyone can foresee?
> The reasoning behind this would be common logging, so we wouldn't have
> to edit several white/blacklists, check several filters for what went
> through and so on.
> And my boss does not want clustering, as depending on the bandwidth it
> uses, we might spread them out over several geographical locations.
> Thanks for the great software.
> With regards,
> Kasper Eenberg
> HOVMARK DATA
> Ravnevej 13
> dk-6705 Esbjerg Ø
> tlf: +45 76 12 59 04
> mobil: +45 40 70 69 63
Julian Field MEng CITP CEng
Buy the MailScanner book at www.MailScanner.info/store
MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc
Follow me at twitter.com/JulesFM
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the MailScanner