>From: "Security" <[EMAIL PROTECTED]>
> I'm very interested in running SpamAssassin site-wide on a few of my
>machines. Currently I'm Running Postfix for an MTA. Can anyone point me
>to some good documentation on setting up SpamAssassin
>With Postfix? I've done some searches but can't seem to
/SpamAssassin/SMTP/SmartHost.pm
Coulda been hazardous mixing my apples with my oranges, but, in this
case, it worked.
-Original Message-
From: Stewart, John [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 5:33 PM
To: 'Craig Hughes'; '[EMAIL PROTECTED]';
'[E
me, I have a copy of Ian's newest script here. Unless he objects,
I can provide a copy of it for you.
-Original Message-
From: Stewart, John [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:32 PM
To: '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Cc: Greg Bla
When I find something that SpamAssassin can't filter, I'll just add it
to the filter tables of my MTA (Postfix). It can filter based on IP
address, "HELO" host, words in the subject line, etc.
Spam Assassin does a better job than doing it yourself, but, in my case,
since I know nobody in mainlan
It probably doesn't apply, but then again... anything to help narrow it
down, right?
I successfully have the proxyfilter working on a FreeBSD box, using
Postfix.
So, it'd probably point towards milter rather than FreeBSD.
( Just in case someone was thinking that FreeBSD was what one should
avo
866 is. 855 and 844 are planned to be.
I work for a long distance company, and have had to hold the hands of
many of our customers as they reprogrammed their PBXes to realize that
866 shouldn't be restricted as if it actually cost them something...
-Original Message-
From: Craig Hughes
Hi, folks. I've made a lot of noise here, and received a lot of useful
information from many of you. So, I thought that it would be a good
time to give a little bit back.
I finally got the "spamproxyd" smtp filter going with Postfix, and it
was all just one little thing that was missing.
In /
ponse on SpamProxy Question Now
another
> On 31 Jan 2002 at 23:04, Greg Blakely wrote:
>
> > I actually DO have spamassassin working with procmail, quite nicely,
> > thank you.
> >
> > But I have a situation where not all my received mail is for users homed
>
Hi folks.
I'm the one who wrote the other day to ask if anyone had heard of the
error I mentioned regarding SpamProxy, and the silence was deafening.
So, I wrote to the author, and he'd not heard of anything like it. So,
I'm left to ask a very BASIC question:
I actually DO have spamassassin wo
t can be found in the SpamAssassin source directory. I can't find
it, though. So, I'm at a loss. With no patch in the source directory, has
the Mail::Audit module been fixed? If so, why am I getting this error?
Sorry if this is a
10 matches
Mail list logo
