Hi Noah,
1. create directories ~/Maildir/.Spam
2. use maildrop as delivery sevice
3. put the following line in .mailfilter of the users home directory that are
interested in spamfiltering:
xfilter "/usr/local/bin/spamassassin -P"
if (/^X-Spam-Status: Yes/)
to Maildir/.Spam/
(of cause s
I use it.
in /etc/courier/courierd just put DEFAULTDELIVERY to :
DEFAULTDELIVERY="| spamc | /usr/bin/maildrop"
This will work, tagging the subject of your spam to ***SPAM*** if
you like to make somethink more complex, like moving messages, deleting
messages with high scores, etc ... I think
On Thu, 31 Jul 2003, Guenter Brast wrote:
> Hi Noah,
>
> 1. create directories ~/Maildir/.Spam
> 2. use maildrop as delivery sevice
> 3. put the following line in .mailfilter of the users home directory that are
> interested in spamfiltering:
>
Regarding this line:
> xfilter "/usr/local/bin/
From: Guenter Brast [mailto:[EMAIL PROTECTED]
>
> 1. create directories ~/Maildir/.Spam
> 2. use maildrop as delivery sevice
> 3. put the following line in .mailfilter of the users home
> directory that are
> interested in spamfiltering:
>
> xfilter "/usr/local/bin/spamassassin -P"
>
> if
I just Installed SpamAssassin 1-2 weeks ago and it works extremely well.
Just add the following to maildroprc:
xfilter "/usr/bin/spamassassin -P -F 0 -L"
Much easier than trying to get a DNS based blacklist going.
--Morgan
At 03:27 PM 6/26/2002 -0600, you wrote:
>Hello all. We are looking at
Alternately: you could run spamd and use spamc as your xfilter. That
combo wins the performance crown for my money. Better to launch a small
C binary than the Perl interpreter once per message.
xfilter "/usr/bin/spamc"
On Wed, 2002-06-26 at 18:05, Morgan Massena wrote:
> I just Installed SpamAss
Quoting "Matthew P. Cox" <[EMAIL PROTECTED]>:
| Alternately: you could run spamd and use spamc as your xfilter. That
| combo wins the performance crown for my money. Better to launch a small
| C binary than the Perl interpreter once per message.
|
| xfilter "/usr/bin/spamc"
Has anyone trie
he filter rules for
this?
--
Ian Cass
- Original Message -
From: "Matthew P. Cox" <[EMAIL PROTECTED]>
To: "Morgan Massena" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, June 26, 2002 11:42 PM
Subject: Re: [courier-users] SpamAssassin
>
[EMAIL PROTECTED]
[EMAIL PROTECTED] Subject: Re:
[courier-users] SpamAssassin
[EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: Re:
[courier-users] SpamAssassin
> -- Forwarded message --
> From: Jérôme Blion <[EMAIL PROTECTED]>
> To: courier-users@lists.sourceforge.net
> Date: Tue, 22 Jul 2008 20:35:55 +0200
> Subject: Re: [courier-users] spamassasin
> Jan Müller a écrit :
>>
>> I have working spamassasin, but can not get it to process cour
Jan Müller a écrit :
3 ideas for you:
- reject message when SMTP connection is still opened: use Courier-pythonfilter
with spamassassin filter. It works perfectly.
- DEFAULTDELIVERY="|/usr/bin/spamc|/usr/lib/courier/bin/maildrop"
- If there is nothing else in your maildroprc, you won't reject an
> -- Forwarded message --
> From: Jérôme Blion <[EMAIL PROTECTED]>
> To: Jan Müller <[EMAIL PROTECTED]>
> Date: Wed, 23 Jul 2008 20:19:15 +0200
> Subject: Re: [courier-users] spamassassin
> Jan Müller a écrit :
>
> 3 ideas for you:
>
> - re
Jan Müller wrote:
> according to
> [http://wiki.apache.org/spamassassin/IntegratedInCourierUsingMaildrop],
> I installed spamassassin. Spamd starts without errors, command-line
> tests work. I set DEFAULTDELIVERY to "| /usr/bin/maildrop" in
> etc/courier/courierd. Created /etc/courier/maildroprc w
On Thu, 24 Jul 2008 09:17:41 +0200, "Jan Müller" <[EMAIL PROTECTED]>
wrote:
>> -- Forwarded message --
>> From: Jérôme Blion <[EMAIL PROTECTED]>
>> To: Jan Müller <[EMAIL PROTECTED]>
>> Date: Wed, 23 Jul 2008 20:19:15 +0200
>&g
according to
[http://wiki.apache.org/spamassassin/IntegratedInCourierUsingMaildrop],
I installed spamassassin. Spamd starts without errors, command-line
tests work. I set DEFAULTDELIVERY to "| /usr/bin/maildrop" in
etc/courier/courierd. Created /etc/courier/maildroprc with exception {
xfilter "/us
Jan Müller wrote:
> when i try to install Courier-pythonfilter: python setup.py install, i
> get an error: invalid Python installation: unable to open
> /usr/lib/python2.5/config/Makefile (No such file or directory) Such
> file really does not exist on my Suse 10.3. What should i do?
You may have
Jan Müller wrote:
> according to
> [http://wiki.apache.org/spamassassin/IntegratedInCourierUsingMaildrop],
> I installed spamassassin. Spamd starts without errors, command-line
> tests work. I set DEFAULTDELIVERY to "| /usr/bin/maildrop" in
> etc/courier/courierd. Created /etc/courier/maildroprc w
> SpamAssassin works great, but it does not filter mail by itself. All it
> does is process the mail and add headers and possibly subject line
> modifications to indicate if the mail is spam or not. If the mail is
> spam, then it is up to you to do something with it. Take a look at the
> headers
>> use Courier-pythonfilter with spamassassin filter. It works perfectly.
>> HTH.
>> Jerome Blion.
>
>> From: Gordon Messmer <[EMAIL PROTECTED]>
>> You may have to install "python-devel" or something like it. I'm not
> familiar with the package naming convention used by SuSE.
>
> I managed to in
Jan Müller wrote:
> > SpamAssassin works great, but it does not filter mail by itself.
> > All it does is process the mail and add headers and possibly subject
> > line modifications to indicate if the mail is spam or not. If the
> > mail is spam, then it is up to you to do something with it. Tak
Jan Müller wrote:
>> From: Gordon Messmer <[EMAIL PROTECTED]>
>> You may have to install "python-devel" or something like it. I'm
>> not familiar with the package naming convention used by SuSE.
>
> I managed to install Courier-pythonfilter. Thanks for the tips.
> However, I can not do (>filterct
On Thu, 2009-01-15 at 01:09 +0100, mattias wrote:
> Can i intregate spamassassin with courier-mta?
Yes, there are a couple of ways to go with this. First, you can use a
global maildroprc to invoke spamc on a per-address basis. I'd suggest
running spamd with its data kept in a database rather tha
Hello,
take a look at this link:
http://wiki.apache.org/spamassassin/IntegratedInMta
there's a Courier section.
It was enough for me.
Regards.
On 11/17/06, Jesper Langkjær <[EMAIL PROTECTED]> wrote:
Hi.
Are there sombody thats have an Howto to install Spamassassin in Courier ?
Kind Regards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Better yet, we have a Gentoo Wiki document:
http://gentoo-wiki.com/HOWTO_Install_Courier_with_maildrop_and_ClamAV_and_SpamAssassin
- --
Arturo "Buanzo" Busleiman - Consultor Independiente en Seguridad Informatica
Me caso este 1ro de diciembre: Lista
On Wednesday, March 5, 2003, at 05:36 AM, Bill Long wrote:
Just a quick check. Does anybody have the full courier suite installed
and
running and using SpamAssassin?
I found a howto on the web which will work, but it uses Maildrop.
I was wondering if anybody has a different setup. Specifically,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 05 March 2003 05:36, Bill Long wrote:
> Just a quick check. Does anybody have the full courier suite installed and
> running and using SpamAssassin?
yes, I've it running on a debian machine.
I've added that line to the sources.list
# spa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 05 March 2003 12:05, you wrote:
> Doesn't this run SpamAssassin in delivery mode? Ie, it has to be accepted
> for local delivery before it gets run by this?
yes, we don't kill messages on the server, just mark them so the user can
decide
>From the looks of it, there is something wrong with your spamd installation
and configuration. Check your spamd startup-script...
Kind regards,
Sander Holthaus
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of gillian bennett
> Sent: Tuesday, Sep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| Sep 21 21:53:09 ver-arc-ms1 spamd[7480]: Argument "" isn't numeric in
| scalar assignment at /usr/bin/spamd line 942.
| Sep 21 21:53:09 ver-arc-ms1 spamd[7480]: Argument "" isn't numeric in
| numeric ne (!=) at /usr/bin/spamd line 943.
Looks as if Aut
on integration of spamassassin with courier still valid with the new
version of spamassasin? Anybody tested this already?
I just apt-get upgraded to SA 3.0 the other day with no problem. my
current xfilter in /etc/courier/maildroprc is:
import USER
if ($LOGNAME ne "")
{
xfil
> My interest is tagging spam, not totally blocking it.
> Any pointers to any direction on integratin SA with courier would be
> helpful. I am not finding much other than a few list postsings.
Maybe this info is of use to you... maybe not..
I have done it this way with maildrop/amavisd-new/SA to p
On Thu, Dec 18, 2003 at 04:14:29PM -0800, Rick Erlandson wrote:
> > My interest is tagging spam, not totally blocking it.
> > Any pointers to any direction on integratin SA with courier would be
> > helpful. I am not finding much other than a few list postsings.
>
> Maybe this info is of use to yo
>> Maybe this info is of use to you... maybe not..
>> I have done it this way with maildrop/amavisd-new/SA to put spam in a
>> certain folder.
>> amavisd-new calls SA to score the spam, but does its own tagging of the
>> message.
>How do you run amavisd-new ? from an /etc/maildroprc?
>Or from a co
Troy Benjegerdes wrote:
How do you run amavisd-new ? from an /etc/maildroprc?
Or from a courier-filter?
The way I do it on *my* servers is to have an "xfilter /usr/bin/amavis"
in /etc/courier/maildroprc
Of course, I'm using amavis-ng. I have no idea what amavis-new is.
- Joe
On Thu, Dec 18, 2003 at 05:14:22PM -0600, Joe Laffeyolor wrote:
>
> Should Spamassassin's SPAM header rewriting work with using a
> /etc/courier/maildroprc with the following in it?
>
> #setup vars snipped
>
> # filter message
> if ( $SIZE < 512000 )
> {
> xfilter "/usr/bin/spamc
On Thu, 18 Dec 2003, Troy Benjegerdes wrote:
>
> Well, first, are you sure spamassasin is actually tagging things?
I have not actually set it up yet! I am reasearching as much info on HOWTO
before I start. But I am about to try...
>
> Second, I don't remember at what point /etc/courier/maildropr
Joe Laffeyolor wrote:
Should Spamassassin's SPAM header rewriting work with using a
/etc/courier/maildroprc with the following in it?
Check all of the headers on your mail. SpamAssassin doesn't modify the
subject line by default. You should, however, get an X-Spam-Status header.
# filte
Joe Laffey wrote:
On Thu, 18 Dec 2003, Troy Benjegerdes wrote:
Second, I don't remember at what point /etc/courier/maildroprc runs, but
in my setup, I had to run spamassasin from the user's .mailfilter to
actually get it to modify the message.
This may be what I need. Can you post a sample .mailfil
On Fri, Dec 19, 2003 at 12:44:25AM -0600, Joe Laffey wrote:
> I am working at getting SA working. No luck, yet.
>
> Currently, I do not even see the log messages in the logs.
>
> Here is what I have:
>
> [12:35am]raw /usr/lib/courier/etc# cat maildropfilter
> /usr/lib/courier/bin/maildrop
> [12:
On Fri, 19 Dec 2003, Troy Benjegerdes wrote:
> On Fri, Dec 19, 2003 at 12:44:25AM -0600, Joe Laffey wrote:
> > I am working at getting SA working. No luck, yet.
> >
> > Currently, I do not even see the log messages in the logs.
> >
> > Here is what I have:
> >
> > [12:35am]raw /usr/lib/courier/etc
From: Lion [mailto:[EMAIL PROTECTED]
>
> Hello.
> Is it possible to use spamassasin as courier filter?
Check out Amavisd-new (http://www.ijs.si/software/amavisd/). It
interfaces with SpamAssassin and quite a few virus scanners and is
pretty easy to integrate with Courier.
Keep in mind that a co
Hello,
I use courier-pythonfilter for both spam and virus scanning during SMTP
transaction.
HTH.
Jerome Blion.
On Mon, 21 Mar 2011 14:46:25 +0100, Matus UHLAR - fantomas
wrote:
> Hello,
>
> Can you advise me a (simple) way to integrate SpamAssassin checking at
MTA
> level?
>
> We use courier
On 3/21/2011 9:46 AM, Matus UHLAR - fantomas wrote:
> Hello,
>
> Can you advise me a (simple) way to integrate SpamAssassin checking at MTA
> level?
>
> We use courierperlfilter for clamav scanning and logging and I could add
> calling spamc to it, but I'd like to know if there are other nice ways.
On Monday 21,March,2011 09:46 PM, Matus UHLAR - fantomas wrote:
> Can you advise me a (simple) way to integrate SpamAssassin checking at MTA
> level?
>
> We use courierperlfilter for clamav scanning and logging and I could add
> calling spamc to it, but I'd like to know if there are other nice way
> On Monday 21,March,2011 09:46 PM, Matus UHLAR - fantomas wrote:
> > Can you advise me a (simple) way to integrate SpamAssassin checking at MTA
> > level?
> >
> > We use courierperlfilter for clamav scanning and logging and I could add
> > calling spamc to it, but I'd like to know if there are ot
On 21.03.2011 20:19, Matus UHLAR - fantomas wrote:
> On 22.03.11 02:38, bamakoj...@gmail.com wrote:
>> The advantage of running spamc from perl/pythonfilter (IMO) is that you
>> can reject mail based on spam score. The disadvantage, if I understand
>> correctly, is that you can't have per-user set
> On 21.03.2011 20:19, Matus UHLAR - fantomas wrote:
> > On 22.03.11 02:38, bamakoj...@gmail.com wrote:
> >> The advantage of running spamc from perl/pythonfilter (IMO) is that you
> >> can reject mail based on spam score. The disadvantage, if I understand
> >> correctly, is that you can't have pe
On 03/23/2011 12:13 PM, Matus UHLAR - fantomas wrote:
>
> This is what spamass-milter already does. Mail to multiple recipients
> apparently can be re-checked in users' filters to get better results, while
> rejecting much of spam at SMTP level. While this can't be done with
> spamass-milter (yet),
> On 03/23/2011 12:13 PM, Matus UHLAR - fantomas wrote:
> > This is what spamass-milter already does. Mail to multiple recipients
> > apparently can be re-checked in users' filters to get better results, while
> > rejecting much of spam at SMTP level. While this can't be done with
> > spamass-milte
On 03/26/2011 02:48 PM, Matus UHLAR - fantomas wrote:
> On 26.03.11 10:27, Gordon Messmer wrote:
>> That's complicated. First, you'd have to decide whether or not to
>> reject the message. This can't be done per-user. After that, you'd
>> need to loop through each user and run spamc for that use
> > On 26.03.11 10:27, Gordon Messmer wrote:
> >> That's complicated. First, you'd have to decide whether or not to
> >> reject the message. This can't be done per-user. After that, you'd
> >> need to loop through each user and run spamc for that user.
> On 03/26/2011 02:48 PM, Matus UHLAR - fa
On 03/27/2011 05:23 AM, Matus UHLAR - fantomas wrote:
> Ok, now what is the way to modify headers in incoming mail? OR modifying
> whole e-mail. Can courierfilter modify the message data file?
Filters are given the filename of the data file. Your filter can modify
it any way that you like. It's
On Mon September 19 2005 19:46, Brian S. Meehan wrote:
> I checked out the URL at http://wiki.apache.org/spamassassin/WritingRules
> and can't seem to get a rule to work in /etc/mail/spamassassin/local.cf
>
> Here's what I've got so far:
>
> header LOCAL_SPAM_SUBJECT_RULE Subject =~ /[SPAM]/i
> sco
Geeze, silly me, I forgot the \ before the [ and ]
Methinks I shouldn't work that late at night...
Thanks Jerry!
(and yes, I know it was off topic for this list.)
b
On Tue, September 20, 2005 01:15, Jerry Amundson wrote:
> On Mon September 19 2005 19:46, Brian S. Meehan wrote:
>> I checked ou
Joe Meadows wrote:
> Hi,
> [snip]
>
> Seems like this ought to be easy to setup and I just need to know the
> magic line or two that will do it :)
It is easy to do. I have some docs up at
http://perlstalker.vuser.org/tiki/tiki-index.php?page=CourierSpamAssassin
--
Randy Smith
http://perlstalke
Joe Meadows wrote:
> BTW, setting "DEFAULTDELIVERY= |/usr/bin/spamc |
> /usr/lib/courier/bin/maildrop" doesn't work either. Apparently when
> using .courier files for delivery instructions the DEFAULTDELIVERY
> setting is ignored.
Yep, that's what dot-courier files are for. They provide delivery
Hi,
Thanks Randy and Gordon for your help with this :) Gordon, I agree, the
dot-courier file setup might be overly complicated. There's really only
a few mail accounts that I care about and I like the flexibility so it
hasn't been too tough to manage, but someday I will probably take the
ne
Jeff Potter wrote:
I'd like to run spamc inside a courier filter, and if the score is too
high, reject the message at the smtp layer. (That's not crazy.) The
"problem" with this is that some users invariably do not want their
messages filtered, while others do -- or more precisely, different use
Well, I'm not sure it's what you had in mind... but I've been running
Amavis as a global filter for a while now. In my case, I prefer to just
have it do virus scanning... but if you wanted spam rejected similarly,
it can easily accomplish that.
If someone had a more direct integration of spamc/
Bill Taroli schrieb:
Well, I'm not sure it's what you had in mind... but I've been running
Amavis as a global filter for a while now. In my case, I prefer to
just have it do virus scanning... but if you wanted spam rejected
similarly, it can easily accomplish that.
If someone had a more direct
Hi Dirk!
I'm just implementing this kind of spam filtering you mentioned. I don't
think I'm breaking the law here in Hungary, but this will prevents users
complaints, I hope. According to this policy you can't fight neither
spam nor viruses?
P.s.: sorry form my bad English.
Balazs Hegedus
> Bill
Dirk Kulmsee wrote:
Bill Taroli schrieb:
Wiebke Doerper wrote:
I would like to use SpamAssassin during the SMTP dialog, to discard
everything with a high spam rating. I know some people have been
thinking of implementing this. Does someone have a working
courier(perl)filter to do it?
Well, I'm
Bill Taroli schrieb:
Dirk Kulmsee wrote:
Bill Taroli schrieb:
Wiebke Doerper wrote:
I would like to use SpamAssassin during the SMTP dialog, to discard
everything with a high spam rating. I know some people have been
thinking of implementing this. Does someone have a working
courier(perl)filter
Dirk Kulmsee said:
> Bill Taroli schrieb:
>
>> Dirk Kulmsee wrote:
>>
>>> Bill Taroli schrieb:
>>>
Wiebke Doerper wrote:
> I would like to use SpamAssassin during the SMTP dialog, to discard
> everything with a high spam rating. I know some people have been
> thinking of imple
Dirk Kulmsee wrote:
> We all would love to block spam at the earliest stage, but at least here
> in Good ol' Germany you are half way in Jail if you do so.
> Mail & letters are PERSONAL and you may not intrude.
This is nonsense. Just put a clause into your AGB (Terms and Conditions),
then you're
Jay Lee schrieb:
Dirk Kulmsee said:
Bill Taroli schrieb:
Dirk Kulmsee wrote:
Bill Taroli schrieb:
Wiebke Doerper wrote:
I would like to use SpamAssassin during the SMTP dialog, to discard
everything with a high spam rating. I know some people have been
thinking of
Julian Mehnle schrieb:
Dirk Kulmsee wrote:
We all would love to block spam at the earliest stage, but at least here
in Good ol' Germany you are half way in Jail if you do so.
Mail & letters are PERSONAL and you may not intrude.
This is nonsense. Just put a clause into your AGB (Terms and C
Jay Lee wrote:
> with some perl scripting, one could probably get something similar with
> Spamassassin at SMTP time
A simple SpamAssassin module for Courier::Filter might look like the
following. I just hacked it together off the top of my head, so it hasn't
been tested, but I will probably incl
Dirk Kulmsee [EMAIL PROTECTED] wrote:
> Julian Mehnle schrieb:
> > For rejecting spam, I rely solely on reputation systems (i.e.
> > blacklists) and I recommend to my users that they use the SpamCop
> > reporting service[2] to report spam.
>
> In my opinion this is not the (always) the way to go. I
Julian Mehnle schrieb:
But this all of this is quickly getting off-topic. :-)
Hi Julian,
you're right.This thread evolves into spam catching instead of Courier
managing.
Thanks 4 your thoughts
--
Dirk Kulmsee
---
SF email is sponsored by -
Jeff Gamsby wrote:
I am trying to setup Spamassassin with courier, but I have this in my
courierd. Will courier read my maildroprc file? I need to keep .forward
compatibility.
DEFAULTDELIVERY="|| dotforward
./Maildir"
No, courier won't read your maildroprc file. It should if you use this,
Jérôme Blion wrote:
>
> I rewrote some parts of these two modules.
> Local socket or paths can be different...
>
> With these modules, the admin is able to set up correct paths to make
> these filters working.
Thanks Jérôme. I've made those changes in CVS. They'll go out with
some other item
charles uchu wrote:
Just setup and learned about autoresponders today using .mailfilter.
It's working good, except that for autoresponses that go back to a
mailbox on the same server the auto-response message takes a -2.6
point hit from SpamAssassin for the "ALL_TRUSTED" (Did not pass
throug
74 matches
Mail list logo
