Ok, great.
Thanks.
Regs,
Sven
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
s
Now I am confused;
At 12:48 AM 28/06/2005, Mark Martinec wrote:
Darryl,
> Can someone please tell me the appropriate setting to allow archives
> through the system (ZIP, TAR etc) but only if they are password protected.
> If not protected, then block.
Add these two rules somewhere towards the
> BTW, on the subject of bugs, the new 2.74 version of razor-agents is out.
> wget
> http://osdn.dl.sourceforge.net/sourceforge/razor/razor-agents-2.74.tar.bz2
>
> Hmm, I'm not used to .bz2
> I did this:
> bunzip2 -v razor-agents-2.74.tar.bz2
> tar xvf razor-agents-2.74.tar
> seems to work.
>
>
Tom wrote:
> the conf file is there!
> thats what makes this error so weird.
> amavis group has rwx on it as well.
> i don't know what more it wants.
> the docs for this app leave a lot to be desired.
> i have no idea what to edit in clamd.conf except the user and socket and pid
> dir and have th
How about removing the word "example" on the conf file?
--
# Comment or remove the line below.
Example
--
Kenneth
Kern, Tom wrote:
the conf file is there!
thats what makes this error so weird.
amavis group has rwx on it as well.
i don't know what more it wants.
the docs for this app leave a lo
the conf file is there!
thats what makes this error so weird.
amavis group has rwx on it as well.
i don't know what more it wants.
the docs for this app leave a lot to be desired.
i have no idea what to edit in clamd.conf except the user and socket and pid
dir and have the socket dir match amavisd
Tom wrote:
> that doesn't work.
> when i try to start clamd manually, i get this -
> ERROR: Please edit the example config file /usr/local/etc/clamd.conf.
> ERROR: Can't open/parse the config file /usr/local/etc/clamd.conf
> i'm getting tried of clamav.
> i don't understand why the earlier verison
Mark wrote:
> Gary,
>> > Seems to have worked. What a pain. Did anyone notify the Net::Server
>> > author
>>
>> Actually, yes, I filed a bug report with CPAN.
> Funny. When Net::Server 0.88 finally fixed the long-standing setuid
> security problem for everybody else, it seems to be failing
that doesn't work.
when i try to start clamd manually, i get this -
ERROR: Please edit the example config file /usr/local/etc/clamd.conf.
ERROR: Can't open/parse the config file /usr/local/etc/clamd.conf
i'm getting tried of clamav.
i don't understand why the earlier verison i ran was in /etc/ a
Thanks, your thorough response is VERY APPRECIATED!
--- Mark Martinec <[EMAIL PROTECTED]> wrote:
> email builder,
>
> > Recently comparing a fresh install to our older conf file and this was
> > part of the diff... wondering if I should change these things in our conf
> > file or not?
> >
> >
email builder,
> Recently comparing a fresh install to our older conf file and this was
> part of the diff... wondering if I should change these things in our conf
> file or not?
>
> -$file = 'file'; # file(1) utility; use recent versions
> -$gzip = 'gzip';
> -$bzip2 = 'bzip2';
> -$lzop =
Paul,
> The new version of Net::Server implemented my requested change for a new
> hook, removing the need for my previous patch. However, I'm not going to
> have time this week to test the minor change to amavisd in time for Mark
> to include it in the next release version.
> Can anyone volunteer
The new version of Net::Server implemented my requested change for a new
hook, removing the need for my previous patch. However, I'm not going to
have time this week to test the minor change to amavisd in time for Mark
to include it in the next release version.
Can anyone volunteer to test this m
Gary,
> > Seems to have worked. What a pain. Did anyone notify the Net::Server
> > author
>
> Actually, yes, I filed a bug report with CPAN.
Funny. When Net::Server 0.88 finally fixed the long-standing setuid
security problem for everybody else, it seems to be failing on ancient
bug-infeste
email wrote:
> All,
> I just ran into this same thing. Also RHEL3.
> /usr/local/sbin/amavisd[32697]: Net::Server: 2005/06/28-17:04:17 Couldn't
> become gid "503": \n\n at line 486 in file
> /usr/lib/perl5/site_perl/5.8.0/Net/Server.pm
>> >> i was going for .83 of Net::Server
>>
>> >> i
All,
I just ran into this same thing. Also RHEL3.
/usr/local/sbin/amavisd[32697]: Net::Server: 2005/06/28-17:04:17 Couldn't
become gid "503": \n\n at line 486 in file
/usr/lib/perl5/site_perl/5.8.0/Net/Server.pm
> >> i was going for .83 of Net::Server
>
> >> i downloaded it to an MS box
All,
Recently comparing a fresh install to our older conf file and this was part
of the diff... wondering if I should change these things in our conf file or
not?
@@ -81,24 +80,7 @@
# when enabling addr extensions do also Postfix/main.cf:
recipient_delimiter=+
$path = '/usr/local/sbin:/usr/
> A release candidate of amavisd-new-2.3.2 is available at:
The -rc1 was short-lived. Based on new information, the -rc2 ignores
certain bogus Perl I/O statuses, which pop up on some installations.
The -rc2 is at:
http://www.ijs.si/software/amavisd/amavisd-new-2.3.2-rc2.tar.gz
Mark
-
Mark wrote:
> A release candidate of amavisd-new-2.3.2 is available at:
> http://www.ijs.si/software/amavisd/amavisd-new-2.3.2-rc1.tar.gz
> Compared to 2.3.2-pre3 it:
> - uses recv() instead of read() to get results from daemonized virus scanners
> in an attempt to avoid a Perl I/O status bu
Tom wrote:
> Tom wrote:
>> i never entered that line. its not there.
>> the amavis settings are in master.cf NOT main.cf
>> Have you commented out the
>> content_filter = smtp-amavis:[127.0.0.1]:10024
>> in postfix main.cf?
>> thanks
> If you followed the Scott Henderson HOWTO, this is how you
thats weird.
i entered it and it works.
last time i didn't have that line in main.cf only the master.cf stuff and it
worked.
Thats really bizzare.
now the only error i get is -
ClamAV-clamd: Can't connect to UNIX socket /tmp/clamd: Connection refused,
retrying (2)
clamav user is a member of amav
Bob, Bart, Michael, Chris,
> > Jun 25 11:12:59 sunrise amavis[1159]: (01159-01)
> > TROUBLE in check_mail: mime_decode-1 FAILED:
> > Error reading: Resource temporarily unavailable
> > at (eval 64) line 153, line 1.
...
> > Here comes the weird part, when i tried to debug it, and set the log
> >
Tom wrote:
> i never entered that line. its not there.
> the amavis settings are in master.cf NOT main.cf
> Have you commented out the
> content_filter = smtp-amavis:[127.0.0.1]:10024
> in postfix main.cf?
> thanks
If you followed the Scott Henderson HOWTO, this is how you would call
amavisd-ne
i never entered that line. its not there.
the amavis settings are in master.cf NOT main.cf
thanks
-Original Message-
From: Gary V [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 28, 2005 2:26 PM
To: Kern, Tom
Cc: amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] how do you tell?
Tom wrote:
> i have those dirs with all the correct perms.
> i telnet'ed to 10024 and was able to send myself an email but i still see no
> sa or amavisd in the maillog.
> it wasn't working before because i had av scanner set to run but no av
> software installed.
> after i installed clamav, it
i have those dirs with all the correct perms.
i telnet'ed to 10024 and was able to send myself an email but i still see no sa
or amavisd in the maillog.
it wasn't working before because i had av scanner set to run but no av software
installed.
after i installed clamav, it was working but still no
A release candidate of amavisd-new-2.3.2 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.3.2-rc1.tar.gz
Compared to 2.3.2-pre3 it:
- uses recv() instead of read() to get results from daemonized virus scanners
in an attempt to avoid a Perl I/O status bug on some Linux install
Tom wrote:
> i'm using 0.83.
> i got it from you(thanks btw!)
> i used to get that error with the old amavis-new but it still worked.
> what am i doing wrong?
Make sure you have some directories that the new version may need:
mkdir /var/amavis/tmp
mkdir /var/amavis/db
mkdir /var/amavis/var
chow
i'm using 0.83.
i got it from you(thanks btw!)
i used to get that error with the old amavis-new but it still worked.
what am i doing wrong?
-Original Message-
From: Gary V [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 28, 2005 1:42 PM
To: Kern, Tom
Cc: amavis-user@lists.sourceforge.net
Su
Tom wrote:
> Hi, i just rebuilt my server with updated versions of
> Spamassassin,amavis,postfix and i'm not sure amavis is working.
> when i do a ps -aux, i see it running but i don't see anything in maillog(log
> level is at 2).
> amavisd debug produces this-
> Jun 28 12:40:13 mta1.charmer.c
Hi, i just rebuilt my server with updated versions of
Spamassassin,amavis,postfix and i'm not sure amavis is working.
when i do a ps -aux, i see it running but i don't see anything in maillog(log
level is at 2).
amavisd debug produces this-
Jun 28 12:40:13 mta1.charmer.com /usr/local/sbin/amavi
Jim,
> can I use an wildcard in amavisd.conf? (as example)
> '.domain.com' => -3.0,
> Normal is
> '[EMAIL PROTECTED]' => -3.0,
Yes, in hash lookup tables you can have entries like:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
user+foo@
user@
sub.example.com
.sub.example.com
.example.com
.com
.
probsd org wrote:
My System:
amavisd-new-2.3.1,1
perl-5.8.7
p5-MIME-Tools-5.417,2
clamav-0.86.1
p5-Mail-SpamAssassin-3.0.4
postfix-2.2.4,1
postfix, amavisd-new, clamav, etc... all running in a
FreeBSD (4.11-STABLE) jail.
After upgrading the FreeBSD perl port to version
5.8.7, I'm noticing the f
Hallo und guten Tag amavis-user,
can I use an wildcard in amavisd.conf? (as example)
'.domain.com' => -3.0,
Normal is
'[EMAIL PROTECTED]' => -3.0,
--
Viele Grüße, Kind regards,
Jim Knuth
[EMAIL PROTECTED]
ICQ #277289867
PGP Fingerprint:
54C9 1A46 D3B2 95B6 454D
74FA AC73 773E 1F78
Gary wrote:
> Tom wrote:
>> i was going for .83 of Net::Server
>> i downloaded it to an MS box that was running ftp.
>> maybe MS screwed with the file.
>> I couldn't do a wget from Redhat. i kept getting "access denied". but from
>> a browser it worked. i'm not running x-windows on the box.
>>
Tom wrote:
> i was going for .83 of Net::Server
> i downloaded it to an MS box that was running ftp.
> maybe MS screwed with the file.
> I couldn't do a wget from Redhat. i kept getting "access denied". but from
> a browser it worked. i'm not running x-windows on the box.
> strange.
Yeah, I go
Joachim wrote:
> Hello list,
> I am using SuSE 9.2
> This week I updated SA agains the known DOS vulnerability
> (using SuSEs update service).
> Now I see in "amavisd debug-sa":
> configuration file "/usr/share/spamassassin/20_body_tests.cf" requires
> version 3.04 of
> SpamAssassin, bu
Mark Martinec wrote:
We have a number of users hopping up and down
about mails from senders already whitelisted
and mails are ofcourse not making it through.
It would probably be useful to have a similar
mechanism for bad headers, based on sender address.
Until that is available, I think the
i was going for .83 of Net::Server
i downloaded it to an MS box that was running ftp.
maybe MS screwed with the file.
I couldn't do a wget from Redhat. i kept getting "access denied". but from a
browser it worked. i'm not running x-windows on the box.
strange.
-Original Message-
Tom wrote:
> Didin't work.
> I get this error -
> tar: Skipping to next header
> tar: Archive contains obsolescent base-64 headers
> gzip: stdin: invalid compressed data--crc error
> gzip: stdin: invalid compressed data--length error
> tar: Child returned status 1
> tar: Error exit delayed from pr
On Mon, Jun 27, 2005 at 02:40:22PM -0600, Gary V wrote:
> Clifton wrote:
> > Perl 5.8.0 had some significant bugs fixed in later releases of
> > 5.8.0, and Mark has many times warned that amavisd can tickle some of
> > them.
>
> > -- Clifton
>
> I think one of the strange things I found when
hi all,
i've a virtual domain mailing system with postfix, fetchmail gets mail from
all my accounts and forwards it to my virtual account on this system.
all of this mail is analized by amavis-new 20030616p10-5 with sa 3.0.3-1.
it detects about 99% of the spam in mails to the mail address (both
Hello list,
I am using SuSE 9.2
This week I updated SA agains the known DOS vulnerability
(using SuSEs update service).
Now I see in "amavisd debug-sa":
configuration file "/usr/share/spamassassin/20_body_tests.cf" requires version
3.04 of
SpamAssassin, but this is code version 3.01.
I understand that keeping it in memory isn't going to help speed
on the local machine, but the advantage is a global cache shared
across many machines - each benefiting from the previous scanning
results of the others.
Given how frequently body caches hits are, I would imagine that
for those o
Hi all,
> Perhaps you are confusing Postfix virtual and alias maps.
this was the very right guess..
thanks.
joerg
On Mo, 20.06.2005, 11:32, Mark Martinec sagte:
> Joerg,
>
>> Sorry, this does not match my experience, here is an example: when i
>> recieve a mail to [EMAIL PROTECTED], the real user
hi all,
> That is correct. See DBI man page for explanation of '?' arguments.
thank you.
it is working now, i had the problem that the mail address in the database
did not match the username + '@' + domain string. now i changed the
setting in the mysql-amavis-squirrelmail plugin to write there not
On Mon, 2005-06-27 at 22:40 -0400, Dale Walsh wrote:
> On Jun 27, 2005, at 09:22 PM, zen wrote:
>
> > my problems is all mails for my virtual domain users bypass spam
> > scanning wether SA or DSPAM but amavisd run virus scanning on it.
> > i need a solution for this .
> What leads you to believe
On Tue, 2005-06-28 at 18:57 +1200, Simon wrote:
> Hi There,
>
> We have a postfix/amavis server setup as a final destination server for
> our (hosting) clients. This is working well... with mysql for all the
> settings.
>
> I have a new client that has their own mail server in-house but would
Didin't work.
I get this error -
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
gzip: stdin: invalid compressed data--crc error
gzip: stdin: invalid compressed data--length error
tar: Child returned status 1
tar: Error exit delayed from previous errors
when i try to
Cami,
> There appears to be a problem with whitelisting not
> being enforced/applied when mails have bad header
> content or incorrect mime boundaries.
>
> This happens when $final_bad_header_destiny = D_DISCARD
>
> Am i missing something? Should whitelisting even be
> allowed to override mails wi
Hi Mark,
There appears to be a problem with whitelisting not
being enforced/applied when mails have bad header
content or incorrect mime boundaries.
This happens when $final_bad_header_destiny = D_DISCARD
Am i missing something? Should whitelisting even be
allowed to override mails with bad hea
Sven,
> I'm working through the README.sql and have two questions.
> First, regarding banned rulenames it says in the policy
> table:
> banned_rulenamesvarchar(64) default NULL
> -- comma-separated list of ...
> -- names mapped through %banned_rules to actual
> -- banned_filename tables
Thomas,
> Is there another way for forwarding all spam emails
> including only one set of X-Spam-* headers?
Yes. For the purpose of delivering spam to a mailbox
accessible to users without a need of further processing
at the time of release, one can turn on appending
address extensions (line +spa
Hi,
I'm working through the README.sql and have two questions.
First, regarding banned rulenames it says in the policy
table:
banned_rulenamesvarchar(64) default NULL
-- comma-separated list of ...
-- names mapped through %banned_rules to actual
-- banned_filename tables
Am I interpr
On Tuesday 28 June 2005 11:21, Mark Martinec wrote:
> > > Perhaps you are examining quarantined mail, not a forwarded mail?
> >
> > True, I looked at a quarantined mail. Thought an "smtp" quarantine was
> > the natural way to forward all spam emails to a single destination, isn't
> > it?
>
> Quaran
Thomas,
> > Perhaps you are examining quarantined mail, not a forwarded mail?
>
> True, I looked at a quarantined mail. Thought an "smtp" quarantine was the
> natural way to forward all spam emails to a single destination, isn't it?
Quarantined messages tries to preserve mail close to the origina
Ed,
> Another request for a little more logging info:
> We've got these indicators for use in per-recipient logging:
> %1 above tag level for this recipient: Y or 0
> %2 above tag2 level for this recipient: Y or 0
> %k above kill level for this recipient: Y or 0
> How about one that i
On Monday 27 June 2005 21:56, Mark Martinec wrote:
> > when forwarding all spam mails to a single destination,
> > existing X-Spam-* headers don't get deleted.
>
> Hm, are sure? With a Postfix (dual-MTA) setup?
> I'm not seeing it here.
>
> > Here's why: check_mail() calls do_spam() before the firs
Hi,
> Is this an amavis question or a postfix question?
Well, what is your question? :) So far you've only
described the scenario.
Regs,
Sven
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple t
59 matches
Mail list logo
