In amavisd.conf-default (and sections of amavisd), looking at these
assignments, am I to assume if $virus_admin (or @virus_admin_maps) is
defined, this definition will carry over to $banned_admin and
$bad_header_admin?
$virus_admin = '[EMAIL PROTECTED]';
# @virus_admin_maps = (\%virus_admin,
On 8/31/05, Hamish Marson <[EMAIL PROTECTED]> wrote:
>
> I have a wishlist...
>
> 1. The ability for users to edit their whitelist/blacklist entries.
> 2. When viewing the quarantine. The ability to hit a button to
> whitelist a sender & have all their quarantined email automatically
> released.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sam Tran wrote:
> The MailZu Team is pleased to announce the availability of MailZu
> 0.6RC3 which is a quarantine management interface for amavisd-new.
> It based on amavisd-new SQL reporting and AM.PDP protocol.
>
> Here is the CHANGELOG: - Add Exch
Benoit,
> I'd like to filter mail by extension and by user but i don't find how
> to do this ...
> Clearly a user "tata" can send an attachments .xls, .doc, .exe, .ppt
> and a user "toto" can only send .doc for example.
This can only be done based on recipient address (see release notes
of versio
Brian,
> So the 'content' field of the msgs table is only updated with an 'S'
> if it at or above kill level. Can someone explain to me why this is?
> It is somewhat confusing when the score is between
> $sa_tag2_level_deflt and $sa_kill_level_deflt. The database would say
> 'C' (clean) yet the lo
Chris,
> I'm struggling to understand the documentation relating to the
> banned_rulenames field in SQL tables.
See release notes of 2.3.0.
> The best I've been able to get to is this, and I wonder if someone can let
> me know if I'm heading in the right direction before I spend too much time
>
Joachim,
> I would like to notify the recipient in my institute so he can
> contact the postmaster if nesessary.
>$final_banned_destiny = D_BOUNCE;
>$warnbannedrecip = 1;
> does not work.
It should work, provided the recipient is considered local
(matches local_domains_maps) or $warn_
Robert wrote:
> I did a port upgrade on my FreeBSD box from amavisd-new-2.2.? to
> amavisd-new-2.3.1,1 and ever since the amavis-stats have been showing
> less virus detection. I checked all logs and everything seems to be
> processing fine. I am running Postfix 2.2.3 with SpamAssassin 3.0.4. I
>
On Wed, Aug 31, 2005 at 12:09:15PM +0200, Martin Svensson wrote:
> Hi all,
>
> I have seen a couple of spams bypass our spamassassin scan because they
> are larger than the 200KB default $sa_mail_body_size_limit. I'm thinking
> about raising that limit to 512KB. If anyone have raised it, what si
Gary wrote:
> I enabled $warnbannedrecip = 1; and my $final_banned_destiny = D_BOUNCE;
> and the recipient does get notified. With D_BOUNCE there would be no
> reason to set warnbannedsender = 1; as the sender will already get a
> bounce notification.
> The recipient received:
> BANNED IN MAIL TO
Joachim wrote:
> Hello list,
> I would like to change the behaviour of Amavisd-new (using 2.1.2) when
> handling banned files.
> I would like to notify the recipient in my institute so he can
> contact the postmaster if nesessary.
> I have set
> $final_banned_destiny = D_BOUNCE;
> so
>
Adrian wrote:
> in sample config file,
> $notify_sender_templ = read_text("$MYHOME/notify_sender.txt");
> # $notify_virus_sender_templ= read_text("$MYHOME/notify_virus_sender.txt");
> # $notify_virus_admin_templ = read_text("$MYHOME/notify_virus_admin.txt");
> # $notify_virus_recips_templ= r
Michael Scheidell wrote:
-Original Message-
From: Mark Burdick [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 31, 2005 8:03 AM
To: Michael Scheidell
Cc: Adrian Mak; amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] amavisd + ClamAV
Interesting comment. Especially since
ons, 31.08.2005 kl. 15.39 skrev Adrian Mak:
> my scenario is when amavisd found a virus from received email, it
> should bounce the email and a email should return to sender saying
> that your email cannot be deliveried due to a virus.
>
> This is my amavisd configuration
>
> $mailfrom_notify_ad
ons, 31.08.2005 kl. 15.59 skrev Mark Martinec:
> > I have seen a couple of spams bypass our spamassassin scan because they
> > are larger than the 200KB default $sa_mail_body_size_limit. I'm thinking
> > about raising that limit to 512KB. If anyone have raised it, what size
> > have you configured
Sorry, amavisd-new version is 2.3.1 here, not 2.1.2
Joe
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Manag
I have been using 512 * 1024 for months (9 or more) on every system I
have built. These systems are no powerhouse machines - they have 512MB
RAM and a PIII processor (450-500MHz).
My systems process an average of 300,000-400,000 message attempts per
month, and CPU cycles are never an issue. I see
Adrian wrote:
> hello list,
> my scenario is when amavisd found a virus from received email, it
> should bounce the email and a email should return to sender saying
> that your email cannot be deliveried due to a virus.
> This is my amavisd configuration
> $mailfrom_notify_admin = "[EMAIL P
What you're looking for is both possible, and an extremely bad idea.
Far more viruses will pass into an e-mail system with a false "FROM"
address than ones that are legitimate. Your proposal will be sending
response messages for every virus it finds, and the majority of those
will be from incorrec
Martin,
> I have seen a couple of spams bypass our spamassassin scan because they
> are larger than the 200KB default $sa_mail_body_size_limit. I'm thinking
> about raising that limit to 512KB. If anyone have raised it, what size
> have you configured it to? Has it done a huge impact on the load?
hello list,
my scenario is when amavisd found a virus from received email, it
should bounce the email and a email should return to sender saying
that your email cannot be deliveried due to a virus.
This is my amavisd configuration
$mailfrom_notify_admin = "[EMAIL PROTECTED]"; # notification
Hello list,
I would like to change the behaviour of Amavisd-new (using 2.1.2) when
handling banned files.
I would like to notify the recipient in my institute so he can
contact the postmaster if nesessary.
I have set
$final_banned_destiny = D_BOUNCE;
so
$warnbannedrecip = 1;
does not w
> -Original Message-
> From: Mark Burdick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 31, 2005 8:03 AM
> To: Michael Scheidell
> Cc: Adrian Mak; amavis-user@lists.sourceforge.net
> Subject: Re: [AMaViS-user] amavisd + ClamAV
>
>
> Interesting comment. Especially since I use ama
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Adrian Mak
> Sent: Wednesday, August 31, 2005 12:55 AM
> To: amavis-user@lists.sourceforge.net
> Subject: [AMaViS-user] where to get template of notify message ?
>
>
You need to start to read th
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Adrian Mak
> Sent: Wednesday, August 31, 2005 12:21 AM
> To: amavis-user@lists.sourceforge.net
> Subject: [AMaViS-user] amavisd + ClamAV
>
>
> My system is Redhat Advanced Server 3
> Current mail s
Hi all,
I have seen a couple of spams bypass our spamassassin scan because they
are larger than the 200KB default $sa_mail_body_size_limit. I'm thinking
about raising that limit to 512KB. If anyone have raised it, what size
have you configured it to? Has it done a huge impact on the load?
Th
>>> Gary V <[EMAIL PROTECTED]> 08/31/05 1:26 AM >>>
>The intent was to insure Postfix could communicate on 127.0.0.1. If
>this machine has a single interface with a single IP address, then
>this should be 'inet_interfaces = all', which is the default, so the
>same effect could be achieved by removi
27 matches
Mail list logo
