assp-user Mailing List for Anti-Spam SMTP Proxy Server

> win32:daemon for Activestate 5.8 is installed.  Is an update required?

No... If it installed you're good to go. But I'm glad to know it's
available. It wasn't until just recently.

> I'm using Windows 2000 server, 256MB RAM, AMD Athlon or Duron 700, CPU is
> typically idling.  The SMTP mail server is Lotus Domino 4.6.7.

Ok... It's not unlike our setup. But I think we have 512mb ram, and that
might help. However your spamdb is considerably smaller than ours, and the
dnsbl is the same. It bothers me that perl dies, though. Perl's not supposed
to do that.

> I think your suspicion regarding Perl crashing due to memory allocation
probs
> may be right.  MySQL is available for Win32 platforms, and I've heard good
> things about it, so should be fine.
>
> It may be good to have a seperation between the IP proxy interface and the
> database engine, such that if the database engine crashes, the SMTP server
> would still be capable of receiving e-mail.  Maybe have seperated
processes
> using interprocess communication (sockets, shared memory)?  I think people
> would like it if they knew that installing ASSP would not result in a
crises
> if it crashed.  Another advantage of seperating the proxy section could
have
> is the possibility of updating ASSP software w/o having to take down the
mail
> server.

Yes, yes and yes. All good points. It also makes restart time nominal.

> The simplicity of your program is fantastic, BTW.

Thanks. Now if I can just make it work without so many support requests
;-]...

j

Hi All.

I've released ASSP version 0.1.4 now. It's mostly bug fixes, but you
probably want them. This fixes the following problems since the last
release:

1) Mail sent sequentially without a RSET between messages could be garbled.
2) Mail servers which require client waits for the "254 Send data" after the
DATA directive are now supported.
3) Spam / nonspam logging work properly again.
4) $ChangeRoot="/my/new/root" works in the configuration file in *nix
5) Changed options with $DEBUG=1 to make it easier for me to isolate
problems.

As always, if you're upgrading, just make sure the path for your config file
is correct in assp.pl

Planned in the future release(s):
1) more bug fixes (thanks to all who have sent me debug files -- keep them
coming!)
2) a web configuration interface (ooooh!)
3) email interface for whitelist & spam reporting
4) a blacklist for senders you just don't like
5) option to run with the databases in a SQL process (ala MySQL) to reduce
the ram that ASSP needs
6) a kitchen sink :-) (If Mozilla can do it, why can't I?)

Enjoy!
John

Hi, Rainer.

We also use Mercury, so I can tell you that ASSP has a good chance of
working with your setup.

Yes, IMAP changes some header information, but, as it turns out, not in ways
that affect spam detection much. The minor changes that POP->IMAP transfer
causes are insignificant compared to the complete loss of headers in most
cases where mail is being forwarded (if it's not forwarded as an
attachment).

John

----- Original Message -----
From: "Rainer Schuetz" <ass...@ra...>
To: <ass...@li...>
Sent: Thursday, February 27, 2003 8:02 AM
Subject: RE: [Assp-user] IMAP-challenge



Hi John,

me again :-)
First a correction: I prefer spam before false /positives/, but you surely
thought that yourself.

I investigated a little more: The loss in the header only takes place when
moving a POP3-received mail to an IMAP-folder.
So the challenge is solved for me - I'll deploy IMAP instead of POP3.

You may want to include that in your doc's?


Thanks again (especially for that nice piece of software),

Rainer

> -----Original Message-----
> From: ass...@li...
> [mailto:ass...@li...]On Behalf Of Rainer
> Schuetz
> Sent: Thursday, February 27, 2003 3:40 PM
> To: ass...@li...
> Subject: [Assp-user] IMAP-challenge
>
>
>
> Hi John,
>
> just got washed my head by the folks of mercury-maillist because I prefer
spam before false negatives. So I
> decided to give your very promising approach a try... Very impressed till
now!
>
> The idea to put spam to an IMAP-mailbox looked very promising too for the
first moment (especially simple
> enough to get it deployed though the users base ;-) ). But I noticed in my
case a big(?) problem: The headers
> of the mail completely change! And as you (very good idea!!) use headers
for identifying spam we loose
> valuable information, don't we?
>
> Is the whole thing an Outlook2K-challenge or a Mercury-challenge (I use
Mercury/32 from www.pmail.com, over
> all a very good server just in my mind not RFC-compliant when using DNSBL
for spam fighting)?
>
>
>
> Thanks in advance, Rainer
>
>
> Original header:
>
> Received: from spooler by rs4u.com (Mercury/32 v3.32); 27 Feb 03 11:38:39
+0100
> X-Envelope-To: <ass...@ra...>
> Return-path: <ass...@li...>
> Received: from sc8-sf-list2.sourceforge.net (127.0.0.1) by rs4u.com
(Mercury/32 v3.32) with ESMTP ID MG00000D;
>    27 Feb 03 11:38:15 +0100
> Received: from 66.35.250.206 (66.35.250.206) by ASSP-nospam ; 27 Feb 03
10:38:14 -0000
> Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13]
helo=sc8-sf-list1.sourceforge.net)
> by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
> id 18oLQd-0003xx-00
> for <ass...@ra...>; Thu, 27 Feb 2003
02:38:15 -0800
> Date: Thu, 27 Feb 2003 02:38:06 -0800
> Subject:  Welcome to the "Assp-user" mailing list
> From: ass...@li...
> To: ass...@ra...
> X-No-Archive: yes
> X-Ack: no
> Sender: ass...@li...
> Errors-To: ass...@li...
> X-BeenThere: ass...@li...
> X-Mailman-Version: 2.0.9-sf.net
> Precedence: bulk
> List-Help: <mailto:ass...@li...?subject=help>
> List-Post: <mailto:ass...@li...>
> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/assp-user>,
> <mailto:ass...@li...?subject=subscribe>
> List-Id: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
<assp-user.lists.sourceforge.net>
> List-Unsubscribe:
<https://lists.sourceforge.net/lists/listinfo/assp-user>,
> <mailto:ass...@li...?subject=unsubscribe>
> List-Archive:
<http://sourceforge.net/mailarchive/forum.php?forum=assp-user>
> Message-Id: <E18...@sc...>
> X-Assp-Spam-Prob: 0.50000
> X-Text-Classification: good_mail
> X-POPFile-Link:
<http://127.0.0.1:8080/jump_to_message?view=popfile1151=1.msg>
>
>
> Header after moving the mail to the IMAP-Folder:
>
> From: <ass...@li...>
> Sender: <ass...@li...>
> To: <ass...@ra...>
> Subject: Welcome to the "Assp-user" mailing list
> Date: Thu, 27 Feb 2003 11:38:06 +0100
> Message-ID: <E18...@sc...>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
> Importance: Normal
> X-Envelope-To: <ass...@ra...>
> X-POPFile-Link:
<http://127.0.0.1:8080/jump_to_message?view=popfile1151=1.msg>
> X-Text-Classification: good_mail
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> X-OlkEid: E16402207940071085880C4A9F72BB21CE340CC6
> X-Assp-Spam-Prob: 0.50000
> X-Ack: no
> X-BeenThere: ass...@li...
> X-Mailman-Version: 2.0.9-sf.net
> List-Help: <mailto:ass...@li...?subject=help>
> List-Subscribe:
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-user-r
eq...@li...?subject=subscribe>
List-Unsubscribe:
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-user-r
eq...@li...?subject=unsubscribe>
X-No-Archive: yes
X-PMFLAGS: 34078848 0 8 3C0E23FA.CNM



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Assp-user mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-user



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Assp-user mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-user

