What are your ideas on having the mbox scanning code handleWhy scan mail when it's already delivered? We handle ~750k mails/day, using amavisd-new and clamd, coming in through load-balanced mail exchangers, which deliver mail to the mbox servers after content scanning. Runs like a charm, and, because of load balancing, it's easily extendible. Plus amavisd-new enables us to run spamassassin on mail for selected domains...
attachments in-line rather than writing to/reading from the
filesystem? Due to the size of our mail system (~ 1 million messages
per day) it seems disk access will be a bottleneck.
Thanks, Joe
Thomas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
