I'm trying to get 3.2.4 up and going with amavisd/dual sendmail, and
trying to incorporate Mail::SpamAssassin::Plugin::SPF.
To attempt a test, I'm intentionally spoofing an email address whose
domain has an SPF record and sending it through a test machine.
I've added X-Envelope-Sender to the he
Matt Kettler <[EMAIL PROTECTED]> wrote on 03/05/2008 08:07:49 PM:
> [image removed]
>
> Re: Adding custom Mime headers
>
> Matt Kettler
>
> to:
>
> leonard.gray
>
> 03/05/2008 08:07 PM
>
> Cc:
>
> users
>
> [EMAIL PROTECTED] wrote:
> >
> > I'm trying to get the RelayCountry plugin runnin
Karsten Bräckelmann <[EMAIL PROTECTED]> wrote on 03/05/2008 01:13:11
PM:
> [image removed]
>
> Re: Adding custom Mime headers
>
> Karsten Bräckelmann
>
> to:
>
> users
>
> 03/05/2008 01:13 PM
>
> On Wed, 2008-03-05 at 11:05 -0500, [EMAIL PROTECTED] wrote:
> >
> > I'm trying to get the Re
der isn't working for
me. No Amavisd or Exim in front.
Does anyone have any ideas or experience with this?
Leonard Gray
Information Technology Services, Washington Savannah River Company
Collaborative Technologies Administration
Internet: [EMAIL PROTECTED]
Phone: (803) 725-6022
<>
Sorry to be "late to the dance",
but is there a relatively simple way to have sa-update traverse a proxy
based firewall? We'd need to provide username / password to get out.
Thanks!
Leonard Gray
Groupware and Email Administration
Information Technology Services, Washington
Sorry if this has been asked ad-nauseum,
but by default, the Mail::SpamAssassin::Plugin::AWL is enabled.
From what I've been able to find on
this topic, AWL is intended to be a user or system maintained database
of whitelisted "from" addresses.
We did nothing to create or populate
this database,
I'm wanting to test SA's SPF implementation
here by running a test message through a "sandbox" machine that
is configured like our production environment.
Our domain has an SPF record, and I've
made sure that it's reflected on our internal network. I've tested
SPF
as a standalone implementation,
Sorry to ask a question I *think* I've
seen the answer to, but should I not use SARE's antidrug.cf with SA 3.1.0?
I think I remember seeing something about that on this list.
Thanks!
We jacked up the scoring on HTML_IMAGE_ONLY_12
to a 5, and are catching about 90% of these now with almost no false
positives.
"Jack Gostl"
<[EMAIL PROTECTED]>
03/07/2006 07:26 AM
To
cc
Subject
All image spam
I've seen some references to this in threads,
but I didn't see
Our intrusion detection software started
picking up thousands of access attempts to /etc/shadow (the UNIX user password
store) shortly after installing SpamAssassin on our mail gateway.
Could one of the developers comment
on why SA might be doing this and/or if this is even an intent? (Running
SA
I finally got curl installed and "fixed".
The problem with both is our proxy server obviously doesn't handle
"basic" proxy authentication. There's a curl option that's
something like --any_authentication that tries all different kinds of auth.
That finally got me through.
I have been only tryi
I'm trying to get rulesdejour going
here and having one heck of a time making it through my proxy.
I would rather use wget than curl (curl
has too many pre-reqs), and have it installed and configured
to access the proxy server. I
have the proxy_user and proxy_password configured in my
/usr/loc
I thought I had read through all of
the necessary and available docs, but cannot find a way to
1) Disable SPF support (we already have
that running without SA)
2) Disable DB_File (BerkeleyDB) support.
We are having huge problems getting DB_File running on our machine
and really don't need this,
Thanks for your efforts and tests. I
think I found the problem.
The production server we are trying
to run on only has 128mb of memory. I can't believe we got a machine
with that little, but it happened. I might try running only 2 children
of SPAMD, refreshing the processes every 5 messages or
I've been experiencing and documenting
a pretty severe performance problem with SA versions 3.0.1 through 3.1x
(nightly) under Solaris 8 and 9, Perl 5.8.3.
We're running Sendmail 8.12.11, and
I've tried milters MimeDefang and Spamass-milter.
I initially thought this problem was
related to the
We have been waiting patiently to resolve
the swapping problem caused by SA 3.0.x's forking algorithms. I have
been watching anxiously over the progress of 3.1 and am very encouraged
about the new pre-forking code.
However, we're have a real need to get
SA installed now for "the never-ending bat
I'd love to implement SPF checks in
SA rather than having to run two milters on our sendmail, but there's a
fundamental flaw in the whitelisting for SPF.
It looks like the whitelist applies
to internet domains or email addresses. Whitelisting those automatically
defeats the purpose of SPF. If y
Martin,
I'm having a little problem with the
patch, as I'm admittedly not extremely "perl savvy". Perhaps
you can see what I might be doing wrong and steer me in the right direction.
1. Saving both patches as text files (named patch1 and patch2 respectively)
into the /Mail-SpamAssassin-3.0.1 d
Hi Alan,
I found out the hard way about this
problem as well. Here's the response I got previously on this issue:
Martin Hepworth <[EMAIL PROTECTED]>
01/19/2005 01:02 PM
To
[EMAIL PROTECTED]
cc
users@spamassassin.apache.org
Subject
Re: New to SA, problems with production
speed
Thanks Martin, that helps let me know
I haven't completely lost it.
I downloaded the patches, and am inexperienced
in how to use "patch". Tried several things, but assumed
to place the patch files in /SpamAssassin-3.0.2 directory, and then ran
patch -i, which didn't really work.
Is the patch pr
This is my first post here, and liable to be a doozie!
Running SA 3.0.2 with Sendmail 8.12.11,
hooked in with spamass-milter 0.2.0, all under Solaris 9. I also
have SPF-Milter installed from spf.pobox.com. SPF is the first milter,
SA is the second
in the sendmail.cf file.
Sendmail running onl
21 matches
Mail list logo
