[Maia-users] Outbound scanning and more?

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mart Pirita wrote:
> Tere.
> 
> As suggested, I have plan to use two, on the same MX priority scanners 
> and one database server, but some questions arrived:
> 
> 1) Does the latest Maia-Mailguard include OCR support?

Maia Mailguard 1.0.2 will work fine with the FuzzyOCR plugin for
SpamAssassin.  No special support is required within Maia for this.


> 1) Does the latest Maia-Mailguard include custom rules?

Custom SpamAssassin rules can be placed in *.cf files in your
/etc/mail/spamassassin subdirectory (or wherever your local.cf file is
located).  These rules are globally applied, however, not per-user
rules--any custom rules you add this way will be used in the scanning of
/all/ mail.

Per-user rule files are not supported by Maia Mailguard (or amavisd-new
for that matter), because doing so would require that the mail be
scanned once for every recipient, rather than just once.  As such,
per-user rule files don't scale well, performance-wise.


> 2) Does the latest Maia-Mailguard handle also outbound traffic? If yes, 
> then does it support also footer attachment, scanning and filtering, 
> keyword and attachment blocking, quarantine etc?

Yes, scanning of outbound mail is handled by the system-default (@.)
user.  Any mail addressed to non-local recipients falls through to the
system-default account, which can be configured to filter and quarantine
mail just like any other account.

Footer attachment, on the other hand, is not currently supported, since
this involves modifying the mail body itself.  Doing so breaks things
like digital signatures, encryption, and other mechanisms that verify
that the mail has not been tampered with in transit.  To do this
properly, footers should be added at the sender's mail client before
signing/encrypting takes place.


> 3) If ordinary inbound mail traffic is about 0,5 million messages per 
> day, and I'd like to use one global quarantine, handled, by 
> administrator, approximately how big will be the MySql database for 
> example one Month?

According to my local stats, the average mail item is about 20 kB in
size, so at that rate you'd be adding about 9.5 GB of data to your
database every day.  How many days' worth of data you accumulate before
auto-expiry will determine the "high water mark" for storage purposes.
If you set your expiry threshold to, say, 3 days, then you should max
out at about 28.5 GB of storage.  Obviously if you want to retain mail
items for longer periods you'll need more space.  Thanks to expiry,
though, your storage needs should not grow beyond the high-water mark
(unless your volume increases, or the average mail size increases).

- --
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGHx83GmqOER2NHewRArtyAKCKn/nxCfjm8Ty+WsEnZ9nTKX9rhwCfRaS4
6+pANsERlpqCx7uq8izRVPE=
=OjNC
-----END PGP SIGNATURE-----