Release from quarantine

[Stephen Swaney]

Being able to release a quarantined message using a GUI will be an
immensely helpful tool.

While the "attachment" feature that Julian added has been a big success
with our users, I've been thinking a bit about how to handle spam and
the interaction of the recipient with an overworked help desk. Rolling
out MailScanner and SpamAssassin can be an interesting experience for a
help desk.  Often (unfortunately) the end users are not properly
prepared for the results of virus and spam filtering.

The new report message options Julian has added will definitely reduce
the number of "confused" recipients, but in a perfect world, the spam
delivery process might work something like this:

  Subject: {Spam?} gjjansen mdkbymfa
           [Msg ID: h78D8sfM014806]


Our MailScanner believes that this message sent to you

    From: 47dotb at erie.net
    Subject: gjansen mdkbymfa

is Unsolicited Commerial Email (spam) and has been quarantined. This
message will be stored for 7 days and then deleted. If you are sure that
this message is incorrectly thought to be Spam, please forward this
email to spamsender at helpdesk.somewhere.com and the quarantined message
will be forwarded to you.

If you want to have messages from this Sender never marked as spam,
please forward this email to whitelist at helpdesk.somewhere.com


spamsender at helpdesk.somewhere.com would be a pipe to to a process that
releases the message from quarantine.

whitelist at helpdesk.somewhere.com would be a pipe to to a process that
whitelists the sender for this recipient.

While these scripts would need to be different for varying site
configurations, MTAs and user preference storage alternatives, some
sample scripts could be provided for MailScanner users who wish to
implement this feature.

Just my 2 cents and hopefully not a "feature bloat" issue

Steve Swaney
Steve at FSL.com

On Fri, 2003-08-08 at 07:07, Steve Freegard wrote:

> Hi Martin,
>
> I've been working on it this morning - the good news is that what is written
> so far isn't MTA specific as it uses the MIME_Mail pear class to re-send the
> mail as an attachement.
>
> It does however rely on having 'Quarantine Whole Messages As Queue Files =
> no' and 'xxx Spam Actions = store ...' for it to work correctly (the
> resulting quarantine files are then stored as message/rfc822 files).
>
> I've still got a fair amount of work to do to sort out permissions and
> polish off the UI, but there will be something workable for the 0.3 release.
>
> Kind regards,,
> Steve.
>



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
Postmaster at FSL.com
Fortress Systems, Ltd.
Email Gateways
info at FSL.com
www.FSL.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20030808/434a9f1d/attachment.html