Great - can't wait ... :-)

Thank you,
Michael


> -----Urspr=FCngliche Nachricht-----
> Von: ass...@li...=20
> [mailto:ass...@li...] Im Auftrag von=20
> John Hanna
> Gesendet: Donnerstag, 27. Februar 2003 00:45
> An: ass...@li...
> Betreff: Re: [Assp-user] ASSP 0.1.3 redlist addresses won't=20
> be rejected
>=20
>=20
> Ok. That makes sense. I'll try to add it in a soon coming release.
>=20
> John
> ----- Original Message -----
> From: <as...@cr...>
> To: <ass...@li...>
> Sent: Wednesday, February 26, 2003 3:19 PM
> Subject: AW: [Assp-user] ASSP 0.1.3 redlist addresses won't=20
> be rejected
>=20
>=20
> Hi John,
>=20
> I've two customers that suffer from receiving lots of=20
> unwanted "product promotion mails" (not the kind of generic=20
> spam normal users will get) based on their business. In most=20
> cases each mail contains products and prices (different=20
> content, not much common words) so putting the into=20
> errors/spam did not block these mails so far. That's why I=20
> would like to have the ability to block mails by the senders=20
> address. I know this can be also achived by using appropriate=20
> sendmail features, but this would cause a "two point"=20
> administration fighting spam.
>=20
> Therefore having a black list can be found on my wish list ;-)
>=20
> Thanks,
> Michael
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: ass...@li...
> > [mailto:ass...@li...] Im Auftrag von John=20
> > Hanna
> > Gesendet: Mittwoch, 26. Februar 2003 22:27
> > An: ass...@li...
> > Betreff: Re: [Assp-user] ASSP 0.1.3 redlist addresses won't be=20
> > rejected
> >
> >
> > Hi. The redlist is not a black list. Addresses on the=20
> redlist simply=20
> > can't add to the whitelist.
> >
> > In my experience I have not found that blacklisting email=20
> addresses is=20
> > of any value. Help me understand why you want to do that?
> >
> > John
> > ----- Original Message -----
> > From: <as...@cr...>
> > To: <ass...@li...>
> > Sent: Saturday, February 22, 2003 1:20 AM
> > Subject: [Assp-user] ASSP 0.1.3 redlist addresses won't be rejected
> >
> >
> > >
> > > Hi,
> > >
> > > I'm running 0.1.3 on linux (Perl 5.8).
> > > I've tried to add some mail addresses to the redlist ()and
> > sucessfully
> > > did, according to perl list.pl r?<address>
> > > But mails from redlist address still pass ASSP an get logged in=20
> > > maillog.txt as "message ok"?!
> > >
> > > Thanks,
> > > Michael
> > >
> > > BTW - thanks John for all your efforts. I like the idea=20
> of blocking=20
> > > SPAM when it arrives. Great code so far!
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: SlickEdit Inc. Develop
> > an edge. The
> > > most comprehensive and flexible code editor you can use.
> > Code faster.
> > > C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.=20
> > > www.slickedit.com/sourceforge=20
> > > _______________________________________________
> > > Assp-user mailing list
> > > Ass...@li...=20
> > > https://lists.sourceforge.net/lists/listinfo/assp-user
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Scholarships for Techies! Can't=20
> > afford IT training? All 2003 ictp students receive=20
> scholarships. Get=20
> > hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.=20
> > www.ictp.com/training/sourceforge.asp
> > _______________________________________________
> > Assp-user mailing list
> > Ass...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/a> ssp-user
> >
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!=20
> Can't afford IT training? All 2003 ictp students receive=20
> scholarships. Get hands-on training in Microsoft, Cisco, Sun,=20
> Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Assp-user mailing list
> Ass...@li...=20
> https://lists.sourceforge.net/lists/listinfo/a> ssp-user
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!=20
> Can't afford IT training? All 2003 ictp students receive=20
> scholarships. Get hands-on training in Microsoft, Cisco, Sun,=20
> Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Assp-user mailing list
> Ass...@li...=20
> https://lists.sourceforge.net/lists/listinfo/a> ssp-user
>=20
>=20

