2009/12/8 Mark Martinec mark.martinec+ama...@ijs.si:
Unfortunately these kinds of errors (like SIGSEGV, SIGBUS, SIGFPE, SIGILL)
can not be trapped by using an eval. The error happens in a library,
below the perl level, and as a result the process just crashes, and
the results are as you
Jeremy,
No, neither one survives. Running razor-check under gdb shows a fault
somewhere in the .xs file that cleans up HTML, but I'm not much of a C
programmer, and there are way too many refs and pointers in there for
me to work out what's wrong. Valgrind had a lot to say about it too.
Luc,
I don't have any spam_quarantine_method parameter set.
Defaults are (as documented in amavisd.conf-default):
$virus_quarantine_method= 'local:virus-%m';
$spam_quarantine_method = 'local:spam-%m.gz';
$banned_files_quarantine_method = 'local:banned-%m';
Alan,
The current deployment is already configured as per the help file and is
working fine. The help file would imply that what the users want is not
possible.
They are all using Outlook and at least 2007 report the following header
fields when replying:
References:
In-Reply-To:
Mark Martinec wrote the following on 09/12/09 16:19:
If it suffices to base the decision on these mail header fields, you can
supply a small custom hook which loads a policy bank, which can do
whatever you want, like disabling adding disclaimers when loaded.
amavisd.conf:
Hi
Merry Christmas to all (who celebrate Christmas)
We are having an issue with case sensitivity of sender names. We store
the sender and recipient email addresses in a single entities sql
table. The records should be
unique on email address and from an sql perspective they are (ie
Grant Maxwell wrote:
Hi
Merry Christmas to all (who celebrate Christmas)
We are having an issue with case sensitivity of sender names. We store
the sender and recipient email addresses in a single entities sql
table. The records should be
unique on email address and from an sql
Hi
Merry Christmas to all (who celebrate Christmas)
We are having an issue with case sensitivity of sender names. We
store
the sender and recipient email addresses in a single entities sql
table. The records should be
unique on email address and from an sql perspective they are (ie
