Hello,
I have problem with the directory tmp inside the home directory of the
user running amavisd-new (which use spamassassin).
That directory is configured as temporary dir for Amavisd-new. I mounted
on it a tmpfs file system. The size of the partition is the one
suggested for this job (to do
Paul,
I just installed amavisd-new-2.5.0 on my Mac OS X system (version
10.4.9). It seems to work fine, except when the daily log roll happens.
When this occurs, logging from amavisd stops for a while, and then starts
up again.
Yes, MacOSX uses postfix. I grep'd for this message and I
I get these warning..
WARNING: bad headers - Improper use of control character (char 0D hex):
Subject: Richiesta di Invio Schede Prodotto\r \n
I saw the amavisd.conf:
# for defanging bad headers only turn on certain minor contents
categories:
$defang_by_ccat{+CC_BADH.,3} = 1; # NUL or CR
I get these warning..
WARNING: bad headers - Improper use of control character (char 0D hex):
Subject: Richiesta di Invio Schede Prodotto\r \n
I saw the amavisd.conf:
# for defanging bad headers only turn on certain minor contents
categories:
$defang_by_ccat{+CC_BADH.,3} = 1; # NUL or CR
Paul,
could you please try with the following replacement subroutine write_log:
# Log either to syslog or to a file
sub write_log($$$;@) {
my($level,$am_id,$errmsg,@args) = @_;
$am_id = !defined $am_id ? '' : ($am_id) ;
# treat $errmsg as sprintf format string if additional arguments
Rocco,
I get these warning..
WARNING: bad headers - Improper use of control character (char 0D hex):
Subject: Richiesta di Invio Schede Prodotto\r \n
If this is coming from your clients, these really need to be fixed,
using a bare CR within a header is an ugly offense. Allowing such
headers
Rocco,
I have problem with the directory tmp inside the home directory of the
user running amavisd-new (which use spamassassin).
That directory is configured as temporary dir for Amavisd-new. I mounted
on it a tmpfs file system. The size of the partition is the one
suggested for this job
I get these warning..
WARNING: bad headers - Improper use of control character
(char 0D hex):
Subject: Richiesta di Invio Schede Prodotto\r \n
If this is coming from your clients, these really need to be
fixed, using a bare CR within a header is an ugly offense.
Allowing such
rocsca,
You probably want:
$allowed_header_tests{'control'} = 0;
Search for '%allowed_header_tests' in RELEASE_NOTES.
Could I disable the check only for incoming mail?
Yes, you can disable the setting globally,
and re-enable it for locally originating mail
with a help of a policy bank,
Leo,
I've encountered problems concerning mails DISCARDed by amavis.
Some mailers (e.g. SurfControl RiskFilter) will interpret the SMTP
status code 254 used by amavis as a temporary error.
This is direct violation of a MUST in rfc2822, complain to the vendor.
rfc2822, section 4.2:
On 05/21/2007 07:24 PM, Mark Martinec wrote:
I've encountered problems concerning mails DISCARDed by amavis.
Some mailers (e.g. SurfControl RiskFilter) will interpret the SMTP
status code 254 used by amavis as a temporary error.
This is direct violation of a MUST in rfc2822, complain to the
[EMAIL PROTECTED],
I'm trying to use amavis + postfix with virtual users, with an extra twist:
a wildcard virtual domain. This is configured in postfix with a regexp
file:
virtual_mailbox_domains = regexp:/etc/postfix/vhosts/domains
which looks like this:
/customer1\.com/
Charlie,
Is anyone using amavisd with postfix and dkfilter? I need to attach
domain keys to my outgoing mail and am getting confused. dkfilter wants
to be a content_filter and if I'm seeing this correctly, it seems that
postfix can only have one content_filter and that needs to be amavisd.
Bill,
I've noticed that when multiple message parts match different clamav
signatures, *all* the signature names must be listed in
@virus_name_to_spam_score_maps for it to be considered spam.
Yes, as documented in RELEASE_NOTES:
[...] When a virus scanner returns
names of viruses, and
Hello fellow listers
Hats off to the devs around here for a great piece of software!
We are involved in deploying some new servers and we are planning to add
a second instance of Postfix/Amavisd-new to our existing instance.
My question is this:
Do we need to run another full instance of
Mark Martinec wrote the following on 5/21/2007 5:06 PM -0800:
Bill,
I've noticed that when multiple message parts match different clamav
signatures, *all* the signature names must be listed in
@virus_name_to_spam_score_maps for it to be considered spam.
Yes, as documented in
Noel Jones wrote the following on 5/21/2007 9:32 PM -0800:
At 09:55 PM 5/21/2007, Bill Landry wrote:
Mark, can you tell me why the Email.Malware are still not detected
without enabling /^MAIL$/? I would like to keep virus scan processing
to a minimum, but if I disable /^MAIL$/, then
17 matches
Mail list logo