Hi John,=20

me again :-)
First a correction: I prefer spam before false /positives/, but you =
surely thought that yourself.

I investigated a little more: The loss in the header only takes place =
when moving a POP3-received mail to an IMAP-folder.
So the challenge is solved for me - I'll deploy IMAP instead of POP3.

You may want to include that in your doc's?


Thanks again (especially for that nice piece of software),

Rainer

> -----Original Message-----
> From: ass...@li...
> [mailto:ass...@li...]On Behalf Of Rainer
> Schuetz
> Sent: Thursday, February 27, 2003 3:40 PM
> To: ass...@li...
> Subject: [Assp-user] IMAP-challenge
>=20
>=20
>=20
> Hi John,
>=20
> just got washed my head by the folks of mercury-maillist because I =
prefer spam before false negatives. So I=20
> decided to give your very promising approach a try... Very impressed =
till now!
>=20
> The idea to put spam to an IMAP-mailbox looked very promising too for =
the first moment (especially simple=20
> enough to get it deployed though the users base ;-) ). But I noticed =
in my case a big(?) problem: The headers=20
> of the mail completely change! And as you (very good idea!!) use =
headers for identifying spam we loose=20
> valuable information, don't we?=20
>=20
> Is the whole thing an Outlook2K-challenge or a Mercury-challenge (I =
use Mercury/32 from www.pmail.com, over=20
> all a very good server just in my mind not RFC-compliant when using =
DNSBL for spam fighting)?=20
>=20
>=20
>=20
> Thanks in advance, Rainer
>=20
>=20
> Original header:
>=20
> Received: from spooler by rs4u.com (Mercury/32 v3.32); 27 Feb 03 =
11:38:39 +0100
> X-Envelope-To: <ass...@ra...>
> Return-path: <ass...@li...>
> Received: from sc8-sf-list2.sourceforge.net (127.0.0.1) by rs4u.com =
(Mercury/32 v3.32) with ESMTP ID MG00000D;
>    27 Feb 03 11:38:15 +0100
> Received: from 66.35.250.206 (66.35.250.206) by ASSP-nospam ; 27 Feb =
03 10:38:14 -0000
> Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] =
helo=3Dsc8-sf-list1.sourceforge.net)
> 	by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 =
(Debian))
> 	id 18oLQd-0003xx-00
> 	for <ass...@ra...>; Thu, 27 Feb 2003 =
02:38:15 -0800
> Date: Thu, 27 Feb 2003 02:38:06 -0800
> Subject:  Welcome to the "Assp-user" mailing list
> From: ass...@li...
> To: ass...@ra...
> X-No-Archive: yes
> X-Ack: no
> Sender: ass...@li...
> Errors-To: ass...@li...
> X-BeenThere: ass...@li...
> X-Mailman-Version: 2.0.9-sf.net
> Precedence: bulk
> List-Help: =
<mailto:ass...@li...?subject=3Dhelp>
> List-Post: <mailto:ass...@li...>
> List-Subscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,
> 	<mailto:ass...@li...?subject=3Dsubscribe>
> List-Id: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy =
<assp-user.lists.sourceforge.net>
> List-Unsubscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,
> 	=
<mailto:ass...@li...?subject=3Dunsubscribe>
> List-Archive: =
<http://sourceforge.net/mailarchive/forum.php?forum=3Dassp-user>
> Message-Id: <E18...@sc...>
> X-Assp-Spam-Prob: 0.50000
> X-Text-Classification: good_mail
> X-POPFile-Link: =
<http://127.0.0.1:8080/jump_to_message?view=3Dpopfile1151=3D1.msg>
>=20
>=20
> Header after moving the mail to the IMAP-Folder:
>=20
> From: <ass...@li...>
> Sender: <ass...@li...>
> To: <ass...@ra...>
> Subject: Welcome to the "Assp-user" mailing list
> Date: Thu, 27 Feb 2003 11:38:06 +0100
> Message-ID: <E18...@sc...>
> MIME-Version: 1.0
> Content-Type: text/plain;
> 	charset=3D"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
> Importance: Normal
> X-Envelope-To: <ass...@ra...>
> X-POPFile-Link: =
<http://127.0.0.1:8080/jump_to_message?view=3Dpopfile1151=3D1.msg>
> X-Text-Classification: good_mail
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> X-OlkEid: E16402207940071085880C4A9F72BB21CE340CC6
> X-Assp-Spam-Prob: 0.50000
> X-Ack: no
> X-BeenThere: ass...@li...
> X-Mailman-Version: 2.0.9-sf.net
> List-Help: =
<mailto:ass...@li...?subject=3Dhelp>
> List-Subscribe:=20
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-use=
r-r...@li...?subject=3Dsubscribe>
List-Unsubscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-use=
r-r...@li...?subject=3Dunsubscribe>
X-No-Archive: yes
X-PMFLAGS: 34078848 0 8 3C0E23FA.CNM



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Assp-user mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-user

Hi John,

just got washed my head by the folks of mercury-maillist because I =
prefer spam before false negatives. So I decided to give your very =
promising approach a try... Very impressed till now!

