Benedict wrote:
Is it possible to have the banned contents email in a separate file so that
it can be edited easily?
Yes, see amavisd.conf-sample and README.customize.
I assume you are talking about template-virus-sender.txt that notifies
the sender (banned and virus). Here is a sample for
Petr Vokac wrote:
Mark Martinec wrote:
M.Lewis,
Is there a way to include the score on the subject line ?
Something along the lines of:
$sa_spam_subject_tag = '*SPAM* [$score] ';
It currently is not configurable. You will need to edit
the program - in sub
On Tue May 30 2006 16:02, Benedict White wrote:
Is it possible to have the banned contents email in a separate file so that
it can be edited easily?
i would add this question:
can i quarantine only banned email, not spamming or viruses ones?
sorry if already answered :(
Maurizio
--
I'm still using 20030616p10-5 on Debian testing. I know that the Debian
folks have decided to force me to use their method of configuring
amavisd-new, instead of the old and sane way of using amavisd.conf. I've
found the web page that tells me how to continue to use my amavisd.conf
file even after
Hi,
I read through the archives of this mailinglist ans well as the amavisd
config file but could not work out this item.
I am not fluent in perl (understatement). I run amavisd with postfix,
clamav, f-prot and spamassassin but with less then 2 months experience.
(Being used to sendmail /
At 04:13 PM 5/31/2006, Hugo van der Kooij wrote:
I would like to exclude a rather specific message from
being scanned. As I
generate this EICAR test message myself I can pretty much
decide myself
what headers to add to the messages. It is an unpublished
EICAR robot so
our customers and our
Oz gov. recently set up an initiative for combating/tracing UCE/UBE/spam,
where ppl can submit received spam for whatever action they'll take
so, I figured I would submit a bunch of NAB phisihing emails that amavis
just deposited to 'infected@' address
of course as soon as I sent them, they
At 04:50 PM 5/31/2006, Voytek Eymont wrote:
Oz gov. recently set up an initiative for
combating/tracing UCE/UBE/spam,
where ppl can submit received spam for whatever action
they'll take
so, I figured I would submit a bunch of NAB phisihing
emails that amavis
just deposited to 'infected@'
The syntax of many settings in newer versions of amavisd-new has
changed but some settings from older versions can be used.
I'd like to think that practically all old config files
(as far back as amavisd-new-20030314 or even earlier)
still work with new versions of amavisd-new.
I go to great
Hugo,
It is an unpublished EICAR robot so
our customers and our engineers can test their email setup
by requesting and eicar file being send per email.
Noel already listed the choices. I'd just like to
remind that such a robot/responder is pretty much
like a mailing list manager: the easiest
Benedict,
Is it possible to have the banned contents email in a separate file
so that it can be edited easily?
I'm not sure if what you are asking was answered by Gary,
or are you asking about quarantining banned contents email
to a separate directory - which is doable, here is an
example from
Vincent,
I am running a Postfix/Amavis mailserver. It correctly checks and blocks
virus mails but i have an issue with spam control, as received spam with
a sufficient level is not getting tagged as spam in the subject and header.
http://www.ijs.si/software/amavisd/#faq-spam
- No
Michael wrote:
I'm still using 20030616p10-5 on Debian testing. I know that the Debian
folks have decided to force me to use their method of configuring
amavisd-new, instead of the old and sane way of using amavisd.conf. I've
found the web page that tells me how to continue to use my
Hi Mark,
The most common reason is that local_domains do not include
all local domains.
Later assignment overrules former. Also, the colossus.nl
does not include rhodos.colossus.nl, to include subdomains
prepend a dot:
@local_domains_acl = ( .colossus.nl, .ludden.nl );
Mark
I go to great lengths to retain upwards compatibility
of config files. Syntactically they should be 100% compatible,
while there are some minor semantical differences as documented
in release notes, and of course new features fall to their
default settings in absence of explicit controls.
15 matches
Mail list logo