quarantined non-spam attachments

[Glenn Steen]

On 02/03/07, Steve Campbell <campbell at cnpapers.com> wrote:
>
> ----- Original Message -----
> From: "Glenn Steen" <glenn.steen at gmail.com>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: Friday, March 02, 2007 3:35 AM
> Subject: Re: quarantined non-spam attachments
>
>
> > On 02/03/07, Brent Addis <brent.addis at pronet.co.nz> wrote:
> >> Hi.
> >>
> >> We currently store mail in quarantine for a few users, for a set period
> >> of days. this includes non spam. Some of these clients have messages
> >> numbering in the thousands. Now, obviously releasing all of these
> >> messages with mailwatch is a bit difficult (Being that it releases one
> >> at a time).
> >>
> >> Is there an easilly scriptable way of either, sending these messages to
> >> the client, in such a way that they can actually see attachments and use
> >> them, or copying out the attachment, which I can put into a directory
> >> for the client to access. Sending standard text as attachments is easy
> >> enough, however the attached files also come through as text, which is
> >> less than helpful for things such as word documents.
> >>
> >> I currently have a script that runs through all the quarantine
> >> directories, copies needed messages into a directory, and either mails
> >> them off, or lets the client access them via ftp/smb/webdav
> >>
> >> Having mailscanner email messages to an email address does not really
> >> work in this situation.
> >>
> >> any ideas, or software that may be able to help?
> >
> > The Message Operations page will let you release them 50/page. You
> > find that on the reports page, so it is simple to limit to one
> > customer or other.
>
> Sorry to interject into this thread, but I only see where I can set these as
> Spam, Ham, or Forget these in Bayes or Clear the flags. All of this is with
> a "Learn" button. I do not see where I can release any of these. Could you
> explain a little please?
>
Right you are, my bad. I was looking at my rather ... non-standard...
MessageOps. Sorry.
Not sure I can produce a usable patch from this.

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