John,
I am hosting a system that is responsible for multiple domains. Right now,
when a spam is caught, a notification will go out to the person who sent
the message. The FROM address will not change to match the domain that the
original email was sent to.
Example: Content-filter at
- added global configuration variable $sql_quarantine_chunksize_max,
Oops, wrong paragraph, here is the one I intended:
- added a global config variable $enforce_smtpd_message_size_limit_64kb_min,
true by default; when true a rfc2822 requirement that a limit on mail size
must not be below
It appears they have sendmail milter available for anti-virus integration.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
Mark wrote:
A second release candidate of amavisd-new-2.4.3 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.4.3-rc2.tar.gz
This is expected to be the last rc before a final release.
Changes since rc1:
- updated some AV entries;
### http://www.kaspersky.com/
Anders,
Why not go all the way? Kaspersky Antivirus ...
Thanks for all the changes, most of them found their way into -rc2.
The exit codes listed in the distribution .conf file seems to be a
little off, I believe that a password protected or corrupted file
shouldn't be listed as a virus,
I've got some servers which are still running amavisd-new 2.3.3, and
need to do some minimal upgrades on them, including SA.
In the past I've had some issues with upgrades to SA requiring an
amavisd version upgrade; should an upgrade from SA 3.1.0 (a year old)
to 3.1.5 (most recent) require
junk wrote:
I'm trying to warn users about potentially banned files. To do this I
want amavis to defang messages with banned files and then pass the
messages to users. Using the following options, the messages are being
passed, but not defanged:
$final_banned_destiny = D_PASS;
On Wed, 20 Sep 2006, Clifton Royston wrote:
In the past I've had some issues with upgrades to SA requiring an
amavisd version upgrade; should an upgrade from SA 3.1.0 (a year old)
to 3.1.5 (most recent) require me to do any amavisd-new upgrades too?
I am running amavisd-new 2.3.3 and SA
Remember that defanging does not modify the original banned file. If
it was malicious when it was sent, it is still malicious as it sits in
the user's inbox.
I understand that. For my purposes, this is the desired behavior.
How are you viewing the test message? If viewing from an MUA, the
Jonathan,
Using the following options, the messages are being passed,
but not defanged:
$final_banned_destiny = D_PASS;
$defang_banned = 1;
Option 1 works well for local hosts. FYI this document is
geared to postfix. I'm using sendmail with amavisd-milter.
AM.PDP protocol does not
Attila,
BTW, don't you plan a reverse AM.PDP protocol, where amavisd would be
the client and an external program the server?
For the first iteration passing only as much information from the e-mail
as possible would be more than enough (at least for me at the moment ;)
and then it could be
Dear All,
I want to reject all messages with certain words on DATA_DOT. Is there
any easy way to implement it with amavisd-new? I am looking for a way
like a lookup table and can easy add or delete some keywords :)
--
Xueron Nee [EMAIL PROTECTED]
12 matches
Mail list logo