The idea to put spam to an IMAP-mailbox looked very promising too for =
the first moment (especially simple enough to get it deployed though the =
users base ;-) ). But I noticed in my case a big(?) problem: The headers =
of the mail completely change! And as you (very good idea!!) use headers =
for identifying spam we loose valuable information, don't we?=20

Is the whole thing an Outlook2K-challenge or a Mercury-challenge (I use =
Mercury/32 from www.pmail.com, over all a very good server just in my =
mind not RFC-compliant when using DNSBL for spam fighting)?=20



Thanks in advance, Rainer


Original header:

Received: from spooler by rs4u.com (Mercury/32 v3.32); 27 Feb 03 =
11:38:39 +0100
X-Envelope-To: <ass...@ra...>
Return-path: <ass...@li...>
Received: from sc8-sf-list2.sourceforge.net (127.0.0.1) by rs4u.com =
(Mercury/32 v3.32) with ESMTP ID MG00000D;
   27 Feb 03 11:38:15 +0100
Received: from 66.35.250.206 (66.35.250.206) by ASSP-nospam ; 27 Feb 03 =
10:38:14 -0000
Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] =
helo=3Dsc8-sf-list1.sourceforge.net)
	by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 =
(Debian))
	id 18oLQd-0003xx-00
	for <ass...@ra...>; Thu, 27 Feb 2003 =
02:38:15 -0800
Date: Thu, 27 Feb 2003 02:38:06 -0800
Subject:  Welcome to the "Assp-user" mailing list
From: ass...@li...
To: ass...@ra...
X-No-Archive: yes
X-Ack: no
Sender: ass...@li...
Errors-To: ass...@li...
X-BeenThere: ass...@li...
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
List-Help: =
<mailto:ass...@li...?subject=3Dhelp>
List-Post: <mailto:ass...@li...>
List-Subscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,
	<mailto:ass...@li...?subject=3Dsubscribe>
List-Id: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy =
<assp-user.lists.sourceforge.net>
List-Unsubscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,
	<mailto:ass...@li...?subject=3Dunsubscribe>
List-Archive: =
<http://sourceforge.net/mailarchive/forum.php?forum=3Dassp-user>
Message-Id: <E18...@sc...>
X-Assp-Spam-Prob: 0.50000
X-Text-Classification: good_mail
X-POPFile-Link: =
<http://127.0.0.1:8080/jump_to_message?view=3Dpopfile1151=3D1.msg>


Header after moving the mail to the IMAP-Folder:

From: <ass...@li...>
Sender: <ass...@li...>
To: <ass...@ra...>
Subject: Welcome to the "Assp-user" mailing list
Date: Thu, 27 Feb 2003 11:38:06 +0100
Message-ID: <E18...@sc...>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=3D"iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-Envelope-To: <ass...@ra...>
X-POPFile-Link: =
<http://127.0.0.1:8080/jump_to_message?view=3Dpopfile1151=3D1.msg>
X-Text-Classification: good_mail
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-OlkEid: E16402207940071085880C4A9F72BB21CE340CC6
X-Assp-Spam-Prob: 0.50000
X-Ack: no
X-BeenThere: ass...@li...
X-Mailman-Version: 2.0.9-sf.net
List-Help: =
<mailto:ass...@li...?subject=3Dhelp>
List-Subscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-use=
r-r...@li...?subject=3Dsubscribe>
List-Unsubscribe: =
<https://lists.sourceforge.net/lists/listinfo/assp-user>,<mailto:assp-use=
r-r...@li...?subject=3Dunsubscribe>
X-No-Archive: yes
X-PMFLAGS: 34078848 0 8 3C0E23FA.CNM

Ok. That makes sense. I'll try to add it in a soon coming release.

John
----- Original Message -----
From: <as...@cr...>
To: <ass...@li...>
Sent: Wednesday, February 26, 2003 3:19 PM
Subject: AW: [Assp-user] ASSP 0.1.3 redlist addresses won't be rejected


Hi John,

I've two customers that suffer from receiving lots of unwanted "product
promotion mails" (not the kind of generic spam normal users will get)
based on their business.
In most cases each mail contains products and prices (different content,
not much common words) so putting the into errors/spam did not block
these mails so far.
That's why I would like to have the ability to block mails by the
senders address. I know this can be also achived by using appropriate
sendmail features, but this would cause a "two point" administration
fighting spam.

Therefore having a black list can be found on my wish list ;-)

Thanks,
Michael

> -----Ursprüngliche Nachricht-----
> Von: ass...@li...
> [mailto:ass...@li...] Im Auftrag von
> John Hanna
> Gesendet: Mittwoch, 26. Februar 2003 22:27
> An: ass...@li...
> Betreff: Re: [Assp-user] ASSP 0.1.3 redlist addresses won't
> be rejected
>
>
> Hi. The redlist is not a black list. Addresses on the redlist
> simply can't add to the whitelist.
>
> In my experience I have not found that blacklisting email
> addresses is of any value. Help me understand why you want to do that?
>
> John
> ----- Original Message -----
> From: <as...@cr...>
> To: <ass...@li...>
> Sent: Saturday, February 22, 2003 1:20 AM
> Subject: [Assp-user] ASSP 0.1.3 redlist addresses won't be rejected
>
>
> >
> > Hi,
> >
> > I'm running 0.1.3 on linux (Perl 5.8).
> > I've tried to add some mail addresses to the redlist ()and
> sucessfully
> > did, according to perl list.pl r?<address>
> > But mails from redlist address still pass ASSP an get logged in
> > maillog.txt as "message ok"?!
> >
> > Thanks,
> > Michael
> >
> > BTW - thanks John for all your efforts. I like the idea of blocking
> > SPAM when it arrives. Great code so far!
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SlickEdit Inc. Develop
> an edge. The
> > most comprehensive and flexible code editor you can use.
> Code faster.
> > C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> > www.slickedit.com/sourceforge
> > _______________________________________________
> > Assp-user mailing list
> > Ass...@li...
> > https://lists.sourceforge.net/lists/listinfo/assp-user
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!
> Can't afford IT training? All 2003 ictp students receive
> scholarships. Get hands-on training in Microsoft, Cisco, Sun,
> Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Assp-user mailing list
> Ass...@li...
> https://lists.sourceforge.net/lists/listinfo/a> ssp-user
>
>



-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Assp-user mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-user

Hi John,

I've two customers that suffer from receiving lots of unwanted "product
promotion mails" (not the kind of generic spam normal users will get)
based on their business.
In most cases each mail contains products and prices (different content,
not much common words) so putting the into errors/spam did not block
these mails so far.
That's why I would like to have the ability to block mails by the
senders address. I know this can be also achived by using appropriate
sendmail features, but this would cause a "two point" administration
fighting spam.

Therefore having a black list can be found on my wish list ;-)

Thanks,
Michael

> -----Urspr=FCngliche Nachricht-----
> Von: ass...@li...=20
> [mailto:ass...@li...] Im Auftrag von=20
> John Hanna
> Gesendet: Mittwoch, 26. Februar 2003 22:27
> An: ass...@li...
> Betreff: Re: [Assp-user] ASSP 0.1.3 redlist addresses won't=20
> be rejected
>=20
>=20
> Hi. The redlist is not a black list. Addresses on the redlist=20
> simply can't add to the whitelist.
>=20
> In my experience I have not found that blacklisting email=20
> addresses is of any value. Help me understand why you want to do that?
>=20
> John
> ----- Original Message -----
> From: <as...@cr...>
> To: <ass...@li...>
> Sent: Saturday, February 22, 2003 1:20 AM
> Subject: [Assp-user] ASSP 0.1.3 redlist addresses won't be rejected
>=20
>=20
> >
> > Hi,
> >
> > I'm running 0.1.3 on linux (Perl 5.8).
> > I've tried to add some mail addresses to the redlist ()and=20
> sucessfully=20
> > did, according to perl list.pl r?<address>
> > But mails from redlist address still pass ASSP an get logged in
> > maillog.txt as "message ok"?!
> >
> > Thanks,
> > Michael
> >
> > BTW - thanks John for all your efforts. I like the idea of blocking=20
> > SPAM when it arrives. Great code so far!
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SlickEdit Inc. Develop=20
> an edge. The=20
> > most comprehensive and flexible code editor you can use.=20
> Code faster.=20
> > C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.=20
> > www.slickedit.com/sourceforge=20
> > _______________________________________________
> > Assp-user mailing list
> > Ass...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/assp-user
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!=20
> Can't afford IT training? All 2003 ictp students receive=20
> scholarships. Get hands-on training in Microsoft, Cisco, Sun,=20
> Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Assp-user mailing list
> Ass...@li...=20
> https://lists.sourceforge.net/lists/listinfo/a> ssp-user
>=20
>=20

Yes, I think it is possible to add filters based on subject and body. =
What do you have in mind?

John
  ----- Original Message -----=20
  From: David Lagani=E8re=20
  To: John Hanna=20
  Sent: Saturday, February 22, 2003 5:35 PM
  Subject: Re: A little question


  Would it be possible to also add filters based on message subjets and =
body text? :)
  And by the way I really like your concept of using a "proxy". With a =
couple more features, you'll have
  the best anti-spam free software out there:)

  Thanks,
  David

  John Hanna wrote:

Hi. Good question. Your situation has not just spam users, but entire =
spam
domains... That's not a current configuration option, but it's not hard =
to
add. If you'd like I'll include it in the next release.

John
----- Original Message -----
From: "David Lagani=E8re" <sp...@se...>
To: <jh...@cp...>
Sent: Tuesday, February 18, 2003 4:04 PM
Subject: A little question


 =20
Hi!

My email is sp...@se... and often, I receive spam destined
for som...@bo.... Is there a way to deny everything
destined for *@box1.securinet.qc.ca and consider spam or something or
would I be better to check out sendmail documentation about that?

Thanks a lot,
David

   =20


 =20

Hi. The redlist is not a black list. Addresses on the redlist simply can't
add to the whitelist.

In my experience I have not found that blacklisting email addresses is of
any value. Help me understand why you want to do that?

John
----- Original Message -----
From: <as...@cr...>
To: <ass...@li...>
Sent: Saturday, February 22, 2003 1:20 AM
Subject: [Assp-user] ASSP 0.1.3 redlist addresses won't be rejected


>
> Hi,
>
> I'm running 0.1.3 on linux (Perl 5.8).
> I've tried to add some mail addresses to the redlist ()and sucessfully
> did, according to
> perl list.pl r?<address>
> But mails from redlist address still pass ASSP an get logged in
> maillog.txt as "message ok"?!
>
> Thanks,
> Michael
>
> BTW - thanks John for all your efforts. I like the idea of blocking SPAM
> when it arrives. Great code so far!
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
> The most comprehensive and flexible code editor you can use.
> Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> www.slickedit.com/sourceforge
> _______________________________________________
> Assp-user mailing list
> Ass...@li...
> https://lists.sourceforge.net/lists/listinfo/assp-user

Hi,

I'm running 0.1.3 on linux (Perl 5.8).
I've tried to add some mail addresses to the redlist ()and sucessfully
did, according to
perl list.pl r?<address>
But mails from redlist address still pass ASSP an get logged in
maillog.txt as "message ok"?!

