[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#685038: marked as done (ITP: mailscanner -- email gateway for virus scanning, spam and phishing detection)

Your message dated Fri, 24 Aug 2012 17:32:16 -0400
with message-id <20120824213215.GC6409@pug.qqx.org>
and subject line Rescinding ITP for mailscanner
has caused the Debian Bug report #685038,
regarding ITP: mailscanner -- email gateway for virus scanning, spam and phishing detection
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
685038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685038
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Aaron Schrab <aaron@schrab.com>

* Package name    : mailscanner
  Version         : 4.84.5.2
  Upstream Author : Julian Field <MailScanner@ecs.soton.ac.uk>
* URL             : http://www.mailscanner.info
* License         : GPL
  Programming Lang: Perl
  Description     : email gateway for virus scanning, spam and phishing detection

MailScanner is a email gateway virus-scanner and spam and
phishing-detector. It uses Exim, sendmail or postfix as its basis,
and supports clamav and some commercial virus scanning engines to do
the actual virus scanning. For spam detection MailScanner uses
spamassassin.

The action taken on virus, spam or phishing mails can be configured
with a flexible ruleset based on sender, receiver, scoring, etc.

Virus checking is disabled and spam checking is enabled by default.

--- End Message ---
--- Begin Message --- 
I am no longer intending to resurrect the mailscanner package.
I'd thought that bug#631537 had been fixed by newer upstream releases, at least initial testing showed that the situation had improved. But, after several releases that address part of that problem, it is still not completely solved.
Also while working on updating the package, I found a number of issues with the code base that make me distrust the upstreams work.
I have now switched to using the amavisd-new package for doing my spam and virus filtering, so I will not be producing updated versions of this package.
--- End Message ---
Reply to: