>> Paradoxically, a simpler solution in your case is to use a more
>> complex MTA+amavisd setup, letting MTA separate mail into originating
>> (=locally submitted) and all the rest, and feeding each flow
>> on a separate amavisd port.
>>
>> When code sections in current versions of amavisd need to
Hello,
I have different SMTP gateways each one configurred exactly at the same
manner. The only difference is the hostname.
I would like to know if I could define "/etc/amavisd.conf" as an NFS share
somewhere and export it on each of my SMTP gateways. The aim is obviously
to change only one confi
> >> This would for example allow switching between several rulesets or
> >> bayes databases.
>
> I have thought about trying to do something similar to allow for 'domain
> based' baysian tables (as amavisd sets up and calls sa->new, set the ENV
> variables so that SA can look up the domain in the
> Alex,
>
>> is there any option to get access to the SA object in an Amavis::Custom
>> module?
>
> Access to the SA object from Amavis::Custom is not available presently
> without hacking code a bit.
>
>> This would for example allow switching between several rulesets or
>> bayes databases.
I
Ralf,
> amavis[12535]: (12535-20) ESMTP ABORTING: Connection broken during data
> transfer
>
> Amavis is in pre-queue mode. Now I have one error to the next error.
> And so on.
> In main.cf the setting is smtpd_proxy_timeout = 300
> In amavis.conf the option $child_timeout is not set.
> In main.cf
Alex,
> is there any option to get access to the SA object in an Amavis::Custom
> module?
Access to the SA object from Amavis::Custom is not available presently
without hacking code a bit.
> This would for example allow switching between several rulesets or
> bayes databases.
> > You should us
Thiemo,
> > Fork is failing because you are running out of swap space.
> > Increase swap space. Are you using memory-based temporary
> > file systems? These can easily fill up available storage.
>
> I run it on a virtual server of a provider and cannot increase anything.
> I already have the premi
Bastian,
> I tried to user different final_spam_destiny settings on multiple
> domains, but it seems not to work.
> What I tried before:
> $final_spam_destiny = {
>".domain1.com"=>"D_PASS",
>".domain2.com"=>"D_PASS",
>"."=>"D_REJECT"
>};
> But these settings are tot
Lucas,
> I would like to take this message to ask about quarantine.
> In my amavis::custom, I use CC_SPAM to discard the e-mail,
> but the message has been stored at disk.
> These filters are developed in checks function.
>
> Is there the way to discard the message entirely?
You could employ the
Thanks Mark, works like a charm, although I am beginning to think, tat I
need to relax my rules a little.
Thanks for amavisd-new, BTW. Makes my life a lot easier!
All the best,
.peter
On Tue, 13 Jan 2009, Mark Martinec wrote:
> Peter,
>
>> Several times in the past I have had the problem of
Peter,
> Several times in the past I have had the problem of files that were pgp
> signed not getting through, because in the conf file it says that files
> with attachments ending with .asc should be blocked.
>
> Jan 13 15:30:59 x.tld /usr/sbin/amavisd[14266]: (14266)
> p.path BANNED:1 xxx...
David,
> I have a project using amavis in order to add auto-compress feature when
> mails meet specific rules.
> I would like to know what function in Amavis::Custom can be use to :
>
> - List Mime-parts
> - Extract files.
> - Delete attached files
> - Adding new attached files.
>
> I can do this
Hi,
Several times in the past I have had the problem of files that were pgp
signed not getting through, because in the conf file it says that files
with attachments ending with .asc should be blocked.
Jan 13 15:30:59 x.tld /usr/sbin/amavisd[14266]: (14266)
p.path BANNED:1 xxx...@x.tld
Luigi,
> What is the configuration directive to disable every kind of header check,
> even if couuld be activated in some policy setting?
>
> What I want is that amavisd completly bypass this kind of check.
@bypass_header_checks_maps = (1);
The following might be desired too if full transparenc
Luigi,
> What is the configuration directive to disable every kind of header check,
> even if couuld be activated in some policy setting?
>
> What I want is that amavisd completly bypass this kind of check.
@bypass_header_checks_maps = (1);
Mark
--
> Paradoxically, a simpler solution in your case is to use a more
> complex MTA+amavisd setup, letting MTA separate mail into originating
> (=locally submitted) and all the rest, and feeding each flow
> on a separate amavisd port.
>
> When code sections in current versions of amavisd need to know
16 matches
Mail list logo