Thanks,
Michael

BTW - thanks John for all your efforts. I like the idea of blocking SPAM
when it arrives. Great code so far!

Yes. You're right. I'm still not sure why I disabled logging... I guess I
wanted to do some test without messing up my maillog.

I did it in two places -- one was the return I already mentioned. This is
another. logmail is only called for messages < 10k.

Of course you would also have trouble saving messages in your spam / nonspam
logs if you're in *nix and are running as a user without permission to write
to the directory.

One more thing that will be in the next release. By the way, I got the
chroot jail working too.

john
----- Original Message -----
From: "David Stanton" <da...@ev...>
To: "'John Hanna'" <jh...@cp...>
Sent: Thursday, February 20, 2003 4:20 PM
Subject: RE: users which allow all mail


> I'm not sure but I'm betting line 513:
> #open(F,'>'.maillogFilename(@_)) && print F $m; close F;
>
> In sub logmail shouldn't be commented out....
>
> I was looking for a reason why I ceased to get any spam in my spam
> directory after the 0.1.3 upgrade...
>
> Do you think this might be it?
>

Hi. Michael Weremecki found a bug using ASSP connecting to the Microsoft IIS
mail service. It may affect other SMTP servers as well -- IIS discards data
in the same packet after the DATA directive. I have a version of ASSP which
waits for the 354 Send Data message now, but I don't plan to release it
until next week.

If you are trying to connect ASSP to the Microsoft IIS mail service, or
believe you have the same symptoms as Michael did, please email me
(jh...@cp...) and I'll send you the interim version (it'd be
something like 0.1.3b if it had a number).

John

------------------------
Michael's symptoms are:

When connected to ASSP, the client never seems to be able to close the
message.  If in telnet, the CRLF.CLRF gets no response (or CRLFCRLF.CRLF as
suggested by others).  In something like POSTIE, it sits there waiting
forever.  As a result the message never gets delivered.

I've noticed that many people are so eager to start using ASSP that they are
not properly setting up a collection of spam / nonspam. While I'm thrilled
for their enthusiasm, I'm also concerned that they will have dissapointing
results if their collections are not right.

In order to help prevent this I've uploaded a sample spam/nonspam starter
set. If you already have a healthy collection of spam / nonspam or your
email is not primarily in English you should ignore this.

If you are just getting started with ASSP, I reccomend this new startup
procedure. (I'll have this in the docs soon.)
1) Download the assp-0.1.3.zip archive, unpack it, and edit your config file
as described in the documentation.
2) Download the asspsmpl-0.1.tgz set (from
http://prdownloads.sourceforge.net/assp/asspsmpl-0.1.tgz?download) and
unpack it with tar -xzf asspsmpl-0.1.tgz (or with your favorite compression
tool). Move the sample notspam and spam directories into your ASSP folder
(as corresponds with your config file), and check that directory permissions
and ownership is as you want. (The ASSP process needs to be able to write to
these directories.)
3) Add any of your local spam or notspam to the collections if you desire.
(Use move2num.pl if you want to convert filenames to numbers.)
4) Use rebuildspamdb.pl to create your spam database -- Ideally you should
have about the same number of spam and nonspam words (sc= and hc= in the
output of the rebuildspamdb.pl program) +/- 5%.
5) Start assp as you would normally.
6) As assp runs it will gradually replace the seed database files with your
own site's spam and nonspam.
7) After a month you can delete the remaining seed files from the
collections -- check the file date to identify them.

Using the seed database will significantly reduce your chances of false
positivies (nonspam being blocked), although it will initially lower your
spam detection rate. However as your own site's spam and ham replace the
seed database this will quickly correct itself.

Enjoy!
John

Hi. I was just looking at the ASSP.sourceforge.net site and saw that there's
posts there from people having trouble with CRLF.CRLF not working and
actually needing CRLFCRLF.CRLF. I just ran a bunch of tests from both
windows and FreeBSD and couldn't get 0.1.3 to have any problems. If you are
using 0.1.3 and
1) you get occasional doubled messages
2) you can telnet to your mail server, but ASSP can't deliver mail through
it (at all or reliably)
3) you find an attachment with blank lines / missing / corrupted data
4) you find any other repeatable communication-related glitch

Please email this list with the following:
Assp version:
assp operating system:
email client:
client operating system:
message transport software:
message transport operating system:

If I don't hear from anybody I'll assume everything is working perfectly.

Thanks!
John

Yea. It could have been. I don't know the explanation of the bounce problem,
but if lines are being dropped, and they happened to be the .<cr><lf> line,
then that would explain it.

If it keeps happening though, let me know so I can know if I should cross
that off my bug list.

john
----- Original Message -----
From: "David Stanton" <da...@ev...>
To: "'John Hanna'" <jh...@cp...>
Sent: Friday, February 14, 2003 8:33 AM
Subject: RE: socket fix (for long attachments) AAACK


>
> Seems to have fixed the corruption problem. I hammered on it internally,
> externally, fast, and slow all morning, and it hasn't missed a byte.
>
> Do you think this might have been part of the bounce issue?
>

5>
Subject: assp 0.1.3 fix
Date: Fri, 14 Feb 2003 08:46:29 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Aaack... Steve, you're right. Line 520 is a "return;" and I had it in for
debugging. It should be deleted and the server restarted. I'll update the
release with that change.

if it's not one thing it's another....

john
----- Original Message -----
From: "Steve B" <st...@bo...>
To: "John Hanna" <jh...@cp...>
Sent: Friday, February 14, 2003 4:18 AM
Subject: assp 0.1.3


