Hi all.
I'm using postfix + amavisd-new-2.4.2 + spamassassin.
Is there any chance to completely disable the insertion of the
X-Spam-Status header field with all the scores, tests, etc. even if the
message is considered spam? I only need the X-Spam-Flag header field
set to YES without all the
Gary V wrote:
R.Smits wrote:
Mark Martinec wrote:
R.Smits,
We want to whitelist all the mail : internal -- internal.
We do NOT want to whitelist : internal -- external
Also ofcourse NOT whitelist : external -- internal (makes sense :-)
Is this possible with one instance of amavis. I
Guys,
thanks a lot for all your replys and support. My problem is now solved and the
8000 mails have been successfully re-queued :-)
Thank you.
Best regards,
Werner
-
Take Surveys. Earn Cash. Influence the Future of IT
Jo,
mlfi_eom: ignore unknown amavisd response insheader=0 X-Spam-Flag YES
...etc repeat for each header that should be added.
Okay, http://www.ijs.si/software/amavisd/README.protocol.txt details the
changes.
Also listed in the COMPATIBILITY section of release notes.
I guess the obvious
Jo,
One of the goals for 2.4.3 was to polish remaining rough corners
in coexistence with DomainKeys and DKIM domain-based mail signing.
http://www.ijs.si/software/amavisd/amavisd-new-docs.html#dkim
Can we get some DKIM documentation that isn't completely focused on
Postfix? Why not
If you have a sendmail milter setup, you have no choice but to use a single
instance of each milter for both signing and verification, following the
normal install instructions for each milter. This setup does not offer
ability to convert mail body to 7-bits before signing, and to include
Mark Martinec wrote:
No, you will have to upgrade the Petr Rehor's milter helper
to 1.1.3. It is promised to be out in few days. This upgrade is
needed anyway to make it work again under FreeBSD and OpenBSD,
so it was not worth providing special compatibility measures.
Mark
Do you know
Adam,
Do you know if amavisd-milter 1.1.3 will solve the problem of appending
headers which breaks DKIM/DK?
Yes, I believe it will. One of the key changes there was to use
a new 'insheader' attribute to AM.PDP, which will explicitly
require newly inserted header fields to be prepended (not
R.Smits wrote:
This is what I know,
mynetworks = 127.0.0.0/8 !192.168.1.1 192.168.1.0/24
In amavisd.conf @mynetworks determines which clients will use the
'MYNETS' policy bank:
@mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
Anders Norrbring skrev:
Mark Martinec skrev:
Matt and others,
When upgrading from 2.4.2 to 2.4.3, I had a problem where I was getting
messages such as '451 4.5.0 Error in processing, id=11761-01, forwarding
FAIL ED: Undefined subroutine Amavis::cmp_ccat called at ./amavisd line
8853. (in re
Am I reading this wrong, or are you saying that amavisd itself has no
DKIM validation itself... that it's just using the results of the
previous verification milter?
Mark Martinec wrote:
The documentation that comes with both milters is already sendmail-centric,
so my documentation section
Gary wrote:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
bypass_spam_checks_maps = [[qw( .example.com .example.net )]],
final_spam_destiny = D_BOUNCE,
};
This will allow clients included in @mynetworks to bypass spam checks
for mail sent to the listed domains (only). Any mail
Gary,
Thank you for the good information.
I am going to test this.
Greetings... Richard
Gary V wrote:
Gary wrote:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
bypass_spam_checks_maps = [[qw( .example.com .example.net )]],
final_spam_destiny = D_BOUNCE,
};
This will
Gary wrote:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
spam_lovers_maps = [[qw( .example.com .example.net )]],
final_spam_destiny = D_BOUNCE,
spam_dsn_cutoff_level_maps = ,
};
Mark, this works in 2.4.2, but no DSN is created in 2.4.3.
Is this the reason?:
- when
On Mon, Oct 02, 2006 at 11:56:35AM +0200, Mark Martinec wrote:
No, you will have to upgrade the Petr Rehor's milter helper
to 1.1.3. It is promised to be out in few days. This upgrade is
needed anyway to make it work again under FreeBSD and OpenBSD,
so it was not worth providing special
Jo,
No, you will have to upgrade the Petr Rehor's milter helper
to 1.1.3. It is promised to be out in few days. This upgrade is
needed anyway to make it work again under FreeBSD and OpenBSD,
so it was not worth providing special compatibility measures.
Eh? This isn't mentioned in the
Also, amavisd 1.4.3 is running just fine under FreeBSD with the 1.1.2
milter right now. It's only that the headers aren't being added.
What is it that is believed not to work with FreeBSD?
Mark Martinec wrote:
The last time I checked, it was crashing on FreeBSD because
MAXAMABUF was
Gary wrote:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
spam_lovers_maps = [[qw( .example.com .example.net )]],
final_spam_destiny = D_BOUNCE,
spam_dsn_cutoff_level_maps = ,
};
Mark, this works in 2.4.2, but no DSN is created in 2.4.3.
Mark wrote:
With 2.4.3 there
Gary,
I found it interesting that 2.4.2 did not croak when I added
spam_dsn_cutoff_level_bysender_maps = undef, to the policy bank. I can
add arbitrarily named items and amavisd-new won't complain (not that
it necessarily should). The only obvious issue with that would be if
someone
Mark wrote:
Gary,
I found it interesting that 2.4.2 did not croak when I added
spam_dsn_cutoff_level_bysender_maps = undef, to the policy bank. I can
add arbitrarily named items and amavisd-new won't complain (not that
it necessarily should). The only obvious issue with that would be if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED],
are there any examples online with having
amavis-new not configured on localhost
working with postfix
for exmaple ,if i want share the amavis service on a special host between
multiple mailhosts
- --
Mit freundlichen Gruessen
Best
Robert wrote:
[EMAIL PROTECTED],
are there any examples online with having
amavis-new not configured on localhost
working with postfix
for exmaple ,if i want share the amavis service on a special host between
multiple mailhosts
- --
Mit freundlichen Gruessen
Best Regards
Robert
22 matches
Mail list logo
