On Fri, May 21, 2010 at 6:39 AM, Mark Martinec wrote:
>> > It's the same issue as was already resolved for the ClamAV plugin,
>> > the data structure changed from hash to a list (so that ordering
>> > of add_header can be maintained).
>> >
>> > See:
>> > https://issues.apache.org/SpamAssassin/sho
On Thu, May 20, 2010 at 9:13 AM, Mark Martinec wrote:
> On Thursday 20 May 2010 08:46:25 Per Jessen wrote:
>> Per Jessen wrote:
>> > Robert Mangiafico wrote:
>> >> On Tue, May 18, 2010 at 2:53 AM, Per Jessen wrote:
>> >>> I googled a bit, and found
On Tue, May 18, 2010 at 2:53 AM, Per Jessen wrote:
> Robert Mangiafico wrote:
>
>> On Wed, May 12, 2010 at 3:59 PM, Robert Mangiafico
>> wrote:
>>> Is SA 3.3.1 no longer compatible with POPAuth? After upgrading, we're
>>> seeing these errors in the logs
On Wed, May 12, 2010 at 3:59 PM, Robert Mangiafico wrote:
> Is SA 3.3.1 no longer compatible with POPAuth? After upgrading, we're
> seeing these errors in the logs:
>
> spamd[29369]: Pseudo-hashes are deprecated at
> /etc/mail/spamassassin/POPAuth.pm line 195, line 54.
&g
Is SA 3.3.1 no longer compatible with POPAuth? After upgrading, we're
seeing these errors in the logs:
spamd[29369]: Pseudo-hashes are deprecated at
/etc/mail/spamassassin/POPAuth.pm line 195, line 54.
spamd[29369]: plugin: eval failed: Can't coerce array into hash at
/etc/mail/spamassassin/POPAu
On Wed, May 12, 2010 at 11:31 AM, Gary Smith wrote:
>> We've found that our MyISAM tables being used with Bayes in MySQL have
>> caused some bottlenecks on our busier mail servers. We're
>> contemplating using inooDB just for the Bayes database. If MySQL will
>> only be using innoDB, does anyone h
We've found that our MyISAM tables being used with Bayes in MySQL have
caused some bottlenecks on our busier mail servers. We're
contemplating using inooDB just for the Bayes database. If MySQL will
only be using innoDB, does anyone have any recommendations for innoDB
settings in my.cnf to optimize