> John,
>
> Spam doesnt seem to be getting added since upgrading
>


----------------------------------------------------------------------------
----


>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.449 / Virus Database: 251 - Release Date: 27/01/2003
>

Hi all. I have the new release uploaded. It not only contains the bugfix for
big emails, it also has better spam filtering and support to allow specific
accounts to receive all mail. I need to clean up the documentation for
that -- spam addressed to two parties, one a spamlover and one a normal user
will still be blocked, and that's not clearly documented anywhere but in
this forum.

This bug fix may also resolve the other communication related errors noted
previously -- If you think assp is broken then try this release and let me
know if it is still broken.

I don't think it will fix the "Qmail reports <lf> with no <cr>" error. Still
have to find time to work on that one.

Thanks for your patience as ASSP continues to become all it can be.

John

Aaaack... I just realized I still have a debug line in that code. Instead
use this one:

   $buf='';
   if($fh->sysread($buf,4096)>0) {
    d(2);
    $this=$Con{$fh};
    $buf=$this->{_}.$buf;
    $bn=$lbn=-1;
    while(($bn=index($buf,"\n",$bn+1)) >= 0) {
     $s=substr($buf,$lbn+1,$bn-$lbn);
     #print DEBUG  "doing <$2>\n" if $DEBUG;
     #print $fgfh $s if $fgfh=$Con{$fh}->{ffh};
     ${$Con{$fh}}{getline}($fh,$s);
     last unless $Con{$fh};  # it's possible that the connection can be
deleted while there's still something in the buffer
     $lbn=$bn;
    }
    d(3);
    if($Con{$fh}) {
     ($this->{_})=substr($buf,$lbn+1);
     if(length($this->{_}) > 10000) {
      d(4);
      ${$Con{$fh}}{getline}($fh,$this->{_});
      ($this->{_})='';
     }
    }
   } else {
    d(5);
    done($fh);
   }



----- Original Message -----
From: "John Hanna" <jh...@cp...>
To: "David Stanton" <da...@ev...>
Cc: <ass...@li...>
Sent: Thursday, February 13, 2003 4:40 PM
Subject: socket fix (for long attachments)


> I finally found the offending section of code. I'll put a release up soon,
> but if you want to patch it yourself here's the fix.For me this starts on
> line 274, but it's likely to be different for you. Just search ASSP.pl for
> sysread and replace the section that matches this, then restart the
server.
>
> Sorry about this bug -- it's the kind of thing that should have shown up
> before. I guess that's why we need a community.
>
>
>    $buf='';
>    if($fh->sysread($buf,4096)>0) {
>     d(2);
>     $this=$Con{$fh};
>     $buf=$this->{_}.$buf;
>     $bn=$lbn=-1;
>     while(($bn=index($buf,"\n",$bn+1)) >= 0) {
>      $s=substr($buf,$lbn+1,$bn-$lbn);
>      #print DEBUG  "doing <$2>\n" if $DEBUG;
>      print $fgfh $s if $fgfh=$Con{$fh}->{ffh};
>      ${$Con{$fh}}{getline}($fh,$s);
>      last unless $Con{$fh};  # it's possible that the connection can be
> deleted while there's still something in the buffer
>      $lbn=$bn;
>     }
>     d(3);
>     if($Con{$fh}) {
>      ($this->{_})=substr($buf,$lbn+1);
>      if(length($this->{_}) > 10000) {
>       d(4);
>       ${$Con{$fh}}{getline}($fh,$this->{_});
>       ($this->{_})='';
>      }
>     }
>    } else {
>     d(5);
>     done($fh);
>    }
>
>

I finally found the offending section of code. I'll put a release up soon,
but if you want to patch it yourself here's the fix.For me this starts on
line 274, but it's likely to be different for you. Just search ASSP.pl for
sysread and replace the section that matches this, then restart the server.

Sorry about this bug -- it's the kind of thing that should have shown up
before. I guess that's why we need a community.


   $buf='';
   if($fh->sysread($buf,4096)>0) {
    d(2);
    $this=$Con{$fh};
    $buf=$this->{_}.$buf;
    $bn=$lbn=-1;
    while(($bn=index($buf,"\n",$bn+1)) >= 0) {
     $s=substr($buf,$lbn+1,$bn-$lbn);
     #print DEBUG  "doing <$2>\n" if $DEBUG;
     print $fgfh $s if $fgfh=$Con{$fh}->{ffh};
     ${$Con{$fh}}{getline}($fh,$s);
     last unless $Con{$fh};  # it's possible that the connection can be
deleted while there's still something in the buffer
     $lbn=$bn;
    }
    d(3);
    if($Con{$fh}) {
     ($this->{_})=substr($buf,$lbn+1);
     if(length($this->{_}) > 10000) {
      d(4);
      ${$Con{$fh}}{getline}($fh,$this->{_});
      ($this->{_})='';
     }
    }
   } else {
    d(5);
    done($fh);
   }

> <5.2.0.9.0.20030213044827.02870b48@192.168.1.55>
Subject: assp 0.1.2 (and previous) is broken for large attachments
Date: Thu, 13 Feb 2003 11:26:44 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

David Stanton just found a bug that causes ASSP to drop 57 bytes every
291840 bytes. I have not yet confirmed this, but we also have had problems
with large attachments becoming corrupted. It is a high priority for me to
look into it. It seems to be related to the way Perl handles sockets and so
it is difficult for me to diagnose and correct. Perhaps there's a socket
guru out there who would like to help resolve this issue?

John



----- Original Message -----
From: Steve B
To: John Hanna
Sent: Wednesday, February 12, 2003 9:52 PM
Subject: Re: assp 0.1.2


