Re: [vchkpw] vpopmail+spamassassin+clamscan
Another method (for different needs, of course): On our site, we just
put qmail-scanner in the qmail queue. All that needs to be done (all?
I spent hours on this :P) is apply the QMAILQUEUE patch to qmail, and
install qmail-scanner by following its instructions:
http://qmail-scanner.sourceforge.net/
qmail-scanner works with spamassassin and clamscan and can do primitive
attachment checks (i.e., block all .exe/.bat/.vbs attachments). The
way we have it set up, it just puts an 'X-Spam-Status: Yes/No' in the
message's header, and users can set their mail clients to use rules
based on that.
The downside: If you're running a very large site and only expect a few
people to use the virus-scanning abilities of spamassassin, you're going
to be burning lots of processor cycles. Our site is relatively small and
we need qmail-scanner anyway to block dangerous attachments, so the
waste of CPU isn't an issue for us.
--
Adam Hooper
[EMAIL PROTECTED]
Tom Walsh wrote:
There was some discussion a while back about making SA work with vpopmail.
Most solutions I saw used .qmail-username or .qmail-default which wasn't the
right method for us. Below is a quick write up on how to use SA+clamscan
from a .qmail file in the users maildir. We also pull user preferences for
SA from SQL, so the line we use to call SA might not be what you want.
Delivery and hand off for scanning is handled by maildrop.
First and foremost, make certain that the user vpopmail has a valid shell...
this is very important as vdeliermail will run anything in the .qmail as the
user vpopmail, provided the application doesn't do a setuid/setgid, which
maildrop does not do. (That alone cost me 3 hours to troubleshoot.)
For each user you want to enable SA and virus scanning put the following in
a .qmail file in the users directory:
| /var/qmail/bin/preline /usr/local/bin/maildrop
/usr/home/vpopmail/domains/.mailfilter
Make sure that this file has been chmod'ed to 600 (u+rw) and is owned by
vpopmail:vchkpw otherwise it will not be run.
The .mailfilter listed above contains (some of this script has come from
another list member, but I forgot his name, if you contact me I will give
credit where credit is due), it must also be chmod'ed to 600 with owner
vpopmail:vchkpw :
import EXT
import HOST
VHOME=`/usr/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
# Check for Spam if it is smaller than 250KB
if($SIZE 262144)
{
xfilter /usr/local/bin/spamc -d 192.168.1.2 -t 20 -f -u [EMAIL PROTECTED]
}
if ((/^X-Spam-Flag:.*YES/))
{
`/bin/test -d $VHOME/Maildir/.Spam`
if( $RETURNCODE == 1 )
{
`/var/qmail/bin/maildirmake $VHOME/Maildir/.Spam;
/usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Spam`
}
to $VHOME/Maildir/.Spam/
}
# If it isn't Spam, then we scan for Virus if it is smaller than 2MB in
size... anything larger... they are on their own
if($SIZE 200)
{
xfilter /usr/home/vpopmail/domains/clamscan.sh
}
if ((/^X-Virus-Status:.*INFECTED/))
{
`/bin/test -d $VHOME/Maildir/.Virus`
if ( $RETUNRCODE == 1 )
{
`/var/qmail/bin/maildirmake $VHOME/Maildir/.Virus;
/usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Virus`
}
to $VHOME/Maildir/.Virus/
}
#If it isn't Spam or Virus, then deliver normally
to $VHOME/Maildir/
The specific lines of interest are the xfilter lines. We use spamc/spamd to
offload the very CPU intensive process of spam scanning to another machine
on the private network. That is what the -d directive is for which tells SA
which IP to connect to for spamd...
The clamscan.sh file is a wrapper for the clamscan binary. We need to do
this because of the incompatibility between how clamscan operates and how
maildrop expects an xfilter program to operate. maildrop expects any message
it sends out to an xfilter program to be returned to it via stdout. The
problem is that the clamscan binary only returns the results of the scan,
not the message, so we have to create a shell script to pass the altered
message back to maildrop via stdout, also we use the shell script to alter
the exit code of clamscan (0 if clean and 1 if infected) to be compatible
with what maildrop expects. maildrop expects the application to return a
exit code of 0, so we have to alter it.
You will need bash in order to use this.
#!/usr/local/bin/bash
# Created by Tom Walsh
# slim at ala.net
MSG=$(/bin/cat /dev/stdin) # Is there a better way to do this?
SCAN=$(echo $MSG | /usr/local/bin/clamscan - --stdout --disable-summary)
EXIT=$?
VIRUS=$(echo $SCAN | awk '{print $2}')
SUBJECT=$(echo $MSG | /usr/local/bin/reformail -x Subject:)
if [ $EXIT == 1 ]; then
SUBJECT=**VIRUS** [$VIRUS] $SUBJECT
MSG=$(echo $MSG | /usr/local/bin/reformail -aX-Virus-Status:
INFECTED -iSubject: $(echo $SUBJECT))
else
MSG=$(echo $MSG | /usr/local/bin/reformail -aX-Virus-Status: CLEAN)
fi
echo $MSG
exit 0
And just for completeness... I have included our spamd config line to let
you
Re: [vchkpw] vpopmail+spamassassin+clamscan
this is what I'm doing ... and working prety fine..
I agree with Mr Adam.
--
Best Regs,
Masood Ahmad Shah
System Administrator
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
| * * * * * * * * * * * * * * * * * * * * * * * *
| Fibre Net (Pvt) Ltd. Lahore, Pakistan
| Tel: +92-42-6677024
| Mobile: +92-300-4277367
| http://www.fibre.net.pk
| * * * * * * * * * * * * * * * * * * * * * * * *
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
- Original Message -
From: Adam Hooper [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 10:43 PM
Subject: Re: [vchkpw] vpopmail+spamassassin+clamscan
| Another method (for different needs, of course): On our site, we just
| put qmail-scanner in the qmail queue. All that needs to be done (all?
| I spent hours on this :P) is apply the QMAILQUEUE patch to qmail, and
| install qmail-scanner by following its instructions:
| http://qmail-scanner.sourceforge.net/
|
| qmail-scanner works with spamassassin and clamscan and can do primitive
| attachment checks (i.e., block all .exe/.bat/.vbs attachments). The
| way we have it set up, it just puts an 'X-Spam-Status: Yes/No' in the
| message's header, and users can set their mail clients to use rules
| based on that.
|
| The downside: If you're running a very large site and only expect a few
| people to use the virus-scanning abilities of spamassassin, you're going
| to be burning lots of processor cycles. Our site is relatively small and
| we need qmail-scanner anyway to block dangerous attachments, so the
| waste of CPU isn't an issue for us.
|
| --
| Adam Hooper
| [EMAIL PROTECTED]
|
| Tom Walsh wrote:
|
| There was some discussion a while back about making SA work with
vpopmail.
|
| Most solutions I saw used .qmail-username or .qmail-default which wasn't
the
| right method for us. Below is a quick write up on how to use SA+clamscan
| from a .qmail file in the users maildir. We also pull user preferences
for
| SA from SQL, so the line we use to call SA might not be what you want.
| Delivery and hand off for scanning is handled by maildrop.
|
| First and foremost, make certain that the user vpopmail has a valid
shell...
| this is very important as vdeliermail will run anything in the .qmail as
the
| user vpopmail, provided the application doesn't do a setuid/setgid,
which
| maildrop does not do. (That alone cost me 3 hours to troubleshoot.)
|
| For each user you want to enable SA and virus scanning put the following
in
| a .qmail file in the users directory:
|
| | /var/qmail/bin/preline /usr/local/bin/maildrop
| /usr/home/vpopmail/domains/.mailfilter
|
| Make sure that this file has been chmod'ed to 600 (u+rw) and is owned by
| vpopmail:vchkpw otherwise it will not be run.
|
| The .mailfilter listed above contains (some of this script has come from
| another list member, but I forgot his name, if you contact me I will
give
| credit where credit is due), it must also be chmod'ed to 600 with owner
| vpopmail:vchkpw :
|
| import EXT
| import HOST
| VHOME=`/usr/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
|
| # Check for Spam if it is smaller than 250KB
| if($SIZE 262144)
| {
| xfilter /usr/local/bin/spamc -d 192.168.1.2 -t 20 -f -u
[EMAIL PROTECTED]
| }
| if ((/^X-Spam-Flag:.*YES/))
| {
| `/bin/test -d $VHOME/Maildir/.Spam`
| if( $RETURNCODE == 1 )
| {
| `/var/qmail/bin/maildirmake $VHOME/Maildir/.Spam;
| /usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Spam`
| }
| to $VHOME/Maildir/.Spam/
| }
|
| # If it isn't Spam, then we scan for Virus if it is smaller than 2MB in
| size... anything larger... they are on their own
| if($SIZE 200)
| {
| xfilter /usr/home/vpopmail/domains/clamscan.sh
| }
| if ((/^X-Virus-Status:.*INFECTED/))
| {
| `/bin/test -d $VHOME/Maildir/.Virus`
| if ( $RETUNRCODE == 1 )
| {
| `/var/qmail/bin/maildirmake $VHOME/Maildir/.Virus;
| /usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Virus`
| }
| to $VHOME/Maildir/.Virus/
| }
|
| #If it isn't Spam or Virus, then deliver normally
| to $VHOME/Maildir/
|
| The specific lines of interest are the xfilter lines. We use spamc/spamd
to
| offload the very CPU intensive process of spam scanning to another
machine
| on the private network. That is what the -d directive is for which tells
SA
| which IP to connect to for spamd...
|
| The clamscan.sh file is a wrapper for the clamscan binary. We need to do
| this because of the incompatibility between how clamscan operates and
how
| maildrop expects an xfilter program to operate. maildrop expects any
message
| it sends out to an xfilter program to be returned to it via stdout. The
| problem is that the clamscan binary only returns the results of the
scan,
| not the message, so
[vchkpw] vpopmail+spamassassin+clamscan
There was some discussion a while back about making SA work with vpopmail.
Most solutions I saw used .qmail-username or .qmail-default which wasn't the
right method for us. Below is a quick write up on how to use SA+clamscan
from a .qmail file in the users maildir. We also pull user preferences for
SA from SQL, so the line we use to call SA might not be what you want.
Delivery and hand off for scanning is handled by maildrop.
First and foremost, make certain that the user vpopmail has a valid shell...
this is very important as vdeliermail will run anything in the .qmail as the
user vpopmail, provided the application doesn't do a setuid/setgid, which
maildrop does not do. (That alone cost me 3 hours to troubleshoot.)
For each user you want to enable SA and virus scanning put the following in
a .qmail file in the users directory:
| /var/qmail/bin/preline /usr/local/bin/maildrop
/usr/home/vpopmail/domains/.mailfilter
Make sure that this file has been chmod'ed to 600 (u+rw) and is owned by
vpopmail:vchkpw otherwise it will not be run.
The .mailfilter listed above contains (some of this script has come from
another list member, but I forgot his name, if you contact me I will give
credit where credit is due), it must also be chmod'ed to 600 with owner
vpopmail:vchkpw :
import EXT
import HOST
VHOME=`/usr/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
# Check for Spam if it is smaller than 250KB
if($SIZE 262144)
{
xfilter /usr/local/bin/spamc -d 192.168.1.2 -t 20 -f -u [EMAIL PROTECTED]
}
if ((/^X-Spam-Flag:.*YES/))
{
`/bin/test -d $VHOME/Maildir/.Spam`
if( $RETURNCODE == 1 )
{
`/var/qmail/bin/maildirmake $VHOME/Maildir/.Spam;
/usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Spam`
}
to $VHOME/Maildir/.Spam/
}
# If it isn't Spam, then we scan for Virus if it is smaller than 2MB in
size... anything larger... they are on their own
if($SIZE 200)
{
xfilter /usr/home/vpopmail/domains/clamscan.sh
}
if ((/^X-Virus-Status:.*INFECTED/))
{
`/bin/test -d $VHOME/Maildir/.Virus`
if ( $RETUNRCODE == 1 )
{
`/var/qmail/bin/maildirmake $VHOME/Maildir/.Virus;
/usr/sbin/chown -R vpopmail:vchkpw $VHOME/Maildir/.Virus`
}
to $VHOME/Maildir/.Virus/
}
#If it isn't Spam or Virus, then deliver normally
to $VHOME/Maildir/
The specific lines of interest are the xfilter lines. We use spamc/spamd to
offload the very CPU intensive process of spam scanning to another machine
on the private network. That is what the -d directive is for which tells SA
which IP to connect to for spamd...
The clamscan.sh file is a wrapper for the clamscan binary. We need to do
this because of the incompatibility between how clamscan operates and how
maildrop expects an xfilter program to operate. maildrop expects any message
it sends out to an xfilter program to be returned to it via stdout. The
problem is that the clamscan binary only returns the results of the scan,
not the message, so we have to create a shell script to pass the altered
message back to maildrop via stdout, also we use the shell script to alter
the exit code of clamscan (0 if clean and 1 if infected) to be compatible
with what maildrop expects. maildrop expects the application to return a
exit code of 0, so we have to alter it.
You will need bash in order to use this.
#!/usr/local/bin/bash
# Created by Tom Walsh
# slim at ala.net
MSG=$(/bin/cat /dev/stdin) # Is there a better way to do this?
SCAN=$(echo $MSG | /usr/local/bin/clamscan - --stdout --disable-summary)
EXIT=$?
VIRUS=$(echo $SCAN | awk '{print $2}')
SUBJECT=$(echo $MSG | /usr/local/bin/reformail -x Subject:)
if [ $EXIT == 1 ]; then
SUBJECT=**VIRUS** [$VIRUS] $SUBJECT
MSG=$(echo $MSG | /usr/local/bin/reformail -aX-Virus-Status:
INFECTED -iSubject: $(echo $SUBJECT))
else
MSG=$(echo $MSG | /usr/local/bin/reformail -aX-Virus-Status: CLEAN)
fi
echo $MSG
exit 0
And just for completeness... I have included our spamd config line to let
you know how to pull settings from SQL:
/usr/local/bin/spamd -a -d -q -x -m 50 -u spamd -i 192.168.1.2 -A
192.168.1.100 -A 192.168.1.101
The -i directive tells spamd to listen on IP 192.168.1.2, by default it only
listens on 127.0.0.1
The -A directives tell spamd which IPs to accept connections from.
You also need to odify your local.cf file to include the settings for
connecting to the SQL server All of that is covered in the README for
SQL: http://www.spamassassin.org/dist/sql/README
I hope that helps somebody... We are going to be ramping up the load on the
SA box shortly to see how well it scales... We are considering doing load
balancing via two SA boxes and a psuedo-random IP selector script that will
feed a variable $IP to the .mailfilter script above... something like:
IP=`/path/to/ipscript.sh`
xfilter /usr/local/bin/spamc -d $IP -t 20 -f -u [EMAIL PROTECTED]
If anybody has any comments or suggestions I would be willing to hear
them... I
[vchkpw] vpopmail + spamassassin
Hi, 1 month again, I've sent an email on this in order to apply spamassin filter on all my domain. Some of you said me to use spamd instead of calling spamassassin from procmail. It work fine, thank you, but know, spam aren't encapsulate in attachements (default), and I can't rewrite subjets (I've put in config file : rewrite_subject 1). Spamassassin work fine, because it add spam status Yes/No in header, but it would change anything in the mail (subject ou attach). Anybody have an idea ? Thank you David
Re: [vchkpw] vpopmail + spamassassin
You're right, in order to use this feature, it's necessary to disabled fast-spamassin. For information, for doing that, you have to configure qmailscanner with parameter --scanners verbose_spamassassin (default paramater is fast_spamassassin). If you use F-Prot anti-virus, do that : ./configure --scanners fprot,verbose_spamassassin [...] Another question, anyboby know how add a message on all outgoing message ? Thank you - Original Message - From: Rick Root [EMAIL PROTECTED] To: David du SERRE-TELMON [EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 9:12 PM Subject: Re: [vchkpw] vpopmail + spamassassin This isn't a vpopmail issue. You're using qmail-scanner, right? If so, this happened to me recnetly when I upgraded because I accidently built with with fast-spamassassin That caused spamc/spamd to return a status rather than rewriting the email. Check the line in qmail-scanner-queue.pl that specifies the spamc options .. . mine reads: my $spamc_options=' -f'; I had to remove some option from that line, then I was all good. - Rick David du SERRE-TELMON wrote: Hi, 1 month again, I've sent an email on this in order to apply spamassin filter on all my domain. Some of you said me to use spamd instead of calling spamassassin from procmail. It work fine, thank you, but know, spam aren't encapsulate in attachements (default), and I can't rewrite subjets (I've put in config file : rewrite_subject 1). Spamassassin work fine, because it add spam status Yes/No in header, but it would change anything in the mail (subject ou attach). Anybody have an idea ? Thank you David
[vchkpw] vpopmail, spamassassin, and squirrelmail
Hi all, Does anyone have a HOW-TO or any information on how to integrate Spamassassin with vpopmail and Squirrelmail? I'm specifically looking to use the squirrelmail spamassassin plugin to allow the users to modify their spam settings. I'm not sure how this is done in conjunction with vpopmail, however. Anyone tried this? The server will have the following packages on it : qmail courier-imap spamassasin (using qmail-scanner) vpopmail (for virtual domains/mailboxes. No local accounts whatsoever.) Panda Software virus scanner (qmail wrapper, doesn't use qmail-scanner) SquirrelMail mySQL database back end (3.23.55, not 4.0 yet) Thanks, -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 807302349405893 --- Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming. signature.asc Description: This is a digitally signed message part
RE: [vchkpw] vpopmail, spamassassin, and squirrelmail
http://www.jerfu.com/toaster It's a pretty straight forward step-by-step for vpopmail+spamassassin+squirrelmail etc etc. -Clayton -Original Message- From: Jason 'XenoPhage' Frisvold [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 6:49 AM To: [EMAIL PROTECTED] Subject: [vchkpw] vpopmail, spamassassin, and squirrelmail Hi all, Does anyone have a HOW-TO or any information on how to integrate Spamassassin with vpopmail and Squirrelmail? I'm specifically looking to use the squirrelmail spamassassin plugin to allow the users to modify their spam settings. I'm not sure how this is done in conjunction with vpopmail, however. Anyone tried this? The server will have the following packages on it : qmail courier-imap spamassasin (using qmail-scanner) vpopmail (for virtual domains/mailboxes. No local accounts whatsoever.) Panda Software virus scanner (qmail wrapper, doesn't use qmail-scanner) SquirrelMail mySQL database back end (3.23.55, not 4.0 yet) Thanks, -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 807302349405893 --- Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming.
Re: [vchkpw] vpopmail, spamassassin, and squirrelmail
Jason, This seems out of scope for the Vpopmail list but I'll tell you what we're trying to do. Your config is like ours except we don't use qmail-scanner or Panda ( we use RAV). Although Clayton's howto is a great start, it doesn't address the issue of allowing people to manage their SA setting within Squirrelmail. There's a Vpopmail user management plugin on the Squirrelmail site which works well. I just finished modifing it to have a setting of Spam filtering ON/OFF This basically puts |maildrop in a user's .qmail file. The second step is to integrate the SA control panel located at http://spamassassin.org/devel/php-sa-mysql-0.5.tar.gz . Still working on that... Note that if you are using procmail and have no need for security, there's some handy plugins already available on the Squirrelmail site that will do all this for you. --chris davis Hi all, Does anyone have a HOW-TO or any information on how to integrate Spamassassin with vpopmail and Squirrelmail? I'm specifically looking to use the squirrelmail spamassassin plugin to allow the users to modify their spam settings. I'm not sure how this is done in conjunction with vpopmail, however. Anyone tried this? The server will have the following packages on it : qmail courier-imap spamassasin (using qmail-scanner) vpopmail (for virtual domains/mailboxes. No local accounts whatsoever.) Panda Software virus scanner (qmail wrapper, doesn't use qmail-scanner) SquirrelMail mySQL database back end (3.23.55, not 4.0 yet) Thanks, -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 807302349405893 --- Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming.
RE: [vchkpw] vpopmail, spamassassin, and squirrelmail
Cool... that's a start, at least... :) Thanks for the info... On Wed, 2003-02-19 at 10:21, Clayton Weise wrote: http://www.jerfu.com/toaster It's a pretty straight forward step-by-step for vpopmail+spamassassin+squirrelmail etc etc. -Clayton -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 807302349405893 --- Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming. signature.asc Description: This is a digitally signed message part
Re: [vchkpw] vpopmail, spamassassin, and squirrelmail
On Wed, 2003-02-19 at 11:09, Christopher Davis wrote: Jason, This seems out of scope for the Vpopmail list but I'll tell you what we're trying to do. My apologies... I'm not completely familiar with SpamAssassin, so I'm not totally sure how it works. I know it has to get the configuration from somewhere. In my limited research (thus far), I've noticed that procmail, maildrop, and .qmail files are used for this.. However, there are no home directories for these users since they're all virtual.. So, I was wondering how to make it work within the confines of vpopmail... Your config is like ours except we don't use qmail-scanner or Panda ( we use RAV). Although Clayton's howto is a great start, it doesn't address the issue of allowing people to manage their SA setting within Squirrelmail. An important part of what I want to do... :) There's a Vpopmail user management plugin on the Squirrelmail site which works well. I just finished modifing it to have a setting of Spam filtering ON/OFF This basically puts |maildrop in a user's .qmail file. The second step is to integrate the SA control panel located at http://spamassassin.org/devel/php-sa-mysql-0.5.tar.gz . Still working on that... Hrm... now I gotta learn PHP.. *sigh* :) Note that if you are using procmail and have no need for security, there's some handy plugins already available on the Squirrelmail site that will do all this for you. Not using procmail, actually... Security is *always* an issue :) --chris davis Thanks for the info... I'd be more than happy to discuss this more off the list... :) -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 807302349405893 --- Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming. signature.asc Description: This is a digitally signed message part
[vchkpw] Vpopmail spamassassin suggestions
Hi guys I have vpopmail qmailscanner working well. I Have spamassassin though that it does not do any marking, I have compiled qmail-scanner after spamassassin but I still do not get a text saying SPAM for that message :( I look at the log and I get the info there and says spam is working but really it's not :) any suggestions or site that have different setup that I can try would be nice. THANKS, REMO
Re: [vchkpw] Vpopmail spamassassin suggestions
I just setup spamassassin the other day, the way I do it is by
putting this line in the .qmail-default for the domain.
|maildrop mailfilter
then have a file called mailfilter in the same directory. change the
VPOP line to whatever you had in your .qmail-default, or you can set
whatever you need it to do with the mail.
[mailfilter]
VPOP=| /var/qmail/vpopmail/bin/vdelivermail ''
/var/qmail/vpopmail/domains/glizard.com/postmaster
VHOME=`/var/qmail/vpopmail/bin/vuserinfo -d $EXT@$HOST`
if ( $SIZE 262144 )
{
exception {
xfilter /usr/bin/spamc -f -u $EXT@$HOST
}
}
if (/^X-Spam-Flag: *YES/)
{
# try filtering it using user-defined rules
exception {
include $VHOME/Maildir/.mailfilter
}
# then try delivering it to a Spam folder
exception {
# to $VPOP
to $VHOME/Maildir/spam/
}
# ah well, I guess they'll just have to live with
disappointment
exception {
to $VPOP
}
}
else
{
exception {
include $VHOME/Maildir/.mailfilter
}
exception {
to $VPOP
}
}
Hope this helps,
Gary
RE: [vchkpw] Vpopmail spamassassin suggestions
-Original Message- From: Remo Mattei [mailto:[EMAIL PROTECTED]] Sent: Friday, 10 January 2003 12:41 PM To: [EMAIL PROTECTED] Subject: [vchkpw] Vpopmail spamassassin suggestions Hi guys I have vpopmail qmailscanner working well. I Have spamassassin though that it does not do any marking, I have compiled qmail-scanner after spamassassin but I still do not get a text saying SPAM for that message :( I look at the log and I get the info there and says spam is working but really it's not :) any suggestions or site that have different setup that I can try would be nice. THANKS, REMO Hi Remo I recently added qmail-scanner/spamassassin instructions to my vpopmail toaster doc at http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm We have been using qmailscanner/spamassassin for a while now and are very pleased with the results. Michael Bowe (B.App.Sc) Managing Director - Pipeline Internet 96 Pakington Street, Geelong West. VIC. 3218 Tel (03) 5229 7643 Fax (03) 5229 0282 Mobile 0419 242 136 http://www.pipeline.com.au/
