How do I scan internal to internal, exchange server only email? It
never seems to leave the exchange server.
If your clients connect directly to the Exchange server there would be no
reason for mail addressed to local recipients to leave the box.
--
Michael Scheidell, CTO
I imagine you o
Sorry for the repeat and response to my own message. Must
have skipped over the tail end of Gary's response. Must
read more thorough next time.
On Mon, 22 Jan 2007 05:02:25 +
<[EMAIL PROTECTED]> wrote:
On Sun, 21 Jan 2007 22:00:26 -0500
Michael Scheidell <[EMAIL PROTECTED]> wrote:
I can
My question is: why would you want to scan internal-only email? Are your
users sending spam to other users? If so, have an Acceptable Use Policy that
forbids such things and then if it happens you can take appropriate action
against your user.
On Sun, Jan 21, 2007 at 09:55:12PM -0700, Gary V wro
On Sun, 21 Jan 2007 22:00:26 -0500
Michael Scheidell <[EMAIL PROTECTED]> wrote:
I can scan incoming spam by MX record on my external box
before it gets
to exchange.server.
I can can outgoing email by setting the external box as
smarthost in
exchange.
How do I scan internal to internal, excha
I can scan incoming spam by MX record on my external box before it gets
to exchange.server.
I can can outgoing email by setting the external box as smarthost in
exchange.
How do I scan internal to internal, exchange server only email? It
never seems to leave the exchange server.
If your client
I can scan incoming spam by MX record on my external box before it gets
to exchange.server.
I can can outgoing email by setting the external box as smarthost in
exchange.
How do I scan internal to internal, exchange server only email? It
never seems to leave the exchange server.
--
Michael Sche
On Sun, Jan 21, 2007 at 07:43:11PM -0500, Tom Allison wrote:
> But call this directly from my "main" script eg:
>
> Mail::SpamAssassin::Logger::add(method => 'file', filename =>
> '/var/log/syslog')
> ??
Yes, but I wouldn't log to the same file that syslog is going to write to...
Just use the sy
Theo Van Dinter wrote:
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging
file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::Sp
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
> When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
> How do you capture the output from the debug to syslog or other logging
> file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::SpamAssassin::Logger::a
When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging file?
I can run it via a command line but if I run Mail::SpamAssassin under a
daemon/fork process similar to Net::Server::PreForkSimple I can't seem
On Sun, Jan 21, 2007 at 10:14:51PM +0100, J. W. Andersen wrote:
> >It sounds more like your system isn't properly passing the message to SA.
> As all my body tests seem to work OK, I guess the messages *are* passed
> to SA. Unless there is
> reason to believe, that postfix or amavis should block t
Greetings
My SA 3.1.7 installs run as user spamd
My /home/spamd/.spamassassin directory looks like this
-rw--- 1 spamd spamd 5210112 Jan 21 14:25 auto-whitelist
-rw--- 1 spamd spamd 60864 Jan 21 14:25 bayes_journal
-rw--- 1 spamd spamd 2711552 Jan 21 14:18 bayes_seen
-rw---
Theo Van Dinter wrote:
On Sun, Jan 21, 2007 at 09:30:48PM +0100, J. W. Andersen wrote:
Am I severely misunderstanding something ? Such as definitions of header
(subject) and body ?
It sounds more like your system isn't properly passing the message to SA.
As all my body tests seem
On Sun, Jan 21, 2007 at 09:30:48PM +0100, J. W. Andersen wrote:
> Am I severely misunderstanding something ? Such as definitions of header
> (subject) and body ?
It sounds more like your system isn't properly passing the message to SA.
> The Scenario here is SuSE 10. SpamAssassin is 3.1.7 (initia
I seem to have a problem processing headers in spamassassin.
First, on every single mail I receive, i get a MISSING_SUBJECT
condition, and the mail does have a valid subject.
Second, I can never make a match in the subject line.
In the local.cf, I have the following:
..
OK, I removed the bayes directory such that /var/cache/spampd is a
directory but there is nothing 'bayes' in that directory (no file, no dir)
cd /var/cache/spampd
rm -rf bayes
/etc/spampd.conf:
bayes_path /var/cache/spampd/bayes
restart and
[6651] dbg: bayes: no dbs present, cannot
On Sunday 21 January 2007 16:44, Matt Kettler wrote:
> Tom Allison wrote:
> > [5411] info: config: SpamAssassin failed to parse line,
> > "/var/cache/spampd/bayes" is not valid for "bayes_path", skipping:
> > bayes_path /var/cache/spampd/bayes
> >
> > debug helped. But what does it mean?
>
> Is th
Matt Kettler wrote:
Tom Allison wrote:
Tom Allison wrote:
I just did an install of spampd on my debian box and am working my
way through the different configurations...
First, I found that /var/cache/spampd/awl had the wrong permissions
so I changed that and I stopped getting errors. Interest
Hi all --
there's an extremely unofficial SpamAssassin 3.2.0 tarball
available at:
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.tar.bz2
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.tar.gz
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.z
Tom Allison wrote:
> Tom Allison wrote:
>> I just did an install of spampd on my debian box and am working my
>> way through the different configurations...
>>
>> First, I found that /var/cache/spampd/awl had the wrong permissions
>> so I changed that and I stopped getting errors. Interestingly, I
Tom Allison wrote:
I just did an install of spampd on my debian box and am working my way
through the different configurations...
First, I found that /var/cache/spampd/awl had the wrong permissions so I
changed that and I stopped getting errors. Interestingly, I have AWL
disabled. But I gue
I just did an install of spampd on my debian box and am working my way through
the different configurations...
First, I found that /var/cache/spampd/awl had the wrong permissions so I changed
that and I stopped getting errors. Interestingly, I have AWL disabled. But I
guess it likes to check
22 matches
Mail list logo