John,

From another forum

quote

There is currently at least one problem with ASSP up to version 0.1.2, it
currently drops 57 bytes every 285k transferred, corrupting any file
attachments. There have been other problems.

Nuff said I wouldn't try using it for production right now...

/quote

I have seen an odd broken mail where the headers show in the body in my
email client. I think they seemed to be the odd spam getting thru, so i just
put it down to badly formed messages. I have had a few doc attachments with
out problem.

Steve.

Because ASSP runs as a SMTP proxy, blocked mail always receives =
notification. The error message is customizable in the config file. The =
error is part of the SMTP conversation -- there's no need for ASSP to =
generate messages. This is especially useful because spam usually has an =
invalid bounce address.

john
  ----- Original Message -----=20
  From: Christopher Rath=20
  To: jh...@cp...=20
  Sent: Sunday, February 09, 2003 4:25 PM
  Subject: Question about ASSP


  Has anyone tried marrying Procmail with ASSP, for the purpose of =
sending a rejection email back to email from addresses not on the =
whitelist?

  =20

  Thanks,

  Christopher

5>
Subject: Re: assp 0.1.2
Date: Mon, 10 Feb 2003 16:33:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Yea... Thanks for that. Actually, the biggest bug with list.pl is that you
have to stop ASSP to use it, and that's not documented. I'm not quite sure
how to fix that either... I think list.pl needs to be incorporated into ASSP
somehow, but I haven't gotten that far yet... It's that "configuration"
interface I've been dreading...

The specific bug you mention can easily be fixed by changing the " to ' on
lines 9 and 21 -- I should have cought that.

I've changed mine and will include it in the next release.

john
----- Original Message -----
From: "Steve B" <st...@bo...>
To: "John Hanna" <jh...@cp...>
Sent: Monday, February 10, 2003 11:52 AM
Subject: Re: assp 0.1.2


> John,
>
> Any know bugs in the list.pl
>
> Usage:
>   perl list.pl {r}[+-?]address@where"
> In string, @yahoo now must be written as \@yahoo at list.pl line 9, near
> "@where.dom
> For example to find if jhanna@yahoo"
> Execution of list.pl aborted due to compilation errors.
>
>
> Steve
>


----------------------------------------------------------------------------
----


>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.449 / Virus Database: 251 - Release Date: 27/01/2003
>

I don't think so. I have never received an executable from someone I don't
email that hasn't been a virus. Note that people whom I email (and are
consequently on ASSP's whitelist) can send me executables. If you can find
10 people who want that as a feature let me know and I'll add it.

john
----- Original Message -----
From: "David Stanton" <da...@ev...>
To: "'John Hanna'" <jh...@cp...>
Sent: Wednesday, February 05, 2003 4:00 PM
Subject: RE: users which allow all mail


> Would it be better to make the file suffix filter optional by address
> too (but separate from the email filter)?
> I'm thinking about brushing up on my perl so I can help out a bit...
> (hate to be a leech)...
>
>
> > -----Original Message-----
> > From: John Hanna [mailto:jh...@cp...]
> > Sent: Wednesday, February 05, 2003 4:51 PM
> > To: David Stanton
> > Cc: ass...@li...
> > Subject: Re: users which allow all mail
> >
> >
> > I think this is a valid request. It's not a current option,
> > but I'll add it to my todo list. Look for another release in
> > a couple of weeks with an option like this.
> >
> > John
> > ----- Original Message -----
> > From: "David Stanton" <da...@ev...>
> > To: <jh...@cp...>
> > Sent: Wednesday, February 05, 2003 2:42 PM
> >
> >
> > > One suggestion.
> > >
> > > How about a configuration option to prevent any spam filtering on a
> > > list of specific email addresses?
> > >
> > > I just have one person using my server who just loves all
> > her mailing
> > > lists etc, but nobody else does. It would be nice if she
> > could be done
> > > on her own...
> > >
> > > Or did I miss the option already?
> > >
> >
> >
>

Just a P.S. on this... Turns up there's a slight hiccup. If a single message
is being sent to two recipients and one is a spam lover and one isn't, as a
proxy, ASSP dosen't have the ability to deliver mail to one and not the
other. It must choose to either maybe block them both, or pass them both
through. If ASSP's behavior is to allow them both, then if a spammer can
guess one of your spam-lover addresses (like perhaps postmaster) s/he could
use that that to spam everyone at your site. Because ASSP rarely blocks
non-spam anyway I've decided to make the program require that all delivery
addresses for an email be spam-lover addresses for the deliver-even-spam
subroutine to kick in.

Would that be ok? It means some rare spam could be blocked for a spam-lover,
but results in better integrety for the rest of us who hate spam.

Also note that most lists get through ASSP if there are enough samples in
the "good mail" collection.

John


----- Original Message -----
From: "John Hanna" <jh...@cp...>
To: "David Stanton" <da...@ev...>
Cc: <ass...@li...>
Sent: Wednesday, February 05, 2003 2:50 PM
Subject: Re: users which allow all mail


> I think this is a valid request. It's not a current option, but I'll add
it
> to my todo list. Look for another release in a couple of weeks with an
> option like this.
>
> John
> ----- Original Message -----
> From: "David Stanton" <da...@ev...>
> To: <jh...@cp...>
> Sent: Wednesday, February 05, 2003 2:42 PM
>
>
> > One suggestion.
> >
> > How about a configuration option to prevent any spam filtering on a list
> > of specific email addresses?
> >
> > I just have one person using my server who just loves all her mailing
> > lists etc, but nobody else does. It would be nice if she could be done
> > on her own...
> >
> > Or did I miss the option already?
> >
>