Archive Filter

[Glenn Steen]

On 09/02/06, Alex Neuman van der Hans <alex at nkpanama.com> wrote:
>  So... logically then, one way I see to do something like this would be:
>
>  1. Create an archive account
>  2. Set scan messages to a ruleset containing:
>
>  From: 127.0.0.1 and To:   archive at yourdomain.tld  no # to prevent outsiders
> from e-mailing the archive account and going through unscanned
>  FromOrTo:   default   yes
>
>  3. Have "Non spam actions" set to "deliver forward archive at yourdomain.tld"
>  4. Have "Archive Mail" set to a ruleset containing:
>  To:   archive at yourdomain.tld   whereveryouwantyourarchive
>  FromOrTo:   default   no
>  5. Figure out how to sort the single box into different mailboxes per user
> or domain or whatever.
>
>  Right?
>
Well, not really necessary.

If I read you right, you could as easily just specify
"archive at domain.tld" in the Archive Mail setting, and use the normal
measures of your MTA to ensure noone can mail that one (apart from
localhost:).

If one has MS archiving to a directory (or a set of directories/user)
then the archive copy is just a copy of the queue file ... So then the
scripting needed becomes trivial... Simply trawl your log, or poll
your MailWatch maillog, for the message queue file ids ("maillog.id"
in MW) that contain a virus infection or is spam ... and remove the
files. Downside with that is that the files _are_ queue files. Sigh.

In the case of having things as mbox file(s), it gets a bit more
iffy... You need (apart from finding the correct mbox to munge)
uniquely identify the message and then use something like the
Mail::Box thing to delete just that message in a safe way.

IIUC, Rodney is using a ruleset on Archive Mail to put every
recipients mail into separate mbox files.

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se