Hi,
do I need to reread or reload mimedefang after sa-update e.g.
/etc/cron.daily/spamassassin to get the changes in spamassassin rules
recognized by mimedefang?
Ciao!
Marcus
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
On Wed, 14 Sep 2016 07:54:50 +0200
Marcus Schopen wrote:
> do I need to reread or reload mimedefang after sa-update e.g.
> /etc/cron.daily/spamassassin to get the changes in spamassassin rules
> recognized by mimedefang?
Yep. "md-mx-ctrl reread" is a pretty non-invasive operation, so it's
quit
Am Mittwoch, den 14.09.2016, 09:35 -0400 schrieb Dianne Skoll:
> On Wed, 14 Sep 2016 07:54:50 +0200
> Marcus Schopen wrote:
>
> > do I need to reread or reload mimedefang after sa-update e.g.
> > /etc/cron.daily/spamassassin to get the changes in spamassassin rules
> > recognized by mimedefang?
On Wed, 14 Sep 2016 17:46:07 +0200
Marcus Schopen wrote:
> Sep 14 17:39:55 scansrv mimedefang-multiplexor[24029]: Cannot destroy
> and recreate a Perl interpreter safely on this platform. Filter rules
> will NOT be reread.
Huh! That is very weird. I don't get anything like that on Debian Jess
Am Mittwoch, den 14.09.2016, 11:51 -0400 schrieb Dianne Skoll:
> On Wed, 14 Sep 2016 17:46:07 +0200
> Marcus Schopen wrote:
>
> > Sep 14 17:39:55 scansrv mimedefang-multiplexor[24029]: Cannot destroy
> > and recreate a Perl interpreter safely on this platform. Filter rules
> > will NOT be reread
On Wed, 14 Sep 2016 18:12:39 +0200
Marcus Schopen wrote:
> Okay, but this might harm a mail which is in process. Any ideas how to
> fix above error?
No... no idea. If you don't use embedded Perl (ie, leave the -E flag off
of the mimedefang-multiplexor command line) then you will be able to
use
Am Mittwoch, den 14.09.2016, 13:08 -0400 schrieb Dianne Skoll:
> On Wed, 14 Sep 2016 18:12:39 +0200
> Marcus Schopen wrote:
>
> > Okay, but this might harm a mail which is in process. Any ideas how to
> > fix above error?
>
> No... no idea. If you don't use embedded Perl (ie, leave the -E flag
On Wed, 14 Sep 2016 20:39:19 +0200
Marcus Schopen wrote:
> Hmmm, what's the performance loss if not using embedded Perl?
There is some, but it's mostly related to startup costs. Once things
are running, there's not a huge difference. Unless you're running a busy
machine (lets say more than 500
On 09/14/2016 11:12 AM, Marcus Schopen wrote:
> Am Mittwoch, den 14.09.2016, 11:51 -0400 schrieb Dianne Skoll:
>> On Wed, 14 Sep 2016 17:46:07 +0200
>> Marcus Schopen wrote:
>>
>>> Sep 14 17:39:55 scansrv mimedefang-multiplexor[24029]: Cannot destroy
>>> and recreate a Perl interpreter safely on t
On 09/14/2016 11:48 PM, Richard Laager wrote:
> On 09/14/2016 11:12 AM, Marcus Schopen wrote:
>> Am Mittwoch, den 14.09.2016, 11:51 -0400 schrieb Dianne Skoll:
>>> On Wed, 14 Sep 2016 17:46:07 +0200
>>> Marcus Schopen wrote:
>>>
Sep 14 17:39:55 scansrv mimedefang-multiplexor[24029]: Cannot de
On Thu, 15 Sep 2016 00:48:01 -0500
Richard Laager wrote:
> So configure.in has a check for this pthread flag, but does not use
> $PTHREAD_FLAG as part of the $CFLAGS for the SAFE_EMBED_PERL test.
> Patch attached, which results in SAFE_EMBED_PERL set and reread
> working for me on Ubuntu 16.04.
Hi Richard,
Am Donnerstag, den 15.09.2016, 00:48 -0500 schrieb Richard Laager:
[...]
> > I'm digging into it right now. The problem seems to be that Perl outputs
> > -lpthread as a required LDFLAG, but gcc needs -pthread (with no "l"), or
> > else it fails linking to the symbol pthread_setspecific
Hi Richard,
Am Donnerstag, den 15.09.2016, 00:48 -0500 schrieb Richard Laager:
[...]
> So configure.in has a check for this pthread flag, but does not use
> $PTHREAD_FLAG as part of the $CFLAGS for the SAFE_EMBED_PERL test. Patch
> attached, which results in SAFE_EMBED_PERL set and reread working
13 matches
Mail list logo
